You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Alex Herbert <al...@gmail.com> on 2019/11/03 15:01:30 UTC
[rng] Releasing 1.3
I think everything is finalised for a release of RNG, namely:
All bugs and issues with SonarCloud and LGTM.com are fixed.
The user guide has been updated for all the new features.
The performance and quality results have been updated in the user guide.
Any objections to me cutting a release candidate for v1.3? I hope to get it done next week.
Alex
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [rng] Releasing 1.3
Posted by Gary Gregory <ga...@gmail.com>.
On Sun, Nov 3, 2019 at 5:44 PM Alex Herbert <al...@gmail.com>
wrote:
>
>
> > On 3 Nov 2019, at 20:12, Alex Herbert <al...@gmail.com> wrote:
> >
> >
> >
> >> On 3 Nov 2019, at 19:30, Gary Gregory <garydgregory@gmail.com <mailto:
> garydgregory@gmail.com>> wrote:
> >>
> >> On Sun, Nov 3, 2019 at 10:01 AM Alex Herbert <alex.d.herbert@gmail.com
> <ma...@gmail.com>>
> >> wrote:
> >>
> >>> I think everything is finalised for a release of RNG, namely:
> >>>
> >>> All bugs and issues with SonarCloud and LGTM.com <http://lgtm.com/>
> are fixed.
> >>> The user guide has been updated for all the new features.
> >>> The performance and quality results have been updated in the user
> guide.
> >>>
> >>> Any objections to me cutting a release candidate for v1.3? I hope to
> get
> >>> it done next week.
> >>>
> >>
> >> You first should make sure binary compatibility is there, Apache RAT
> check
> >> passes, and so on. That will avoid possible issues in a RC.
> >
> > rat:check and clirr:check are part of the default maven build so errors
> should not enter the codebase.
> >
> > The clirr:clirr report is full of infos for all the new API methods and
> classes.
> >
> > I'll start with a release dry run and see how everything looks.
> >
> > The only outstanding “issue” is that the full code for release has to be
> built using JDK 9.
> >
> > The extra examples maven modules contains some code using Java 9
> modules. All my attempts to get a build to work with JDK 11 have failed on
> the javadoc tool which complains about building for code using modules that
> references packages in the named module [1]. My last attempt using JDK
> 11.0.4 had the same error I found with JDK 11.0.2. I have not a found a fix
> for a multi-module Maven project that uses different java source versions
> and includes some java 9 source explicitly using modules.
> >
> > Given that JDK 11.0.5 is out I will have another look at this. A brief
> scan of the release notes for 11.0.5 does not mention anything but it is
> worth a try. I’d rather do a release using JDK 11 than JDK 9.
>
> JDK 11 works depending on the vendor and the source version!
>
> Steps
>
> 1. Optional. Update commons-rng-examples/examples-jpms/pom.xml to changes
> the source and target from 9 to 11. This is:
>
> <maven.compiler.source>11</maven.compiler.source>
> <maven.compiler.target>11</maven.compiler.target>
> <maven.compiler.release>11</maven.compiler.release>
>
> 2. Build using: mvn clean package site site:stage -P commons-rng-examples
>
>
> Tested two JDK 11 distributions:
>
> Official JDK from https://jdk.java.net/java-se-ri/11 <
> https://jdk.java.net/java-se-ri/11>
>
> java -version
> java version "11.0.5" 2019-10-15 LTS
> Java(TM) SE Runtime Environment 18.9 (build 11.0.5+10-LTS)
> Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.5+10-LTS, mixed mode)
>
> OpenAdopt JDK
> https://adoptopenjdk.net/releases.html?variant=openjdk11&jvmVariant=hotspot#x64_linux
> <
> https://adoptopenjdk.net/releases.html?variant=openjdk11&jvmVariant=hotspot#x64_linux
> >
>
> java -version
> openjdk version "11.0.5" 2019-10-15
> OpenJDK Runtime Environment AdoptOpenJDK (build 11.0.5+10)
> OpenJDK 64-Bit Server VM AdoptOpenJDK (build 11.0.5+10, mixed mode)
>
>
> I tried 4 variants:
>
> Source 9, JDK 11.0.5
> Source 9, OpenAdopt JDK 11.0.5
> Source 11, JDK 11.0.5
> Source 11, OpenAdopt JDK 11.0.5
>
>
> Source 9, JDK 11.0.5
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.8.2:site (default-site) on
> project commons-rng-examples-jpms-lib: Error generating
> maven-javadoc-plugin:3.1.1:javadoc report:
> [ERROR] Exit code: 1 - javadoc: error - The code being documented uses
> modules but the packages defined in
> https://docs.oracle.com/javase/9/docs/api/ are in the unnamed module.
> [ERROR] javadoc: error - The code being documented uses modules but the
> packages defined in
> https://commons.apache.org/proper/commons-rng/commons-rng-client-api/apidocs/
> are in the unnamed module.
> [ERROR] javadoc: error - The code being documented uses modules but the
> packages defined in
> https://commons.apache.org/proper/commons-rng/commons-rng-sampling/apidocs/
> are in the unnamed module.
>
> Source 9, OpenAdopt JDK 11.0.5
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.8.2:site (default-site) on
> project commons-rng-examples-jpms-lib: Error generating
> maven-javadoc-plugin:3.1.1:javadoc report:
> [ERROR] Exit code: 1 - javadoc: error - The code being documented uses
> modules but the packages defined in
> https://docs.oracle.com/javase/9/docs/api/ are in the unnamed module.
>
>
> Source 11, JDK 11.0.5
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.8.2:site (default-site) on
> project commons-rng-examples-jpms-lib: Error generating
> maven-javadoc-plugin:3.1.1:javadoc report:
> [ERROR] Exit code: 1 - javadoc: error - The code being documented uses
> modules but the packages defined in
> https://commons.apache.org/proper/commons-rng/commons-rng-client-api/apidocs/
> are in the unnamed module.
> [ERROR] javadoc: error - The code being documented uses modules but the
> packages defined in
> https://commons.apache.org/proper/commons-rng/commons-rng-sampling/apidocs/
> are in the unnamed module.
>
>
> Source 11, OpenAdopt JDK 11.0.5
>
> OK
>
>
>
> So there are at least two options:
>
> 1. Release using JDK 9
>
I did not read all the details but I know that if you compile with JDK 9
and you use a JRE classes in the NIO Buffer hierarchy, things will break
when running on Java 8 due to some methods in the JRE being
added/moved/ICantRecallTheDetails in the hierarchy.
IOW, you are opening yourself up to a world of pain. The KISS is to compile
with your target platform, otherwise, you can get in trouble.
Gary
> 2. Update the examples project to use source 11 for the Java modules code
> and release using a non-oracle JDK 11
>
> Note that updating to use source 11 will break the Jenkins build which
> uses JDK 9 to run a full build including the -P commons-rng-examples
> profile. This could be ignored, updated to JDK 11 or dropped in favour of
> adding an appropriate JDK 11 run using Travis.
>
> Another option is to somehow get around the javadoc issue with modules and
> unnamed modules.
>
> WDYT?
>
> Alex
>
>
> >
> > Alex
> >
> >
> > [1] https://github.com/apache/commons-rng/pull/32 <
> https://github.com/apache/commons-rng/pull/32>
> >>
> >> Gary
> >>
> >>
> >>>
> >>> Alex
> >>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org <mailto:
> dev-unsubscribe@commons.apache.org>
> >>> For additional commands, e-mail: dev-help@commons.apache.org <mailto:
> dev-help@commons.apache.org>
>
Re: [rng] Releasing 1.3
Posted by Rob Tompkins <ch...@gmail.com>.
I would cd into ./target/commons-release-plugin/scm and try the svn commit from there manually. That’s the directory where everything gets staged.
I also think your svn password gets cached generally, but that’s predicated on having checked something into svn previously. Given our recent migration to all git based projects i could see that not working the first time. You can also pass “-Duser.password=...” at the command step, but that’s ugly in my opinion and can be avoided by putting that password down in your settings.xml.
Keep me posted and I’ll try to answer quickly,
-Rob
> On Nov 4, 2019, at 2:31 PM, Alex Herbert <al...@gmail.com> wrote:
>
>
>
>> On 4 Nov 2019, at 18:38, Rob Tompkins <ch...@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 <ch...@gmail.com> wrote:
>>>
>>>
>>>
>>>> On Nov 4, 2019, at 1:16 PM, Alex Herbert <al...@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 <al...@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
>>>>> 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'
>>>>> 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
>>>>
>>>> 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?
>
>>>
>>> -Rob
>>>
>>>>
>>>> Alex
>>>>
>>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [rng] Releasing 1.3
Posted by Alex Herbert <al...@gmail.com>.
> On 4 Nov 2019, at 19:31, Alex Herbert <al...@gmail.com> wrote:
>
>
>
>> On 4 Nov 2019, at 18:38, Rob Tompkins <chtompki@gmail.com <ma...@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 <chtompki@gmail.com <ma...@gmail.com>> wrote:
>>>
>>>
>>>
>>>> On Nov 4, 2019, at 1:16 PM, Alex Herbert <alex.d.herbert@gmail.com <ma...@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.herbert@gmail.com <ma...@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-unsubscribe@commons.apache.org <ma...@commons.apache.org>
>> For additional commands, e-mail: dev-help@commons.apache.org <ma...@commons.apache.org>
Re: [rng] Releasing 1.3
Posted by Alex Herbert <al...@gmail.com>.
> On 4 Nov 2019, at 18:38, Rob Tompkins <ch...@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 <ch...@gmail.com> wrote:
>>
>>
>>
>>> On Nov 4, 2019, at 1:16 PM, Alex Herbert <al...@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 <al...@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
>>>> 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'
>>>> 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
>>>
>>> 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?
>>
>> -Rob
>>
>>>
>>> Alex
>>>
>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
Re: [rng] Releasing 1.3
Posted by Rob Tompkins <ch...@gmail.com>.
Also keep me posted. I’ll be near my keyboard all day. -Rob
> On Nov 4, 2019, at 1:21 PM, Rob Tompkins <ch...@gmail.com> wrote:
>
>
>
>> On Nov 4, 2019, at 1:16 PM, Alex Herbert <al...@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 <al...@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
>>> 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'
>>> 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
>>
>> 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.
>
> -Rob
>
>>
>> Alex
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [rng] Releasing 1.3
Posted by Rob Tompkins <ch...@gmail.com>.
> On Nov 4, 2019, at 1:16 PM, Alex Herbert <al...@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 <al...@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
>> 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'
>> 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
>
> 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.
-Rob
>
> Alex
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [rng] Releasing 1.3
Posted by Alex Herbert <al...@gmail.com>.
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 <al...@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
> 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'
> 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
The dev area still has version 1.2-RC2 from the last release. Would this
effect anything in the release process?
Alex
Re: [rng] Releasing 1.3
Posted by Alex Herbert <al...@gmail.com>.
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 <al...@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
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'
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
Re: [rng] Releasing 1.3
Posted by Alex Herbert <al...@gmail.com>.
On 04/11/2019 12:43, Gilles Sadowski wrote:
> Hello.
>
> Le lun. 4 nov. 2019 à 13:05, Alex Herbert <al...@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.
This command does not work with Java 9:
mvn -N -Pcommons-rng-examples commons-build:download-page
You have to build the download page using Java 8. Then switch to Java 9
again.
>
>> I am looking at the clirr report to check and add @since tags.
>>
>> Q. How to annotate implementation of a new interface on an existing class?
>>
>> Should all the new interface methods have @since tags?
> Isn't it good enough to have the tag in the class Javadoc?
For new classes. This is new methods added to existing classes due to
implementation of a new interface.
I've taken the safe option to put @since on all the new methods.
I also added @since to all the new enum values in RandomSource.
Alex
>
> Gilles
>
>>> [...]
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [rng] Releasing 1.3
Posted by Gilles Sadowski <gi...@gmail.com>.
Hello.
Le lun. 4 nov. 2019 à 13:05, Alex Herbert <al...@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).
> I am looking at the clirr report to check and add @since tags.
>
> Q. How to annotate implementation of a new interface on an existing class?
>
> Should all the new interface methods have @since tags?
Isn't it good enough to have the tag in the class Javadoc?
Gilles
> >
> > [...]
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [rng] Releasing 1.3
Posted by Alex Herbert <al...@gmail.com>.
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.
I am looking at the clirr report to check and add @since tags.
Q. How to annotate implementation of a new interface on an existing class?
Should all the new interface methods have @since tags?
>
>> 2. Update the examples project to use source 11 for the Java modules code and release using a non-oracle JDK 11
>>
>> Note that updating to use source 11 will break the Jenkins build which uses JDK 9 to run a full build including the -P commons-rng-examples profile. This could be ignored, updated to JDK 11 or dropped in favour of adding an appropriate JDK 11 run using Travis.
>>
>> Another option is to somehow get around the javadoc issue with modules and unnamed modules.
> Let's not delay because of side issues. :-)
> Hopefully, this will be fixed in a future JDK version, or when we
> upgrade the target
> of all modules.
>
> Best,
> Gilles
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [rng] Releasing 1.3
Posted by Gilles Sadowski <gi...@gmail.com>.
Hi.
> [...]
>
> So there are at least two options:
>
> 1. Release using JDK 9
+1
> 2. Update the examples project to use source 11 for the Java modules code and release using a non-oracle JDK 11
>
> Note that updating to use source 11 will break the Jenkins build which uses JDK 9 to run a full build including the -P commons-rng-examples profile. This could be ignored, updated to JDK 11 or dropped in favour of adding an appropriate JDK 11 run using Travis.
>
> Another option is to somehow get around the javadoc issue with modules and unnamed modules.
Let's not delay because of side issues. :-)
Hopefully, this will be fixed in a future JDK version, or when we
upgrade the target
of all modules.
Best,
Gilles
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [rng] Releasing 1.3
Posted by Alex Herbert <al...@gmail.com>.
> On 3 Nov 2019, at 20:12, Alex Herbert <al...@gmail.com> wrote:
>
>
>
>> On 3 Nov 2019, at 19:30, Gary Gregory <garydgregory@gmail.com <ma...@gmail.com>> wrote:
>>
>> On Sun, Nov 3, 2019 at 10:01 AM Alex Herbert <alex.d.herbert@gmail.com <ma...@gmail.com>>
>> wrote:
>>
>>> I think everything is finalised for a release of RNG, namely:
>>>
>>> All bugs and issues with SonarCloud and LGTM.com <http://lgtm.com/> are fixed.
>>> The user guide has been updated for all the new features.
>>> The performance and quality results have been updated in the user guide.
>>>
>>> Any objections to me cutting a release candidate for v1.3? I hope to get
>>> it done next week.
>>>
>>
>> You first should make sure binary compatibility is there, Apache RAT check
>> passes, and so on. That will avoid possible issues in a RC.
>
> rat:check and clirr:check are part of the default maven build so errors should not enter the codebase.
>
> The clirr:clirr report is full of infos for all the new API methods and classes.
>
> I'll start with a release dry run and see how everything looks.
>
> The only outstanding “issue” is that the full code for release has to be built using JDK 9.
>
> The extra examples maven modules contains some code using Java 9 modules. All my attempts to get a build to work with JDK 11 have failed on the javadoc tool which complains about building for code using modules that references packages in the named module [1]. My last attempt using JDK 11.0.4 had the same error I found with JDK 11.0.2. I have not a found a fix for a multi-module Maven project that uses different java source versions and includes some java 9 source explicitly using modules.
>
> Given that JDK 11.0.5 is out I will have another look at this. A brief scan of the release notes for 11.0.5 does not mention anything but it is worth a try. I’d rather do a release using JDK 11 than JDK 9.
JDK 11 works depending on the vendor and the source version!
Steps
1. Optional. Update commons-rng-examples/examples-jpms/pom.xml to changes the source and target from 9 to 11. This is:
<maven.compiler.source>11</maven.compiler.source>
<maven.compiler.target>11</maven.compiler.target>
<maven.compiler.release>11</maven.compiler.release>
2. Build using: mvn clean package site site:stage -P commons-rng-examples
Tested two JDK 11 distributions:
Official JDK from https://jdk.java.net/java-se-ri/11 <https://jdk.java.net/java-se-ri/11>
java -version
java version "11.0.5" 2019-10-15 LTS
Java(TM) SE Runtime Environment 18.9 (build 11.0.5+10-LTS)
Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.5+10-LTS, mixed mode)
OpenAdopt JDK https://adoptopenjdk.net/releases.html?variant=openjdk11&jvmVariant=hotspot#x64_linux <https://adoptopenjdk.net/releases.html?variant=openjdk11&jvmVariant=hotspot#x64_linux>
java -version
openjdk version "11.0.5" 2019-10-15
OpenJDK Runtime Environment AdoptOpenJDK (build 11.0.5+10)
OpenJDK 64-Bit Server VM AdoptOpenJDK (build 11.0.5+10, mixed mode)
I tried 4 variants:
Source 9, JDK 11.0.5
Source 9, OpenAdopt JDK 11.0.5
Source 11, JDK 11.0.5
Source 11, OpenAdopt JDK 11.0.5
Source 9, JDK 11.0.5
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.8.2:site (default-site) on project commons-rng-examples-jpms-lib: Error generating maven-javadoc-plugin:3.1.1:javadoc report:
[ERROR] Exit code: 1 - javadoc: error - The code being documented uses modules but the packages defined in https://docs.oracle.com/javase/9/docs/api/ are in the unnamed module.
[ERROR] javadoc: error - The code being documented uses modules but the packages defined in https://commons.apache.org/proper/commons-rng/commons-rng-client-api/apidocs/ are in the unnamed module.
[ERROR] javadoc: error - The code being documented uses modules but the packages defined in https://commons.apache.org/proper/commons-rng/commons-rng-sampling/apidocs/ are in the unnamed module.
Source 9, OpenAdopt JDK 11.0.5
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.8.2:site (default-site) on project commons-rng-examples-jpms-lib: Error generating maven-javadoc-plugin:3.1.1:javadoc report:
[ERROR] Exit code: 1 - javadoc: error - The code being documented uses modules but the packages defined in https://docs.oracle.com/javase/9/docs/api/ are in the unnamed module.
Source 11, JDK 11.0.5
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.8.2:site (default-site) on project commons-rng-examples-jpms-lib: Error generating maven-javadoc-plugin:3.1.1:javadoc report:
[ERROR] Exit code: 1 - javadoc: error - The code being documented uses modules but the packages defined in https://commons.apache.org/proper/commons-rng/commons-rng-client-api/apidocs/ are in the unnamed module.
[ERROR] javadoc: error - The code being documented uses modules but the packages defined in https://commons.apache.org/proper/commons-rng/commons-rng-sampling/apidocs/ are in the unnamed module.
Source 11, OpenAdopt JDK 11.0.5
OK
So there are at least two options:
1. Release using JDK 9
2. Update the examples project to use source 11 for the Java modules code and release using a non-oracle JDK 11
Note that updating to use source 11 will break the Jenkins build which uses JDK 9 to run a full build including the -P commons-rng-examples profile. This could be ignored, updated to JDK 11 or dropped in favour of adding an appropriate JDK 11 run using Travis.
Another option is to somehow get around the javadoc issue with modules and unnamed modules.
WDYT?
Alex
>
> Alex
>
>
> [1] https://github.com/apache/commons-rng/pull/32 <https://github.com/apache/commons-rng/pull/32>
>>
>> Gary
>>
>>
>>>
>>> Alex
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org <ma...@commons.apache.org>
>>> For additional commands, e-mail: dev-help@commons.apache.org <ma...@commons.apache.org>
Re: [rng] Releasing 1.3
Posted by Alex Herbert <al...@gmail.com>.
> On 3 Nov 2019, at 19:30, Gary Gregory <ga...@gmail.com> wrote:
>
> On Sun, Nov 3, 2019 at 10:01 AM Alex Herbert <al...@gmail.com>
> wrote:
>
>> I think everything is finalised for a release of RNG, namely:
>>
>> All bugs and issues with SonarCloud and LGTM.com are fixed.
>> The user guide has been updated for all the new features.
>> The performance and quality results have been updated in the user guide.
>>
>> Any objections to me cutting a release candidate for v1.3? I hope to get
>> it done next week.
>>
>
> You first should make sure binary compatibility is there, Apache RAT check
> passes, and so on. That will avoid possible issues in a RC.
rat:check and clirr:check are part of the default maven build so errors should not enter the codebase.
The clirr:clirr report is full of infos for all the new API methods and classes.
I'll start with a release dry run and see how everything looks.
The only outstanding “issue” is that the full code for release has to be built using JDK 9.
The extra examples maven modules contains some code using Java 9 modules. All my attempts to get a build to work with JDK 11 have failed on the javadoc tool which complains about building for code using modules that references packages in the named module [1]. My last attempt using JDK 11.0.4 had the same error I found with JDK 11.0.2. I have not a found a fix for a multi-module Maven project that uses different java source versions and includes some java 9 source explicitly using modules.
Given that JDK 11.0.5 is out I will have another look at this. A brief scan of the release notes for 11.0.5 does not mention anything but it is worth a try. I’d rather do a release using JDK 11 than JDK 9.
Alex
[1] https://github.com/apache/commons-rng/pull/32 <https://github.com/apache/commons-rng/pull/32>
>
> Gary
>
>
>>
>> Alex
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>>
Re: [rng] Releasing 1.3
Posted by Gary Gregory <ga...@gmail.com>.
On Sun, Nov 3, 2019 at 10:01 AM Alex Herbert <al...@gmail.com>
wrote:
> I think everything is finalised for a release of RNG, namely:
>
> All bugs and issues with SonarCloud and LGTM.com are fixed.
> The user guide has been updated for all the new features.
> The performance and quality results have been updated in the user guide.
>
> Any objections to me cutting a release candidate for v1.3? I hope to get
> it done next week.
>
You first should make sure binary compatibility is there, Apache RAT check
passes, and so on. That will avoid possible issues in a RC.
Gary
>
> Alex
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>