Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error when using -Dversions.outputFile parameter > NoSuchFileException #558

Closed
ghost opened this issue Feb 11, 2022 · 3 comments
Closed

Comments

@ghost
Copy link

ghost commented Feb 11, 2022

Plugin Version:
2.9.0

Env:
Maven Version: Maven Wrapper with apache-maven-3.8.4
Java version: 17.0.1, vendor: Eclipse Adoptium, runtime: ...\jdk-17.0.1.12-hotspot
Default locale: de_DE, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"

Plugin configuration:

<configuration>
   <allowMajorUpdates>false</allowMajorUpdates>
   <rulesUri>file://${maven.configurations}/version.ruleset.xml</rulesUri>
</configuration>

Call:
mvnw versions:display-property-updates -pl . -Dversions.outputFile=dependency.updates.txt -DoutputEncoding=UTF-8 --fail-fast -Dmaven.repo.local=.m2-local --no-transfer-progress --batch-mode -T4

Error:

[ERROR] Cannot send output to ...\dependency.updates.txt
java.nio.file.NoSuchFileException: ...\dependency.updates.txt
    at sun.nio.fs.WindowsException.translateToIOException (WindowsException.java:85)
    at sun.nio.fs.WindowsException.rethrowAsIOException (WindowsException.java:103)
    at sun.nio.fs.WindowsException.rethrowAsIOException (WindowsException.java:108)
    at sun.nio.fs.WindowsFileSystemProvider.newByteChannel (WindowsFileSystemProvider.java:236)
    at java.nio.file.spi.FileSystemProvider.newOutputStream (FileSystemProvider.java:484)
    at java.nio.file.Files.newOutputStream (Files.java:228)
    at org.codehaus.plexus.util.FileUtils.fileAppend (FileUtils.java:410)
    at org.codehaus.mojo.versions.AbstractVersionsDisplayMojo.logLine (AbstractVersionsDisplayMojo.java:141)
    at org.codehaus.mojo.versions.DisplayPropertyUpdatesMojo.execute (DisplayPropertyUpdatesMojo.java:180)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
    at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (MultiThreadedBuilder.java:196)
    at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call (MultiThreadedBuilder.java:186)
    at java.util.concurrent.FutureTask.run (FutureTask.java:264)
    at java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:539)
    at java.util.concurrent.FutureTask.run (FutureTask.java:264)
    at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1136)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:635)
    at java.lang.Thread.run (Thread.java:833)
[INFO] The following version properties are referencing the newest available version:

It is not a permission issue. I already checked that and version 2.8.1 was working just fine.

Strangely the build finished successfully and if there is already a file with the same name, it will be deleted

This is my first issue.
Sorry if i missed some information. I will add them when needed.

Thank you very much.

Best regards,
Mike

@stefanseifert
Copy link
Contributor

looks like a duplicate of #542 - and that is already fixed on the master branch (no release yet)

@ghost
Copy link
Author

ghost commented Feb 17, 2022

Oh sorry, i didn't saw it. Thanks.

@ghost ghost closed this as completed Feb 17, 2022
@lalo-mx
Copy link

lalo-mx commented Mar 2, 2022

Is there a planned release?

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants