Re: Maven Wrapper
Hi all, would it also be possible for some sort of official statement that when copying the maven wrapper scripts (For Apache Projects), this doesn't explicitly have to be mentioned in the NOTICE or LICENSE file? I know that this could ease quite some +1/-1 discussions (especially on the incubator). Chris Am 13.02.20, 06:12 schrieb "James Gao" : With maven wrapper, most maven project could be build out of box iff jdk is installed, and the maven version used for build is locked by the project owner. So in run time, each version of wrapper should be able to integrate with as many as versions of maven. And so does the wrapper plugin, but plugin is seldom used by by developers. What the wrapper depends on are two very stable things: a) how maven is distributed (a zip/tgz archive and its internal file structures), b) how maven is executed without wrapper (entry scripts, e.g. bin/mvn and bin/mvn.cmd) No matter how wrapper is distributed (via plugin or just copy from another project), the deployed wrapper based on previous dependents, will deploy a configurable version of maven to a personal location on the fly if needed, then executed the previous deployed maven, but will not update the deployed script itself. So although wrapper will be released with maven core, it still better not to lock the runtime version of maven. On Thu, Feb 13, 2020 at 4:24 AM Robert Scholte wrote: > well, with every release of Maven, some versions needed to be updated, see > the commit logs. > Also the release instructions show some relation with the Maven version. > > Based on that it looks like it should be part of core. > I've understood doing a release of is a bit problematic due to some > chicken-egg issue. > > However, I did start with the plugin and that one is now capable of > recognizing the runtime version of Maven, not hardcoded. > > So it depends, I just haven't figured it out yet. > On 12-2-2020 20:28:24, Enrico Olivelli wrote: > Il Mer 12 Feb 2020, 19:58 Robert Scholte ha scritto: > > > Hi, > > > > This month we've finished the incubator process to move to code from the > > maven wrapper to our project. > > > > Cool > > > > > Initially the idea was to move both the maven-wrapper and the > > takari-maven-plugin (which contains a wrapper goal) to our codebase, but > > due to conflicting licensing we only moved the maven-wrapper. > > > > Right now I've moved the code of the maven-wrapper to his own branch > under > > maven-studies. > > From here we can work on it. I think it makes sense to make it a module > of > > Maven core, but that's still a decision we need to make. > > > > Is it strictly dependent on a Maven version? I thought it was totally > independent. > Why not having a separate repository and release lifecycle? > > Enrico > > > > For the maven-wrapper-plugin a new repository has been created. And I've > > started with a clean branch, trying to set the base of this plugin. > > > > Both are open for further development, not just by me. > > > > So here are the 2 new git repositories: > > https://gitbox.apache.org/repos/asf/maven-wrapper-plugin.git > > (branch MWRAPPER-0_WIP) > > https://gitbox.apache.org/repos/asf/maven-studies.git (branch > > maven-wrapper) > > > > > > Enjoy, > > Robert >
Re: Maven Wrapper
With maven wrapper, most maven project could be build out of box iff jdk is installed, and the maven version used for build is locked by the project owner. So in run time, each version of wrapper should be able to integrate with as many as versions of maven. And so does the wrapper plugin, but plugin is seldom used by by developers. What the wrapper depends on are two very stable things: a) how maven is distributed (a zip/tgz archive and its internal file structures), b) how maven is executed without wrapper (entry scripts, e.g. bin/mvn and bin/mvn.cmd) No matter how wrapper is distributed (via plugin or just copy from another project), the deployed wrapper based on previous dependents, will deploy a configurable version of maven to a personal location on the fly if needed, then executed the previous deployed maven, but will not update the deployed script itself. So although wrapper will be released with maven core, it still better not to lock the runtime version of maven. On Thu, Feb 13, 2020 at 4:24 AM Robert Scholte wrote: > well, with every release of Maven, some versions needed to be updated, see > the commit logs. > Also the release instructions show some relation with the Maven version. > > Based on that it looks like it should be part of core. > I've understood doing a release of is a bit problematic due to some > chicken-egg issue. > > However, I did start with the plugin and that one is now capable of > recognizing the runtime version of Maven, not hardcoded. > > So it depends, I just haven't figured it out yet. > On 12-2-2020 20:28:24, Enrico Olivelli wrote: > Il Mer 12 Feb 2020, 19:58 Robert Scholte ha scritto: > > > Hi, > > > > This month we've finished the incubator process to move to code from the > > maven wrapper to our project. > > > > Cool > > > > > Initially the idea was to move both the maven-wrapper and the > > takari-maven-plugin (which contains a wrapper goal) to our codebase, but > > due to conflicting licensing we only moved the maven-wrapper. > > > > Right now I've moved the code of the maven-wrapper to his own branch > under > > maven-studies. > > From here we can work on it. I think it makes sense to make it a module > of > > Maven core, but that's still a decision we need to make. > > > > Is it strictly dependent on a Maven version? I thought it was totally > independent. > Why not having a separate repository and release lifecycle? > > Enrico > > > > For the maven-wrapper-plugin a new repository has been created. And I've > > started with a clean branch, trying to set the base of this plugin. > > > > Both are open for further development, not just by me. > > > > So here are the 2 new git repositories: > > https://gitbox.apache.org/repos/asf/maven-wrapper-plugin.git > > (branch MWRAPPER-0_WIP) > > https://gitbox.apache.org/repos/asf/maven-studies.git (branch > > maven-wrapper) > > > > > > Enjoy, > > Robert >
Re: Maven Wrapper
well, with every release of Maven, some versions needed to be updated, see the commit logs. Also the release instructions show some relation with the Maven version. Based on that it looks like it should be part of core. I've understood doing a release of is a bit problematic due to some chicken-egg issue. However, I did start with the plugin and that one is now capable of recognizing the runtime version of Maven, not hardcoded. So it depends, I just haven't figured it out yet. On 12-2-2020 20:28:24, Enrico Olivelli wrote: Il Mer 12 Feb 2020, 19:58 Robert Scholte ha scritto: > Hi, > > This month we've finished the incubator process to move to code from the > maven wrapper to our project. > Cool > > Initially the idea was to move both the maven-wrapper and the > takari-maven-plugin (which contains a wrapper goal) to our codebase, but > due to conflicting licensing we only moved the maven-wrapper. > > Right now I've moved the code of the maven-wrapper to his own branch under > maven-studies. > From here we can work on it. I think it makes sense to make it a module of > Maven core, but that's still a decision we need to make. > Is it strictly dependent on a Maven version? I thought it was totally independent. Why not having a separate repository and release lifecycle? Enrico > For the maven-wrapper-plugin a new repository has been created. And I've > started with a clean branch, trying to set the base of this plugin. > > Both are open for further development, not just by me. > > So here are the 2 new git repositories: > https://gitbox.apache.org/repos/asf/maven-wrapper-plugin.git > (branch MWRAPPER-0_WIP) > https://gitbox.apache.org/repos/asf/maven-studies.git (branch > maven-wrapper) > > > Enjoy, > Robert
Re: Maven Wrapper
Il Mer 12 Feb 2020, 19:58 Robert Scholte ha scritto: > Hi, > > This month we've finished the incubator process to move to code from the > maven wrapper to our project. > Cool > > Initially the idea was to move both the maven-wrapper and the > takari-maven-plugin (which contains a wrapper goal) to our codebase, but > due to conflicting licensing we only moved the maven-wrapper. > > Right now I've moved the code of the maven-wrapper to his own branch under > maven-studies. > From here we can work on it. I think it makes sense to make it a module of > Maven core, but that's still a decision we need to make. > Is it strictly dependent on a Maven version? I thought it was totally independent. Why not having a separate repository and release lifecycle? Enrico > For the maven-wrapper-plugin a new repository has been created. And I've > started with a clean branch, trying to set the base of this plugin. > > Both are open for further development, not just by me. > > So here are the 2 new git repositories: > https://gitbox.apache.org/repos/asf/maven-wrapper-plugin.git > (branch MWRAPPER-0_WIP) > https://gitbox.apache.org/repos/asf/maven-studies.git (branch > maven-wrapper) > > > Enjoy, > Robert
Maven Wrapper
Hi, This month we've finished the incubator process to move to code from the maven wrapper to our project. Initially the idea was to move both the maven-wrapper and the takari-maven-plugin (which contains a wrapper goal) to our codebase, but due to conflicting licensing we only moved the maven-wrapper. Right now I've moved the code of the maven-wrapper to his own branch under maven-studies. >From here we can work on it. I think it makes sense to make it a module of >Maven core, but that's still a decision we need to make. For the maven-wrapper-plugin a new repository has been created. And I've started with a clean branch, trying to set the base of this plugin. Both are open for further development, not just by me. So here are the 2 new git repositories: https://gitbox.apache.org/repos/asf/maven-wrapper-plugin.git (branch MWRAPPER-0_WIP) https://gitbox.apache.org/repos/asf/maven-studies.git (branch maven-wrapper) Enjoy, Robert
Re: [maven-resolver] DefaultDependencyCollector not collecting direct provided dependencies
ProjectDependencyResolver does what I expect for provided dependencies [1].
With DefaultDependencyCollector, provided-scope dependencies of the
root node are not picked up, because the root node itself is a
dependency (with a scope), making the provided-scope dependencies
transitive ones.
With ProjectDependencyResolver, the root node is not a dependency. It
does not have a scope. Therefore provided-scope dependencies below the
root are direct dependencies.
Added a image to show the comparison [2]. Case closed.
[1]:
https://github.com/suztomo/maven-provided-scope/blob/master/src/test/java/suztomo/TestProjectDependencyResolver.java#L136
[2]:
https://github.com/suztomo/maven-provided-scope#comparison-between-defaultdependencycollector-and-projectdependencyresolver
On Mon, Feb 10, 2020 at 3:05 PM Tomo Suzuki wrote:
>
> I created a test case to demonstrate this behavior:
> https://github.com/suztomo/maven-provided-scope/blob/master/src/test/java/suztomo/AppTest.java#L72
>
> On Fri, Feb 7, 2020 at 5:36 PM Tomo Suzuki wrote:
> >
> > Hi Maven developers,
> >
> > I find DefaultDependencyCollector is not getting "direct" and
> > "provided" dependencies by default. Is this expected behavior?
> >
> > Background:
> > We use maven-resolver in our Java code. We create
> > RepositorySystemSesison through MavenRepositorySystemUtils.newSession
> > [1]. We use the session and DefaultDependencyCollector through
> > RepositorySystem.collectDependencies [2] to get the dependency graph
> > of a Maven artifact.
> >
> > Problem:
> > The dependency graph from RepositorySystem.collectDependencies does
> > not have direct provided dependencies. I expect provided dependencies
> > should be included in the graph when they are direct dependencies.
> >
> > Analysis:
> > - MavenRepositorySystemUtils.newSession [3] creates
> > ScopedDependencySelector("test", "provided")
> > - ScopeDependencySelector.deriveChildSelector [4] creates clone of
> > itself with transitive=true. When transitive=true, it does not select
> > "provided" dependency.
> > - DefaultDependencyCollector.collectDependencies [5] always call
> > deriveChildSelector before using the selector from the session.
> > - Therefore, ScopeDependencySelector always has transitive=true ( to
> > exclude provided dependencies) when it's used with
> > DefaultDependencyCollector.
> >
> > [1]:
> > https://github.com/GoogleCloudPlatform/cloud-opensource-java/blob/50da79355e042c5ff14ec72230cc6edbddcf8436/dependencies/src/main/java/com/google/cloud/tools/opensource/dependencies/RepositoryUtility.java#L112
> > [2]:
> > https://github.com/GoogleCloudPlatform/cloud-opensource-java/blob/50da79355e042c5ff14ec72230cc6edbddcf8436/dependencies/src/main/java/com/google/cloud/tools/opensource/dependencies/DependencyGraphBuilder.java#L179
> > [3]:
> > https://github.com/apache/maven/blob/master/maven-resolver-provider/src/main/java/org/apache/maven/repository/internal/MavenRepositorySystemUtils.java#L102
> > [4]:
> > https://github.com/apache/maven-resolver/blob/47edcfe69c4e52ced4cb93d65b7348b5645cdd68/maven-resolver-util/src/main/java/org/eclipse/aether/util/graph/selector/ScopeDependencySelector.java#L119
> > [5]:
> > https://github.com/apache/maven-resolver/blob/18dd2b5cde851256a9f44db25097efee0691d6b4/maven-resolver-impl/src/main/java/org/eclipse/aether/internal/impl/collect/DefaultDependencyCollector.java#L255
> >
> > --
> > Regards,
> > Tomo
>
>
>
> --
> Regards,
> Tomo
--
Regards,
Tomo
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Re: [RESULT] [VOTE] Release Apache Maven Shade Plugin version 3.2.2
I meant Release Apache Maven Shade Plugin version 3.2.2... Le mercredi 12 février 2020, 12:42:55 CET Hervé BOUTEMY a écrit : > Hi, > > The vote has passed with the following result: > > +1 : Mark Struberg, Romain Manni-Bucau, Enrico Olivelli, Hervé Boutemy, > Olivier Lamy, Arnaud Héritier > > PMC quorum: reached > > I will promote the artifacts to the central repo. > > > > - > 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
[RESULT] [VOTE] Release Maven Parent POMs version 34 
Hi, The vote has passed with the following result: +1 : Mark Struberg, Romain Manni-Bucau, Enrico Olivelli, Hervé Boutemy, Olivier Lamy, Arnaud Héritier PMC quorum: reached I will promote the artifacts to the central repo. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Checkstyle Plugin version 3.1.1
+1 On Wed, 12 Feb 2020 at 7:03 pm, Arnaud Héritier wrote: > +1 > > On Tue, Feb 11, 2020 at 10:12 PM Romain Manni-Bucau > > wrote: > > > +1 (non binding) > > > > Le mar. 11 févr. 2020 à 20:04, Stephane Nicoll < > stephane.nic...@gmail.com> > > a écrit : > > > > > +1 (non-binding anymore). > > > > > > Cheers, > > > S. > > > > > > On Tue, Feb 11, 2020 at 1:47 PM Enrico Olivelli > > > wrote: > > > > > > > Thank you Hervé > > > > > > > > I need two more binding +1 please > > > > > > > > Enrico > > > > > > > > Il Sab 8 Feb 2020, 21:43 Hervé BOUTEMY ha > > > scritto: > > > > > > > > > +1 > > > > > > > > > > I was able to rebuild (with JDK 8) .jar, -sources.jar and > > > > > -source-release.zip > > > > > archives from source-release archive, deleting first DEPENDENCIES, > > > > LICENSE > > > > > and > > > > > NOTICE > > > > > > > > > > Regards, > > > > > > > > > > Hervé > > > > > > > > > > Le samedi 8 février 2020, 10:11:29 CET Enrico Olivelli a écrit : > > > > > > Hi, > > > > > > > > > > > > We solved 7 issues: > > > > > > > > > > > > > > > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317223&ve > > > > > > rsion=12345558 > > > > > > > > > > > > In particular this release allows users to upgrade to latest and > > > > > > greatest checkstyle version 8.29. > > > > > > > > > > > > There are still a couple of issues left in JIRA: > > > > > > > > > > > > > > > > > > > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MCHECKSTYLE%20AND > > > > > > > > > > > > > > > > > > > > > %20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC%2C%20updated > > > > > > %20DESC > > > > > > > > > > > > Staging repo: > > > > > > https://repository.apache.org/content/repositories/maven-1549/ > > > > > > > > > > > > > > > > > > > > > https://repository.apache.org/content/repositories/maven-1549/org/apache/mav > > > > > > > > > > > > > > > > > > > > > en/plugins/maven-checkstyle-plugin/3.1.1/maven-checkstyle-plugin-3.1.1-sourc > > > > > > e-release.zip > > > > > > > > > > > > Source release checksum(s): > > > > > > maven-checkstyle-plugin-3.1.1-source-release.zip sha512: > > > > > > > > > > > > > > > > > > > > > 753015ff86d22d840ffbcab81b8d5170e6db7a9dc21963686faa2a54d3232964dace2f7316ff > > > > > > 84a27e06700cf32a57088d9bee5d51463d0f0b5c01e7f87a1268 > > > > > > > > > > > > Staging site: > > > > > > > > > > > > > > > > > > > > > https://maven.apache.org/plugins-archives/maven-checkstyle-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 > > > > > > > > > > > > Enrico Olivelli > > > > > > > > > > > > > > - > > > > > > 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 > > > > > > > > > > > > > > > > > > > > > > -- > - > Arnaud Héritier > http://aheritier.net > Mail/GTalk: aheritier AT gmail DOT com > Twitter/Skype : aheritier > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: [VOTE] Release Apache Maven Parent POMs version 34
+1 On Thu, Jan 30, 2020 at 8:49 AM Enrico Olivelli wrote: > +1 (non binding) > > Interesting https://issues.apache.org/jira/browse/MPOM-223 Introduce > parent > for extensions ! > > Enrico > > Il giorno gio 30 gen 2020 alle ore 08:20 Karl Heinz Marbaise < > khmarba...@gmx.de> ha scritto: > > > Hi, > > +1 from me. > > > > Kind regards > > Karl Heinz Marbaise > > On 26.01.20 10:16, Hervé BOUTEMY wrote: > > > Hi, > > > > > > We solved 9 issues: > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250&version=12344077&styleName=Text > > > > > > Changes since the last release: > > > > > > https://github.com/apache/maven-parent/compare/maven-parent-33...maven-parent-34#diff > > > > > > There are still a couple of issues left in JIRA: > > > > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MPOM%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC > > > > > > Staging repo: > > > https://repository.apache.org/content/repositories/maven-1548/ > > > > > > https://repository.apache.org/content/repositories/maven-1548/org/apache/maven/maven-parent/34/maven-parent-34-source-release.zip > > > > > > Source release checksum(s): > > > maven-parent-34-source-release.zip sha512: > > > caf523e3def4d414985b3f96ec6939a43a96d977510001e08f23aa3b44dd182b92ec7557204de649e63d6a5bc926042f62fde83406cd428ca710d62af7151b7a > > > > > > Staging site: > > > https://maven.apache.org/pom-archives/maven-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 > > > > > -- - Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier
Re: [VOTE] Release Apache Maven PMD Plugin version 3.13.0
+1 On Sat, Feb 1, 2020 at 1:08 AM wrote: > +1 > > Regards, > > Hervé > > - Mail original - > De: "Karl Heinz Marbaise" > À: "Maven Developers List" , "Andreas Dangel" < > adan...@apache.org> > Envoyé: Lundi 27 Janvier 2020 10:49:32 > Objet: Re: [VOTE] Release Apache Maven PMD Plugin version 3.13.0 > > Hi, > > +1 from me. > > Kind regards > Karl Heinz Marbaise > On 25.01.20 12:04, Andreas Dangel wrote: > > Hi, > > > > We solved 12 issues: > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12345409&styleName=Text&projectId=12317621 > > > > There are still a couple of issues left in JIRA: > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MPMD%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC > > > > Staging repo: > > https://repository.apache.org/content/repositories/maven-1547/ > > > https://repository.apache.org/content/repositories/maven-1547/org/apache/maven/plugins/maven-pmd-plugin/3.13.0/maven-pmd-plugin-3.13.0-source-release.zip > > > > Source release checksum(s): > > maven-pmd-plugin-3.13.0-source-release.zip sha512: > > > 9b5238f49f5189a720d0f6b294bc2be715eddae51c84f3d498f091694cd98047eb548b09d705ac4823f2a8bd4716d6e48b77a650f35f15008ad12f2e8604 > > > > Staging site: > > https://maven.apache.org/plugins-archives/maven-pmd-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 > > -- - Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier
Re: [VOTE] Release Apache Maven Checkstyle Plugin version 3.1.1
+1 On Tue, Feb 11, 2020 at 10:12 PM Romain Manni-Bucau wrote: > +1 (non binding) > > Le mar. 11 févr. 2020 à 20:04, Stephane Nicoll > a écrit : > > > +1 (non-binding anymore). > > > > Cheers, > > S. > > > > On Tue, Feb 11, 2020 at 1:47 PM Enrico Olivelli > > wrote: > > > > > Thank you Hervé > > > > > > I need two more binding +1 please > > > > > > Enrico > > > > > > Il Sab 8 Feb 2020, 21:43 Hervé BOUTEMY ha > > scritto: > > > > > > > +1 > > > > > > > > I was able to rebuild (with JDK 8) .jar, -sources.jar and > > > > -source-release.zip > > > > archives from source-release archive, deleting first DEPENDENCIES, > > > LICENSE > > > > and > > > > NOTICE > > > > > > > > Regards, > > > > > > > > Hervé > > > > > > > > Le samedi 8 février 2020, 10:11:29 CET Enrico Olivelli a écrit : > > > > > Hi, > > > > > > > > > > We solved 7 issues: > > > > > > > > > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317223&ve > > > > > rsion=12345558 > > > > > > > > > > In particular this release allows users to upgrade to latest and > > > > > greatest checkstyle version 8.29. > > > > > > > > > > There are still a couple of issues left in JIRA: > > > > > > > > > > > > > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MCHECKSTYLE%20AND > > > > > > > > > > > > > > > %20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC%2C%20updated > > > > > %20DESC > > > > > > > > > > Staging repo: > > > > > https://repository.apache.org/content/repositories/maven-1549/ > > > > > > > > > > > > > > > https://repository.apache.org/content/repositories/maven-1549/org/apache/mav > > > > > > > > > > > > > > > en/plugins/maven-checkstyle-plugin/3.1.1/maven-checkstyle-plugin-3.1.1-sourc > > > > > e-release.zip > > > > > > > > > > Source release checksum(s): > > > > > maven-checkstyle-plugin-3.1.1-source-release.zip sha512: > > > > > > > > > > > > > > > 753015ff86d22d840ffbcab81b8d5170e6db7a9dc21963686faa2a54d3232964dace2f7316ff > > > > > 84a27e06700cf32a57088d9bee5d51463d0f0b5c01e7f87a1268 > > > > > > > > > > Staging site: > > > > > > > > > > > > > > > https://maven.apache.org/plugins-archives/maven-checkstyle-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 > > > > > > > > > > Enrico Olivelli > > > > > > > > > > > - > > > > > 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 > > > > > > > > > > > > > > -- - Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier
Re: [VOTE] Release Apache Maven Shade Plugin version 3.2.2
+1 On Wed, Feb 12, 2020 at 8:01 AM Olivier Lamy wrote: > +1 > > On Sun, 9 Feb 2020 at 19:25, Hervé BOUTEMY wrote: > > > Hi, > > > > We solved 28 issues: > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317921&version=1230&styleName=Text > > > > Staging repo: > > https://repository.apache.org/content/repositories/maven-1550/ > > > > > https://repository.apache.org/content/repositories/maven-1550/org/apache/maven/plugins/maven-shade-plugin/3.2.2/maven-shade-plugin-3.2.2-source-release.zip > > > > Source release checksum(s): > > maven-shade-plugin-3.2.2-source-release.zip sha512: > > > c9ecdf2003c5c983005e62ad4f0bcae408c25583496d32fc7c7912ba34060048f541cea135c3d308146f39c0cb17795124cf9e1d50f42373c9456f47d2d61830 > > > > 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 > -- - Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier
