Hi, Thanks for the link Hervé. That is an interesting initiative, I was not aware of it.
Please write down your opinion on toolchains in the JIRA issue I created, to establish new and updated instructions for our release build process https://issues.apache.org/jira/browse/MNGSITE-419 I'd like for us to decide whether it is OK to build components, that require Java 7, using Java 8 during a release or not. There is already a step in our release instructions that covers checking Javadoc. You should build the site with reporting turned on. That's what I did and that's when I realized that the Javadoc for the components was not compatible with Java 8. So it was detected before I cut the release. This and the fact that the component requires Java 7 made me decide to use toolchains for the build. -- Dennis Lundberg Den lör 1 aug. 2020 kl 08:28 skrev Hervé BOUTEMY <[email protected]>: > ok, I see: it will be tricky to reproduce... > I fear I won't be able to publish to "Reproducible Central" > https://github.com/jvm-repo-rebuild/reproducible-central > > for future releases, I think we should avoid such toolchain usage > It means that before doing a release, checking if javadoc can be built > should also be done, to avoid discovering issues during the release > > Regards, > > Hervé > > Le vendredi 31 juillet 2020, 08:42:26 CEST Dennis Lundberg a écrit : > > Thanks Hervé, > > > > The build was done using AdoptOpenJdk 8 update 242, but using toolchains. > > Failed Javadoc was one of the reasons for using toolchains, there were > just > > soo many errors. The toolchain itself used Java 7 update 79 from Oracle, > so > > the bytecode should be different if you don't use toolchains. > > > > You can see more details about my build process and problems in this JIRA > > issue: > > https://issues.apache.org/jira/browse/MNGSITE-419 > > > > -- > > Dennis Lundberg > > > > Den tors 30 juli 2020 kl 22:36 skrev Hervé BOUTEMY < > [email protected]>: > > > +1 > > > > > > trying to check reproducible builds, found that reference build was > done > > > with > > > JDK 8 on Windows > > > But I got 2 issues to reproduce: > > > 1. javadoc fails with JDK 8 > > > 2. your bytecode is different from mine > > > > > > what detailed distribution of JDK did you use, please? Mine is > > > AdoptOpenJDK > > > 1.8.0_202 > > > > > > Regards, > > > > > > Hervé > > > > > > Le vendredi 24 juillet 2020, 16:08:10 CEST Dennis Lundberg a écrit : > > > > Hi, > > > > > > > > We solved 12 > > > > > > > issues: > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12342 > > > > > > > 756&styleName=Text&projectId=12317922&Create=Create&atl_token=A5KQ-2QAV-T4 > > > JA> > > > > -FDED_7bf996098e890abc72bf3628a70b9090574f431d_lin > > > > > > > > There are still a couple of issues left in > > > > > > > JIRA: > > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AN > > > > > > > D%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20maven-shared-u > > > ti> > > > > ls%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC > > > > > > > > Staging > > > > > > > repo: > > > https://repository.apache.org/content/repositories/maven-1598/https:// > > > > > > > repository.apache.org/service/local/repositories/maven-1598/content/org/ap > > > ac > > > > > > > he/maven/shared/maven-shared-utils/3.3.3/maven-shared-utils-3.3.3-source-r > > > el> > > > > ease.zip > > > > > > > > Source release checksum(s): > > > > > > > maven-shared-utils-3.3.3-source-release.zip sha512: > > > > 6085d3bb3d065efaca7ed43f7342c2b71c624235ff38cd1410a06a4c915e39a13cb00e65e8 > > > c0> > > > > cd7203dc5b2d1deeb392eaab2aa0a43bfadb7c9d4286a2b473bc > > > > > > > > Staging > > > > > > > site: > > > https://maven.apache.org/components/shared-archives/maven-shared-utils > > > > > > > -LATEST/ > > > > > > > > Guide to testing staged > > > > > > > releases: > > > https://maven.apache.org/guides/development/guide-testing-releases. > > > > > > > html > > > > > > > > Vote open for at least 72 hours. > > > > > > > > [ ] +1 > > > > [ ] +0 > > > > [ ] -1 > > > > > > > > As some of you might have noticed we ended up with version 3.3.3 > instead > > > > > > of > > > > > > > the planned 3.3.1. I had some issues with the release process and > burned > > > > > > 2 > > > > > > > releases. I will address that in a JIRA issue shortly. Please let me > > > > know > > > > if I have missed anything. > > > > > > > > -- > > > > Dennis Lundberg > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
