> On 4 Nov 2019, at 19:31, Alex Herbert <alex.d.herb...@gmail.com> wrote: > > > >> On 4 Nov 2019, at 18:38, Rob Tompkins <chtom...@gmail.com >> <mailto:chtom...@gmail.com>> wrote: >> >> Also keep me posted. I’ll be near my keyboard all day. -Rob >> >>> On Nov 4, 2019, at 1:21 PM, Rob Tompkins <chtom...@gmail.com >>> <mailto:chtom...@gmail.com>> wrote: >>> >>> >>> >>>> On Nov 4, 2019, at 1:16 PM, Alex Herbert <alex.d.herb...@gmail.com >>>> <mailto:alex.d.herb...@gmail.com>> wrote: >>>> >>>> >>>>>> On 04/11/2019 17:36, Alex Herbert wrote: >>>>> >>>>> >>>>>> On 04/11/2019 15:40, Alex Herbert wrote: >>>>>> >>>>>> On 04/11/2019 12:43, Gilles Sadowski wrote: >>>>>>> Hello. >>>>>>> >>>>>>> Le lun. 4 nov. 2019 à 13:05, Alex Herbert <alex.d.herb...@gmail.com >>>>>>> <mailto:alex.d.herb...@gmail.com>> a écrit : >>>>>>>> >>>>>>>> On 04/11/2019 00:42, Gilles Sadowski wrote: >>>>>>>>> Hi. >>>>>>>>> >>>>>>>>>> [...] >>>>>>>>>> >>>>>>>>>> So there are at least two options: >>>>>>>>>> >>>>>>>>>> 1. Release using JDK 9 >>>>>>>>> +1 >>>>>>>> OK. I'll run through the release with JDK 9. I do not think we have any >>>>>>>> NIO classes so the issue raised by Gary should not be present. >>>>>>> Here >>>>>>> $ JAVA_HOME=/usr/lib/jvm/java-9-openjdk-amd64 mvn >>>>>>> -Pcommons-rng-examples clean package install site site:stage >>>>>>> built fine (but I did not check the reports). >>>>>> >>>>>> Good to know. >>>>>> >>>>>> I've been through a dry run and the outputs look as expected. >>>>> >>>>> The commons-release-plugin:1.7 has failed on the final step to stage the >>>>> files in Nexus. >>>>> >>>>> All the files appear to be present but the plugin fails when processing >>>>> the parent for the multi-module project. >>>>> >>>>> Here is the command that is currently failing: >>>>> >>>>> mvn -X -e -Duser.name=aherbert -Pcommons-rng-examples -Prelease clean >>>>> package site site:stage deploy -rf :commons-rng >>>>> >>>>> [DEBUG] -- end configuration -- >>>>> [INFO] Checking out dist from: >>>>> scm:svn:https://dist.apache.org/repos/dist/dev/commons/rng >>>>> <https://dist.apache.org/repos/dist/dev/commons/rng> >>>>> Executing: /bin/sh -c cd >>>>> '/scratch/commons-rng/dist-archive/target/commons-release-plugin' && >>>>> 'svn' '--username' 'aherbert' '--no-auth-cache' '--non-interactive' >>>>> 'checkout' 'https://dist.apache.org/repos/dist/dev/commons/rng@' >>>>> '/scratch/commons-rng/dist-archive/target/commons-release-plugin/scm-cleanup >>>>> >>>>> <https://dist.apache.org/repos/dist/dev/commons/rng@'%20'/scratch/commons-rng/dist-archive/target/commons-release-plugin/scm-cleanup>' >>>>> Executing: /bin/sh -c cd >>>>> '/scratch/commons-rng/dist-archive/target/commons-release-plugin/scm-cleanup' >>>>> && 'svn' 'remove' '--targets' >>>>> '/tmp/maven-scm-5448861436738372728-targets' >>>>> [INFO] Cleaning distribution area for: commons-rng >>>>> Executing: /bin/sh -c cd >>>>> '/scratch/commons-rng/dist-archive/target/commons-release-plugin/scm-cleanup' >>>>> && 'svn' '--username' 'aherbert' '--no-auth-cache' '--non-interactive' >>>>> 'commit' '--file' '/tmp/maven-scm-1469264231.commit' '--encoding' 'UTF-8' >>>>> '--targets' '/tmp/maven-scm-14546727756421455038-targets' >>>>> [INFO] >>>>> ------------------------------------------------------------------------ >>>>> [INFO] BUILD FAILURE >>>>> [INFO] >>>>> ------------------------------------------------------------------------ >>>>> [INFO] Total time: 7.376 s >>>>> [INFO] Finished at: 2019-11-04T17:19:15Z >>>>> [INFO] >>>>> ------------------------------------------------------------------------ >>>>> [ERROR] Failed to execute goal >>>>> org.apache.commons:commons-release-plugin:1.7:clean-staging >>>>> (clean-staging) on project commons-rng: Failed to commit files: null >>>>> [null] -> [Help 1] >>>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute >>>>> goal org.apache.commons:commons-release-plugin:1.7:clean-staging >>>>> (clean-staging) on project commons-rng: Failed to commit files: null >>>>> [null] >>>>> at org.apache.maven.lifecycle.internal.MojoExecutor.execute >>>>> (MojoExecutor.java:215) >>>>> 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 jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) >>>>> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke >>>>> (NativeMethodAccessorImpl.java:62) >>>>> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke >>>>> (DelegatingMethodAccessorImpl.java:43) >>>>> at java.lang.reflect.Method.invoke (Method.java:564) >>>>> 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) >>>>> Caused by: org.apache.maven.plugin.MojoFailureException: Failed to commit >>>>> files: null [null] >>>>> at >>>>> org.apache.commons.release.plugin.mojos.CommonsStagingCleanupMojo.execute >>>>> (CommonsStagingCleanupMojo.java:193) >>>>> 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 jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) >>>>> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke >>>>> (NativeMethodAccessorImpl.java:62) >>>>> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke >>>>> (DelegatingMethodAccessorImpl.java:43) >>>>> at java.lang.reflect.Method.invoke (Method.java:564) >>>>> 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) >>>>> >>>>> I think all the files have been staged correctly. >>>>> >>>>> Any ideas? >>>>> >>>>> Can this be ignored as a bug in the commons-release-plugin:1.7 trying to >>>>> clean something that is not there? >>>>> >>>>> Alex >>>>> >>>> It seems the above command stalled before creating the release artefacts. >>>> I have no: >>>> >>>> commons-rng-1.3-src.tar.gz >>>> commons-rng-1.3-src.zip >>>> commons-rng-1.3-bin.tar.gz >>>> commons-rng-1.3-bin.zip >>>> >>>> In the dist-archive/target directory. >>>> >>>> When I run >>>> >>>> svn checkout https://dist.apache.org/repos/dist/dev/commons/rng >>>> <https://dist.apache.org/repos/dist/dev/commons/rng> >>>> >>>> The dev area still has version 1.2-RC2 from the last release. Would this >>>> effect anything in the release process? >>> >>> Maybe...I would delete that and retry. > > I cleaned the old RC and it got a bit further. This is where is now breaks: > > [INFO] Staging release: commons-rng, version: 1.3 > Executing: /bin/sh -c cd > '/scratch/commons-rng/dist-archive/target/commons-release-plugin/scm' && > 'svn' '--username' 'aherbert' '--no-auth-cache' '--non-interactive' 'commit' > '--file' '/tmp/maven-scm-92724952.commit' '--encoding' 'UTF-8' '--targets' > '/tmp/maven-scm-3088677623902684789-targets' > [ERROR] Committing dist files failed: svn: E215004: Authentication failed and > interactive prompting is disabled; see the --force-interactive option > > Unfortunately I am now at home and not in an interactive shell. So could it > be related to that? Where does svn get password from?
This is definitely a svn problem. I recreated a file in https://dist.apache.org/repos/dist/dev/commons/rng <https://dist.apache.org/repos/dist/dev/commons/rng> and I am back to the original error that occurs when the release plugin tries to clean the dev directory. So every time the release plugin issues a svn command that requires a commit (and password authentication) it fails. Is there something obvious that I have not set to allow svn commands to run within the 'svn —non-interactive' mode used by the release plugin? The only instructions in the rng release howto guide were instructions to configure id.apache.org <http://id.apache.org/> using the contents of ~/.ssh/id_rsa.pub. I have done this and can login to home.apache.org <http://home.apache.org/> using sftp. Is there somewhere else I have to configure remote ssh authentication for the release process? Thanks, Alex > >>> >>> -Rob >>> >>>> >>>> Alex >>>> >>>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> <mailto:dev-unsubscr...@commons.apache.org> >> For additional commands, e-mail: dev-h...@commons.apache.org >> <mailto:dev-h...@commons.apache.org>
