Re: [All] Main site is outdated
Le jeu. 8 déc. 2022 à 00:32, sebb a écrit : > > On Wed, 7 Dec 2022 at 13:20, Alex Herbert wrote: > > > > So I can see the file to edit is index.html at this location: > > > > svn checkout --depth files > > https://svn.apache.org/repos/infra/websites/production/commons/content/ > > > > But should this be edited manually, or is it generated/updated via > > some automation? > > That URL is where the website is served; when the site is built from > source it will be overwritten. > > The actual site source is here: > > https://svn.apache.org/repos/asf/commons/cms-site/trunk/ > > There is some documentation here: > > https://commons.apache.org/site-publish.html > > > I ask as the newly released statistics component entry requires more > > than just a version number to be updated. The entire link and badge > > requires adding. > > That needs to be done here I think: > > https://svn.apache.org/repos/asf/commons/cms-site/trunk/content/xdoc/index.xml.vm Thanks for the reminder. Main web site has been updated. Regards, Gilles >>> [...] - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [All] Main site is outdated
On Thu, 8 Dec 2022 at 10:17, Gilles Sadowski wrote: > > Le jeu. 8 déc. 2022 à 00:32, sebb a écrit : > > > > On Wed, 7 Dec 2022 at 13:20, Alex Herbert wrote: > > > > > > So I can see the file to edit is index.html at this location: > > > > > > svn checkout --depth files > > > https://svn.apache.org/repos/infra/websites/production/commons/content/ > > > > > > But should this be edited manually, or is it generated/updated via > > > some automation? > > > > That URL is where the website is served; when the site is built from > > source it will be overwritten. > > > > The actual site source is here: > > > > https://svn.apache.org/repos/asf/commons/cms-site/trunk/ > > > > There is some documentation here: > > > > https://commons.apache.org/site-publish.html > > > > > I ask as the newly released statistics component entry requires more > > > than just a version number to be updated. The entire link and badge > > > requires adding. > > > > That needs to be done here I think: > > > > https://svn.apache.org/repos/asf/commons/cms-site/trunk/content/xdoc/index.xml.vm > > Thanks for the reminder. > > Main web site has been updated. I have corrected the doap files to match those in conf/component_releases.properties so that running this: > conf/parse-latest-release.py currently makes no changes. This mainly added releases that have been manually updated in the component_releases.properties but not in the doap file. Only the latest Jexl 3.2.1 release required an update and the release date for compress 1.22. The following link is still out-of-date on the main site: jexl 3.2 -> 3.2.1 When I build locally (see below) there is no svn diff and the link is correct in the staging area at: https://svn.apache.org/repos/infra/websites/staging/commons/trunk/content/index.html Gilles, it looks like (from the commit message) that you ran commons-site-publish.sh. But somehow the link for Jexl is still pointing at 3.2 and not 3.2.1. So I do not know what went wrong for this link. For the release process: After the component doap file is updated then the commons site should be rebuilt. This used to be done by a build-bot but now must be done manually. This requires running: > svn co https://svn.apache.org/repos/asf/commons/cms-site/trunk/ ==> edit doap/doap_.rdf > conf/parse-latest-release.py > svn diff => check you have not downgraded other components - fix their doap file and repeat > svn commit conf doap -m 'Regenerated component releases' > commons-site-build.sh > svn diff target/site > svn commit target/site -m 'Update the staging site prior to deployment' => inspect at https://svn.apache.org/repos/infra/websites/staging/commons/trunk/content/index.html > commons-site-publish.sh => inspect target/commons-site-publish.svnmucc => Run svnmucc command printed by the script If this is correct then I can update the release guide we use in the math-derived component to reflect these steps. Alex Alex - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [All] Main site is outdated
Le jeu. 8 déc. 2022 à 13:15, Alex Herbert a écrit : > > On Thu, 8 Dec 2022 at 10:17, Gilles Sadowski wrote: > > > > Le jeu. 8 déc. 2022 à 00:32, sebb a écrit : > > > > > > On Wed, 7 Dec 2022 at 13:20, Alex Herbert > > > wrote: > > > > > > > > So I can see the file to edit is index.html at this location: > > > > > > > > svn checkout --depth files > > > > https://svn.apache.org/repos/infra/websites/production/commons/content/ > > > > > > > > But should this be edited manually, or is it generated/updated via > > > > some automation? > > > > > > That URL is where the website is served; when the site is built from > > > source it will be overwritten. > > > > > > The actual site source is here: > > > > > > https://svn.apache.org/repos/asf/commons/cms-site/trunk/ > > > > > > There is some documentation here: > > > > > > https://commons.apache.org/site-publish.html > > > > > > > I ask as the newly released statistics component entry requires more > > > > than just a version number to be updated. The entire link and badge > > > > requires adding. > > > > > > That needs to be done here I think: > > > > > > https://svn.apache.org/repos/asf/commons/cms-site/trunk/content/xdoc/index.xml.vm > > > > Thanks for the reminder. > > > > Main web site has been updated. > > I have corrected the doap files to match those in > conf/component_releases.properties so that running this: > > > conf/parse-latest-release.py > > currently makes no changes. I've just run it, and it "downgrades" * RNG (to 1.1) * Collections (to 4.1) :-? > > This mainly added releases that have been manually updated in the > component_releases.properties but not in the doap file. Only the > latest Jexl 3.2.1 release required an update and the release date for > compress 1.22. > > The following link is still out-of-date on the main site: > > jexl 3.2 -> 3.2.1 > > When I build locally (see below) there is no svn diff and the link is > correct in the staging area at: > > https://svn.apache.org/repos/infra/websites/staging/commons/trunk/content/index.html > > Gilles, it looks like (from the commit message) that you ran > commons-site-publish.sh. Yes. > But somehow the link for Jexl is still > pointing at 3.2 and not 3.2.1. So I do not know what went wrong for > this link. No idea either. Gilles > > > For the release process: > > After the component doap file is updated then the commons site should > be rebuilt. This used to be done by a build-bot but now must be done > manually. This requires running: > > > svn co https://svn.apache.org/repos/asf/commons/cms-site/trunk/ > ==> edit doap/doap_.rdf > > conf/parse-latest-release.py > > svn diff > => check you have not downgraded other components - fix their doap > file and repeat > > svn commit conf doap -m 'Regenerated component releases' > > > commons-site-build.sh > > svn diff target/site > > svn commit target/site -m 'Update the staging site prior to deployment' > => inspect at > https://svn.apache.org/repos/infra/websites/staging/commons/trunk/content/index.html > > > commons-site-publish.sh > => inspect target/commons-site-publish.svnmucc > => Run svnmucc command printed by the script > > If this is correct then I can update the release guide we use in the > math-derived component to reflect these steps. > > Alex > > > Alex > > - > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [All] Main site is outdated
On Thu, 8 Dec 2022 at 12:43, Gilles Sadowski wrote: > > > > > conf/parse-latest-release.py > > > > currently makes no changes. > > I've just run it, and it "downgrades" > * RNG (to 1.1) > * Collections (to 4.1) > > :-? That is strange. The script shebang uses env to pick the python version. My version is: /usr/bin/env python --version Python 2.7.17 But it also works with: python3 --version Python 3.6.9 Perhaps you do not have the latest doap files. Run 'svn update' from the trunk folder or checkout clean again. Alex - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [VOTE][LAZY] Release Apache Commons Parent 55 based on RC1
Hi Gary, I tried with the latest git master for numbers, rng and lang. The updated spdx-maven-plugin is not compatible with java 8. I get the following error: [ERROR] Failed to execute goal org.spdx:spdx-maven-plugin:0.6.3:createSPDX (build-spdx) on project commons-lang3: Execution build-spd x of goal org.spdx:spdx-maven-plugin:0.6.3:createSPDX failed: An API incompatibility was encountered while executing org.spdx:spdx-ma ven-plugin:0.6.3:createSPDX: java.lang.UnsupportedClassVersionError: org/spdx/spdxRdfStore/RdfStore has been compiled by a more recen t version of the Java Runtime (class file version 55.0), this version of the Java Runtime only recognizes class file versions up to 5 2.0 mvn -v Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63) Maven home: /usr/local/apache-maven-3 Java version: 1.8.0_352, vendor: Private Build, runtime: /usr/lib/jvm/java-8-openjdk-amd64/jre Default locale: en_GB, platform encoding: UTF-8 OS name: "linux", version: "4.15.0-200-generic", arch: "amd64", family: "unix" Note: I am not clear exactly what the issue is as it does not happen in the first jar module of the rng project reactor. The first module commons-rng-client-api has no dependencies and this builds ok. The next module commons-rng-core only depends on the client-api. This also builds. The reactor breaks on the simple module which depends on core and the client-api. However in numbers the reactor breaks on the first module commons-numbers-core. This has no runtime dependencies. So some part of the spdx plugin is being invoked only in some modules that has a class compiled for Java 11. Building under JDK 11 was fine for all 3 named projects. Note that numbers and rng previously had set to true as the configuration in CP 54 broke the build. I changed to false and the multi-module build was fine. mvn -v Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63) Maven home: /usr/local/apache-maven-3 Java version: 11.0.17, vendor: Ubuntu, runtime: /usr/lib/jvm/java-11-openjdk-amd64 Default locale: en_GB, platform encoding: UTF-8 OS name: "linux", version: "4.15.0-200-generic", arch: "amd64", family: "unix" So cyclonedx is fixed, but spdx is now not Java 8 compatible. Alex On Wed, 7 Dec 2022 at 19:50, Gary Gregory wrote: > > We made some enhancements since Apache Commons Parent 54 was released, > so I would like to release Apache Commons Parent 55. > > This is the parent POM for Apache Commons, it doesn't contain Java > code, and therefore no JApiCmp API compatibility check or report on > the site. > > Apache Commons Parent 55 RC1 is available for review here: > https://dist.apache.org/repos/dist/dev/commons/commons-parent/55-RC1 > (svn revision 58537) > > The Git tag commons-parent-55-RC1 commit for this RC is > 1a8382d227787216d76c1fea62b641158d0a265e which you can browse here: > > https://gitbox.apache.org/repos/asf?p=commons-parent.git;a=commit;h=1a8382d227787216d76c1fea62b641158d0a265e > You may checkout this tag using: > git clone https://gitbox.apache.org/repos/asf/commons-parent.git > --branch commons-parent-55-RC1 commons-parent-55-RC1 > > Maven artifacts are here: > > https://repository.apache.org/content/repositories/orgapachecommons-1611/org/apache/commons/commons-parent/55/ > > These are the artifacts and their hashes: > > #Release SHA-512s > #Wed Dec 07 14:37:02 EST 2022 > commons-parent-55-bom.json=e96e4d8f44b900ae5b12abbf81c1fa9a5c28e13c0767290e85c0f9e0486c9b3d2f6dac6ba8f4ca3f25c00716b5b6c180f16e0cfa17a51b1fd3c63c57f13deded > commons-parent-55-bom.xml=11bdf25c251b8b99f5684740e05fa08e8ad01dddeb6544327083696a578bc48785a8d27d03cd7b1ce8f3ace8f4e1b60d32819e4a3b6bc1ed775be5d549e32d33 > commons-parent-55-site.xml=735ffceca46a0574d430b4e1213a2462b9475143c0788913312b8af117eaf3b7c02a075aaf6d9b30d2560822339651cb511b838f6c9f2bced46de1fc1227c5ff > commons-parent-55-src.tar.gz=1a0307090faca60eaf8a034201521262828c283c8e51dd92a1add0adf48bb55898e0d990daa407648e7b65d6e85a7629ecfb30f4195fbc47d6bf0d14e9664254 > commons-parent-55-src.zip=13c5158f0957853e1df39aa5aa03180b404caa727fef276c969bc811de1e6b3b5465341d544869b338597805b085c21fee63b3d2f6f42dd93dd297fe5e6c8cda > org.apache.commons_commons-parent-55.spdx.json=14f27b64c60287116e84e2ae9b4d66017260287962c29baef621e9e2b06c06578768453a05bafa90cbe1aa2fe04e248aaedf9b64e8683c658452dedd798e8538 > > I have tested this with 'mvn clean install' using: > > Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63) > Maven home: /usr/local/Cellar/maven/3.8.6/libexec > Java version: 1.8.0_352, vendor: Homebrew, runtime: > /usr/local/Cellar/openjdk@8/1.8.0+352/libexec/openjdk.jdk/Contents/Home/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "mac os x", version: "13.0.1", arch: "x86_64", family: "mac" > Darwin 22.1.0 Darwin Kernel Version 22.1.0: Sun Oct 9 20:14:54 > PDT 2022; root:xnu-8792.41.9~2/RELEASE_X86_64 x86_64 > > Details of changes since 54 are in the release notes: > > https://dist.apache.org/repos/dis
Re: [All] Main site is outdated
Le jeu. 8 déc. 2022 à 14:13, Alex Herbert a écrit : > > On Thu, 8 Dec 2022 at 12:43, Gilles Sadowski wrote: > > > > > > > > conf/parse-latest-release.py > > > > > > currently makes no changes. > > > > I've just run it, and it "downgrades" > > * RNG (to 1.1) > > * Collections (to 4.1) > > > > :-? > > That is strange. > > The script shebang uses env to pick the python version. My version is: > > /usr/bin/env python --version > Python 2.7.17 > > But it also works with: > > python3 --version > Python 3.6.9 > > Perhaps you do not have the latest doap files. Run 'svn update' from > the trunk folder I had done that, to no avail. > or checkout clean again. I did that; it now works. Thanks, Gilles - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [imaging] I want to know the roadmap up to the version 1.0 in the future
[Moving to "dev" ML...] Le jeu. 8 déc. 2022 à 16:56, Gary Gregory a écrit : > > Since we had alpha releases, should we have a beta? +1 It would allow modifying the API in order to e.g. provide a code that self-documents the caller's responsibility wrt validation of external input. [Something which "cottonspace" might want to help with (?).] Gilles >> [...] - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [All] Main site is outdated
On Thu, 8 Dec 2022 at 13:50, Gilles Sadowski wrote: > > Le jeu. 8 déc. 2022 à 14:13, Alex Herbert a écrit : > > > > On Thu, 8 Dec 2022 at 12:43, Gilles Sadowski wrote: > > > > > > > > > > > conf/parse-latest-release.py > > > > > > > > currently makes no changes. > > > > > > I've just run it, and it "downgrades" > > > * RNG (to 1.1) > > > * Collections (to 4.1) > > > > > > :-? > > > > That is strange. > > > > The script shebang uses env to pick the python version. My version is: > > > > /usr/bin/env python --version > > Python 2.7.17 > > > > But it also works with: > > > > python3 --version > > Python 3.6.9 > > > > Perhaps you do not have the latest doap files. Run 'svn update' from > > the trunk folder > > I had done that, to no avail. > > > or checkout clean again. > > I did that; it now works. Good to know. I checked the index.html for the staging and live site and the differences are minor: svn co --depth files https://svn.apache.org/repos/infra/websites/production/commons/content/ svn co --depth files https://svn.apache.org/repos/infra/websites/staging/commons/trunk/content content2 diff content/index.html content2/index.html < 2021-07-12 --- > 2022-11-01 559,560c559,560 < https://search.maven.org/artifact/org.apache.commons/commons-jexl3/3.2/jar"; rel="nofollow"> < https://img.shields.io/maven-central/v/org.apache.commons/commons-jexl3"; alt="3.2" style="max-wid th:100%;" /> --- > href="https://search.maven.org/artifact/org.apache.commons/commons-jexl3/3.2.1/jar"; > rel="nofollow"> > src="https://img.shields.io/maven-central/v/org.apache.commons/commons-jexl3"; > alt="3.2.1" style="max-w idth:100%;" /> 562c562 < 2021-06-07 --- > 2021-06-25 The date is for compress. The version difference for jexl. There may have been a generation or transfer error somewhere so I've directly commited the correct index file. Alex - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [imaging] I want to know the roadmap up to the version 1.0 in the future
No objection from me :) 1.0b or 1.0, doing any progress on [Imaging] would be grand. -Bruno On Thu, 8 Dec 2022 at 17:11, Gilles Sadowski wrote: > [Moving to "dev" ML...] > > Le jeu. 8 déc. 2022 à 16:56, Gary Gregory a > écrit : > > > > Since we had alpha releases, should we have a beta? > > +1 > > It would allow modifying the API in order to e.g. provide a code that > self-documents the caller's responsibility wrt validation of external > input. [Something which "cottonspace" might want to help with (?).] > > Gilles > > >> [...] > > - > To unsubscribe, e-mail: user-unsubscr...@commons.apache.org > For additional commands, e-mail: user-h...@commons.apache.org > >
Re: [imaging] I want to know the roadmap up to the version 1.0 in the future
Then I encourage 1.0-beta1 ;-) Gary On Thu, Dec 8, 2022, 11:29 Bruno Kinoshita wrote: > No objection from me :) 1.0b or 1.0, doing any progress on [Imaging] would > be grand. > > -Bruno > > On Thu, 8 Dec 2022 at 17:11, Gilles Sadowski wrote: > > > [Moving to "dev" ML...] > > > > Le jeu. 8 déc. 2022 à 16:56, Gary Gregory a > > écrit : > > > > > > Since we had alpha releases, should we have a beta? > > > > +1 > > > > It would allow modifying the API in order to e.g. provide a code that > > self-documents the caller's responsibility wrt validation of external > > input. [Something which "cottonspace" might want to help with (?).] > > > > Gilles > > > > >> [...] > > > > - > > To unsubscribe, e-mail: user-unsubscr...@commons.apache.org > > For additional commands, e-mail: user-h...@commons.apache.org > > > > >
Re: [VOTE][LAZY] Release Apache Commons Parent 55 based on RC1
Hi Alex, Thank you for your review. I cannot reproduce your error. I tested locally now with commons-parent git master 55-SNAPSHOT with commons-text (the component I tested for the RC), commons-lang, and commons-rng. For 'mvn install -DskipTests', I see output like: ... [INFO] <<< spdx-maven-plugin:0.6.3:createSPDX (build-spdx) < verify @ commons-lang3 <<< [INFO] [INFO] [INFO] --- spdx-maven-plugin:0.6.3:createSPDX (build-spdx) @ commons-lang3 --- [INFO] Creating SPDX File C:\Users\ggregory\git\a\commons-lang\target\site\org.apache.commons_commons-lang3-3.13.0-SNAPSHOT.spdx.json [WARNING] Unable to map maven licenses to a declared license. Using NOASSERTION [WARNING] Could not determine the SPDX relationship type for dependency artifact ID commons-text scope provided [WARNING] Could not determine the SPDX relationship type for dependency artifact ID commons-lang3 scope provided [INFO] ... My output for commons-rng is here: https://paste.apache.org/sml51 All I did is edit the parent POM version in the root pom.xml I am running with: Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63) Maven home: C:\java\apache-maven-3.8.6 Java version: 1.8.0_352, vendor: Temurin, runtime: C:\Program Files\Eclipse Adoptium\jdk-8.0.352.8-hotspot\jre Default locale: en_US, platform encoding: Cp1252 OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows" Microsoft Windows [Version 10.0.19044.2251] Gary On 2022/12/08 13:18:46 Alex Herbert wrote: > Hi Gary, > > I tried with the latest git master for numbers, rng and lang. The > updated spdx-maven-plugin is not compatible with java 8. I get the > following error: > > [ERROR] Failed to execute goal > org.spdx:spdx-maven-plugin:0.6.3:createSPDX (build-spdx) on project > commons-lang3: Execution build-spd > x of goal org.spdx:spdx-maven-plugin:0.6.3:createSPDX failed: An API > incompatibility was encountered while executing org.spdx:spdx-ma > ven-plugin:0.6.3:createSPDX: java.lang.UnsupportedClassVersionError: > org/spdx/spdxRdfStore/RdfStore has been compiled by a more recen > t version of the Java Runtime (class file version 55.0), this version > of the Java Runtime only recognizes class file versions up to 5 > 2.0 > > mvn -v > Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63) > Maven home: /usr/local/apache-maven-3 > Java version: 1.8.0_352, vendor: Private Build, runtime: > /usr/lib/jvm/java-8-openjdk-amd64/jre > Default locale: en_GB, platform encoding: UTF-8 > OS name: "linux", version: "4.15.0-200-generic", arch: "amd64", family: "unix" > > Note: I am not clear exactly what the issue is as it does not happen > in the first jar module of the rng project reactor. The first module > commons-rng-client-api has no dependencies and this builds ok. The > next module commons-rng-core only depends on the client-api. This also > builds. The reactor breaks on the simple module which depends on core > and the client-api. However in numbers the reactor breaks on the first > module commons-numbers-core. This has no runtime dependencies. So some > part of the spdx plugin is being invoked only in some modules that has > a class compiled for Java 11. > > Building under JDK 11 was fine for all 3 named projects. > > Note that numbers and rng previously had set to true > as the configuration in CP 54 broke the build. I changed to false and > the multi-module build was fine. > > mvn -v > Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63) > Maven home: /usr/local/apache-maven-3 > Java version: 11.0.17, vendor: Ubuntu, runtime: > /usr/lib/jvm/java-11-openjdk-amd64 > Default locale: en_GB, platform encoding: UTF-8 > OS name: "linux", version: "4.15.0-200-generic", arch: "amd64", family: "unix" > > So cyclonedx is fixed, but spdx is now not Java 8 compatible. > > Alex > > On Wed, 7 Dec 2022 at 19:50, Gary Gregory wrote: > > > > We made some enhancements since Apache Commons Parent 54 was released, > > so I would like to release Apache Commons Parent 55. > > > > This is the parent POM for Apache Commons, it doesn't contain Java > > code, and therefore no JApiCmp API compatibility check or report on > > the site. > > > > Apache Commons Parent 55 RC1 is available for review here: > > https://dist.apache.org/repos/dist/dev/commons/commons-parent/55-RC1 > > (svn revision 58537) > > > > The Git tag commons-parent-55-RC1 commit for this RC is > > 1a8382d227787216d76c1fea62b641158d0a265e which you can browse here: > > > > https://gitbox.apache.org/repos/asf?p=commons-parent.git;a=commit;h=1a8382d227787216d76c1fea62b641158d0a265e > > You may checkout this tag using: > > git clone https://gitbox.apache.org/repos/asf/commons-parent.git > > --branch commons-parent-55-RC1 commons-parent-55-RC1 > > > > Maven artifacts are here: > > > > https://repository.apache.org/content/repositories/orgapachecommons-1611/org/apache/commons/commons-parent/55/ > > > > These are the artifacts and their hashes: > > > > #Release SHA-512s
Re: [VOTE][LAZY] Release Apache Commons Parent 55 based on RC1
Java version: 1.8.0_352, vendor: Private Build Private build? What's that? Gary On Thu, Dec 8, 2022, 08:19 Alex Herbert wrote: > Hi Gary, > > I tried with the latest git master for numbers, rng and lang. The > updated spdx-maven-plugin is not compatible with java 8. I get the > following error: > > [ERROR] Failed to execute goal > org.spdx:spdx-maven-plugin:0.6.3:createSPDX (build-spdx) on project > commons-lang3: Execution build-spd > x of goal org.spdx:spdx-maven-plugin:0.6.3:createSPDX failed: An API > incompatibility was encountered while executing org.spdx:spdx-ma > ven-plugin:0.6.3:createSPDX: java.lang.UnsupportedClassVersionError: > org/spdx/spdxRdfStore/RdfStore has been compiled by a more recen > t version of the Java Runtime (class file version 55.0), this version > of the Java Runtime only recognizes class file versions up to 5 > 2.0 > > mvn -v > Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63) > Maven home: /usr/local/apache-maven-3 > Java version: 1.8.0_352, vendor: Private Build, runtime: > /usr/lib/jvm/java-8-openjdk-amd64/jre > Default locale: en_GB, platform encoding: UTF-8 > OS name: "linux", version: "4.15.0-200-generic", arch: "amd64", family: > "unix" > > Note: I am not clear exactly what the issue is as it does not happen > in the first jar module of the rng project reactor. The first module > commons-rng-client-api has no dependencies and this builds ok. The > next module commons-rng-core only depends on the client-api. This also > builds. The reactor breaks on the simple module which depends on core > and the client-api. However in numbers the reactor breaks on the first > module commons-numbers-core. This has no runtime dependencies. So some > part of the spdx plugin is being invoked only in some modules that has > a class compiled for Java 11. > > Building under JDK 11 was fine for all 3 named projects. > > Note that numbers and rng previously had set to true > as the configuration in CP 54 broke the build. I changed to false and > the multi-module build was fine. > > mvn -v > Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63) > Maven home: /usr/local/apache-maven-3 > Java version: 11.0.17, vendor: Ubuntu, runtime: > /usr/lib/jvm/java-11-openjdk-amd64 > Default locale: en_GB, platform encoding: UTF-8 > OS name: "linux", version: "4.15.0-200-generic", arch: "amd64", family: > "unix" > > So cyclonedx is fixed, but spdx is now not Java 8 compatible. > > Alex > > On Wed, 7 Dec 2022 at 19:50, Gary Gregory wrote: > > > > We made some enhancements since Apache Commons Parent 54 was released, > > so I would like to release Apache Commons Parent 55. > > > > This is the parent POM for Apache Commons, it doesn't contain Java > > code, and therefore no JApiCmp API compatibility check or report on > > the site. > > > > Apache Commons Parent 55 RC1 is available for review here: > > https://dist.apache.org/repos/dist/dev/commons/commons-parent/55-RC1 > > (svn revision 58537) > > > > The Git tag commons-parent-55-RC1 commit for this RC is > > 1a8382d227787216d76c1fea62b641158d0a265e which you can browse here: > > > https://gitbox.apache.org/repos/asf?p=commons-parent.git;a=commit;h=1a8382d227787216d76c1fea62b641158d0a265e > > You may checkout this tag using: > > git clone https://gitbox.apache.org/repos/asf/commons-parent.git > > --branch commons-parent-55-RC1 commons-parent-55-RC1 > > > > Maven artifacts are here: > > > https://repository.apache.org/content/repositories/orgapachecommons-1611/org/apache/commons/commons-parent/55/ > > > > These are the artifacts and their hashes: > > > > #Release SHA-512s > > #Wed Dec 07 14:37:02 EST 2022 > > > commons-parent-55-bom.json=e96e4d8f44b900ae5b12abbf81c1fa9a5c28e13c0767290e85c0f9e0486c9b3d2f6dac6ba8f4ca3f25c00716b5b6c180f16e0cfa17a51b1fd3c63c57f13deded > > > commons-parent-55-bom.xml=11bdf25c251b8b99f5684740e05fa08e8ad01dddeb6544327083696a578bc48785a8d27d03cd7b1ce8f3ace8f4e1b60d32819e4a3b6bc1ed775be5d549e32d33 > > > commons-parent-55-site.xml=735ffceca46a0574d430b4e1213a2462b9475143c0788913312b8af117eaf3b7c02a075aaf6d9b30d2560822339651cb511b838f6c9f2bced46de1fc1227c5ff > > > commons-parent-55-src.tar.gz=1a0307090faca60eaf8a034201521262828c283c8e51dd92a1add0adf48bb55898e0d990daa407648e7b65d6e85a7629ecfb30f4195fbc47d6bf0d14e9664254 > > > commons-parent-55-src.zip=13c5158f0957853e1df39aa5aa03180b404caa727fef276c969bc811de1e6b3b5465341d544869b338597805b085c21fee63b3d2f6f42dd93dd297fe5e6c8cda > > > org.apache.commons_commons-parent-55.spdx.json=14f27b64c60287116e84e2ae9b4d66017260287962c29baef621e9e2b06c06578768453a05bafa90cbe1aa2fe04e248aaedf9b64e8683c658452dedd798e8538 > > > > I have tested this with 'mvn clean install' using: > > > > Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63) > > Maven home: /usr/local/Cellar/maven/3.8.6/libexec > > Java version: 1.8.0_352, vendor: Homebrew, runtime: > > /usr/local/Cellar/openjdk@8 > /1.8.0+352/libexec/openjdk.jdk/Contents/Home/jre > > Default locale: en_US, plat
Re: [VOTE][LAZY] Release Apache Commons Parent 55 based on RC1
On Thu, 8 Dec 2022 at 18:18, Gary Gregory wrote: > > Java version: 1.8.0_352, vendor: Private Build > > Private build? What's that? I did not notice that. It is strange. I believe this is the version installed by my package manager on Ubuntu: $ java -version openjdk version "1.8.0_352" OpenJDK Runtime Environment (build 1.8.0_352-8u352-ga-1~18.04-b08) OpenJDK 64-Bit Server VM (build 25.352-b08, mixed mode) $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.6 LTS Release:18.04 Codename: bionic I'll try on my MacBook as it has a different java 8. Otherwise I will try to download a different java 8 for this linux box. Alex - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [VOTE][LAZY] Release Apache Commons Parent 55 based on RC1
I can confirm JDK 8 on my macbook is OK for rng, numbers and lang. Tried 55-SNAPSHOT from git master and also the tagged 55 RC1 (double checking). Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f) Maven home: /usr/local/apache-maven-3.6.3 Java version: 1.8.0_301, vendor: Oracle Corporation, runtime: /Library/Java/JavaVirtualMachines/jdk1.8.0_301.jdk/Contents/Home/jre Default locale: en_US, platform encoding: UTF-8 OS name: "mac os x", version: "10.16", arch: "x86_64", family: "mac" I'll investigate a bit more tomorrow why the JDK 8 build on my other machine is loading a Java 11 class. I may have some problem with the maven cache and the jars that are loaded. Alex On Thu, 8 Dec 2022 at 18:30, Alex Herbert wrote: > > On Thu, 8 Dec 2022 at 18:18, Gary Gregory wrote: > > > > Java version: 1.8.0_352, vendor: Private Build > > > > Private build? What's that? > > I did not notice that. It is strange. > > I believe this is the version installed by my package manager on Ubuntu: > > $ java -version > openjdk version "1.8.0_352" > OpenJDK Runtime Environment (build 1.8.0_352-8u352-ga-1~18.04-b08) > OpenJDK 64-Bit Server VM (build 25.352-b08, mixed mode) > > $ lsb_release -a > No LSB modules are available. > Distributor ID: Ubuntu > Description:Ubuntu 18.04.6 LTS > Release:18.04 > Codename: bionic > > I'll try on my MacBook as it has a different java 8. > > Otherwise I will try to download a different java 8 for this linux box. > > Alex - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [VOTE][LAZY] Release Apache Commons Parent 55 based on RC1
Thanks for the update Alex! Gary On Thu, Dec 8, 2022, 15:11 Alex Herbert wrote: > I can confirm JDK 8 on my macbook is OK for rng, numbers and lang. > > Tried 55-SNAPSHOT from git master and also the tagged 55 RC1 (double > checking). > > Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f) > Maven home: /usr/local/apache-maven-3.6.3 > Java version: 1.8.0_301, vendor: Oracle Corporation, runtime: > /Library/Java/JavaVirtualMachines/jdk1.8.0_301.jdk/Contents/Home/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "mac os x", version: "10.16", arch: "x86_64", family: "mac" > > I'll investigate a bit more tomorrow why the JDK 8 build on my other > machine is loading a Java 11 class. I may have some problem with the > maven cache and the jars that are loaded. > > Alex > > On Thu, 8 Dec 2022 at 18:30, Alex Herbert > wrote: > > > > On Thu, 8 Dec 2022 at 18:18, Gary Gregory > wrote: > > > > > > Java version: 1.8.0_352, vendor: Private Build > > > > > > Private build? What's that? > > > > I did not notice that. It is strange. > > > > I believe this is the version installed by my package manager on Ubuntu: > > > > $ java -version > > openjdk version "1.8.0_352" > > OpenJDK Runtime Environment (build 1.8.0_352-8u352-ga-1~18.04-b08) > > OpenJDK 64-Bit Server VM (build 25.352-b08, mixed mode) > > > > $ lsb_release -a > > No LSB modules are available. > > Distributor ID: Ubuntu > > Description:Ubuntu 18.04.6 LTS > > Release:18.04 > > Codename: bionic > > > > I'll try on my MacBook as it has a different java 8. > > > > Otherwise I will try to download a different java 8 for this linux box. > > > > Alex > > - > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
