releasing maven-javadoc-plugin
I would like to release Apache parent POM this WE (then Maven parent POMs), with plugin versions that support Reproducible Builds The last plugin to upgrade is maven-javadoc-plugin: Reproducible Builds for that plugin is ok (MJAVADOC-627), but there are 4 issues open affected to the future version and assigned: https://issues.apache.org/jira/projects/MJAVADOC/versions/12345698 Should I just change the target version? Regards, Hervé - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Defining EoL for Older Maven Versions
Chiming in late since I remember we discussed this before. Here is my view. All releases beyond the most recent one are essentially end of lifed. We never backport, we have no explicit support and whenever we fix something it goes into the next release. That is what we concluded last time and that is the reason why the download page only offers the latest version. Anything else is misleading our users with some sort of support or guarantee that things continue to work and are tested when really they are not. Of course we make a best effort to keep things smooth ... but thats really where it ends. Manfred Karl Heinz Marbaise wrote on 2019-12-16 12:57 (GMT -08:00): > On 15.12.19 12:14, Elliotte Rusty Harold wrote: >> Tentative +1. >> >> Is there any reason we would ever backport a fix to 3.0 or 3.2? E.g. >> this was the last release to support Java 1.6. > > Unfortunately my crystal ball is under repair...I can't see into the > future... > > I would say if we a really bad security issue would could decide to do a > backport for older releases...But based on the history I know and can > read through the mailing archives it has not happened yet... > > > >> >> Or would we simply tell users to upgrade to 3.6.3? >> >> >> On Sat, Dec 14, 2019 at 6:31 AM Karl Heinz Marbaise >> wrote: >>> >>> Hi, >>> >>> based on the history we have defined Maven 2.X EoL five years after the >>> last release...[1] >>> >>> Based on that I would suggest to define End Of Life for the following >>> Maven versions cause their release date is also five years ago... >>> >>> >>> Maven 3.0.5...3.2.5 included. >>> >>> We have never backported some things in the last five year... >>> >>> WDYT? >>> >>> Kind regards >>> Karl Heinz Marbaise >>> >>> >>> [1]: https://maven.apache.org/docs/history.html#Maven_2 >>> >>> - >>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >>> For additional commands, e-mail: dev-h...@maven.apache.org > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Defining EoL for Older Maven Versions
On 15.12.19 12:14, Elliotte Rusty Harold wrote: Tentative +1. Is there any reason we would ever backport a fix to 3.0 or 3.2? E.g. this was the last release to support Java 1.6. Unfortunately my crystal ball is under repair...I can't see into the future... I would say if we a really bad security issue would could decide to do a backport for older releases...But based on the history I know and can read through the mailing archives it has not happened yet... Or would we simply tell users to upgrade to 3.6.3? On Sat, Dec 14, 2019 at 6:31 AM Karl Heinz Marbaise wrote: Hi, based on the history we have defined Maven 2.X EoL five years after the last release...[1] Based on that I would suggest to define End Of Life for the following Maven versions cause their release date is also five years ago... Maven 3.0.5...3.2.5 included. We have never backported some things in the last five year... WDYT? Kind regards Karl Heinz Marbaise [1]: https://maven.apache.org/docs/history.html#Maven_2 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Source Plugin version 3.2.1
for those interested, I add the "Reproducible Builds (free) Bounty" :) instructions: - use JDK 8 on an Unix (and please share if you find a trick to build on Windows, geting the same result) - please install locally maven-buildinfo-plugin https://github.com/apache/maven-studies/tree/maven-buildinfo-plugin - build with "mvn -Papache-release,run-its -Dgpg.skip verify buildinfo:save" - check the content of target/buildinfo against reference in attachment If you don't want to install maven-buildinfo-plugin, you can check the output checksums by hand, there are only 3 files to check in such a simple mono-module project: maven-source-plugin-3.2.1.jar, maven-source-plugin-3.2.1-source-release.zip and maven-source-plugin-3.2.1-sources.jar Regards, Hervé Le lundi 16 décembre 2019, 19:37:00 CET Hervé BOUTEMY a écrit : > Hi, > > We solved 2 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317924 > rsion=12346480=Text > > Staging repo: > https://repository.apache.org/content/repositories/maven-1545/ > https://repository.apache.org/content/repositories/maven-1545/org/apache/mav > en/plugins/maven-source-plugin/3.2.1/maven-source-plugin-3.2.1-source-releas > e.zip > > Source release checksum(s): > maven-source-plugin-3.2.1-source-release.zip sha512: > 4d7252839cc74dae8100a47adadbe6fc2c8f4d57e930fa695e4e6c75a8571b1246a63aa25de > 0cf2d73601e599faea2a31be43b1fe442e36d463702d885ccf8b7 > > Staging site: > https://maven.apache.org/plugins-archives/maven-source-plugin-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 > > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org buildinfo.version=1.0-SNAPSHOT name=Apache Maven Source Plugin group-id=org.apache.maven.plugins artifact-id=maven-source-plugin version=3.2.1 # source information # TBD source.* artifact, url should be parameters source.scm.uri=scm:git:https://gitbox.apache.org/repos/asf/maven-source-plugin.git source.scm.tag=maven-source-plugin-3.2.1 # build instructions build-tool=mvn # effective build environment information java.version=1.8.0_161 java.vendor=Oracle Corporation os.name=Linux # Maven rebuild instructions and effective environment mvn.rebuild-args=-DskipTests verify mvn.version=Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f) mvn.minimum.version=3.0 # output outputs.0.filename=maven-source-plugin-3.2.1.jar outputs.0.length=32159 outputs.0.checksums.sha512=afd93bc84239e5e6e725ee7aea79b3e3e7fb2003861dcb955d3687993085da6130a695689cd25fd824cab153ef08eebddb2bed31685d3bd458a8a0de8d66de07 outputs.1.filename=maven-source-plugin-3.2.1-source-release.zip outputs.1.length=204286 outputs.1.checksums.sha512=4d7252839cc74dae8100a47adadbe6fc2c8f4d57e930fa695e4e6c75a8571b1246a63aa25de0cf2d73601e599faea2a31be43b1fe442e36d463702d885ccf8b7 outputs.2.filename=maven-source-plugin-3.2.1-sources.jar outputs.2.length=23814 outputs.2.checksums.sha512=29549f3a61227c37d5207fc3eafa542a243b8a6a9778fae4e5a5eec57e7f0e6b79bfb421feca6ab162ea60dedc6ac0b72fa3e7b4d64de71f5796c020b0807929 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[VOTE] Release Apache Maven Source Plugin version 3.2.1
Hi, We solved 2 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317924=12346480=Text Staging repo: https://repository.apache.org/content/repositories/maven-1545/ https://repository.apache.org/content/repositories/maven-1545/org/apache/maven/plugins/maven-source-plugin/3.2.1/maven-source-plugin-3.2.1-source-release.zip Source release checksum(s): maven-source-plugin-3.2.1-source-release.zip sha512: 4d7252839cc74dae8100a47adadbe6fc2c8f4d57e930fa695e4e6c75a8571b1246a63aa25de0cf2d73601e599faea2a31be43b1fe442e36d463702d885ccf8b7 Staging site: https://maven.apache.org/plugins-archives/maven-source-plugin-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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[ANN] Apache Maven Release Plugin 3.0.0-M1 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Release Plugin, version 3.0.0-M1. This plugin is used to release a project with Maven, saving a lot of repetitive, manual work. Releasing a project is made in two steps: prepare and perform. https://maven.apache.org/plugins/maven-release-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-release-plugin 3.0.0-M1 You can download the appropriate sources etc. from the download page: https://maven.apache.org/plugins/maven-release-plugin/download.cgi Release Notes - Maven Release Plugin - Version 3.0.0-M1 ** Bug * [MRELEASE-229] - release:rollback is missing remove tag implementation * [MRELEASE-601] - The Maven 2 release plugin modifies CDATA elements in pom.xml files. * [MRELEASE-694] - -SNAPSHOT is unexpectedly appended to version in branched pom.xml * [MRELEASE-908] - Git HTTP authentication failing if there are spaces in the password * [MRELEASE-928] - exposing the password for SCM URL if build failed to commit files to SCM * [MRELEASE-947] - Wiki page URL for maven-release-plugin is wrong - post Codehaus termination * [MRELEASE-964] - Error injecting: org.apache.maven.shared.release.phase.RewritePomsForReleasePhase * [MRELEASE-966] - release plugin does not respect "mvn -f" * [MRELEASE-968] - Maven release plugin missing plexus-cipher dependency * [MRELEASE-975] - NPE when using an unknown project versionpolicy id * [MRELEASE-997] - Unable to release:perform on windows if a file name contains spaces on windows * [MRELEASE-1009] - Compilation failure when using Java 10 * [MRELEASE-1034] - Remove SCM tag blocks rollback in some situations ** New Feature * [MRELEASE-956] - Release Strategy Interface * [MRELEASE-980] - Provide the ability to control commit messages * [MRELEASE-985] - Override SNAPSHOT dependencies from command line * [MRELEASE-998] - Add ability to create custom phases * [MRELEASE-1029] - update project.build.outputTimestamp property on prepare * [MRELEASE-1031] - display release phases to give insight on what's going on during release ** Improvement * [MRELEASE-703] - [PATCH] Migration from obsolete plexus-maven-plugin to plexus-containers-component-metadata * [MRELEASE-873] - Remove possibly confusing non-standard goals from example * [MRELEASE-896] - Disable by default and deprecate useReleaseProfile parameter * [MRELEASE-909] - Add workItem/task support for scm deliver * [MRELEASE-958] - Using three digit version number (semver) * [MRELEASE-976] - release:branch should also support project version policies * [MRELEASE-977] - release:branch should prompt for branch name if none is given * [MRELEASE-979] - Support NamingPolicies to manage Branch and Tag names * [MRELEASE-992] - Deprecated maven flag --no-plugin-updates shows warnings in the console output * [MRELEASE-993] - Use shallow checkout per default (git scm) * [MRELEASE-994] - Drop Maven2 support * [MRELEASE-1005] - Extract ResourceGenerator from ReleasePhase * [MRELEASE-1007] - Rework usage workingDirectory and commonBasedir * [MRELEASE-1023] - Minor code cleanups * [MRELEASE-1032] - add https://m.a.o/xsd/maven-4.0.0.xsd schema instead of http://m.a.o/maven-v4_0_0.xsd ** Task * [MRELEASE-356] - Deprecate the automated release profile * [MRELEASE-990] - switch to Git * [MRELEASE-1027] - New Release * [MRELEASE-1033] - Site: Dead link to wiki ** Dependency upgrade * [MRELEASE-952] - Replace JDom as XML transformer * [MRELEASE-1010] - Upgrade maven-plugins parent to version 32 * [MRELEASE-1024] - Upgrade to SCM 1.11.2 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
