version plugin can not send output to the file specified in versions.outputFile #542
Assignees
Comments
|
you're right - this seems to be a regression in plexus-utils 3.4.0 and 3.4.1 - it works with plexus-utils 3.3.1 |
stefanseifert
added a commit
that referenced
this issue
Jan 25, 2022
…s behavior root cause seems to be a regression in plexus-utils 3.4.0 with FileUtils.fileAppend failing to create a new file if it does not exist already
stefanseifert
added a commit
that referenced
this issue
Jan 25, 2022
…s behavior root cause seems to be a regression in plexus-utils 3.4.0 with FileUtils.fileAppend failing to create a new file if it does not exist already^
stefanseifert
added a commit
that referenced
this issue
Jan 26, 2022
…s behavior root cause seems to be a regression in plexus-utils 3.4.0 with FileUtils.fileAppend failing to create a new file if it does not exist already^
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A bug in version plugin 2.9.0.
Reproduce step:
mvn versions:display-dependency-updates -Dverbose=true -Dversions.outputFile=./dependencyUpdate.txt -DoutputEncoding=UTF-8
[INFO] The following dependencies in Dependencies are using the newest version: [ERROR] Cannot send output to /mnt/c/xxx/dependencyUpdate.txt java.nio.file.NoSuchFileException: /mnt/c/xxxx/dependencyUpdate.txt at sun.nio.fs.UnixException.translateToIOException (UnixException.java:86) at sun.nio.fs.UnixException.rethrowAsIOException (UnixException.java:102) at sun.nio.fs.UnixException.rethrowAsIOException (UnixException.java:107) at sun.nio.fs.UnixFileSystemProvider.newByteChannel (UnixFileSystemProvider.java:214) at java.nio.file.spi.FileSystemProvider.newOutputStream (FileSystemProvider.java:434) at java.nio.file.Files.newOutputStream (Files.java:216) 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.DisplayDependencyUpdatesMojo.logUpdates (DisplayDependencyUpdatesMojo.java:463) at org.codehaus.mojo.versions.DisplayDependencyUpdatesMojo.execute (DisplayDependencyUpdatesMojo.java:363) 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.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288) at org.apache.maven.cli.MavenCli.main (MavenCli.java:192) at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke (Method.java:498) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:356)The text was updated successfully, but these errors were encountered: