Re: [VOTE] Release Apache Maven Shade Plugin version 3.2.4
+1 On Sun, 24 May 2020 at 01:38, Hervé BOUTEMY wrote: > Hi, > > We solved 4 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317921=12348077=Text > > Staging repo: > https://repository.apache.org/content/repositories/maven-1578/ > > https://repository.apache.org/content/repositories/maven-1578/org/apache/maven/plugins/maven-shade-plugin/3.2.4/maven-shade-plugin-3.2.4-source-release.zip > > Source release checksum(s): > maven-shade-plugin-3.2.4-source-release.zip sha512: > 9c0b09724c9cc0e27251ca7949203d14b83a6cb898daeab64291d39123964b9f5243e9529694622a53499c96db223307be04a89fbe45371fd61535e3b0a5fc5f > > Staging site: > https://maven.apache.org/plugins-archives/maven-shade-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 > > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
PR spam
Hi First I'm not against PR and people asking review. But for obvious changes, we can probably avoid PR (ie some spam especially when people tag you in the description of a PR). We have a long history about commit-then-review so let's keep this. Such change don't really need a PR https://github.com/apache/maven-site-plugin/pull/26/files I received around 15 emails for this from github and gitbox (as I was tagged in the description). So please create PR only for complicated change. Upgrade of a dependency is NOT a complicated change (except if it breaks backward compat and btw most of the time there is a Jira for this which generate even more emails). I'm just asking to reduce the level of emails we received as at the end the result is people don't really look at notifications... cheers -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: [DISCUSS] checking reproducible builds
makes sense to me.
Robert
On 30-5-2020 22:56:19, Hervé BOUTEMY wrote:
any objection that I create a new maven-artifact-plugin Git repository
initialized with current maven-buildinfo-plugin Git history?
Regards,
Hervé
Le mercredi 27 mai 2020, 19:26:55 CEST Robert Scholte a écrit :
> maven-studies are just a sandbox, experimental code. Once it has a good
> shape, it can be promoted to a separate project. So no, we're not going to
> release the maven-buildinfo-plugin.
>
> Robert
> On 26-5-2020 23:17:29, Konrad Windszus wrote:
> As creating a new maven-artifact-plugin will probably take some time, maybe
> it would be possible to push a release build of
> https://github.com/apache/maven-studies/tree/maven-buildinfo-plugin to
> Maven Central. Or is there already a rough schedule for coming up with the
> new maven-artifact-plugin?
>
> Thanks,
> Konrad
>
> On 2020/03/08 20:04:56, "Robert Scholte" wrote:
> > I'm thinking of maven-artifact-plugin, having goals related to artifacts.
> > That implies that the save goal should be renamed.
> > A couple of goals of the maven-dependency-plugin are actually more
> > artifact-related are might be worth moving.
> >
> > Robert
> >
> > On 8-3-2020 13:44:07, Michael Osipov wrote:
> >
> > Am 2020-03-08 um 12:48 schrieb Hervé BOUTEMY:
> > > Le dimanche 8 mars 2020, 00:31:07 CET Michael Osipov a écrit :
> > >> Am 2020-03-07 um 19:04 schrieb Hervé BOUTEMY:
> > >>> Le samedi 7 mars 2020, 17:39:20 CET Michael Osipov a écrit :
> > This is expected because I am on 1.8.0_242. I don't have Java 7
> > installed anymore on the server.
> > >>>
> > >>> for the discussion I wanted us to have, just being able to test and
> > >>> see
> > >>> how we detect issues, this is perfect, isn't it?
> > >>
> > >> This is really nice. Here is the diffoscope output:
> > > you're discovering the wonders of diffoscope :)
> > >
> > >>> --- maven-site-plugin-3.9.0.jar
> > >>> +++ reference/maven-site-plugin-3.9.0.jar
> > >>> ├── zipinfo {}
> > >>> │ @@ -1,8 +1,8 @@
> > >
> > > [...]
> > >
> > >>> META-INF/MANIFEST.MF
> > >>> │ @@ -1,10 +1,10 @@
> > >>> │ Manifest-Version: 1.0
> > >>> │ +Implementation-Vendor: The Apache Software Foundation^M
> > >>> │ Implementation-Title: Apache Maven Site Plugin
> > >>> │ Implementation-Version: 3.9.0
> > >>> │ +Build-Jdk-Spec: 1.7^M
> > >>> │ Specification-Vendor: The Apache Software Foundation
> > >>> │ -Specification-Title: Apache Maven Site Plugin^M
> > >>> │ -Build-Jdk-Spec: 1.8^M
> > >>> │ Created-By: Maven Jar Plugin 3.2.0
> > >>> │ +Specification-Title: Apache Maven Site Plugin^M
> > >>> │ Specification-Version: 3.9
> > >>> │ -Implementation-Vendor: The Apache Software Foundation^M
> > >>
> > >> I wonder where the CRs code from...this could be the default
> > >> serialization format on every platform.
> > >
> > > FYI I don't have such CRs in output on my Linux box
> >
> > This cannot be. See
> > https://github.com/AdoptOpenJDK/openjdk-jdk11u/blob/master/src/java.base/s
> > hare/classes/java/util/jar/Manifest.java and search for \r\n. Old Sun code
> > uses *always* CRLF. Plase recheck on your side and run a hexdump on the
> > Manifest file.
> >
> > >>> how did you find the experience? any improvement proposal?
> > >>> and any idea on where to put this goal in the future?
> > >>
> > >> There is room for improvement when I quickly read the code. I will
> > >> write
> > >> separately on this.
> > >
> > > sure, code can be improved: don't hesitate
> > > but I was not asking yet for code improvement (I'm confident, it will
> > > happen) but *experience* improvement
> > >
> > >> I'd leave as a plugin for now.
> > >
> > > you mean a separate plugin? same "buildinfo" name as current? "save"
> > > goal
> > > name?
> >
> > OK, let's talk about experience:
> >
> > * buildinfo may be changed to broader name, e.g.,
> > maven-reproducibility-plugin. Explanain follows
> > * 'save' does too much. It should save only and not compare. Save should
> > either run at initialize or at build-resources phase, imho
> > * Add a 'compare' goal, not phase bound. It performs the actual
> > comparsion.
> >
> > Strictly speaking if the plugin is called buildinfo it should handle the
> > buildinfo files only.
> >
> > >> At least in 3.7.x.
> > >
> > > 3.7.x as Maven 3.7.x?
> > > does that mean that you think it should be one day integrated into Maven
> > > core? what's the rationale?
> >
> > Not really, but if this happens, not before 4.x. I don't have any
> > rationale or entry point for this yet.
> >
> > Michael
> >
> >
> > -
> > 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
Re: next level of compatibility (was Re: [maven-site] branch master updated: few precisions)
Le mardi 26 mai 2020, 00:05:39 CEST Robert Scholte a écrit : > I missed the proposal for the version. I saw 3.2.5 and that can't be > correct, hence I tried to explain what the correct version should be. So > correct minimum version will be one of: 3.0, 3.1.0, 3.2.1, 3.3.1, 3.5.0 > This is the version we should compile with, our integration tests use the > latest bugfix for all. > > Just like the discussions around what the minimum Java version should be, > the same counts for the minimum Maven version. > > What is the benefit for version X? (Keep in mind, that every individual > plugin may choose a different minimum in case a specific change/feature is > required) 3.1.0 is very clear to me: switch to eclipse aether (package > change) and JSR330 support for plugins. All others contain (close to) no > changes to the API, so there's no real gain. > > By using higher versions of Maven you might force people to upgrade Maven or > stick to old plugins in case they can't upgrade. I don't think it should be > our plugins to enforce a higher version of Maven. Hence I don't see any > reason to require 3.5.0 or 3.6.0. > > I think it is pretty impressive that we can say that our plugins still > support a wide range of Maven versions. > > So my vote will be 3.1.0 ok for me Regards, Hervé > > Robert > > On 25-5-2020 22:53:47, Olivier Lamy wrote: > @All > Can we update the compatibility plan document saying we support from 3.5.4 > and 3.6.3. > plugins will use API from 3.5.4 and can use java8 from now (June 2020) . > As 3.7.0 is on his way (soon) supporting 3 series seems enough. (with 3.7.0 > using java8) > @Robert > As you didn't answer, I wonder if you still have strong opinions? > > On Sun, 24 May 2020 at 18:46, Michael Osipov wrote: > > Am 2020-05-24 um 10:41 schrieb Olivier Lamy: > > > On Sat, 23 May 2020 at 21:33, Robert Scholte > > > > wrote: > > >> As discussed before: compatibility should either be 3.3.1 (since 3.3.0 > > >> didn't make it) or 3.5.0, we should not include the (highest) bugfix > > >> version. > > > > > > Great this means we can can rid of this hackhish refection stuff for > > > aether... > > > > > > you mean we should support 3.3.1 3.3.3 and 3.3.9? > > > by support I mean fixing security issues. > > > so in this case what happen in case of a security issue for 3.3.1 do we > > > have a to release 3.3.1.1 3.3.3.1 3.3.9.1 > > > Not sure I understand what we mean with support? > > > anyway if we say all plugins must be at least 3.3.1 it's good progress > > > > I think we have discussed this before as I have raised this at least > > once this one. The upshot is that we try to support (in terms of API and > > ABI) in Plugins and Components a huge variety of Maven versions, but > > only the last stable minor branch of Maven receives fixes. > > -- > Olivier Lamy > http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [DISCUSS] checking reproducible builds
any objection that I create a new maven-artifact-plugin Git repository
initialized with current maven-buildinfo-plugin Git history?
Regards,
Hervé
Le mercredi 27 mai 2020, 19:26:55 CEST Robert Scholte a écrit :
> maven-studies are just a sandbox, experimental code. Once it has a good
> shape, it can be promoted to a separate project. So no, we're not going to
> release the maven-buildinfo-plugin.
>
> Robert
> On 26-5-2020 23:17:29, Konrad Windszus wrote:
> As creating a new maven-artifact-plugin will probably take some time, maybe
> it would be possible to push a release build of
> https://github.com/apache/maven-studies/tree/maven-buildinfo-plugin to
> Maven Central. Or is there already a rough schedule for coming up with the
> new maven-artifact-plugin?
>
> Thanks,
> Konrad
>
> On 2020/03/08 20:04:56, "Robert Scholte" wrote:
> > I'm thinking of maven-artifact-plugin, having goals related to artifacts.
> > That implies that the save goal should be renamed.
> > A couple of goals of the maven-dependency-plugin are actually more
> > artifact-related are might be worth moving.
> >
> > Robert
> >
> > On 8-3-2020 13:44:07, Michael Osipov wrote:
> >
> > Am 2020-03-08 um 12:48 schrieb Hervé BOUTEMY:
> > > Le dimanche 8 mars 2020, 00:31:07 CET Michael Osipov a écrit :
> > >> Am 2020-03-07 um 19:04 schrieb Hervé BOUTEMY:
> > >>> Le samedi 7 mars 2020, 17:39:20 CET Michael Osipov a écrit :
> > This is expected because I am on 1.8.0_242. I don't have Java 7
> > installed anymore on the server.
> > >>>
> > >>> for the discussion I wanted us to have, just being able to test and
> > >>> see
> > >>> how we detect issues, this is perfect, isn't it?
> > >>
> > >> This is really nice. Here is the diffoscope output:
> > > you're discovering the wonders of diffoscope :)
> > >
> > >>> --- maven-site-plugin-3.9.0.jar
> > >>> +++ reference/maven-site-plugin-3.9.0.jar
> > >>> ├── zipinfo {}
> > >>> │ @@ -1,8 +1,8 @@
> > >
> > > [...]
> > >
> > >>> META-INF/MANIFEST.MF
> > >>> │ @@ -1,10 +1,10 @@
> > >>> │ Manifest-Version: 1.0
> > >>> │ +Implementation-Vendor: The Apache Software Foundation^M
> > >>> │ Implementation-Title: Apache Maven Site Plugin
> > >>> │ Implementation-Version: 3.9.0
> > >>> │ +Build-Jdk-Spec: 1.7^M
> > >>> │ Specification-Vendor: The Apache Software Foundation
> > >>> │ -Specification-Title: Apache Maven Site Plugin^M
> > >>> │ -Build-Jdk-Spec: 1.8^M
> > >>> │ Created-By: Maven Jar Plugin 3.2.0
> > >>> │ +Specification-Title: Apache Maven Site Plugin^M
> > >>> │ Specification-Version: 3.9
> > >>> │ -Implementation-Vendor: The Apache Software Foundation^M
> > >>
> > >> I wonder where the CRs code from...this could be the default
> > >> serialization format on every platform.
> > >
> > > FYI I don't have such CRs in output on my Linux box
> >
> > This cannot be. See
> > https://github.com/AdoptOpenJDK/openjdk-jdk11u/blob/master/src/java.base/s
> > hare/classes/java/util/jar/Manifest.java and search for \r\n. Old Sun code
> > uses *always* CRLF. Plase recheck on your side and run a hexdump on the
> > Manifest file.
> >
> > >>> how did you find the experience? any improvement proposal?
> > >>> and any idea on where to put this goal in the future?
> > >>
> > >> There is room for improvement when I quickly read the code. I will
> > >> write
> > >> separately on this.
> > >
> > > sure, code can be improved: don't hesitate
> > > but I was not asking yet for code improvement (I'm confident, it will
> > > happen) but *experience* improvement
> > >
> > >> I'd leave as a plugin for now.
> > >
> > > you mean a separate plugin? same "buildinfo" name as current? "save"
> > > goal
> > > name?
> >
> > OK, let's talk about experience:
> >
> > * buildinfo may be changed to broader name, e.g.,
> > maven-reproducibility-plugin. Explanain follows
> > * 'save' does too much. It should save only and not compare. Save should
> > either run at initialize or at build-resources phase, imho
> > * Add a 'compare' goal, not phase bound. It performs the actual
> > comparsion.
> >
> > Strictly speaking if the plugin is called buildinfo it should handle the
> > buildinfo files only.
> >
> > >> At least in 3.7.x.
> > >
> > > 3.7.x as Maven 3.7.x?
> > > does that mean that you think it should be one day integrated into Maven
> > > core? what's the rationale?
> >
> > Not really, but if this happens, not before 4.x. I don't have any
> > rationale or entry point for this yet.
> >
> > Michael
> >
> >
> > -
> > 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:
[VOTE] Release Maven Resolver Ant Tasks version 1.2.1
Hi, We solved 6 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=12348151 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOLVER%20AND%20component%20%3D%20%22ant%20tasks%22%20AND%20resolution%20%3D%20Unresolved%20 Staging repo: https://repository.apache.org/content/repositories/maven-1583/ https://repository.apache.org/content/repositories/maven-1583/org/apache/maven/resolver/maven-resolver-ant-tasks/1.2.1/maven-resolver-ant-tasks-1.2.1-source-release.zip Source release checksum(s): maven-resolver-ant-tasks-1.2.1-source-release.zip sha512: 746c4377e3923c071d8ed8117cc2f8e9303e325551f81040e7cb0bb5eae1cc7c604ae21e2c88496bb8b0f9919a1a121aaabcaa2aef64805b8e1a223f76fab07c Staging site: https://maven.apache.org/resolver-archives/resolver-ant-tasks-LATEST/ Guide to testing staged releases: https://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Maven Parents - apache-release profile
apache-release profile is configured in Apache parent [1], then inherited in every Maven parent POM the only question I can see currently is if overriding the inherited config makes sense, or even eventually cause some sort of conflict (because IIUC the style of profile activation configuration with maven-release-plugin changed over time) But i don't see any question regarding activating the profile in more parent POMs Regards, Hervé [1] https://github.com/apache/maven-apache-parent/blob/apache-23/pom.xml#L226 Le vendredi 29 mai 2020, 17:59:24 CEST Karl Heinz Marbaise a écrit : > Hi, > > I have observed that we have differernt usage of release profiles. > > In maven-plugins parent we have the configuration > > apache-release,run-its > whereas we have in maven-skins: > > -Papache-release,run-its > > and the maven-parent itself has a configuration: > > apache-release > > which brings me to the question: > > If I corretly see it at the moment the "apache-release" profile is > needed in the apache-parent to activate the signing of the artifacts. > > So this brings me to the question: > > Shouldn't that been activated in all parents? (of course only > maven-parent) ? > > WDYT ? > > Kind regards > Karl Heinz Marbaise > > > - > 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 Shade Plugin version 3.2.4
+1 On 23-5-2020 17:38:38, Hervé BOUTEMY wrote: Hi, We solved 4 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317921=12348077=Text Staging repo: https://repository.apache.org/content/repositories/maven-1578/ https://repository.apache.org/content/repositories/maven-1578/org/apache/maven/plugins/maven-shade-plugin/3.2.4/maven-shade-plugin-3.2.4-source-release.zip Source release checksum(s): maven-shade-plugin-3.2.4-source-release.zip sha512: 9c0b09724c9cc0e27251ca7949203d14b83a6cb898daeab64291d39123964b9f5243e9529694622a53499c96db223307be04a89fbe45371fd61535e3b0a5fc5f Staging site: https://maven.apache.org/plugins-archives/maven-shade-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
Re: [VOTE] Release Apache Maven Shade Plugin version 3.2.4
here is my +1 more votes needed, please Regards, Hervé Le samedi 23 mai 2020, 17:38:26 CEST Hervé BOUTEMY a écrit : > Hi, > > We solved 4 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317921 > rsion=12348077=Text > > Staging repo: > https://repository.apache.org/content/repositories/maven-1578/ > https://repository.apache.org/content/repositories/maven-1578/org/apache/mav > en/plugins/maven-shade-plugin/3.2.4/maven-shade-plugin-3.2.4-source-release. > zip > > Source release checksum(s): > maven-shade-plugin-3.2.4-source-release.zip sha512: > 9c0b09724c9cc0e27251ca7949203d14b83a6cb898daeab64291d39123964b9f5243e952969 > 4622a53499c96db223307be04a89fbe45371fd61535e3b0a5fc5f > > Staging site: > https://maven.apache.org/plugins-archives/maven-shade-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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[GitHub] [maven-site] asfgit closed pull request #168: [MNGSITE-412] Add Reposilite to the list of available repository managers
asfgit closed pull request #168: URL: https://github.com/apache/maven-site/pull/168 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[GitHub] [maven-site] dzikoysk commented on pull request #168: [MNGSITE-412] Add Reposilite to the list of available repository managers
dzikoysk commented on pull request #168: URL: https://github.com/apache/maven-site/pull/168#issuecomment-636315538 Any thoughts on that? :) This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[VOTE] Release Apache Maven Wrapper Plugin version 3.0.1
Hi, I'd like to do a bootstrap release of the maven-wrapper-plugin, in order to configure it in the next maven-core. We solved 1 issue: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12323721=12348346=Text There are no issues in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MWRAPPER%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC Staging repo: https://repository.apache.org/service/local/repositories/maven-1584/ https://repository.apache.org/service/local/repositories/maven-1584/content/org/apache/maven/plugins/maven-wrapper-plugin/3.0.1/maven-wrapper-plugin-3.0.1-source-release.zip (note: there are some issues with https://repository.apache.org/ : you cannot browse through the content, but you can download the zip ) Source release checksum(s): maven-wrapper-plugin-3.0.1-source-release.zip sha512: 04084e8806af4507996ce7d9caafc1a9ff2c9e278ba1c0f41552edb6516d75f1685177130c76c04c262376437d96be3083c2b46309c482ab07b74785c35dafcb Staging site: https://maven.apache.org/plugins-archives/maven-wrapper-plugin-LATEST/ Guide to testing staged releases: As this is a special bootstrapping release, the following instructions are a proper way of testing: - clone/download+unpack current master branch of Apache Maven core ( https://github.com/apache/maven ) (this will make all apache-maven-wrapper distributions available in your local repository) - run 'mvn -Dmaven.repo.local=/temp/wrapper-itrepo install' - download+unpack sources from maven-wrapper-plugin (see above) - run 'mvn -Dmaven.repo.local=/temp/wrapper-itrepo install' - go to the root of any Maven project - run 'mvn -Dmaven.repo.local=/temp/wrapper-itrepo wrapper:wrapper -DwrapperVersion=3.7.0-SNAPSHOT' with optional extra arguments NOTE: be aware of the difference between maven-wrapper and the maven-wrapper-plugin. The maven-wrapper-plugin only downloads and unpacks the maven wrapper scripts. The content of the maven-wrapper scripts are not part of the plugin, hence not part of this release. Adjustments to that content belong to Maven core https://maven.apache.org/guides/development/guide-testing-releases.html Vote open for at least 72 hours. [ ] +1 [ ] +0 [ ] -1
[VOTE] [CANCELLED] Release Apache Maven Wrapper Plugin version 3.0.0
Plugin is using an old parent, so the code in not reproducible Cancelling the vote. Robert On 29-5-2020 14:09:38, Robert Scholte wrote: Hi, I'd like to do a bootstrap release of the maven-wrapper-plugin, in order to configure it in the next maven-core. There are no issues in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MWRAPPER%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC Staging repo: https://repository.apache.org/service/local/repositories/maven-1580/ https://repository.apache.org/service/local/repositories/maven-1580/content/org/apache/maven/plugins/maven-wrapper-plugin/3.0.0/maven-wrapper-plugin-3.0.0-source-release.zip Source release checksum(s): maven-wrapper-plugin-3.0.0-source-release.zip sha512: 0a62e2aab0cc1de834439b13d69c9a2210ac60f2c7a959975520f5a42f63f2fe7064c865afb89323960519778c1b35621ac66247fcb2cc861564900b1c31727f Staging site: https://maven.apache.org/plugins-archives/maven-wrapper-plugin-LATEST/ Guide to testing staged releases: As this is a special bootstrapping release, the following instructions are a proper way of testing: - clone/download+unpack current master branch of Apache Maven core ( https://github.com/apache/maven ) (this will make all apache-maven-wrapper distributions available in your local repository) - run 'mvn -Dmaven.repo.local=/temp/wrapper-itrepo install' - download+unpack sources from maven-wrapper-plugin (see above) - run 'mvn -Dmaven.repo.local=/temp/wrapper-itrepo install' - go to the root of any Maven project - run 'mvn -Dmaven.repo.local=/temp/wrapper-itrepo wrapper:wrapper -DwrapperVersion=3.7.0-SNAPSHOT' with optional extra arguments NOTE: be aware of the difference between maven-wrapper and the maven-wrapper-plugin. The maven-wrapper-plugin only downloads and unpacks the maven wrapper scripts. The content of the maven-wrapper scripts are not part of the plugin, hence not part of this release. Adjustments to that content belong to Maven core https://maven.apache.org/guides/development/guide-testing-releases.html Vote open for at least 72 hours. [ ] +1 [ ] +0 [ ] -1
