Re: [VOTE] Release Maven Resolver Ant Tasks 1.5.1
+1 On Tue, 21 May 2024 at 9:13 PM, Tamás Cservenák wrote: > Howdy, > > We solved 6 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=12353627 > > There are still some issues in JIRA: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOLVER%20AND%20status%20%3D%20Open%20AND%20component%20%3D%20%22Ant%20Tasks%22 > > Staging repository: > https://repository.apache.org/content/repositories/maven-2123/ > > Source release SHA512: > > fdeba5927b93693e8d926e9af442434634d4a8656c4392b36c2ab88e0c790304d1b8f49d576d7d6bdc4d8099a4d770b9212bbaf53bb61fe9a199e26d3d583a03 > > 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 >
Re: [VOTE] Release Apache Maven 4.0.0-beta-3
+1 On Thu, 23 May 2024 at 1:12 AM, Guillaume Nodet wrote: > This is a vote to release Apache Maven 4.0.0-beta-3, as I've cut another > release to fix blocking issues found in beta-2. > > > We solved 25 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12354634 > > There are still some issues in JIRA: > https://issues.apache.org/jira/projects/MNG/issues > > Release candidates: > https://dist.apache.org/repos/dist/dev/maven/maven-4/4.0.0-beta-3/ > > Staging repository: > https://repository.apache.org/content/repositories/maven-2126/ > > Source release SHA512: > - apache-maven-4.0.0-beta-3-src.zip > > 4125acba32218e341b34c1bbe7700f5aa71947fd1a6a5d418825822099800e3b798a5300eaf711e0709866b7e5fc6fee323515af18d8ab25d7eaac034d72b1c6 > - apache-maven-4.0.0-beta-3-src.tar.gz > > 8ca063a72fdacbcbe4afc33fc46e6c8920327092d11f3d8a77723ce995c3e24d1e8413cce3d5bc59a47657316834bfb9d4706d8bdffa5da5e147bcb404381808 > > Staging site: > https://maven.apache.org/ref/4-LATEST/ > > Guide to testing staged releases: > https://maven.apache.org/guides/development/guide-testing-releases.html > > The vote is open for at least 72 hours. > > [ ] +1 > [ ] +0 > [ ] -1 > > -- > Guillaume Nodet >
Re: [VOTE] Release Maven Fluido Skin version 2.0.0-M9
+1 On Mon, 20 May 2024 at 18:54, Michael Osipov wrote: > > Hi, > > we solved 5 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317926=12353690 > > There are still a couple of issues left in JIRA: > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSKINS%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20%22Fluido%20Skin%22 > > Staging repo: > https://repository.apache.org/content/repositories/maven-2122/ > https://repository.apache.org/content/repositories/maven-2122/org/apache/maven/skins/maven-fluido-skin/2.0.0-M9/maven-fluido-skin-2.0.0-M9-source-release.zip > > Source release checksum(s): > maven-fluido-skin-2.0.0-M9-source-release.zip > sha512: > 73c6ddaf32433d2f24b36f838979ad60ea2c0984521e8c71c28639a20c67131884afc14b5a319e07cfc3de80d818c03c0cc73b40f29de715c4966f633cf983e6 > > Staging site: > https://maven.apache.org/components/skins-archives/maven-fluido-skin-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 > - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Invoker Plugin version 3.7.0
+1 On Thu, 23 May 2024 at 8:05 AM, Slawomir Jaranowski wrote: > Hi, > > We solved 17 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317525=12354467 > > There are still a couple of issues left in JIRA: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MINVOKER%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC > > Staging repo: > https://repository.apache.org/content/repositories/maven-2128/ > > https://repository.apache.org/content/repositories/maven-2128/org/apache/maven/plugins/maven-invoker-plugin/3.7.0/maven-invoker-plugin-3.7.0-source-release.zip > > Source release checksum(s): > maven-invoker-plugin-3.7.0-source-release.zip - SHA-512 : > > f85e038b4b24e1f89940094d44059d0aacc9197975e0bf5b98bd616f649fd08f557c097dc72bd46866ba529499ade40f9400107200bd7461851a8f1205fae821 > > Staging site: > https://maven.apache.org/plugins-archives/maven-invoker-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 > > -- > Sławomir Jaranowski >
Re: [VOTE] Release Apache Maven 3.9.7
+1 On Wed, 22 May 2024 at 20:10, Tamás Cservenák wrote: > > Howdy, > > We solved 21 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12353964 > > There are still a couple of issues left in JIRA: > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20resolution%20%3D%20Unresolved > > Staging repo: > https://repository.apache.org/content/repositories/maven-2125/ > > Dev dist directory (binary bundles updated): > https://dist.apache.org/repos/dist/dev/maven/maven-3/3.9.7/ > > Source release checksums: > apache-maven-3.9.7-src.tar.gz.sha512 > a3c211ce683afbde9c4becf8b32397d14d3e7d8e8261094da037dcf27a697a93134440e055e7a9e7e26af2db543d4d9c4e7b0296560f5193df7ba90b9a68d1d1 > > apache-maven-3.9.7-src.zip.sha512 > cdd8249807e251d07c613a65120058993e47a4cbf7f6dbda8599c7ca7ab4ed3fedc727e651f43cba0e9b0d604055c1106c1243be64a1d52c5ddf72dbec5e65dc > > Staged site: > https://maven.apache.org/ref/3-LATEST/ > > Draft for release notes: > https://github.com/apache/maven-site/pull/521 > > Guide to testing staged releases: > http://maven.apache.org/guides/development/guide-testing-releases.html > > Vote open for 72h > > [ ] +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 Maven Indexer 7.1.3
+1 On Fri, 17 May 2024 at 5:10 PM, Tamás Cservenák wrote: > Howdy, > > We solved 8 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317523=12354090 > > There are still some issues in JIRA: > https://issues.apache.org/jira/projects/MINDEXER/issues > > Staging repository: > https://repository.apache.org/content/repositories/maven-2118/ > > Source release SHA512: > > 78ce43d62de64322110f22de896d14d89fa6d93815a24ca60cb7aa08895d0d672b24c8e567cd10fe2e62b9bfd266af8d03f450173c3035ffc202f7c0a441b4ca > > Staging site: > https://maven.apache.org/maven-indexer-archives/maven-indexer-LATEST/ > > Guide to testing staged releases: > https://maven.apache.org/guides/development/guide-testing-releases.html > > Vote open for 72 hours. > > [ ] +1 > [ ] +0 > [ ] -1 >
Re: [VOTE] Release Apache Maven Dependency Analyzer version 1.14.0
+1 On Mon, 13 May 2024 at 06:41, Slawomir Jaranowski wrote: > > Hi, > > We solved 10 issues: > https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317922%20AND%20fixVersion%20%3D%2012353840%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC > > There are still a couple of issues left in JIRA: > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20maven-dependency-analyzer > > Staging repo: > https://repository.apache.org/content/repositories/maven-2115/ > https://repository.apache.org/content/repositories/maven-2115/org/apache/maven/shared/maven-dependency-analyzer/1.14.0/maven-dependency-analyzer-1.14.0-source-release.zip > > Source release checksum(s): > maven-dependency-analyzer-1.14.0-source-release.zip - SHA-512 : > 177624ae1f2cff0a05bd694a70f7e139f7cad79db63287644dfbf307cc5be09624202f2ff00f16125926a4614553065603eb61143f690bf38e347ff6b2d00282 > > Staging site: > https://maven.apache.org/shared-archives/maven-dependency-analyzer-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 > > -- > Sławomir Jaranowski - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[ANN] Apache Maven Build cache extension
The Apache Maven team is pleased to announce the release of the Apache Maven Build cache extension, version 1.2.0 Build cache is an extension that makes large Maven builds more efficient. A combination of features achieves that: - Incremental builds work on the modified part of the project graph part only - Project state restoration (partial) avoids repeating expensive tasks like code generation - etc... More details available: https://maven.apache.org/extensions/maven-build-cache-extension/ You can look at the configuration to use it: https://maven.apache.org/extensions/maven-build-cache-extension/getting-started.html Release Notes - Maven Build Cache Extension - Version 1.2.0 ** Bug * [MBUILDCACHE-76] - pom project version change not detected * [MBUILDCACHE-79] - MBUILDCACHE-67 broke the partial restore process * [MBUILDCACHE-80] - Incremental builds with a higher goal than the highest cached goal is rebuilding the full project from scratch * [MBUILDCACHE-81] - Add an option to include project version as part of the cache hash key * [MBUILDCACHE-88] - Tests in failure when ran on jdk21 ** New Feature * [MBUILDCACHE-90] - Configuration option to make mandatory the use of the clean phase in order to cache the build result * [MBUILDCACHE-93] - Command line configuration to disable saving in cache ** Improvement * [MBUILDCACHE-71] - buildinfo.xml should be stored after storing the project's artifacts * [MBUILDCACHE-86] - Bugfix and enhancements with the restoration of outputs on disk Enjoy, -The Apache Maven team - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[RESULT] [VOTE] Apache Maven Build cache extension 1.2.0
Hi The vote has passed with the following result: +1 Romain, Kevin, Slawomir, Tamas, Olivier I will finish the release process. Cheers Olivier - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Apache Maven Build cache extension 1.2.0
I restored https://maven.apache.org/extensions-archives/maven-build-cache-extension-1.1.0/ Vote is almost closed now no real need to restore this as default. LOL I had to remember some svn commands I haven't used for ages On Sat, 11 May 2024 at 08:43, Olivier Lamy wrote: > > > On Fri, 10 May 2024 at 23:28, Brian Demers wrote: > >> FYI, It looks like the site was published ahead of the release: >> https://maven.apache.org/extensions/maven-build-cache-extension/ >> > > I'm not sure; it looks like there must be some configuration problems > somewhere. > the process is to commit site content to svn > https://svn.apache.org/repos/asf/maven/website/components/extensions-archives/maven-build-cache-extension-LATEST/ > which is automatic and configured in the om of the project. > And then copy this to > https://svn.apache.org/repos/asf/maven/website/components/extensions/ > which is supposed to serve the last release content. > but hey, "good" surprise, this is empty so now I'm lost as to > understand where the content of https://maven.apache.org/extensions/ is > coming from :) > it looks like because of this > https://svn.apache.org/repos/asf/maven/website/content/extensions/maven-build-cache-extension > sorry, I had no idea this was such a setup. They're totally different from > the rest and did not follow our documentation process. > I will try to restore the content later today. > BTW Good catch! > > > > >> >> >> [image: image.png] >> >> On Wed, May 8, 2024 at 8:43 PM Olivier Lamy wrote: >> >>> Hi, >>> Vote for release of Apache Maven Build cache extension 1.2.0 >>> We fixed 9 issues: >>> >>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12324820=12353957 >>> >>> Staging repo: >>> https://repository.apache.org/content/repositories/maven-2114/ >>> Staged sources dist: >>> >>> https://repository.apache.org/content/repositories/maven-2114/org/apache/maven/extensions/maven-build-cache-extension/1.2.0/maven-build-cache-extension-1.2.0-source-release.zip >>> >>> sha512: >>> bc1a4b84c4f21a73964d8f65c3d37e372dfa8fc6d64e13db3f2d7ff2111485b41eb6bd24872626597070fd28cdcb55e0702cf9a2f106bedc7ec1483fbcd2aeb2 >>> >>> Staged website: >>> >>> https://maven.apache.org/extensions-archives/maven-build-cache-extension-LATEST/ >>> >>> Vote open for 72h >>> [+1] >>> [0] >>> [-1] >>> >>> Cheers >>> Olivier >>> >>> - >>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >>> For additional commands, e-mail: dev-h...@maven.apache.org >>> >>>
Re: [VOTE] Apache Maven Build cache extension 1.2.0
+1 On Thu, 9 May 2024 at 10:43, Olivier Lamy wrote: > > Hi, > Vote for release of Apache Maven Build cache extension 1.2.0 > We fixed 9 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12324820=12353957 > > Staging repo: https://repository.apache.org/content/repositories/maven-2114/ > Staged sources dist: > https://repository.apache.org/content/repositories/maven-2114/org/apache/maven/extensions/maven-build-cache-extension/1.2.0/maven-build-cache-extension-1.2.0-source-release.zip > > sha512: > bc1a4b84c4f21a73964d8f65c3d37e372dfa8fc6d64e13db3f2d7ff2111485b41eb6bd24872626597070fd28cdcb55e0702cf9a2f106bedc7ec1483fbcd2aeb2 > > Staged website: > https://maven.apache.org/extensions-archives/maven-build-cache-extension-LATEST/ > > Vote open for 72h > [+1] > [0] > [-1] > > Cheers > Olivier - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Apache Maven Build cache extension 1.2.0
On Fri, 10 May 2024 at 23:28, Brian Demers wrote: > FYI, It looks like the site was published ahead of the release: > https://maven.apache.org/extensions/maven-build-cache-extension/ > I'm not sure; it looks like there must be some configuration problems somewhere. the process is to commit site content to svn https://svn.apache.org/repos/asf/maven/website/components/extensions-archives/maven-build-cache-extension-LATEST/ which is automatic and configured in the om of the project. And then copy this to https://svn.apache.org/repos/asf/maven/website/components/extensions/ which is supposed to serve the last release content. but hey, "good" surprise, this is empty so now I'm lost as to understand where the content of https://maven.apache.org/extensions/ is coming from :) it looks like because of this https://svn.apache.org/repos/asf/maven/website/content/extensions/maven-build-cache-extension sorry, I had no idea this was such a setup. They're totally different from the rest and did not follow our documentation process. I will try to restore the content later today. BTW Good catch! > > > [image: image.png] > > On Wed, May 8, 2024 at 8:43 PM Olivier Lamy wrote: > >> Hi, >> Vote for release of Apache Maven Build cache extension 1.2.0 >> We fixed 9 issues: >> >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12324820=12353957 >> >> Staging repo: >> https://repository.apache.org/content/repositories/maven-2114/ >> Staged sources dist: >> >> https://repository.apache.org/content/repositories/maven-2114/org/apache/maven/extensions/maven-build-cache-extension/1.2.0/maven-build-cache-extension-1.2.0-source-release.zip >> >> sha512: >> bc1a4b84c4f21a73964d8f65c3d37e372dfa8fc6d64e13db3f2d7ff2111485b41eb6bd24872626597070fd28cdcb55e0702cf9a2f106bedc7ec1483fbcd2aeb2 >> >> Staged website: >> >> https://maven.apache.org/extensions-archives/maven-build-cache-extension-LATEST/ >> >> Vote open for 72h >> [+1] >> [0] >> [-1] >> >> Cheers >> Olivier >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >> For additional commands, e-mail: dev-h...@maven.apache.org >> >>
[VOTE] Apache Maven Build cache extension 1.2.0
Hi, Vote for release of Apache Maven Build cache extension 1.2.0 We fixed 9 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12324820=12353957 Staging repo: https://repository.apache.org/content/repositories/maven-2114/ Staged sources dist: https://repository.apache.org/content/repositories/maven-2114/org/apache/maven/extensions/maven-build-cache-extension/1.2.0/maven-build-cache-extension-1.2.0-source-release.zip sha512: bc1a4b84c4f21a73964d8f65c3d37e372dfa8fc6d64e13db3f2d7ff2111485b41eb6bd24872626597070fd28cdcb55e0702cf9a2f106bedc7ec1483fbcd2aeb2 Staged website: https://maven.apache.org/extensions-archives/maven-build-cache-extension-LATEST/ Vote open for 72h [+1] [0] [-1] Cheers Olivier - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Invoker version 3.3.0
+1 On Wed, 8 May 2024 at 7:00 AM, Slawomir Jaranowski wrote: > Hi, > > We solved 12 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12351567 > > There are still a couple of issues left in JIRA: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20maven-invoker > > Staging repo: > https://repository.apache.org/content/repositories/maven-2113/ > > https://repository.apache.org/content/repositories/maven-2113/org/apache/maven/shared/maven-invoker/3.3.0/maven-invoker-3.3.0-source-release.zip > > Source release checksum(s): > maven-invoker-3.3.0-source-release.zip - SHA-512 : > > 746c8a1dd96c193690ae76f15198ab173767e1e9f5621697e6f6b4e207e698428c79f4c84f049ff216ca9e454ad3ffa2b80756a21c4d7cac577dc526083d86e3 > > Staging site: > https://maven.apache.org/shared-archives/maven-invoker-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 > > -- > Sławomir Jaranowski >
Re: Sisu Plexus release?
On Wed, 8 May 2024 at 17:04, Tamás Cservenák wrote: > > Howdy, > > Olivier, I find this quite interesting, that according to you doing an > Eclipse release (even M one) is "just push a few buttons and run > something for a minute". > On the other hand, on Slack you educate Christoph about the "Apache way". > Please calm down and remain respectful. As I said, I tried to search for any process or vote with the last release, and I could not find anything. That's why it's my conclusion. By the way, I cannot see anything non-respectful in the approach about trying to figure out how a major piece of our stack is managed. > > Your PR [1] has been reviewed by Sisu project lead (Stuart McCulloch) and > is merged. All is fine. > > The problem is in the "release must happen RIGHT NOW" stance of yours (for > whatever reason). > No Sisu committer will or can throw away everything they currently do (or > planned to do), just to make Sisu release happen, as you ask for it. > We are doing our best, and release for sure will happen soonish, as there > are several merged, but also several ongoing changes to be done yet (see > open PRs). > > [1] https://github.com/eclipse/sisu.plexus/pull/52 > > On Wed, May 8, 2024 at 7:55 AM Christoph Läubrich > wrote: > > > Hi Olivier, > > > > I'm not 100% sure about the sisu[1] problem at Eclipse BUT usually there > > is no need for a vote or similar but from tiem to time there is a > > release or progress review. If I look here > > https://projects.eclipse.org/projects/technology.sisu/who you have 100% > > commits over the last three month, so it would make sense that @Konrad > > Windszus or @cstamas simply start a committer vote to make you a > > committer of the project, after that I would (if Stuart is non > > responsive anymore) start a Project Lead election for either any of you, > > at that point you then can do what ever is required (even though any > > committer can technically perform a release or ask for a release review > > some actions might require a Project Lead approval e.g. pushing to > > central), if you have any questions regarding Eclipse process you can > > ask the Eclipse EMO (e...@eclipse.org added as CC). > > > > If you need any help I can offer to give some help from my experience in > > other Eclipse Projects, at a first glance looking at the release page[1] > > a release review seems overdue but I'm not an expert on this specific > > topic, it just wont hurt to schedule one just to be sure. > > > > HTH > > Christoph > > > > [1] https://projects.eclipse.org/projects/technology.sisu > > [2] https://projects.eclipse.org/projects/technology.sisu/governance > > > > Am 07.05.24 um 23:23 schrieb Olivier Lamy: > > > Hi, > > > Sure but as a long-term developer, I cannot release this plexus part > > anymore. > > > It used to be very easy to release this major part of the system (but > > > for some reason this has been moved somewhere else. not something to > > > discuss again, of course) > > > I have been asking sisu dev mailing list for a release, but no answer > > yet. > > > I have been looking at this project mailing list archive. > > > There is an email about a possible process > > > (https://www.eclipse.org/lists/sisu-dev/msg00116.html), but as far as > > > I can see, this 0.9.0.M2 release has been done without any voting > > > process etc. > > > So releasing looks to be only a matter of having a few minutes to run > > > m-release-p and publish. (being contributor to another Eclipse > > > project, I cannot see anything with vote mandatory). > > > > > > If it's easier we can certainly move this sisu plexus project back to > > > where it was few years ago under the groupId org.codehaus.plexus and > > > releasing will not be a problem for maven contributors. > > > > > > regards > > > Olivier > > > > > > > > > On Mon, 6 May 2024 at 20:16, Tamás Cservenák > > wrote: > > >> > > >> Btw, I feel really strange to have to explain to a long term maven > > >> contributor, that he can do maven release whenever he feels so > > >> > > >> T > > >> > > >> On Mon, May 6, 2024 at 11:59 AM Tamás Cservenák > > wrote: > > >> > > >>> Howdy, > > >>> > > >>> I think you reversed the question... 3.9.7 was done and ready to go > > until > > >>> you stepped in. > > >>> > > &g
Sisu Plexus release?
Hi, Sure but as a long-term developer, I cannot release this plexus part anymore. It used to be very easy to release this major part of the system (but for some reason this has been moved somewhere else. not something to discuss again, of course) I have been asking sisu dev mailing list for a release, but no answer yet. I have been looking at this project mailing list archive. There is an email about a possible process (https://www.eclipse.org/lists/sisu-dev/msg00116.html), but as far as I can see, this 0.9.0.M2 release has been done without any voting process etc. So releasing looks to be only a matter of having a few minutes to run m-release-p and publish. (being contributor to another Eclipse project, I cannot see anything with vote mandatory). If it's easier we can certainly move this sisu plexus project back to where it was few years ago under the groupId org.codehaus.plexus and releasing will not be a problem for maven contributors. regards Olivier On Mon, 6 May 2024 at 20:16, Tamás Cservenák wrote: > > Btw, I feel really strange to have to explain to a long term maven > contributor, that he can do maven release whenever he feels so > > T > > On Mon, May 6, 2024 at 11:59 AM Tamás Cservenák wrote: > > > Howdy, > > > > I think you reversed the question... 3.9.7 was done and ready to go until > > you stepped in. > > > > IMHO the real question is: > > Is your issue (using overloaded methods in mojo config) really so urgent > > to halt 3.9.7 release? > > What is the problem with doing 3.9.8 maybe even two weeks later? > > > > > > Thanks > > T > > > > On Mon, May 6, 2024 at 7:45 AM Olivier Lamy wrote: > > > >> Is 3.9.7 really so urgent? > >> Maybe we can wait a couple of days. > >> I have been asking the sisu dev mailing list for a release. > >> This should not be too long. > >> I can see you are in the committers list > >> (https://projects.eclipse.org/projects/technology.sisu/who) with > >> Konrad so maybe you can help to expedite this? > >> > >> regards > >> Olivier > >> > >> > >> On Sun, 5 May 2024 at 21:05, Tamás Cservenák wrote: > >> > > >> > Howdy, > >> > > >> > Maven 3.9.7 was ready to be released 3 days ago and contains multiple > >> fixes > >> > contributed by non committers. > >> > > >> > MNG-8116 was added 2 days ago. I really see no reason to be blocked, to > >> > "stop and wait" for a bugfix, as we can always spin 3.9.8. > >> > Releases are cheap, and can be done whenever we (anyone of us) feels > >> right > >> > to do so... > >> > > >> > 3.9.7 is not the "last Maven 3.9.x" or anything like that, to have a > >> "now > >> > or never" situation. Just spin 3.9.8 whenever you think is ready. > >> > > >> > My 5 cents > >> > T > >> > > >> > On Sun, May 5, 2024 at 2:14 AM Olivier Lamy wrote: > >> > > >> > > Hi > >> > > Can we please integrate > >> https://issues.apache.org/jira/browse/MNG-8116 > >> > > The fix is ready and really simple. > >> > > > >> > > thanks > >> > > Olivier > >> > > > >> > > On Wed, 24 Apr 2024 at 07:12, Tamás Cservenák > >> wrote: > >> > > > > >> > > > Howdy, > >> > > > > >> > > > This is just a short newsflash about upcoming planned releases > >> related to > >> > > > Maven. > >> > > > > >> > > > Recently we got a huge spike in plugin releases, with various fixes > >> and > >> > > > improvements. I will not enumerate all of them here, just use `mvn > >> > > > versions:display-plugin-updates` to pick them up ;) > >> > > > (and more plugins to come). > >> > > > > >> > > > What I do want to share is about our upcoming Maven releases... > >> > > > > >> > > > Maven 3.9.7 is nearing (read: coming soon), and will have an > >> important > >> > > > Resolver update and other important fixes. Most importantly, the > >> > > file-locks > >> > > > are getting nice improvement (feedback VERY welcome). > >> > > > > >> > > > Maven 3.9.7 issues: > >> > > > > >> > > > >> https://issues.apache.org/jira/issues/?jql=project%
Re: Quo Vadis Maven?
if you think it's urgent do whatever you want.. On Mon, 6 May 2024 at 20:01, Tamás Cservenák wrote: > > Howdy, > > I think you reversed the question... 3.9.7 was done and ready to go until > you stepped in. > > IMHO the real question is: > Is your issue (using overloaded methods in mojo config) really so urgent to > halt 3.9.7 release? > What is the problem with doing 3.9.8 maybe even two weeks later? > > > Thanks > T > > On Mon, May 6, 2024 at 7:45 AM Olivier Lamy wrote: > > > Is 3.9.7 really so urgent? > > Maybe we can wait a couple of days. > > I have been asking the sisu dev mailing list for a release. > > This should not be too long. > > I can see you are in the committers list > > (https://projects.eclipse.org/projects/technology.sisu/who) with > > Konrad so maybe you can help to expedite this? > > > > regards > > Olivier > > > > > > On Sun, 5 May 2024 at 21:05, Tamás Cservenák wrote: > > > > > > Howdy, > > > > > > Maven 3.9.7 was ready to be released 3 days ago and contains multiple > > fixes > > > contributed by non committers. > > > > > > MNG-8116 was added 2 days ago. I really see no reason to be blocked, to > > > "stop and wait" for a bugfix, as we can always spin 3.9.8. > > > Releases are cheap, and can be done whenever we (anyone of us) feels > > right > > > to do so... > > > > > > 3.9.7 is not the "last Maven 3.9.x" or anything like that, to have a "now > > > or never" situation. Just spin 3.9.8 whenever you think is ready. > > > > > > My 5 cents > > > T > > > > > > On Sun, May 5, 2024 at 2:14 AM Olivier Lamy wrote: > > > > > > > Hi > > > > Can we please integrate https://issues.apache.org/jira/browse/MNG-8116 > > > > The fix is ready and really simple. > > > > > > > > thanks > > > > Olivier > > > > > > > > On Wed, 24 Apr 2024 at 07:12, Tamás Cservenák > > wrote: > > > > > > > > > > Howdy, > > > > > > > > > > This is just a short newsflash about upcoming planned releases > > related to > > > > > Maven. > > > > > > > > > > Recently we got a huge spike in plugin releases, with various fixes > > and > > > > > improvements. I will not enumerate all of them here, just use `mvn > > > > > versions:display-plugin-updates` to pick them up ;) > > > > > (and more plugins to come). > > > > > > > > > > What I do want to share is about our upcoming Maven releases... > > > > > > > > > > Maven 3.9.7 is nearing (read: coming soon), and will have an > > important > > > > > Resolver update and other important fixes. Most importantly, the > > > > file-locks > > > > > are getting nice improvement (feedback VERY welcome). > > > > > > > > > > Maven 3.9.7 issues: > > > > > > > > > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%203.9.7 > > > > > > > > > > Resolver 1.9.19 issues (mostly bug fixes): > > > > > > > > > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOLVER%20AND%20fixVersion%20%3D%201.9.19 > > > > > > > > > > At the same time, we plan to release Maven Daemon (m39) as well, to > > have > > > > it > > > > > aligned with Maven 3,9,7: with many bug fixes and > > improvements/alignments > > > > > to "how Maven 3 behave". Our goal is to make the two (mvn and mvnd) > > > > > interchangeable on workstations. > > > > > > > > > > Next, Maven 4 is turning beta, so the next release will be beta1! And > > > > > again, same thing for Maven Damon (m40), we will have a release that > > will > > > > > include Maven 4 beta-1. > > > > > > > > > > Maven 4 beta-1 > > > > > > > > > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%204.0.0-beta-1 > > > > > > > > > > Resolver 2.0.0 (currently alpha-11, will become beta after Maven4 > > beta-1 > > > > > release): > > > > > > > > > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOLVER%20AND%20fixVersion%20%3D%202.0.0-alpha-11 > > > > > > > > > > Keep your eyes on our upcoming releases, > > > > > and have fun! > > > > > - The Apache Maven team > > > > > > > > - > > > > 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: Quo Vadis Maven?
Is 3.9.7 really so urgent? Maybe we can wait a couple of days. I have been asking the sisu dev mailing list for a release. This should not be too long. I can see you are in the committers list (https://projects.eclipse.org/projects/technology.sisu/who) with Konrad so maybe you can help to expedite this? regards Olivier On Sun, 5 May 2024 at 21:05, Tamás Cservenák wrote: > > Howdy, > > Maven 3.9.7 was ready to be released 3 days ago and contains multiple fixes > contributed by non committers. > > MNG-8116 was added 2 days ago. I really see no reason to be blocked, to > "stop and wait" for a bugfix, as we can always spin 3.9.8. > Releases are cheap, and can be done whenever we (anyone of us) feels right > to do so... > > 3.9.7 is not the "last Maven 3.9.x" or anything like that, to have a "now > or never" situation. Just spin 3.9.8 whenever you think is ready. > > My 5 cents > T > > On Sun, May 5, 2024 at 2:14 AM Olivier Lamy wrote: > > > Hi > > Can we please integrate https://issues.apache.org/jira/browse/MNG-8116 > > The fix is ready and really simple. > > > > thanks > > Olivier > > > > On Wed, 24 Apr 2024 at 07:12, Tamás Cservenák wrote: > > > > > > Howdy, > > > > > > This is just a short newsflash about upcoming planned releases related to > > > Maven. > > > > > > Recently we got a huge spike in plugin releases, with various fixes and > > > improvements. I will not enumerate all of them here, just use `mvn > > > versions:display-plugin-updates` to pick them up ;) > > > (and more plugins to come). > > > > > > What I do want to share is about our upcoming Maven releases... > > > > > > Maven 3.9.7 is nearing (read: coming soon), and will have an important > > > Resolver update and other important fixes. Most importantly, the > > file-locks > > > are getting nice improvement (feedback VERY welcome). > > > > > > Maven 3.9.7 issues: > > > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%203.9.7 > > > > > > Resolver 1.9.19 issues (mostly bug fixes): > > > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOLVER%20AND%20fixVersion%20%3D%201.9.19 > > > > > > At the same time, we plan to release Maven Daemon (m39) as well, to have > > it > > > aligned with Maven 3,9,7: with many bug fixes and improvements/alignments > > > to "how Maven 3 behave". Our goal is to make the two (mvn and mvnd) > > > interchangeable on workstations. > > > > > > Next, Maven 4 is turning beta, so the next release will be beta1! And > > > again, same thing for Maven Damon (m40), we will have a release that will > > > include Maven 4 beta-1. > > > > > > Maven 4 beta-1 > > > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%204.0.0-beta-1 > > > > > > Resolver 2.0.0 (currently alpha-11, will become beta after Maven4 beta-1 > > > release): > > > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOLVER%20AND%20fixVersion%20%3D%202.0.0-alpha-11 > > > > > > Keep your eyes on our upcoming releases, > > > and have fun! > > > - The Apache Maven team > > > > - > > 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 Maven Plugin Tools version 3.13.0
+1 On Fri, 3 May 2024 at 16:57, Michael Osipov wrote: > > Hi, > > we solved 5 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317820=12354458 > > There are still a couple of issues left in JIRA: > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MPLUGIN%20AND%20resolution%20%3D%20Unresolved > > Staging repo: > https://repository.apache.org/content/repositories/maven-2108/ > https://repository.apache.org/content/repositories/maven-2108/org/apache/maven/plugin-tools/maven-plugin-tools/3.13.0/maven-plugin-tools-3.13.0-source-release.zip > > Source release checksum(s): > maven-plugin-tools-3.13.0-source-release.zip > sha512: > a572bd12b252a6794051277050dc1f9750f60f6ab06f097b3a26acd5de35b4a99c2796eb36b4faac6a9bb98a0d21c6df4a5c61f8f766f60e6af524c9bcb3211d > > Staging site: > https://maven.apache.org/plugin-tools-archives/plugin-tools-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 > - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Quo Vadis Maven?
Hi Can we please integrate https://issues.apache.org/jira/browse/MNG-8116 The fix is ready and really simple. thanks Olivier On Wed, 24 Apr 2024 at 07:12, Tamás Cservenák wrote: > > Howdy, > > This is just a short newsflash about upcoming planned releases related to > Maven. > > Recently we got a huge spike in plugin releases, with various fixes and > improvements. I will not enumerate all of them here, just use `mvn > versions:display-plugin-updates` to pick them up ;) > (and more plugins to come). > > What I do want to share is about our upcoming Maven releases... > > Maven 3.9.7 is nearing (read: coming soon), and will have an important > Resolver update and other important fixes. Most importantly, the file-locks > are getting nice improvement (feedback VERY welcome). > > Maven 3.9.7 issues: > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%203.9.7 > > Resolver 1.9.19 issues (mostly bug fixes): > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOLVER%20AND%20fixVersion%20%3D%201.9.19 > > At the same time, we plan to release Maven Daemon (m39) as well, to have it > aligned with Maven 3,9,7: with many bug fixes and improvements/alignments > to "how Maven 3 behave". Our goal is to make the two (mvn and mvnd) > interchangeable on workstations. > > Next, Maven 4 is turning beta, so the next release will be beta1! And > again, same thing for Maven Damon (m40), we will have a release that will > include Maven 4 beta-1. > > Maven 4 beta-1 > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%204.0.0-beta-1 > > Resolver 2.0.0 (currently alpha-11, will become beta after Maven4 beta-1 > release): > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOLVER%20AND%20fixVersion%20%3D%202.0.0-alpha-11 > > Keep your eyes on our upcoming releases, > and have fun! > - The Apache Maven team - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Script Interpreter version 1.6
+1 On Tue, 30 Apr 2024 at 7:51 AM, Slawomir Jaranowski wrote: > Hi, > > We solved 4 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12354488 > > There are no more issues left in JIRA: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20maven-script-interpreter > > Staging repo: > https://repository.apache.org/content/repositories/maven-2105/ > > https://repository.apache.org/content/repositories/maven-2105/org/apache/maven/shared/maven-script-interpreter/1.6/maven-script-interpreter-1.6-source-release.zip > > Source release checksum(s): > maven-script-interpreter-1.6-source-release.zip - SHA-512 : > > 328a0a033952e6cecb264bf02198808c08e04b05165a72dd3bd168415055703bae1a6732c41ab61638b6e70991ff400c0f03e17d91c287c053e38a15b06c071a > > Staging site: > https://maven.apache.org/shared-archives/maven-script-interpreter-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 > > -- > Sławomir Jaranowski >
Re: maven-compat removal?
On Tue, 30 Apr 2024 at 15:56, Guillaume Nodet wrote: > > Maven-compat has been deprecated years ago, so the goal would be to get rid > of it. > For months, efforts have been made to first make maven-compat completely > optional. > This is now the case in maven itself. > However, some plugins still rely on it and they should be migrated to use > Maven 3 apis. > This is a required step before being able to get rid of maven-compat. > > I'm still hesitant about the time table, whether maven-compat should be > removed from > 4.0 distribution or not. It may be slightly premature, since a few plugins > still depend on it. > if we could have at least core plugins (default lifecycle) ready, that could work, but that's some work. but do you have some timeline in mind for 4.0? or it's just whenever it;s ready :) > Le mar. 30 avr. 2024 à 02:02, Olivier Lamy a écrit : > > > > Hi, > > I can see plenty of PRs with maven-compat removal. > > Maybe this could be explained and so more people could help for this task? > > > > cheers > > Olivier > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > -- > > Guillaume Nodet - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
maven-compat removal?
Hi, I can see plenty of PRs with maven-compat removal. Maybe this could be explained and so more people could help for this task? cheers Olivier - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Resolver 1.9.20
+1 On Fri, 26 Apr 2024 at 21:00, Tamás Cservenák wrote: > > Howdy, > > Note: Maven Resolver 1.x lineage is in "bugfix only" maintenance mode. > > This Resolver 1.9.20 release is a bugfix release: A behaviour change > introduced by BF collector was fixed, that may affect 3rd party code. > > We solved 4 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=12354578 > > There are still some issues in JIRA: > https://issues.apache.org/jira/projects/MRESOLVER/issues > > Staging repository: > https://repository.apache.org/content/repositories/maven-2101/ > > Source release SHA512: > 11b6d19927c3bf6ee486132ad1aed274fded1ac5bc996244efa9da7b831befeddec71775552fe5540fc6d1b3ca7dada68090cd38652d6592c29a9ab6e9a11b1b > > Staging site: > https://maven.apache.org/resolver-archives/resolver-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: [VOTE] Release Apache Maven Reporting Impl version 4.0.0-M14
+1 On Sat, 27 Apr 2024 at 00:51, Michael Osipov wrote: > > Hi, > > we solved 2 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12354095 > > There is one issue left in JIRA: > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20maven-reporting-impl > > Staging repo: > https://repository.apache.org/content/repositories/maven-2103/ > https://repository.apache.org/content/repositories/maven-2103/org/apache/maven/reporting/maven-reporting-impl/4.0.0-M14/maven-reporting-impl-4.0.0-M14-source-release.zip > > Source release checksum(s): > maven-reporting-impl-4.0.0-M14-source-release.zip > sha512: > 94c6a1110d104be08f5dcc08815439f083d8bad3a018be6396aa7d103b4639a474a71c885f499154ed59a933f551cec67c5e7b5cd3facc8472d0fb292eaf946b > > Staging site: > https://maven.apache.org/shared-archives/maven-reporting-impl-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 > - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Install Plugin 3.1.2
+1 On Fri, 26 Apr 2024 at 8:40 PM, Tamás Cservenák wrote: > Howdy, > > We solved 5 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317524=12353548 > > There are still a couple of issues left in JIRA: > https://issues.apache.org/jira/projects/MINSTALL/issues > > Staging repo: > https://repository.apache.org/content/repositories/maven-2099/ > > Source release checksum(s): > > f5847a66c2acc2b21b4afa5f4aa257ce3b41fcc63315720ccd68fa2cc497de8bef251ad500c6df051a2441846d521ce24de62858670f0c95101271166e9c6ce8 > > Staging site: > https://maven.apache.org/plugins-archives/maven-install-plugin-LATEST/ > > Guide to testing staged releases: > https://maven.apache.org/guides/development/guide-testing-releases.html > > Vote open for 72 hours. > > [ ] +1 > [ ] +0 > [ ] -1 >
Re: [VOTE] Release Maven Deploy Plugin 3.1.2
+1 On Fri, 26 Apr 2024 at 8:40 PM, Tamás Cservenák wrote: > Howdy, > > We solved 3 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317228=12354128 > > There are still a couple of issues left in JIRA: > https://issues.apache.org/jira/projects/MDEPLOY/issues > > Staging repo: > https://repository.apache.org/content/repositories/maven-2100/ > > Source release checksum(s): > > d45cc8431614d34b7d55c0a13e4a6387004add2dd3f5138b17d56be59e9787dcfe97f1e2250bc1549e4a9226dc9459673fd2dd9183f4926732253a344d231d79 > > Staging site: > https://maven.apache.org/plugins-archives/maven-deploy-plugin-LATEST/ > > Guide to testing staged releases: > https://maven.apache.org/guides/development/guide-testing-releases.html > > Vote open for 72 hours. > > [ ] +1 > [ ] +0 > [ ] -1 >
Re: [VOTE] Release Apache Maven Doxia Sitetools version 2.0.0-M18
+1 On Wed, 24 Apr 2024 at 05:03, Michael Osipov wrote: > > Hi, > > we solved 12 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317320=12354412 > > There are still a couple of issues left in JIRA: > https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317320%20AND%20status%20%3D%20Open > > Staging repo: > https://repository.apache.org/content/repositories/maven-2098 > https://repository.apache.org/content/repositories/maven-2098/org/apache/maven/doxia/doxia-sitetools/2.0.0-M18/doxia-sitetools-2.0.0-M18-source-release.zip > > Source release checksum(s): > doxia-sitetools-2.0.0-M18-source-release.zip > sha512: > 93247b25edb430485e26f634a3d9686182e125ff4ac3b2490274a7f97961e97d4d38b6fd8bd85a2378131ed55d0caadcd6902b4e5156937a00c7bc98eb3c36a4 > > Staging site: > https://maven.apache.org/doxia/doxia-sitetools-archives/doxia-sitetools-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 > - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Wrapper 3.3.1
+1 On Tue, 23 Apr 2024 at 02:28, Tamás Cservenák wrote: > > Howdy, > > The importance of this release is to gain over 3.3.0: Two changes are in > this release, both are equally important, but MWRAPPER-134 adds simple > means for tooling to discover wrapper versions being used. With 3.3.0 we > lost this ability to figure out wrapper versions easily. > > We solved 2 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12323721=12354586 > > There are still a couple of issues left in JIRA: > https://issues.apache.org/jira/projects/MWRAPPER/issues > > Staging repo: > https://repository.apache.org/content/repositories/maven-2097 > > Source release checksum SHA512: > 270d843df1b5db108f5420c3ef9310ff1238d49b077c35cff6a5eca9f584f6f41ee9d82cba169fce2c6e768281cda9d84383ec75171640163d0966cc0f206949 > > Staging site: > https://maven.apache.org/wrapper-archives/wrapper-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 Toolchains Plugin 3.2.0
The Apache Maven team is pleased to announce the release of the Apache Maven Toolchains Plugin, version 3.2.o The Toolchains Plugins enable sharing tool configuration across plugins. For example, to make sure that plugins like compiler, surefire, and javadoc all use the same JDK for execution, independently from JRE used to run Maven itself. https://maven.apache.org/plugins/maven-toolchains-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-toolchains-plugin 3.2.0 You can download the appropriate sources etc. from the download page: https://maven.apache.org/plugins/maven-toolchains-plugin/download.cgi Release Notes - Maven Toolchains Plugin - Version 3.2.0 ** Improvement * [MTOOLCHAINS-49] - Automatic discovery of JDK toolchains ** Bug * [MTOOLCHAINS-41] - Broken link to JDK toolchain version range definitions ** Task * [MTOOLCHAINS-43] - Cleanup - Pom ** Dependency upgrade * [MTOOLCHAINS-42] - Upgrade maven-plugin parent to 37 * [MTOOLCHAINS-45] - Upgrade maven-plugin parent to 39 * [MTOOLCHAINS-50] - Upgrade to maven parent 41 * [MTOOLCHAINS-51] - Upgrade to maven 3.9.6 at compile time and 3.6.3 at runtime Enjoy, -The Apache Maven team - 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.5.3
+1 On Sun, 21 Apr 2024 at 01:54, Hervé Boutemy wrote: > > Hi, > > We solved 3 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317921=12354342=Text > > Staging repo: > https://repository.apache.org/content/repositories/maven-2096/ > https://repository.apache.org/content/repositories/maven-2096/org/apache/maven/plugins/maven-shade-plugin/3.5.3/maven-shade-plugin-3.5.3-source-release.zip > > Source release checksum(s): > maven-shade-plugin-3.5.3-source-release.zip sha512: > a97d291f66f7f4a96af936c27061305e3856cb1e32ee5130cbf9b2f9a31d2ac7c1551ab17cd41e75887ac2345b815fad248fb381f437bf1376467a4fcdf24544 > > 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
[RESULT][VOTE] Apache Maven Toolchains Plugin 3.2.0
Hi, The vote has passed with the following result: +1 Karl, Slawomir, Tamas, Herve, Olivier I will finish the release process. cheers Olivier - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Apache Maven Toolchains Plugin 3.2.0
My +1 On Thu, 18 Apr 2024 at 10:50, Olivier Lamy wrote: > > Hi, > I'd like to release Apache Maven Toolchains Plugin 3.2.0 > We fixed 7 issues. > Staging repo: https://repository.apache.org/content/repositories/maven-2094/ > > Source release checksum SHA512: > c26ee136b19220cfdde41211426432feb8b042f23d96d9c490c0befa4986c89919ba412285a8acf621a2763ccfc5b768813df84669440bdef0a805ff623ef2ca > > Staging site: > https://maven.apache.org/plugins-archives/maven-toolchains-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 Maven Resolver 1.9.19
+1
On Tue, 16 Apr 2024 at 23:20, Tamás Cservenák wrote:
>
> Howdy,
>
> Note: Maven Resolver 1.x lineage is in "bugfix only" maintenance mode.
>
> This Resolver 1.9.19 release is a bugfix release: A file locking related
> bug was fixed, that explains a lot about mysterious "could not acquire
> lock" problems. A cosmetic bugfix, where generated classpath string may
> contain trailing colon (":"). And finally, an improvement, that makes
> resolver able to work on FS implementations that do not allow mtime
> updates, like some cloud FS implementations are.
>
> We solved 10 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=12353946
>
> There are still some issues in JIRA:
> https://issues.apache.org/jira/projects/MRESOLVER/issues
>
> Staging repository:
> https://repository.apache.org/content/repositories/maven-2090
>
> Source release SHA512:
> 1f8e0f457a0e27e61e9850f6c234d3fdca79764bf847a47cd40c09cb1bcdb8a2e1d6e21ff5789cb8bab416cb4b7c024afe84e68f19401f79f658ce7cc05cb8b4
>
> Staging site:
> https://maven.apache.org/resolver-archives/resolver-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: [VOTE] Release Apache Maven Wrapper 3.3.0
+1 On Thu, 18 Apr 2024 at 05:36, Tamás Cservenák wrote: > > Howdy, > > We solved 21 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12323721=12352995 > > There are still a couple of issues left in JIRA: > https://issues.apache.org/jira/projects/MWRAPPER/issues > > Staging repo: > https://repository.apache.org/content/repositories/maven-2093 > > Source release checksum SHA512: > 4c495321f25d7001ba76a0cb4fd207b59905c4fef9066df8ca6f37eb645a74e55234710222d46df297bfd6ca17138630778ffa27c026a23e4b1045e0e98d9a04 > > Staging site: > https://maven.apache.org/wrapper-archives/wrapper-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
[VOTE] Apache Maven Toolchains Plugin 3.2.0
Hi, I'd like to release Apache Maven Toolchains Plugin 3.2.0 We fixed 7 issues. Staging repo: https://repository.apache.org/content/repositories/maven-2094/ Source release checksum SHA512: c26ee136b19220cfdde41211426432feb8b042f23d96d9c490c0befa4986c89919ba412285a8acf621a2763ccfc5b768813df84669440bdef0a805ff623ef2ca Staging site: https://maven.apache.org/plugins-archives/maven-toolchains-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 JAR Plugin version 3.4.1
+1 On Wed, 17 Apr 2024 at 07:13, Slawomir Jaranowski wrote: > > Hi, > > We solved 2 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317526=12354551 > > There are still a couple of issues left in JIRA: > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MJAR%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC > > Staging repo: > https://repository.apache.org/content/repositories/maven-2092/ > https://repository.apache.org/content/repositories/maven-2092/org/apache/maven/plugins/maven-jar-plugin/3.4.1/maven-jar-plugin-3.4.1-source-release.zip > > Source release checksum(s): > maven-jar-plugin-3.4.1-source-release.zip - SHA-512 : > 7a55772e85af9ce8268ab0d5792197a2341f4c49c1deeba7f8ba98c2b8d56ec3f1d6b34d79b4c4d92dee1df3e3a9e69a5b9ef8974086fa6c3785db5c6fe14e6f > > Staging site: > https://maven.apache.org/plugins-archives/maven-jar-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 > > -- > Sławomir Jaranowski - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven GPG Plugin 3.2.4
+1 On Tue, 16 Apr 2024 at 23:29, Tamás Cservenák wrote: > > Howdy, > > Note: This is a bugfix release related to "best practices". > > We solved 2 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317521=12354486 > > There are still a couple of issues left in JIRA: > https://issues.apache.org/jira/projects/MGPG/issues > > Staging repo: > https://repository.apache.org/content/repositories/maven-2091 > > Source release checksum SHA512: > 4d6c4417744fe0bb192440f1d220c22f8601ccafbba53a261e990cff8e5fc6e25afe5376a795f77c3f5a227d8457e68558a7faff9ce0cca8242b5cfb29253f1f > > Staging site: > https://maven.apache.org/plugins-archives/maven-gpg-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
Release of maven-toolchains-plugin
Hi, I'd like to release maven-toolchains-plugin. let me know if someone need more time? otherwise I will do it tomorrow. Cheers Olivier - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Project Parent POMs version 42
+1 On Sun, 14 Apr 2024 at 7:31 AM, Slawomir Jaranowski wrote: > Hi, > > Notice: Maven ASF 32 from staging is needed for testing > > We solved 16 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250=12353850 > > There are still a couple of issues left in JIRA: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MPOM%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20maven%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC > > Git diff: > > https://github.com/apache/maven-parent/compare/maven-parent-41...maven-parent-42 > > Staging repo: > https://repository.apache.org/content/repositories/maven-2088/ > > https://repository.apache.org/content/repositories/maven-2088/org/apache/maven/maven-parent/42/maven-parent-42-source-release.zip > > Source release checksum(s): > maven-parent-42-source-release.zip - SHA-512 : > > 087e93a2ce864874de6bb9aaedb91db84d1cd4a5a6b5d225de874b436c402d765978c7c18f0b4707f34935a220413089c79c15fcf17628044f943fefc61594a4 > > > 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 > > -- > Sławomir Jaranowski >
Re: [VOTE] Release ASF Parent POM version 32
+1 On Sun, 14 Apr 2024 at 02:47, Slawomir Jaranowski wrote: > > Hi, > > We solved 21 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250=12353849 > > There are still a couple of issues left in JIRA: > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MPOM%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20asf%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC > > Git diff: > https://github.com/apache/maven-apache-parent/compare/apache-31...apache-32 > > Staging repo: > https://repository.apache.org/content/repositories/orgapacheapache-1037/ > https://repository.apache.org/content/repositories/orgapacheapache-1037/org/apache/apache/32/apache-32-source-release.zip > > Source release checksum(s): > apache-32-source-release.zip - SHA-512 : > a75bd6649bd665d70c00c71d64999b346b1734e148244461f1b5c7ba0de8d44021f65f6228807fac30c4d593022ac06ab887fcc4a41cc019bbef02d2d323db03 > > Staging site: > https://maven.apache.org/pom-archives/asf-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 > > -- > Sławomir Jaranowski - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Move AFS Parent POM and Maven Parent POMs issues to GitHub
+1 On Sat, 13 Apr 2024 at 11:56 PM, Slawomir Jaranowski wrote: > Hi, > > Rationale: > > - more of changes in those projects are the dependencies updates make by > the Dependabot, next we create issues in Jira by manual copy paste to have > a release notes > - we can use Release Drafter for preparing release notes on GitHub - no > manual works and easy to publish > - release notes on GitHub are more easier to find > - it is our internal project used in ASF > > Taks to do: > > - release next version ASF 32 / Maven 42 as is > - make jira project MPOM - read only > - leave current open issues in jira as is - with notes about migration - if > someone want to work on it, will copy it to GitHub > - enable issues on GitHub > - update project documentation > > If the vote passes - I will take care of it. > > Jira project: > https://issues.apache.org/jira/projects/MPOM > > GitHub repositories: > https://github.com/apache/maven-apache-parent > https://github.com/apache/maven-parent > > Vote open for at least 72 hours. > > [ ] +1 > [ ] +0 > [ ] -1 > > -- > Sławomir Jaranowski >
Re: [VOTE] Release Apache Maven Reporting API version 4.0.0-M11
+1 On Sun, 14 Apr 2024 at 7:57 PM, Michael Osipov wrote: > Hi, > > we solved 1 issue: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12354553 > > There is one issue left in JIRA: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20maven-reporting-api > > Staging repo: > https://repository.apache.org/content/repositories/maven-2089/ > > https://repository.apache.org/content/repositories/maven-2089/org/apache/maven/reporting/maven-reporting-api/4.0.0-M11/maven-reporting-api-4.0.0-M11-source-release.zip > > Source release checksum(s): > maven-reporting-api-4.0.0-M11-source-release.zip > sha512: > > 61cf9ed8be060931042472cd576eeb9ae6452c9e628a45bbe05417c5cc2ef6a076e0dcb5e9cace31152fc590b765867e2edf05814dcd04554a095308bfb7ad3b > > Staging site: > https://maven.apache.org/shared-archives/maven-reporting-api-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: [VOTE] Release Apache Maven JAR Plugin version 3.4.0
+1 On Wed, 10 Apr 2024 at 7:28 AM, Slawomir Jaranowski wrote: > Hi, > > We solved 12 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317526=12352303 > > There are still a couple of issues left in JIRA: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MJAR%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC > > Staging repo: > https://repository.apache.org/content/repositories/maven-2085/ > > https://repository.apache.org/content/repositories/maven-2085/org/apache/maven/plugins/maven-jar-plugin/3.4.0/maven-jar-plugin-3.4.0-source-release.zip > > Source release checksum(s): > maven-jar-plugin-3.4.0-source-release.zip - SHA-512 : > > 542c14a583dad400ca9dc64cc209144bdb539a919ddd8d8361e5ff13402605289fa3634a2cb87f2ece23f8c408275e12ac37e15a92c74ddd3a9a65d8f2954ba9 > > Staging site: > https://maven.apache.org/plugins-archives/maven-jar-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 > > -- > Sławomir Jaranowski >
Re: [VOTE] Release Apache Maven GPG Plugin 3.2.3
+1 On Mon, 8 Apr 2024 at 19:36, Tamás Cservenák wrote: > > Howdy, > > Note: > This is a bugfix release for https://issues.apache.org/jira/browse/MGPG-121 > but also contains updated key dependencies. > > We solved 8 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317521=12354440 > > There are still a couple of issues left in JIRA: > https://issues.apache.org/jira/projects/MGPG/issues > > Staging repo: > https://repository.apache.org/content/repositories/maven-2084/ > > Source release checksum SHA512: > d63f3a788d57e15b32e0824fb7b7e9e46e8dbe8824d8bc7cb750aea4ba903d8fc3b430db84c06b11c1ca864c1a233d46c98b7f2cc8c3967969389cf04365fb2d > > Staging site: > https://maven.apache.org/plugins-archives/maven-gpg-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 Invoker Plugin 3.6.1 Released
Hi The Apache Maven team is pleased to announce the release of the Apache Maven Invoker Plugin, version 3.6.1 The Invoker Plugin is used to run a set of Maven projects. The plugin can determine whether each project execution is successful and can optionally verify the output generated from a given project execution. https://maven.apache.org/plugins/maven-invoker-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-invoker-plugin 3.6.1 You can download the appropriate sources etc. from the download page: https://maven.apache.org/plugins/maven-invoker-plugin/download.cgi Release Notes - Maven Invoker Plugin - Version 3.6.1 ** Improvement * [MINVOKER-352] - Remove usage commons-lang3 ** Task * [MINVOKER-355] - Update Groovy 4.0.18 to 4.0.20 to support jdk22 * [MINVOKER-356] - Various dependencies update via dependabot see release notes on github Enjoy, -The Apache Maven team - 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.3.1
+1 On Sat, 30 Mar 2024 at 11:55, Hervé Boutemy wrote: > > Hi, > > We solved 3 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317924=12353471=Text > > Staging repo: > https://repository.apache.org/content/repositories/maven-2081/ > https://repository.apache.org/content/repositories/maven-2081/org/apache/maven/plugins/maven-source-plugin/3.3.1/maven-source-plugin-3.3.1-source-release.zip > > Source release checksum(s): > maven-source-plugin-3.3.1-source-release.zip sha512: > aaa76709d054491118546c8f67829aa9c8435b6b2e6e2577573ac049823d1ca2c54c730e4800291cd3756a677f75af0278be886d16e057cf88fc014991f0004f > > 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 > - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[RESULT][VOTE] Release Apache Maven Invoker Plugin version 3.6.1
Hi, The vote has passed. +1: Sylwester, Slawomir, Herve, Olivier All good. Time to finish the release process. cheers Olivier - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Invoker Plugin version 3.6.1
My +1 On Wed, 27 Mar 2024 at 16:44, Olivier Lamy wrote: > > Hi, > I'd like to release Apache Maven Invoker plugin version 3.6.1 > We solved 3 issues (well that's what Jira says): > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317525=12354446 > > The main reason is an upgrade of Groovy, which have been done because > of dependabot but helps to easily test projects with jdk22. > So this one deserves a special hand-crafted Jira entry! > > Staging repo: > https://repository.apache.org/content/repositories/maven-2077/ > https://repository.apache.org/content/repositories/maven-2077/org/apache/maven/plugins/maven-invoker-plugin/3.6.1/maven-invoker-plugin-3.6.1-source-release.zip > > Source release checksum(s): > maven-invoker-plugin-3.6.1-source-release.zip sha512: > 3fd036cbeb88125a791ff6e3c849de7322b8d8afa65e4b96646a0d7a959069df7bdfba41d83ffafa096811d4ec794659ef44c0508da47ae8f9cbaf6e1eb6 > > Staging site: > https://maven.apache.org/plugins-archives/maven-invoker-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 Invoker Plugin version 3.6.1
Congratulations you’re the winner as you found the mystery ticket!! Thanks for reporting it, I will definitely update the title :) On Wed, 27 Mar 2024 at 6:23 PM, Gary Gregory wrote: > The current title of the ticket > https://issues.apache.org/jira/browse/MINVOKER-355 does not mention what > is > being updated. Amusing to me :-p since you write about it here ;-) > > Gary > > > On Wed, Mar 27, 2024, 2:45 AM Olivier Lamy wrote: > > > Hi, > > I'd like to release Apache Maven Invoker plugin version 3.6.1 > > We solved 3 issues (well that's what Jira says): > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317525=12354446 > > > > The main reason is an upgrade of Groovy, which have been done because > > of dependabot but helps to easily test projects with jdk22. > > So this one deserves a special hand-crafted Jira entry! > > > > Staging repo: > > https://repository.apache.org/content/repositories/maven-2077/ > > > > > https://repository.apache.org/content/repositories/maven-2077/org/apache/maven/plugins/maven-invoker-plugin/3.6.1/maven-invoker-plugin-3.6.1-source-release.zip > > > > Source release checksum(s): > > maven-invoker-plugin-3.6.1-source-release.zip sha512: > > > > > 3fd036cbeb88125a791ff6e3c849de7322b8d8afa65e4b96646a0d7a959069df7bdfba41d83ffafa096811d4ec794659ef44c0508da47ae8f9cbaf6e1eb6 > > > > Staging site: > > https://maven.apache.org/plugins-archives/maven-invoker-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 > > > > >
[VOTE] Release Apache Maven Invoker Plugin version 3.6.1
Hi, I'd like to release Apache Maven Invoker plugin version 3.6.1 We solved 3 issues (well that's what Jira says): https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317525=12354446 The main reason is an upgrade of Groovy, which have been done because of dependabot but helps to easily test projects with jdk22. So this one deserves a special hand-crafted Jira entry! Staging repo: https://repository.apache.org/content/repositories/maven-2077/ https://repository.apache.org/content/repositories/maven-2077/org/apache/maven/plugins/maven-invoker-plugin/3.6.1/maven-invoker-plugin-3.6.1-source-release.zip Source release checksum(s): maven-invoker-plugin-3.6.1-source-release.zip sha512: 3fd036cbeb88125a791ff6e3c849de7322b8d8afa65e4b96646a0d7a959069df7bdfba41d83ffafa096811d4ec794659ef44c0508da47ae8f9cbaf6e1eb6 Staging site: https://maven.apache.org/plugins-archives/maven-invoker-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 Archiver version 3.6.2
+1 On Mon, 25 Mar 2024 at 08:36, Slawomir Jaranowski wrote: > > Hi, > > We solved 3 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12353577 > > There are still a couple of issues left in JIRA: > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20maven-archiver > > Staging repo: > https://repository.apache.org/content/repositories/maven-2076/ > https://repository.apache.org/content/repositories/maven-2076/org/apache/maven/maven-archiver/3.6.2/maven-archiver-3.6.2-source-release.zip > > Source release checksum(s): > [NAME-OF]-source-release.zip sha512: [SHA512SUM] the sources doesn't match this checksum :P > > Staging site: > https://maven.apache.org/shared-archives/maven-archiver-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 > > -- > Sławomir Jaranowski - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven GPG Plugin 3.2.2
+1 On Sun, 24 Mar 2024 at 08:06, Tamás Cservenák wrote: > > Howdy, > > Note: this is a bugfix release for > https://issues.apache.org/jira/browse/MGPG-113 > > We solved 3 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317521=12354419 > > There are still a couple of issues left in JIRA: > https://issues.apache.org/jira/projects/MGPG/issues > > Staging repo: > https://repository.apache.org/content/repositories/maven-2075/ > > Source release checksum SHA512: > 1bb3d9dbf6992ec58b6f08f8cd39d8f002c0ac7be4b7197bbb54057152824a400acebd77e6366e20c5d30a10575be1607e66bdf3a5667c2efef812826b877d8c > > Staging site: > https://maven.apache.org/plugins-archives/maven-gpg-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
Release of maven-invoker-plugin
Hi, I'd like to release m-invoker-p. Don't be too excited there is not much new shiny new feature. But Groovy's upgrade makes it easier to use with jdk22 without too much XML to add in your pom to override the Groovy version. cheers Olivier - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Compiler Plugin version 3.13.0
+1 On Fri, 15 Mar 2024 at 17:37, Slawomir Jaranowski wrote: > > Hi, > > We solved 10 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317225=12354079 > > There are still a couple of issues left in JIRA: > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MCOMPILER%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC > > Staging repo: > https://repository.apache.org/content/repositories/maven-2072/ > https://repository.apache.org/content/repositories/maven-2072/org/apache/maven/plugins/maven-compiler-plugin/3.13.0/maven-compiler-plugin-3.13.0-source-release.zip > > Source release checksum(s): > maven-compiler-plugin-3.13.0-source-release.zip - SHA-512 : > 99897c8350e50ba0ad9fcba210dad772d7f9e465358c35752942b71e3c7d2ca54d1e9115cc657130829135f1598a091436463744ef00de0cbee6042862abddf5 > > Staging site: > https://maven.apache.org/plugins-archives/maven-compiler-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 > > -- > Sławomir Jaranowski - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven GPG Plugin 3.2.1
+1 On Fri, 15 Mar 2024 at 6:25 PM, Tamás Cservenák wrote: > Howdy, > > Note: this is a bugfix release for > https://issues.apache.org/jira/browse/MGPG-112 > > We solved 2 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317521=12354394 > > There are still a couple of issues left in JIRA: > https://issues.apache.org/jira/projects/MGPG/issues > > Staging repo: > https://repository.apache.org/content/repositories/maven-2074/ > > Source release checksum SHA512: > > 19bb9d57b2caec3524ecc3abc8efb818061541874011763c474c0d60608a3b156eb0ad92299bba2a24ba86b8021c2b5d89c2531a918e913453e170dcfa125d1e > > Staging site: > https://maven.apache.org/plugins-archives/maven-gpg-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 >
Re: [VOTE] Release Apache Maven Doxia Sitetools version 2.0.0-M17
+1 On Sun, 10 Mar 2024 at 06:38, Michael Osipov wrote: > > Hi, > > we solved 7 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317320=12354091 > > There are still a couple of issues left in JIRA: > https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317320%20AND%20status%20%3D%20Open > > Staging repo: > https://repository.apache.org/content/repositories/maven-2071 > https://repository.apache.org/content/repositories/maven-2071/org/apache/maven/doxia/doxia-sitetools/2.0.0-M17/doxia-sitetools-2.0.0-M17-source-release.zip > > Source release checksum(s): > doxia-sitetools-2.0.0-M17-source-release.zip > sha512: > abb8c6385e68706da8f9ec15b245b23296ffb69919bb47ddca8b36662d607dcec18164095222d908dcf00ca303885eff2b8794b2acc9aca7ef9787d9fa133af7 > > Staging site: > https://maven.apache.org/doxia/doxia-sitetools-archives/doxia-sitetools-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 > - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Assembly Plugin version 3.7.0
+1 On Fri, 8 Mar 2024 at 04:28, Slawomir Jaranowski wrote: > > Hi, > > We solved 25 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317220=12353243 > > There are still a couple of issues left in JIRA: > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MASSEMBLY%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC > > Staging repo: > https://repository.apache.org/content/repositories/maven-2069/ > https://repository.apache.org/content/repositories/maven-2069/org/apache/maven/plugins/maven-assembly-plugin/3.7.0/maven-assembly-plugin-3.7.0-source-release.zip > > Source release checksum(s): > maven-assembly-plugin-3.7.0-source-release.zip - SHA-512 : > fd25b79c126cf728fddc04f9f0cb56cbd5434d4f67001f88947ca677086a5d34e843154c6fe9dfb47ac85889ddd656a5df0ba3e1f6486e1a9d887fedf6d1200e > > > Staging site: > https://maven.apache.org/plugins-archives/maven-assembly-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 > > -- > Sławomir Jaranowski - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Require Java 17 for Maven 4
+1 On Wed, 28 Feb 2024 at 17:31, Benjamin Marwell wrote: > > Hi Maven Devs/Users/Committers and PMC members! > > After several discussions on the mailing lists, I would like to > start a vote in favour of setting the minimal Java bytecode target > of Maven-Core 4 to 17 and hence require Java 17 for Maven 4. > > This is a procedural majority vote [1*]: > You can also vote with fractions and negative votes are not vetoes. > > Please also notice: > * Maven 3 will stay at Java 8 no matter what. > * We may raise Maven 4 to JDK 21 later if we feel like it (depending > on the release date). > This is not part of this vote. > * The linked PR is not part of this vote (this is not a code vote). > But you may take a look at it to understand the intended change. > > PR: https://github.com/apache/maven/pull/1430 > > Maven-Parent will not be raised with this vote, the other PR is not > part of this vote. > > Please refrain from starting discussions in this thread, but do > include a reasoning on downvotes and feel free to start a new > discussion on the mailing list, or comment on the existing ones. > > --- > > Vote open for 72 hours: > > [ ] +1 (set JDK17 min version for Maven 4.x) > [ ] +0 > [ ] -1 (please include reasoning) > > --- > > - Ben > > [1*]: https://www.apache.org/foundation/voting.html > > - > 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.5.2
+1 On Sun, 18 Feb 2024 at 04:00, Hervé Boutemy wrote: > > Hi, > > We solved 6 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317921=12352505=Text > > Staging repo: > https://repository.apache.org/content/repositories/maven-2065/ > https://repository.apache.org/content/repositories/maven-2065/org/apache/maven/plugins/maven-shade-plugin/3.5.2/maven-shade-plugin-3.5.2-source-release.zip > > Source release checksum(s): > maven-shade-plugin-3.5.2-source-release.zip sha512: > 23fcd21e6b915114efa133b1c4e46fa0b3d77874ff9d974e4bdb24940ea0ed9b7ffaf7f3d1e8a8549837cfe1de7ff2fc8ae7fc68bfc0477ea7a4b8b53e42f6f7% > > 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
Re: Java version for Maven 4?
Personnaly (take it as a vote), I find this a good idea to say: - 3.x: jdk 8 (whatever someone wants to release some fixes) - 4.x: jdk 17 On Tue, 6 Feb 2024 at 20:50, Kévin Buntrock wrote: > > From my modest point of view : glued to old stack projects do not move at > all. Why move to a new maven version if the one used works? > > Furthermore, I'm quite impressed by the number of projects starting in java > 21 for clients I was considering really shy new adopters. Java 21 is here, > works well, and gets adopted. > > Therefore, my vote goes to the current last LTS to run maven 4, a project > not even released. > > Le mar. 6 févr. 2024 à 09:00, Benjamin Marwell a > écrit : > > > > we need to think about companies > > that pay for old JDK support > > > > There was a suggestion on slack that companies could provide "dev and > > release manager" for Maven 3 and manage the JDK 8 Maven 3 until they lose > > interest. This already works well for other projects. > > > > Even if no one stands up for volunteering: Maven 3 will continue to work > > just fine, even after releases of Maven 4. > > > > > > About the companies who run their own JDK team: > > Well, they made that a conscious decision. They surely had planned for > > versions after Java 8. If not, I don't see why we should take their problem > > and make it ours. > > > > - Ben > > > > > > On Mon, 5 Feb 2024, 23:15 Gary Gregory, wrote: > > > > > An interesting question for me is whether we need to think about > > companies > > > that pay for old JDK support and how that affects our support for these > > old > > > JDKs. > > > > > > Gary > > > > > > On Mon, Feb 5, 2024, 4:28 PM Elliotte Rusty Harold > > > wrote: > > > > > > > On Mon, Feb 5, 2024 at 2:22 PM Romain Manni-Bucau < > > rmannibu...@gmail.com > > > > > > > > wrote: > > > > > > > > > > Hi Elliotte, > > > > > > > > > Java 11 support is already EOL for most vendor until you go "premium" > > > > > flavor which will likely be very few people and most of them will be > > > able > > > > > to pay somebody to backport the needed stuff in custom distro of > > their > > > > work > > > > > if needed anyday so not sure we should consider it. > > > > > > > > At least three big tech companies I know of build their own JDKs. At > > > > least one, possibly two, ship and support older JDKs for their > > > > customers. None of them are tied to Oracle and what Oracle is willing > > > > to support. If Oracle and all its data went to the great bit bucket in > > > > the sky tomorrow, they'd keep right on rolling. It would not even be a > > > > speed bump. They don't pay for premium support. They compete to > > > > provide premium support.* > > > > > > > > * There are some caveats here I won't go into for confidentiality > > > > reasons, but I can say that Azul's business model works. > > > > > > > > > On the other side most libraries tend to move forward faster and if > > you > > > > > like big ones, i'll take Spring or JakartaEE as an example - big user > > > > base > > > > > rather than big company$ ;) - and they don't even support Java 11 > > > > anymore. > > > > > > > > Used by big tech customers. Not so much used by big tech companies > > > > themselves, that tend to run on stacks developed in house over more > > > > than a decade. > > > > > > > > -- > > > > Elliotte Rusty Harold > > > > elh...@ibiblio.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: [VOTE] Release Apache Maven JLink Plugin version 3.2.0
+1 On Tue, 30 Jan 2024 at 05:37, Benjamin Marwell wrote: > > Hi, > > We solved 6 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321432=12349496 > > There are still two issues left in JIRA: > https://issues.apache.org/jira/projects/MJLINK/issues > > Staging repo: > https://repository.apache.org/content/repositories/maven-2064 > https://repository.apache.org/service/local/repositories/maven-2064/content/org/apache/maven/plugins/maven-jlink-plugin/3.2.0/maven-jlink-plugin-3.2.0-source-release.zip > > Source release checksum(s): > maven-jlink-plugin-3.2.0-source-release.zip sha512: > 0cedc1a75b2ed7c085017ad65f18a10b2da4d06217dcb0eb6a1e6e22a8dadab2df4986b020392d15c7215e0b594f25e47d7341ed4e157a6b7e60be63158d008b% > > Staging site: > https://maven.apache.org/plugins-archives/maven-jlink-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
Re: [VOTE] Release Maven Resolver 2.0.0-alpha-7
+1 On Fri, 26 Jan 2024 at 04:58, Tamás Cservenák wrote: > > Howdy, > > Note: This is a sixth (alpha-4 was scrubbed) preview release of Resolver > 2.0.0, that would allow any downstream consumers to try it out and adapt. > The supplier is aligned with Maven 4.0.0-alpha-12. Delivered features are > mostly smaller improvements, bug fixes and dependency updates. One notable > change is that this release makes "file locking" enabled by default. This > alpha contains pretty much every major feature we planned for 2.0.0. Of > course, we do NOT exclude more issues to be added (most likely bugs) down > the road, but the final 2.0.0 release is getting near. > > For configuration changes, see > https://maven.apache.org/resolver-archives/resolver-LATEST/configuration.html > > IF the vote is successful, the staging site will NOT be moved to > https://maven.apache.org/resolver/ but instead will be made reachable from > https://maven.apache.org/resolver-archives/resolver-2.0.0-alpha-7/ only. > > The 1.9.18 is still the "latest stable" release of Maven Resolver. > > === > > We solved 20 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=12354065 > > There are still some issues in JIRA: > https://issues.apache.org/jira/projects/MRESOLVER/issues > > Staging repository: > https://repository.apache.org/content/repositories/maven-2063 > > Source release SHA512: > af765437edad19adb5cca208841c431bafc983288f5fd6ea09f6446a8ad30bcb27e2c0b81e4652ab4a95ecc8ca95a03cbeb20e3283a3ff1ced40caf6c3dbcf1b > > Staging site: > https://maven.apache.org/resolver-archives/resolver-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: Strange behavior using maven build-cache extension in maven-release-plugin goals
interesting.
is the deploy goal executed twice as well when you run "mvn deploy"?
(as you marked as it as alwaysRun)
On Sun, 21 Jan 2024 at 23:00, Javier Gómez wrote:
>
> Hi all,
>
> We are starting to apply the build-cache maven extension in our local and CI
> environment, and we have seen strange behavior in several maven projects,
> when using the release plugin in conjunction with build-cache, which we have
> been able to reproduce both locally and in CI.
>
> Our usual release plugin configuration is:
>
>
> org.apache.maven.plugins
> maven-release-plugin
> 3.0.0
>
> -DskipEnforceSnapshots -DskipITs -DskipTests
> -DskipUTs
> deploy
>
> SemVerVersionPolicy
> GithubReleaseStrategy
> @{prefix} Prepare release
> @{releaseLabel}
> @{prefix} Prepare for next
> development iteration
> @{project.version}
>
>
> When we add the build-cache extension to the project, and execute the release
> with: mvn release:prepare release:perform -DreleaseVersion=x.y.z we can
> observe a strange behavior when maven is launching the release:perform goal,
> we see that the deploy goal is executed 2 times for each artifact (in fact it
> seems that the maven lifecycle restarts, once it reaches the deploy and
> begins to execute the validate again) and when it reaches the 2nd execution
> of deploy, it fails (since the user we use do not have permissions to
> overwrite artifacts). Below I show an extract from the log:
>
> ...
>
> [INFO] [INFO]
>
> [INFO] [INFO] Reactor Build Order:
> [INFO] [INFO]
> [INFO] [INFO] temp.mectagcore:mectagcore [pom]
> [INFO] [INFO] temp.mectagcore:mectagcore-domain [jar]
> [INFO] [INFO] temp.mectagcore:mectagcore-boot[jar]
> [INFO] [INFO] temp.mectagcore:jacoco-report-aggregate[pom]
> [INFO] [INFO]
> [INFO] [INFO] -< temp.mectagcore:mectagcore >-
> [INFO] [INFO] Building temp.mectagcore:mectagcore 1.0.0 [1/9]
> [INFO] [INFO] from pom.xml
> [INFO] [INFO] [ pom
> ]-
> [INFO] [INFO] Going to calculate checksum for project
> [groupId=temp.mectagcore, artifactId=mectagcore]
> [INFO] [INFO] Project inputs calculated in 12 ms. SHA-256 checksum
> [16534757c14aae9b1ff1961664995f0e7e9396fb88309d207a8a23c080c7f661] calculated
> in 4 ms.
> [INFO] [INFO] Attempting to restore project temp.mectagcore:mectagcore from
> build cache
> [INFO] [INFO] Local build found by checksum
> 16534757c14aae9b1ff1961664995f0e7e9396fb88309d207a8a23c080c7f661
> [INFO] [INFO] Found cached build, restoring temp.mectagcore:mectagcore from
> cache by checksum
> 16534757c14aae9b1ff1961664995f0e7e9396fb88309d207a8a23c080c7f661
> [INFO] [INFO] Project temp.mectagcore:mectagcore restored partially. Highest
> cached goal: verify, requested: deploy
> [INFO] role: 'org.apache.maven.plugin.Mojo', implementation:
> 'org.apache.maven.plugin.failsafe.IntegrationTestMojo', role hint:
> 'org.apache.maven.plugins:maven-failsafe-plugin:3.0.0:integration-test'
> [INFO] role: 'org.apache.maven.plugin.Mojo', implementation:
> 'org.apache.maven.plugin.failsafe.VerifyMojo', role hint:
> 'org.apache.maven.plugins:maven-failsafe-plugin:3.0.0:verify'
> [INFO] ---
> [INFO] [INFO] Skipping plugin execution (cached): enforcer:enforce
> [INFO] [INFO] Skipping plugin execution (cached): enforcer:enforce
> [INFO] [INFO] Skipping plugin execution (cached): build-helper:add-source
> [INFO] [INFO] Mojo execution is forced by project property:
> amiga-assembly:amiga-assembly
> [INFO] [INFO]
> [INFO] [INFO] --- amiga-assembly:5.5.0:amiga-assembly
> (amiga-assembly-execution) @ mectagcore ---
> [INFO] [INFO] Mojo execution is forced by project property: source:jar-no-fork
> [INFO] [INFO]
> [INFO] [INFO] --- source:3.2.1:jar-no-fork (attach-sources) @ mectagcore ---
> [INFO] [INFO] Skipping plugin execution (cached): failsafe:integration-test
> [INFO] [INFO] Skipping plugin execution (cached): failsafe:verify
> [INFO] [INFO]
> [INFO] [INFO] --- install:3.1.1:install (default-install) @ mectagcore ---
> [INFO] role: 'org.apache.maven.plugin.Mojo', implementation:
> 'org.apache.maven.plugins.install.InstallMojo', role hint:
> 'org.apache.maven.plugins:maven-install-plugin:3.1.1:install'
> [INFO] role: 'org.apache.maven.plugin.Mojo', implementation:
> 'org.apache.maven.plugins.install.InstallFileMojo', role hint:
> 'org.apache.maven.plugins:maven-install-plugin:3.1.1:install-file'
> [INFO] ---
> [INFO] [INFO] Installing
> /tmp/mic-mectagcore/code/target/checkout/code/pom.xml to
> /home/alambike/.m2/repository/temp/mectagcore/mectagcore/1.0.0/mectagcore-1.0.0.pom
> [INFO] [INFO]
> [INFO] [INFO] ---
Re: New year - new challenge - required Maven 3.6.3 as minimal for core Maven Plugins
On Sat, 30 Dec 2023 at 18:24, Slawomir Jaranowski wrote: > > pt., 29 gru 2023 o 18:40 Michael Osipov napisał(a): > > > Am 2023-12-29 um 14:42 schrieb Slawomir Jaranowski: > > > Hi, > > > > > > Last year we mark all Maven versions 3.6.x and older as EOL [1] > > > > > > But we still try to support minimal API version for Core Maven Plugins as > > > 3.2.5 > > > > > > I would like to propose to sich it for at least to 3.6.3 > > > > > > Reasonable reasons: (for me) > > > - for standard CI build we use Maven 3.6.3 and newer > > > - many of external plugins, like MojoHaus are switched to 3.6.3 > > > - we have a hacks in code to try support old version in plugin, like > > > in: EnhancedPluginDescriptorBuilder in plugin-tools [2], we can cleanup > > > such code > > > - I don't believe to someone want to do more fixes for EOL Maven version > > in > > > plugins - so we should be a honest for users > > > - and we should go forward > > > > > > [1] https://maven.apache.org/docs/history.html > > > [2] > > > > > https://github.com/apache/maven-plugin-tools/blob/master/maven-plugin-report-plugin/src/main/java/org/apache/maven/plugins/plugin/descriptor/EnhancedPluginDescriptorBuilder.java > > > > > > > I remember that we had a discussion that the next base/API version > > should be 3.5.4 because it is the first version using > > org.apache.maven.resolver:maven-resolver-api [1]. Please don't confuse > > API compat with maintenance/support for a specific Maven version. I > > believe that we have made this clear more than once. > > > > Is thre anything specific fixed in 3.6.3 behavior you consider crucial > > which makes maintenance easier than with 3.5.4? > > > > > I remember the discussion ... and next year we are still on 3.2.5 > > I can not a list what was exactly improved in 3.6.3 against to 3.5.4, but I > see in mentioned code > > // clear() is required for maven < 3.6.2 > mojoDescriptor.getParameters().clear(); > > So my question is: > > Why should we use 3.5.4 instead of 3.6.4 as minimum in plugins? > Especially as we do not maintain anymore core 3.5.4 neither 3.6,4 see https://maven.apache.org/docs/history.html we could simply align with core versions we still marked as maintained, and that would make our lives easier. this doesn't mean we have to migrate everything, but at least this could be a rule > > M > > > > [1] > > https://cwiki.apache.org/confluence/display/MAVEN/Maven+Ecosystem+Cleanup > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > > -- > Sławomir Jaranowski - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Compiler Plugin version 3.12.1
+1 On Thu, 21 Dec 2023 at 17:54, Slawomir Jaranowski wrote: > > Hi, > > We solved 2 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317225=12354061 > > There are still a couple of issues left in JIRA: > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MCOMPILER%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC > > Staging repo: > https://repository.apache.org/content/repositories/maven-2051/ > https://repository.apache.org/content/repositories/maven-2051/org/apache/maven/plugins/maven-compiler-plugin/3.12.1/maven-compiler-plugin-3.12.1-source-release.zip > > Source release checksum(s): > maven-compiler-plugin-3.12.1-source-release.zip - SHA-512 : > 8aba1fcb580110119422b5e323d36af6179fcefc485d3354189cfecad987825ca168a61687d52c2a6561559d14387946f6f46606649cc3980cb67136d7dbc8eb > > Staging site: > https://maven.apache.org/plugins-archives/maven-compiler-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 > > -- > Sławomir Jaranowski - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Javadoc Plugin version 3.6.3
+1 On Fri, 1 Dec 2023 at 07:41, Michael Osipov wrote: > > Hi, > > we solved 5 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317529=12353857 > > There are still a couple of issues left in JIRA: > https://issues.apache.org/jira/projects/MJAVADOC/issues > > Staging repo: > https://repository.apache.org/content/repositories/maven-2041/ > https://repository.apache.org/content/repositories/maven-2041/org/apache/maven/plugins/maven-javadoc-plugin/3.6.3/maven-javadoc-plugin-3.6.3-source-release.zip > > Source release checksum(s): > maven-javadoc-plugin-3.6.3-source-release.zip > sha512: > 724078534531971f9b2a616fe4493f103311686275a495fd7dcdfe019ec0eec5f0f9a85b3329584a68ffcddd244840245ee9265c4aa512b94201701076c70a68 > > Staging site: > https://maven.apache.org/plugins-archives/maven-javadoc-plugin-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 > - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[ANN] Apache Maven Build Cache Extension 1.1.0
Hi The Apache Maven team is pleased to announce the release of the Apache Maven Build Cache Extension 1.1.0. Build cache is an extension that makes large Maven builds more efficient. https://maven.apache.org/extensions/maven-build-cache-extension/ Release Notes - Maven Build Cache Extension - Version 1.1.0 ** Bug * [MBUILDCACHE-32] - Do not print exception when probing builds in remote repo * [MBUILDCACHE-61] - XXMM hash algorithm does not work on Java 17 * [MBUILDCACHE-64] - Apply global exclusions to folder names * [MBUILDCACHE-66] - Mojo execution can be out of scope * [MBUILDCACHE-67] - Any error in restoring from the cache should resume the non cache build ** New Feature * [MBUILDCACHE-62] - Add METRO hash implementation ** Task * [MBUILDCACHE-75] - Upgrade Maven parent 41 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[RESULT}[VOTE] Apache Maven Build Cache Extension 1.1.0
Hi, The vote has passed with the following result. +1: Karl, Guillaume, Kevin, Tamas, Romain, Herve, Slawomir, Olivier I will finish the release process. Thanks for your vote. cheers Olivier - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven 3.9.6
+1 On Tue, 28 Nov 2023 at 20:24, Tamás Cservenák wrote: > > Howdy, > > Note: This release improves Windows experience (via use of Resolver 1.9.18) > and makes possible using newer bytecode as Maven components (by upping > Sisu) and adds ability to exclude plugins from validation. > > --- > > We solved 5 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12353686 > > There are still a couple of issues left in JIRA: > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20resolution%20%3D%20Unresolved > > Staging repo: > https://repository.apache.org/content/repositories/maven-2039 > > Dev dist directory (binary bundles updated): > https://dist.apache.org/repos/dist/dev/maven/maven-3/3.9.6/ > > Source release checksums: > apache-maven-3.9.6-src.tar.gz.sha512 > c14b97703082af495225cec652ad1ec58cbcd069040cdfa16a7b9270058574c73524ce15217e83153fe23b2449ef1afd73a4ef42bd05abd3cfdfadfc3da7f7bf > > apache-maven-3.9.6-src.zip.sha512 > e1773ea34a90a16a4ba68bd0304fe73b34fbc2d02f74c195aaa610a959ccd9ce500194b72dc957a2b8af2af28c63e342f7f98fcd4e5b795a0af8364e5fb72bcf > > Staged site: > https://maven.apache.org/ref/3-LATEST/ > > Draft for release notes: > https://github.com/apache/maven-site/pull/469 > > Guide to testing staged releases: > http://maven.apache.org/guides/development/guide-testing-releases.html > > Vote open for 72h > > [ ] +1 > [ ] +0 > [ ] -1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Apache Maven Build Cache Extension 1.1.0
My +1 On Mon, 27 Nov 2023 at 12:12, Olivier Lamy wrote: > > Hi, > I'd like to release the Apache Maven Build Cache Extension 1.1.0. > We've fixed 8 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12352470=Text=12324820 > > Staging repo https://repository.apache.org/content/repositories/maven-2038/ > > source release > https://repository.apache.org/content/repositories/maven-2038/org/apache/maven/extensions/maven-build-cache-extension/1.1.0/maven-build-cache-extension-1.1.0-source-release.zip > > sha512 > https://repository.apache.org/content/repositories/maven-2038/org/apache/maven/extensions/maven-build-cache-extension/1.1.0/maven-build-cache-extension-1.1.0-source-release.zip.sha512 > > Staging site: > https://maven.apache.org/extensions-archives/maven-build-cache-extension-LATEST/ > > Vote open for 72h > > +1 > 0 > -1 > > regards > Olivier - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[VOTE] Apache Maven Build Cache Extension 1.1.0
Hi, I'd like to release the Apache Maven Build Cache Extension 1.1.0. We've fixed 8 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12352470=Text=12324820 Staging repo https://repository.apache.org/content/repositories/maven-2038/ source release https://repository.apache.org/content/repositories/maven-2038/org/apache/maven/extensions/maven-build-cache-extension/1.1.0/maven-build-cache-extension-1.1.0-source-release.zip sha512 https://repository.apache.org/content/repositories/maven-2038/org/apache/maven/extensions/maven-build-cache-extension/1.1.0/maven-build-cache-extension-1.1.0-source-release.zip.sha512 Staging site: https://maven.apache.org/extensions-archives/maven-build-cache-extension-LATEST/ Vote open for 72h +1 0 -1 regards Olivier - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Site Plugin version 4.0.0-M12
+1 On Wed, 22 Nov 2023 at 07:22, Michael Osipov wrote: > > Hi, > > IMPORTANT: This require the following staging repositories: > > * Maven Reporting Impl 4.0.0-M12 > * Maven Reporting Exec 4.0.0-M12 > > we solved 7 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317923=12353780 > > There are still a couple of issues left in JIRA: > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSITE%20AND%20resolution%20%3D%20Unresolved > > Staging repo: > https://repository.apache.org/content/repositories/maven-2036/ > https://repository.apache.org/content/repositories/maven-2036/org/apache/maven/plugins/maven-site-plugin/4.0.0-M12/maven-site-plugin-4.0.0-M12-source-release.zip > > Source release checksum(s): > maven-site-plugin-4.0.0-M12-source-release.zip > sha512: > 463da0c6ccb7d0fbbf8b5460ed61c361b6560b6f394857328e251df645e0c2ae08a9872dd74ee06878baaeea26821947dc3453bb380439fa8b6733ac6d93a18c > > Staging site: > https://maven.apache.org/plugins-archives/maven-site-plugin-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 > - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Reporting Exec version 2.0.0-M12
+1 How many Mxxx will we get? :) On Wed, 22 Nov 2023 at 06:12, Michael Osipov wrote: > > Hi, > > IMPORTANT: This require the following staging repositories: > > * Maven Reporting Impl 4.0.0-M12 > > we solved 4 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12353779 > > There are still a couple of issues left in JIRA: > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20maven-reporting-exec > > Staging repo: > https://repository.apache.org/content/repositories/maven-2035/ > https://repository.apache.org/content/repositories/maven-2035/org/apache/maven/reporting/maven-reporting-exec/2.0.0-M12/maven-reporting-exec-2.0.0-M12-source-release.zip > > Source release checksum(s): > maven-reporting-exec-2.0.0-M12-source-release.zip > sha512: > e37d85dd227f7ae8c254c054681b25558899ad0eb40b43c90640af4fa11ed05efa0439bda584e498bbc587b551427fe88ec94972d7c270f7a517b9f71b343c0c > > Staging site: > https://maven.apache.org/shared-archives/maven-reporting-exec-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 > - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Reporting Impl version 4.0.0-M12
+1 On Wed, 22 Nov 2023 at 06:00, Michael Osipov wrote: > > Hi, > > we solved 5 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12353750 > > There is one issue left in JIRA: > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20maven-reporting-impl > > Staging repo: > https://repository.apache.org/content/repositories/maven-2034/ > https://repository.apache.org/content/repositories/maven-2034/org/apache/maven/reporting/maven-reporting-impl/4.0.0-M12/maven-reporting-impl-4.0.0-M12-source-release.zip > > Source release checksum(s): > maven-reporting-impl-4.0.0-M12-source-release.zip > sha512: > cb827514757e9dfb4a8a726723782124b3412602ff26c290c186acd20a2749a2aa37e49c8a6f5e4c04c55744a04baf914b28fba428a9db67f7a0f5c02ef0 > > Staging site: > https://maven.apache.org/shared-archives/maven-reporting-impl-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 > - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Resolver 1.9.18
+1 On Thu, 23 Nov 2023 at 2:17 am, Tamás Cservenák wrote: > Howdy, > > Note1: Maven Resolver 1.x lineage is in "bugfix only" maintenance mode. > Note2: Resolver 1.9.17 release is declared "broken" by RM, release 1.9.18 > undos the unwanted code change that happened in FileUtils@1.9.17 and > restores source compatibility between 2.x and 1.9.x. > > We solved 2 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=12353878 > > There are still some issues in JIRA: > https://issues.apache.org/jira/projects/MRESOLVER/issues > > Staging repository: > https://repository.apache.org/content/repositories/maven-2037 > > Source release SHA512: > > b74842017a4a2869dbe118a69d29d9eae39df33fc6f1dd056e5440c7489694aa1e6f53705a77d7a8af7a7a48301b1a6b48577486202900de358463acc3045e82 > > Staging site: > https://maven.apache.org/resolver-archives/resolver-LATEST/ > > Guide to testing staged releases: > https://maven.apache.org/guides/development/guide-testing-releases.html > > Vote open for 72 hours. > > [ ] +1 > [ ] +0 > [ ] -1 >
Release of build cache extension
Hi, I'd like to release build cache extension 1.1.0 in the next few days. Let me know if you have any issues with that. cheers Olivier - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Resolver 1.9.17
+1 On Sat, 18 Nov 2023 at 09:27, Tamás Cservenák wrote: > > Howdy, > > Note: Maven Resolver 1.x lineage is in "bugfix only" maintenance mode. > > We solved 4 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=12353659 > > There are still some issues in JIRA: > https://issues.apache.org/jira/projects/MRESOLVER/issues > > Staging repository: > https://repository.apache.org/content/repositories/maven-2032/ > > Source release SHA512: > c594df21e82b198abefb1fdad67d68c1c6eda69e279ebb9bd1e1c20e361ae40f4bab99dfc00f9699e9129760a864b703ced61322361debe3abeefafcd78f3633 > > Staging site: > https://maven.apache.org/resolver-archives/resolver-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: [VOTE] Release Maven Project Info Reports Plugin version 3.5.0
+1 On Sat, 18 Nov 2023 at 07:56, Michael Osipov wrote: > > Hi, > > we solved 3 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317821=12353875 > > There are still a couple of issues left in JIRA: > https://issues.apache.org/jira/projects/MPIR/issues > > Staging repo: > https://repository.apache.org/content/repositories/maven-2031/ > https://repository.apache.org/content/repositories/maven-2031/org/apache/maven/plugins/maven-project-info-reports-plugin/3.5.0/maven-project-info-reports-plugin-3.5.0-source-release.zip > > Source release checksum(s): > maven-project-info-reports-plugin-3.5.0-source-release.zip > sha512: > c5c9feedceacccfeec06bb503ec9e80f08a88671892cf260a0385cbde84f2bee3e283c8e62b3c1d20cf847af0e81033c618cf4fe6dbc20f2b56050331fb8a2d4 > > Staging site: > https://maven.apache.org/plugins-archives/maven-project-info-reports-plugin-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 > - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Changing Minimum Build Requirements for plugins to JDK11
oh right, sorry I didn't read correctly.
Do you want to build with Java 11 as a minimum but limit to the usage of Java 8?
What is the point?
We (as Maven developers) will have to use Java 11 to build plugins but
not be able to use Java 11 features in the code.
That sounds frustrating to me :)
Or I don't understand the change you are trying to propose?
My confusion was I read let's make java 11 as a minimum for plugins.
Which sounds a good change to me.
That's why I was thinking about some bytecode enforcer rule to check
plugins bytecode and not only dependencies so users stucked with Java
8 can add such rule.
On Tue, 14 Nov 2023 at 17:45, Olivier Lamy wrote:
>
> Hi
> Do we have a bytecode enforcer rule but for plugins?
> That would help users who are eventually stuck with Java 8 and so cannot
> upgrade plugins going to be 11 required.
>
>
>
> Cheers
> Olivier
>
>
> On Tue, 14 Nov 2023 at 5:38 am, Karl Heinz Marbaise wrote:
>>
>> Hi,
>>
>> currently we have already the build requirements for Maven Core at JDK11+
>>
>> So in consequence I would suggest to lift the minimum requirement for
>> building plugins to JDK11.
>>
>> That means also we can use "--release 8" option
>> (8) instead of
>> source/target which is not correct based on the warnings we get like:
>> "[WARNING] bootstrap class path not set in conjunction with -source 8"
>> which we get in all plugins based on the configuration in maven parent
>> using this:
>>
>> 8
>> 1.${javaVersion}
>> 1.${javaVersion}
>>
>> which is not correct because we don't use animalsniffer anymore.
>>
>> So my suggestion is to lift the JDK build requirements to JDK11...
>> and use the 8 which
>> will prevent the warning. Also brings us back the safety net which
>> animal-sniffer was before.
>>
>>
>> Later on version of maven-parent (v42?) should change the whole
>> configuration (there are some related parts like maven-pmd-plugin,
>> maven-enforcer-plugin (enforce-byte-code max)..also toolchain-plugin...
>>
>> Furthermore we could get rid of the profile for JDK11+ related to
>> spotless-maven-plugin ...
>>
>> Based on the upgrade to maven-parent v41 we could also enhance the build
>> pipelines to build on JDK21
>>
>> 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: Changing Minimum Build Requirements for plugins to JDK11
Hi
Do we have a bytecode enforcer rule but for plugins?
That would help users who are eventually stuck with Java 8 and so cannot
upgrade plugins going to be 11 required.
Cheers
Olivier
On Tue, 14 Nov 2023 at 5:38 am, Karl Heinz Marbaise
wrote:
> Hi,
>
> currently we have already the build requirements for Maven Core at JDK11+
>
> So in consequence I would suggest to lift the minimum requirement for
> building plugins to JDK11.
>
> That means also we can use "--release 8" option
> (8) instead of
> source/target which is not correct based on the warnings we get like:
> "[WARNING] bootstrap class path not set in conjunction with -source 8"
> which we get in all plugins based on the configuration in maven parent
> using this:
>
> 8
> 1.${javaVersion}
> 1.${javaVersion}
>
> which is not correct because we don't use animalsniffer anymore.
>
> So my suggestion is to lift the JDK build requirements to JDK11...
> and use the 8 which
> will prevent the warning. Also brings us back the safety net which
> animal-sniffer was before.
>
>
> Later on version of maven-parent (v42?) should change the whole
> configuration (there are some related parts like maven-pmd-plugin,
> maven-enforcer-plugin (enforce-byte-code max)..also toolchain-plugin...
>
> Furthermore we could get rid of the profile for JDK11+ related to
> spotless-maven-plugin ...
>
> Based on the upgrade to maven-parent v41 we could also enhance the build
> pipelines to build on JDK21
>
> 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
>
>
Re: [VOTE] Release Apache Maven ASF Parent 31
+1 On Thu, 9 Nov 2023 at 08:27, Slawomir Jaranowski wrote: > > Hi, > > We solved 11 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250=12353313 > > Changes since the last release for Apache Maven ASF Parent: > https://github.com/apache/maven-apache-parent/compare/apache-30...apache-31 > > Staging repo: > https://repository.apache.org/content/repositories/orgapacheapache-1036/ > https://repository.apache.org/content/repositories/orgapacheapache-1036/org/apache/apache/31/apache-31-source-release.zip > > Source release checksum(s): > apache-31-source-release.zip - SHA-512 : > b60e0ef1899ab77a44b9afe5af50087d353fc67bda991fca11815abc18514f4fea6e90c452a503d56bb342a2a1854f9b4a7f655ce48bda90c5dab67468a06316 > > Staging site: > https://maven.apache.org/pom-archives/asf-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 > > -- > Sławomir Jaranowski > > - > 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 POMs 41
+1 On Thu, 9 Nov 2023 at 08:57, Slawomir Jaranowski wrote: > > Hi, > > NOTE: Staging of Apache ASF parent 41 is required for testing. > > We solved 10 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250=12353349 > > Changes since the last release for Apache Maven POMs: > https://github.com/apache/maven-parent/compare/maven-parent-40...maven-parent-41 > > Staging repo: > https://repository.apache.org/content/repositories/maven-2026/ > https://repository.apache.org/content/repositories/maven-2026/org/apache/maven/maven-parent/41/maven-parent-41-source-release.zip > > Source release checksum(s): > maven-parent-41-source-release.zip - SHA-512 : > d3a76493f784edf7032c73b5497837d64db0441a30da1debcb99c3341748c774b791d5f88f4b825937d84394116fe72012b6da9a0dd20e5c5d890269178f6834 > > > 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 > -- > Sławomir Jaranowski > > - > 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 Clean Plugin version 3.3.2
+1 On Mon, 23 Oct 2023 at 16:11, Slawomir Jaranowski wrote: > > Hi, > > We solved 4 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317224=12353735 > > There are still a couple of issues left in JIRA: > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MCLEAN%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC > > Staging repo: > https://repository.apache.org/content/repositories/maven-2017/ > https://repository.apache.org/content/repositories/maven-2017/org/apache/maven/plugins/maven-clean-plugin/3.3.2/maven-clean-plugin-3.3.2-source-release.zip > > Source release checksum(s): > maven-clean-plugin-3.3.2-source-release.zip - SHA-512 : > 7038bca2cc3bc3cdd1dd5d9c363a19150242508e165380feac02bc1b2bf75fee695ecb6fc6f9ed10a3a1ec14f9e46d2963487400b9fce008afa423939b754c5f > > Staging site: > https://maven.apache.org/plugins-archives/maven-clean-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 > > -- > Sławomir Jaranowski - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Retire Maven Docck Plugin
+1 On Tue, 17 Oct 2023 at 08:50, Slawomir Jaranowski wrote: > > Hi, > > - Last release was in 2015 > - use Maven 2.2.1 > - we have a Maven Plugin Tools - which should be one project for build and > check Maven plugins > - no active development ... > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MDOCCK%20AND%20(%20resolution%20%3D%20Unresolved%20OR%20fixVersion%20%3D%203.0.0) > - no working with current plugins > > I therefore propose that we retire maven-docck-plugin - > https://maven.apache.org/plugins/maven-docck-plugin/ > > If this vote is successful I will make one final release of the plugin, > making it clear on the plugin site that it has been retired. > After that the source code will be moved into read-only mode. > > The process for retiring a plugin is described here: > https://maven.apache.org/developers/retirement-plan-plugins.html > > The vote is open for 72 hours. > > [ ] +1 Yes, it's about time > [ ] -1 No, because... > > [1] > > -- > Sławomir Jaranowski - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Reporting Impl version 4.0.0-M11
+1 On Sat, 14 Oct 2023 at 23:56, Herve Boutemy wrote: > > +1 > > Reproducible Build ok: reference build done with JDK 8 on Windows > > Regards, > > Hervé > > On 2023/10/13 20:39:58 Michael Osipov wrote: > > Hi, > > > > IMPORTANT: This require the following staging repositories: > > > > * Doxia 2.0.0-M8 > > * Maven Reporting API 4.0.0-M8 > > * Doxia Sitetools 2.0.0-M13 > > > > we solved 5 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12353073 > > > > There is one issue left in JIRA: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20maven-reporting-impl > > > > Staging repo: > > https://repository.apache.org/content/repositories/maven-2003/ > > https://repository.apache.org/content/repositories/maven-2003/org/apache/maven/reporting/maven-reporting-impl/4.0.0-M11/maven-reporting-impl-4.0.0-M11-source-release.zip > > > > Source release checksum(s): > > maven-reporting-impl-4.0.0-M11-source-release.zip > > sha512: > > 82616775ae4d99aaca9d17aae8efa86c4b435206dfda8367e4e1a56bc44d12806e18566ad568673b092948772e3fcdc1b697defcb2cef51e1d7551e73eeb > > > > Staging site: > > https://maven.apache.org/shared-archives/maven-reporting-impl-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 > > > > > > - > 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 Maven Site Plugin version 4.0.0-M11
+1 On Sun, 15 Oct 2023 at 00:47, Michael Osipov wrote: > > Am 2023-10-14 um 00:18 schrieb Michael Osipov: > > Hi, > > > > IMPORTANT: This require the following staging repositories: > > > > * Doxia 2.0.0-M8 > > * Maven Reporting API 4.0.0-M8 > > * Doxia Sitetools 2.0.0-M13 > > * Maven Reporting Impl 4.0.0-M11 > > * Maven Reporting Exec 4.0.0-M11 > > > > we solved 5 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317923=12353714 > > > > There are still a couple of issues left in JIRA: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSITE%20AND%20resolution%20%3D%20Unresolved > > > > Staging repo: > > https://repository.apache.org/content/repositories/maven-2005/ > > https://repository.apache.org/content/repositories/maven-2005/org/apache/maven/plugins/maven-site-plugin/4.0.0-M11/maven-site-plugin-4.0.0-M11-source-release.zip > > > > Source release checksum(s): > > maven-site-plugin-4.0.0-M11-source-release.zip > > sha512: > > fc628fca1fd2c3629a89da9c44b64994e1b5478a7b8f5d465328cdde8064e3f1212768a4053e563160cf08cece96cf8af5a8cd936d9c1b5eafb90bcc922d933f > > > > Staging site: > > https://maven.apache.org/plugins-archives/maven-site-plugin-LATEST/ > > > > Guide to testing staged releases: > > https://maven.apache.org/guides/development/guide-testing-releases.html > > > > Vote open for 72 hours. > > +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
Re: [VOTE] Release Apache Maven Doxia Sitetools version 2.0.0-M13
+1 On Mon, 16 Oct 2023 at 07:47, Slawomir Jaranowski wrote: > > +1 > > pt., 13 paź 2023 o 22:10 Michael Osipov napisał(a): > > > Hi, > > > > we solved 3 issues: > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317320=12353711 > > > > There are still a couple of issues left in JIRA: > > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317320%20AND%20status%20%3D%20Open > > > > Staging repo: > > https://repository.apache.org/content/repositories/maven-2002 > > > > https://repository.apache.org/content/repositories/maven-2002/org/apache/maven/doxia/doxia-sitetools/2.0.0-M13/doxia-sitetools-2.0.0-M13-source-release.zip > > > > Source release checksum(s): > > doxia-sitetools-2.0.0-M13-source-release.zip > > sha512: > > > > 0aa7aa72dd71136acd2ce207ebc01ff893b6f1dbff2a025cf998b4e06103e30924c5bd5030546c349ad7040538fb04b5b06fd877da346dda19ca68d23e08272c > > > > Staging site: > > > > https://maven.apache.org/doxia/doxia-sitetools-archives/doxia-sitetools-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 > > > > > > -- > Sławomir Jaranowski - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Reporting Exec version 2.0.0-M11
+1 On Sat, 14 Oct 2023 at 23:57, Herve Boutemy wrote: > > +1 > > Reproducible Build ok: reference build done with JDK 8 on Windows > > Regards, > > Hervé > > On 2023/10/13 20:58:45 Michael Osipov wrote: > > Hi, > > > > IMPORTANT: This require the following staging repositories: > > > > * Doxia 2.0.0-M8 > > * Maven Reporting API 4.0.0-M8 > > * Doxia Sitetools 2.0.0-M13 > > * Maven Reporting Impl 4.0.0-M11 > > > > we solved 3 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12353712 > > > > There are still a couple of issues left in JIRA: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20maven-reporting-exec > > > > Staging repo: > > https://repository.apache.org/content/repositories/maven-2004/ > > https://repository.apache.org/content/repositories/maven-2004/org/apache/maven/reporting/maven-reporting-exec/2.0.0-M11/maven-reporting-exec-2.0.0-M11-source-release.zip > > > > Source release checksum(s): > > maven-reporting-exec-2.0.0-M11-source-release.zip > > sha512: > > 824ae603848338a3b2addfd4bcdee0dbcfded1b133daf91f8b7189e7cc06b9e3ad59a916f61ee6fb02945d16075fc39edd647551b1489e5c5b22b286fea79746 > > > > Staging site: > > https://maven.apache.org/shared-archives/maven-reporting-exec-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 > > > > > > - > 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: [DISCUSS] Maven Resolver 2.x HTTP/2 transport modules
On Sat, 14 Oct 2023 at 10:51, Tamás Cservenák wrote: > > Howdy, > > ok, so I think agreed on the name (and artifactId) of the two new module: > * maven-resolver-transport-jdk (uses Java11+ java.net.http.HttpClient) > * maven-resolver-transport-jetty (uses Jetty HttpClient, probably 12.x) no need real of Jety 12. This will not make a real difference except to make Java 17 mandatory. > > and the existing ones are: > > * maven-resolver-transport-classpath (CP transport, is not HTTP, just FTR) > * maven-resolver-transport-file (file transport, is not HTTP, just FTR) > * maven-resolver-transport-http (uses Apache HttpClient 4.x, HTTP/1.1 > capable) > > Cannot rename the misleading "-http" one, as that would cause disruption > with existing code, we have to live with it for now (to be renamed in > resolver 3.0 or so) :( > Aren't we already talking now about a jump from 1.9.x to 2.x :) relocation if so desperate? > As for CLI names and Maven4 inclusion in distro (these are Maven4 changes, > not resolver changes), I'd propose: > * "jdk" included in distro > * "jetty" not included in distro (users can add it via .mvn/extensions.xml) > * "apache" (and deprecated CLI synonym "native") included in distro > * maven-resolver-transport-wagon is to be dropped from Maven4 (not shipped > by default, users can add it as core extension and make it work via > standard resolver priority mechanism. Wagon itself IS present in the Maven4 > core, as it is required for Maven3 compatibility provided by Maven4). > > Transport priorities (how Resolver selects transport if multiple one exists > for same protocol): > wagon = -1.0f (unchanged, same as today) > https://github.com/apache/maven-resolver/blob/maven-resolver-1.9.16/maven-resolver-transport-wagon/src/main/java/org/eclipse/aether/transport/wagon/WagonTransporterFactory.java#L47 > apache = 5.0f (unchanged, same as today) > https://github.com/apache/maven-resolver/blob/maven-resolver-1.9.16/maven-resolver-transport-http/src/main/java/org/eclipse/aether/transport/http/HttpTransporterFactory.java#L51 > jdk = 10.0f (proposed, to prevail "apache" transport, both will be present > in distro) > jetty = 15.0f (proposed, to prevail "jdk" transport, if present) > > Note re priorities: Resolver "prioritized components" mechanism was present > since day 0 of resolver, and its purpose was to select a given > implementation if multiple ones are suited (like in our case, > TransportFactory for HTTP URL). Before Maven 3.9, wagon transport was the > ONLY HTTP capable transport present on classpath, so selection was trivial. > In Maven 3.9 both wagon and apache transports were present in distro, and > apache "prevails" by default (due default priorities, while CLI switches > tweak priorities). To not introduce changes in this area, the idea is to > position jdk transport above apache (hence priority 10, to prevail apache, > become default), while jetty priority of 15 (it is not present in distro by > default) is simply to make it "if present, it prevails". So to say, to > simplify users' lives who took effort to set it as a core extension (and to > not have to tweak more than that). +1 lgtm > > Note1: Essentially we can play "same game" as we did with Maven 3.9: we > will switch default transport AGAIN IF user uses Java11+ (but this time > from apache/native to jdk), providing fallback for users hitting a blocker > bug in the form of `-Dmaven.resolver.transport=apache`, and for those still > relying on Wagon (ie. using legacy config), they would need two steps a) > make wagon transport be in .mvn/extensions.xml and b) use > `-Dmaven.resolver.transport=wagon`. I believe this is acceptable, while we > are in "alpha" with Maven 4. Of course, this last paragraph is just a > proposal, does not have to happen (we can make it in 4.1 or alike). > Note2: the "...if user uses Java11+" is nicely handled by Sisu. If Maven4 > remains Java8 bytecode level, and the user uses Java8 to run Maven4, Sisu > will silently omit jdk transport (as Java8 will be unable to load the > Java11 bytecode). > > If anyone objects, please yell here. Otherwise will continue along > these lines. > > Thanks > T > > > > On Fri, Oct 13, 2023 at 1:12 PM Romain Manni-Bucau > wrote: > > > Le ven. 13 oct. 2023 à 11:07, Tamás Cservenák a > > écrit : > > > > > Howdy, > > > > > > Maven Central supports HTTP/2 for quite some time. > > > Google Mirror of Maven Central in the EU has supported HTTP/3 since a > > while > > > ago. > > > > > > And while I agree that HTTP/2 over HTTP/1.1 is not huge diff (it is, for > > > example in the sense of used ports, that may be important on farm-sized > > CI, > > > also there is noticeable perf improvement as well), the real boost will > > be > > > probably HTTP/3. Sadly, a year or more ago, when I did perf testing, > > > Jetty12 was still alpha, but I wonder what HTTP/3 numbers would be today. > > > > > > > Until you protect servers against ddos, so we shouldnt benefit from there > > and boost is
Re: [DISCUSS] Maven Resolver 2.x HTTP/2 transport modules
btw be careful with jdk httpclient as it doesn't really a way to
cleanup resources (see https://bugs.openjdk.org/browse/JDK-8304165)
could be an issue with mvnd
On Fri, 13 Oct 2023 at 19:20, Christoph Läubrich wrote:
>
> You can find JDK http client debugging / configuration options here:
>
> https://docs.oracle.com/en/java/javase/20/docs/api/java.net.http/module-summary.html
>
> sadly they seem not configurable per cbut only globally but probably
> someone like to suggest this to the JDK team (e.g. something like
> builder.setProperty(...) )
>
>
> Am 13.10.23 um 10:28 schrieb Michael Osipov:
> > I agree that this is a full rewrite, sadly.
> >
> > Have you evaluated what degree of logging both JEtty Client and the JDK
> > Client offer? I consider the JDK client likely as useless in this regard.
> > Don't know about Jetty. At least AHC saved me a lot of trouble...
> >
> > On 2023/10/13 08:23:33 Tamás Cservenák wrote:
> >> And just add more context about transports:
> >>
> >> Currently we have Wagon and AHC 4.x ("native") transport in Maven (since
> >> 3.9). Numbers show that "native" is far superior over Wagon (I think we can
> >> all agree on this).
> >>
> >> Sadly, "native" relies on EOL (or soon EOL?) library AHC 4.x (that is one
> >> of the best HTTP libraries I used), and this implies we are stuck with
> >> HTTP/1.1 only and (probably, hopefully?) bugfix releases only. Ironically,
> >> the moment we provided "superior" HTTP transport in Maven, we got stuck at
> >> the same time. While there is AHC 5.x (sync, that is not HTTP/2 capable,
> >> and async, both require heavy rewrite), switching to it requires _full
> >> rewrite_ as mentioned. Plus the "go async" if you want to leverage any new
> >> protocol. Basically it is like writing resolver transport from scratch.
> >>
> >> Hence, I think it is more sane to invest our effort into something more
> >> stable, that at the same time gives us (promises us) future headroom as
> >> well, and IMHO JDK/JRE net.http.HttpClient and (in my experience) Jetty
> >> HttpClient are such things. There is no need for _full rewrite_ between
> >> major versions.
> >>
> >> In the longer term, this will actually lower the needed effort to maintain
> >> these resolver transports, while at the same time prevent us being cornered
> >> again.
> >>
> >> On Fri, Oct 13, 2023 at 10:11 AM Tamás Cservenák
> >> wrote:
> >>
> >>> Howdy,
> >>>
> >>> Re perf (and this was already discussed about a year ago, please do not
> >>> derail discussion): look around
> >>> https://github.com/apache/maven-resolver/pull/231 and related JIRAs,
> >>> there are the numbers. TL;DR: jetty and jdk clients are consistently
> >>> fastest and are "side by side" (with the benefit of Jetty doing HTTP/3 as
> >>> well, but with the downside of huge dep trail), while Wagon is
> >>> consistently
> >>> the slowest. Differences wildly differ but are very notable.
> >>>
> >>> Personally, I am not interested in doing a full rewrite of existing AHC
> >>> transport (as the expected amount of bugs doing this is pretty much on par
> >>> with doing fully new transport from scratch). I'd rather just choose a
> >>> library with a more stable API, like Jetty is. Moreover, forcing "async"
> >>> style in 2023 is something I'd avoid in today's written Java code (esp
> >>> with
> >>> 21 virtual threads). But sure, if you want to do it, go for it (this work
> >>> would at least move Maven as a project forward, not backward).
> >>>
> >>> On Fri, Oct 13, 2023 at 9:52 AM Michael Osipov
> >>> wrote:
> >>>
> Regardless of the names, the following questions code to my mind:
>
> * Does it make sense to put effort into too many clients?
> * How many users will actually switch the client? I bet < 10%
>
> olegk@ and me assessed many times on JIRA that HTTP/2 will have little
> performance benefit for our use case of transport. I'd like to see a move
> to Apache HttpClient 5 Async which does everything, but that is work.
> Having both AHC async and Jetty HTTP Client is a logical overlap and
> unnecessary maintenance burden. While I know nothing about the Jetty
> Client, the AHC (any version) has exceptional logging output down to
> bytes
> of streams which helps very often to analyze problem with users.
>
> I personally refuse and close out issue on JIRA where the user is not
> able to present that kind of debugging information. Poking in the dark.
>
> M
>
> -
> 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: [DISCUSS] Maven Resolver 2.x HTTP/2 transport modules
On Fri, 13 Oct 2023 at 19:12, Tamás Cservenák wrote: > > I prefer "jdk" over "jre", as IMHO using the term "jre" would be confusing > for users. > When Oracle dropped delivering standalone "jre", users stopped using the > term as well. Also, a long time ago, there was constant confusion > that Maven needed JDK and not JRE to run, as users were by mistake > installing JREs and failed to get full Maven functionality... (am talking > about 2000s :) ). yup jdk makes more sense to me as well (as anyway Maven users have a jdk as they are compiling sources. Regarding logs with Jetty, no worries you can even get more than what you really need :) Jetty have a nice easy to use async API (it's the natural usage of it) http2 sounds a good nice to have (even if it doesn't improve so much performance at least this can reduce load on server by reducing concurrent connection number) http3 not sure it;s something to focus on at least now... > > IMHO, if we start using the term "jre" today, that might just confuse > users... > > my 5 cents. > > On Fri, Oct 13, 2023 at 9:50 AM Romain Manni-Bucau > wrote: > > > s/jdk/jre/ otherwise agree > > > > Le ven. 13 oct. 2023 à 09:38, Tamás Cservenák a > > écrit : > > > > > Howdy, > > > > > > I am leaning toward: > > > maven-resolver-transport-jetty (name "jetty") <- NEW > > > maven-resolver-transport-jdk (name "jdk") <- NEW > > > maven-resolver-transport-http (name "http", CLI name "native") w/o module > > > rename > > > maven-resolver-transport-file > > > maven-resolver-transport-classpath > > > > > > As I agree with above mentioned reasons (jetty version, etc) but I would > > > not go for existing -http module rename, as we promised "simple upgrade" > > > for Resolver 1.x users... In short, code that works with 1.x resolver > > > should still work unchanged with 2.x resolver (if it does not use > > > deprecated stuff that is about to be dropped). > > > > > > The "name" is actually Sisu component name (ATNamed), but is also a short > > > name used on Maven CLI to select transport. Again, "native" is cuckoo egg > > > here, rest is nicely aligned. > > > > > > Maven4 could advertise existing maven-resolver-transport-http as CLI name > > > "something else" instead of "native" (but offer some transition period > > > supporting "native" CLI name as well)... > > > > > > Re CLI name, we could offer indirection, like following "meta names" that > > > may mean one or more actual transport implementations (am talking about > > CLI > > > param maven.resolver.transport): > > > - "http": means jdk, jetty, http > > > - "http1": means jdk, jetty, http > > > - "http2": means jdk, jetty > > > - "http3": means jetty > > > > > > etc > > > > > > Hence, I'd: > > > - not rename (change artifactId) the existing Apache HttpClient 4.x > > backed > > > transport module (would break code using 1.x) > > > - name new modules simply -jetty and -jdk (with corresponding "names" as > > > well, have those aligned) > > > - transition badly named "native" on CLI into something else (but what?) > > > > > > On Fri, Oct 13, 2023 at 9:08 AM Christoph Läubrich > > > wrote: > > > > > > > maybe better > > > > > > > > - jdk impl -> jdk > > > > - jetty -> jetty > > > > - current apache -> apache > > > > > > > > Am 13.10.23 um 02:30 schrieb Olivier Lamy: > > > > > On Fri, 13 Oct 2023 at 07:36, Tamás Cservenák > > > > wrote: > > > > >> > > > > >> Currently the names are like these: > > > > >> > > > > > > > > > https://github.com/apache/maven/blob/maven-3.9.x/maven-core/src/main/java/org/apache/maven/internal/aether/DefaultRepositorySystemSessionFactory.java#L107-L109 > > > > >> > > > > >> So "wagon", "native" (for maven-resolver-transport-http), and "auto" > > > (to > > > > >> apply Resolver built-in auto selection. > > > > >> Hence, I envision "jetty" and "jdk"? > > > > > > > > > > jetty sounds good. > > > > > But frankly native looks wrong to m
Re: [DISCUSS] Maven Resolver 2.x HTTP/2 transport modules
On Fri, 13 Oct 2023 at 07:36, Tamás Cservenák wrote: > > Currently the names are like these: > https://github.com/apache/maven/blob/maven-3.9.x/maven-core/src/main/java/org/apache/maven/internal/aether/DefaultRepositorySystemSessionFactory.java#L107-L109 > > So "wagon", "native" (for maven-resolver-transport-http), and "auto" (to > apply Resolver built-in auto selection. > Hence, I envision "jetty" and "jdk"? jetty sounds good. But frankly native looks wrong to me (wrong marketing :)) as it is using apache httpclient so this would deserve to be named with what is reality used. reading from the outside using native currently gives a false idea about what is really used. native for me means C code :) native sounds more appropriate for the "jdk native" implementation. maybe the naming could be fixed now with 2.0.0 upgrade. such: - jdk impl -> native - jetty -> jetty - current apache -> htttpciient to have some backward compact maybe auto could use htttpciient just some thought from the peanut gallery. > > T > > On Thu, Oct 12, 2023 at 11:01 PM Olivier Lamy wrote: > > > On Fri, 13 Oct 2023 at 05:52, Guillaume Nodet wrote: > > > > > > Le jeu. 12 oct. 2023 à 21:15, Tamás Cservenák a > > > écrit : > > > > > > > Howdy, > > > > > > > > As part of the new Resolver major version, one of the goals is to > > introduce > > > > HTTP/2 capable transports. And as always, naming... > > > > > > > > Current transport module names (==artifactId) are (already quite long > > for > > > > my taste): > > > > * maven-resolver-transport-classpath (CP transport, is not HTTP, just > > FTR) > > > > * maven-resolver-transport-file (file transport, is not HTTP, just FTR) > > > > * maven-resolver-transport-http (uses Apache HttpClient 4.x, HTTP/1.1 > > > > capable) > > > > * maven-resolver-transport-wagon (uses Wagon, so is not only HTTP, > > HTTP/1.1 > > > > capable) > > > > > > > > > > Is wagon something we still want to push forward ? > > > > > > > > > > > > > > And now the two new contenders: > > > > * Java11+ java.net.http.HttpClient based (HTTP/2 capable) > > > > * Java11+ Jetty12 based (HTTP/2 capable) > > > > > > > > So, the major question is how to name these modules (== artifactId)? > > > > > > > > * maven-resolver-transport-java11? > > > > > > * maven-resolver-transport-jetty12? > > > > > > > > Maybe some form of proto+imple? > > > > > > > > * maven-resolver-transport-http2-java11 (or shorter > > > > maven-resolver-transport-h2-java11) > > > > > > > > > > Http is enough imho. Which version is supported by which implementation > > is > > > an internal detail. Unless there are HTTP/2 server which does not > > support > > > HTTP/1.1 in which case it could become relevant. Or any client > > supporting > > > HTTP/2 and not HTTP/1.1... > > > > > > > > > > > > > * maven-resolver-transport-http2-jetty (or shorter > > > > maven-resolver-transport-h2-jetty) > > > > > > > > > > agree on the no need of Jetty version. > > We should be able to use Jetty transport for http1 as well (the Jetty > > client can support multiple protocols including http3). > > maybe maven-resolver-transport-jetty (as it shouldn't have an http2 > > limitation) > > > > what will be the names to use in poms or cli to activate those > > transporters? > > Maybe we should keep them short to not have an extra long > > configuration esp when using cli. > > > > > > > > I like the longest better because they are more descriptive of what they > > > actually are. > > > So protocol + client sounds fine. > > > > > > > > > > > > > > But there are not ONLY HTTP/2 (they are also HTTP/1.1 capable as well). > > > > Also, the Jetty version matters, so once in future there will be > > Jetty13 > > > > etc... > > > > > > > > > > Do we really care ? We need different providers if they provide different > > > things. I don't think jetty 12 provides anything different than jetty > > 13. > > > In addition, we won't be able to ship both jetty 12 and jetty 13 at the > > > same time, so I think we can keep a single one, which means we can drop > >
Re: [DISCUSS] Maven Resolver 2.x HTTP/2 transport modules
On Fri, 13 Oct 2023 at 05:52, Guillaume Nodet wrote: > > Le jeu. 12 oct. 2023 à 21:15, Tamás Cservenák a > écrit : > > > Howdy, > > > > As part of the new Resolver major version, one of the goals is to introduce > > HTTP/2 capable transports. And as always, naming... > > > > Current transport module names (==artifactId) are (already quite long for > > my taste): > > * maven-resolver-transport-classpath (CP transport, is not HTTP, just FTR) > > * maven-resolver-transport-file (file transport, is not HTTP, just FTR) > > * maven-resolver-transport-http (uses Apache HttpClient 4.x, HTTP/1.1 > > capable) > > * maven-resolver-transport-wagon (uses Wagon, so is not only HTTP, HTTP/1.1 > > capable) > > > > Is wagon something we still want to push forward ? > > > > > > And now the two new contenders: > > * Java11+ java.net.http.HttpClient based (HTTP/2 capable) > > * Java11+ Jetty12 based (HTTP/2 capable) > > > > So, the major question is how to name these modules (== artifactId)? > > > > * maven-resolver-transport-java11? > > * maven-resolver-transport-jetty12? > > > > Maybe some form of proto+imple? > > > > * maven-resolver-transport-http2-java11 (or shorter > > maven-resolver-transport-h2-java11) > > > > Http is enough imho. Which version is supported by which implementation is > an internal detail. Unless there are HTTP/2 server which does not support > HTTP/1.1 in which case it could become relevant. Or any client supporting > HTTP/2 and not HTTP/1.1... > > > > > * maven-resolver-transport-http2-jetty (or shorter > > maven-resolver-transport-h2-jetty) > > agree on the no need of Jetty version. We should be able to use Jetty transport for http1 as well (the Jetty client can support multiple protocols including http3). maybe maven-resolver-transport-jetty (as it shouldn't have an http2 limitation) what will be the names to use in poms or cli to activate those transporters? Maybe we should keep them short to not have an extra long configuration esp when using cli. > > I like the longest better because they are more descriptive of what they > actually are. > So protocol + client sounds fine. > > > > > > But there are not ONLY HTTP/2 (they are also HTTP/1.1 capable as well). > > Also, the Jetty version matters, so once in future there will be Jetty13 > > etc... > > > > Do we really care ? We need different providers if they provide different > things. I don't think jetty 12 provides anything different than jetty 13. > In addition, we won't be able to ship both jetty 12 and jetty 13 at the > same time, so I think we can keep a single one, which means we can drop the > version. > Which version we ship is a separate discussion and it impacts the runtime > JDK requirements I suppose. > > Same for java11, maybe jdk would be better to indicate this is the http > client from the jdk (if you're using jdk 17, that one will be used, not the > one from jdk 11). I do understand it has been introduced in JDK 11, but > still... > > So in short, i'd go for: > maven-resolver-transport-http-jetty > maven-resolver-transport-http-jdk > maven-resolver-transport-http-httpclient > maven-resolver-transport-file > maven-resolver-transport-classpath > > Cheers > Guillaume > > > > > > > Ideas welcome. > > > > Thanks > > T > > > > PS: Given java.net.http.HttpClient based transport will be dependency-less, > > it reminds me of good old wagon-http-lightweight, but unlike wagon one > > (that was quite limited), this will be fully capable transport. > > > > > -- > > Guillaume Nodet - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven 3.9.5
+1 tested with various projects no issue found. thanks! On Mon, 2 Oct 2023 at 05:07, Tamás Cservenák wrote: > > Howdy, > > Note: This release completes the main goals of Maven 3.9.x lineage, among > others moving to Java 8 and transition to latest Resolver 1.9.x features > (new robust transports, local repository locking, provided checksums, > remote repository filtering and more). Maven Resolver 1.9.x lineage is > already in "bugfix only" (no new features) maintenance mode, and this makes > Maven 3.9.x lineage getting into this maintenance mode as well. I do > foresee some more Maven 3.9.x releases with usual fluff (bug fixes, > lifecycle plugin updates), but the focus should move to upcoming Maven 4, > Resolver 2 and mvnd (at least when "core" is considered). > > --- > > We solved 8 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12353460 > > There are still a couple of issues left in JIRA: > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20resolution%20%3D%20Unresolved > > Staging repo: > https://repository.apache.org/content/repositories/maven-1995 > > Dev dist directory (binary bundles updated): > https://dist.apache.org/repos/dist/dev/maven/maven-3/3.9.5/ > > Source release checksums: > apache-maven-3.9.5-src.zip sha512: > f1e7f36a6423c4f6d98e599120ede3a9f9f62448edeb2d49ffbdc05e36548190049bc83aae4f49e3305da1060d7b8e49477a55cb78b938951fd41ab3d360995f > > apache-maven-3.9.5-src.tar.gz sha512: > fd8f9c4f3c6af001d11146102ba491b248163cd45d8be16907f7dcdc763eef4a081a02286b28a74de7f48c3f377a0a4491d2fa9155c906466aa3c831a5b4ef8e > > Staged site: > https://maven.apache.org/ref/3-LATEST/ > > Draft for release notes: > https://github.com/apache/maven-site/pull/458 > > Guide to testing staged releases: > http://maven.apache.org/guides/development/guide-testing-releases.html > > Vote open for 72h > > [ ] +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 Maven Resolver 1.9.16
+1 On Sat, 23 Sept 2023 at 04:29, Tamás Cservenák wrote: > > Howdy, > > Note: Maven Resolver 1.x lineage after this release is going into "bugfix > only" maintenance mode (and will be branched off as maven-resolver-1.9.x), > while master branch will become 2.x. > > We solved 6 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=12353482 > > There are still some issues in JIRA: > https://issues.apache.org/jira/projects/MRESOLVER/issues > > Staging repository: > https://repository.apache.org/content/repositories/maven-1991 > > Source release SHA512: > b9a03c88bcb21c6bc0af3faf0b8fdf0001e9c2250957f715333e195730350ad5e4519069786f88990f22ac87b7b513d8c84ca5ffbb160ecca2fd0986b89da3da > > Staging site: > https://maven.apache.org/resolver-archives/resolver-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: [VOTE] Release Apache Maven Shade Plugin version 3.5.1
+1 On Fri, 22 Sept 2023 at 05:53, Slawomir Jaranowski wrote: > > Hi, > > We solved 4 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317921=12353341 > > There are still a couple of issues left in JIRA: > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHADE%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC > > Staging repo: > https://repository.apache.org/content/repositories/maven-1990/ > https://repository.apache.org/content/repositories/maven-1990/org/apache/maven/plugins/maven-shade-plugin/3.5.1/maven-shade-plugin-3.5.1-source-release.zip > > Source release checksum(s): > maven-shade-plugin-3.5.1-source-release.zip - SHA-512 : > 02a72361203356dfccd4a4dca9459e9ef9e7b7e3852500633de920200c3525ef28bdf5e585791105dbf62ab61050c65300fc1d58495983307ddb58e9562e58c8 > > 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 > > -- > Sławomir Jaranowski - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Enforcer version 3.4.1
+1 On Fri, 8 Sept 2023 at 03:40, Slawomir Jaranowski wrote: > > Hi, > > We solved 2 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317520=12353576 > > There are still a couple of issues left in JIRA: > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MENFORCER%20AND%20resolution%20%3D%20Unresolved > > Staging repo: > https://repository.apache.org/content/repositories/maven-1987/ > https://repository.apache.org/content/repositories/maven-1987/org/apache/maven/enforcer/enforcer/3.4.1/enforcer-3.4.1-source-release.zip > > Source release checksum(s): > enforcer-3.4.1-source-release.zip - SHA-512 : > 64fcd4a97487ae50976426da63f3ba58cb0fe47a72235afa8f05e5d6e8118ad09dbc8269c5ff106ab1e274dd54e439c737585df1232b85be7ea202aee6ac5864 > > Staging site: > https://maven.apache.org/enforcer-archives/enforcer-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 > > -- > Sławomir Jaranowski - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [DISCUSS] Major changed for 4.x
Hi, On Tue, 22 Aug 2023 at 17:36, Guillaume Nodet wrote: > > Hi everyone, > > I hope you guys have been able to rest a bit during the summer (for those > that are back to work already)... > > I've pushed a few important PRs in the past months and I'd really like to > get the discussion going around those. Those are major changes that I > think we should introduce in Maven 4 asap: > * Better support for alternative POM syntaxes > * Needed infrastructure to evolve the model > * POM mixins > * Support for XML entities / XInclude I really like the idea of being able to improve the model. I find a bit scary the idea of XML entities/XInclude especially for all the possible security problems that I can imagine coming with that. No real example in mind, but I had so many issues problems in the last 10 years with XML entities/XInclude :) but maybe I'm wrong. how do you exactly plan to do that? > > The first 3 changes are stacked onto each other. The first one is the > support for alternative POM syntaxes [2]. Note that no syntax is provided > by the PR, but an example extension is provided in the IT PR [3], the > reader being generated using the maven model and the IT's project is using > it [4]. The main idea is to provide an enhanced XML syntax if we want, as > it was discussed for the POM 5.0 [5]. > > The second one provides the ability to make evolution to the model without > breaking the maven ecosystem. The model has been stuck in 4.0.0 version > for 15 years or so, most of the things that would have required a change > have been delayed or worked around. The consumer POM that has been > introduced in Maven 4 is a first step, but I think we should go further. > Please read the details in the PR [6]. > > The third one is the support for POM mixins [7]. That one is still a > draft. Two ITs have been written to leverage mixins using GAV or as > relative paths [8]. This definitely needs some work, but the current state > definitely shows that it can be implemented and introduced in the next > alphas. > > The last one is a relatively small PR [9] which brings support for XML > entities and XInclude loaded from external files. All loaded files are > loaded using relative URLs (absolute URLs are rejected for security > reasons). The entities and xinclude bits are all inlined during the raw -> > consumer POM transformation so that they don't appear in repositories. I > wrote this PR as a possible alternative for mixins, that's the main reason > why I include it in this discussion. > > I'm not necessarily looking for in-depth reviews of the PRs, but at least > to find a consensus and general agreement on the way forward. > > Cheers, > Guillaume > > [2] https://github.com/apache/maven/pull/1197 > [3] > https://github.com/apache/maven-integration-testing/pull/276/files#diff-ffb3dec529cab94ebf3c5830444275ad2b2e4826fe1df843454882efadd2446c > [4] > https://github.com/apache/maven-integration-testing/pull/276/files#diff-8d7362e60d231ad8c5d4b7746873da2855d9cf1fd5aeeca9c143ed942bd94b38 > [5] > https://cwiki.apache.org/confluence/display/MAVEN/POM+Model+Version+5.0.0 > [6] https://github.com/apache/maven/pull/1160 > [7] > https://github.com/apache/maven/pull/1209/commits/211e27acd21a6cb8cee30ccd066499fc613a5c82 > [8] > https://github.com/apache/maven-integration-testing/tree/b2642d74caae854051dc77acd19b972dfe66b1cd/core-it-suite/src/test/resources/mng-5102-mixins > [9] https://github.com/apache/maven/pull/1205 > > -- > > Guillaume Nodet - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [maven-build-cache-extension] branch master updated: remove unused logback dependency (#88)
-1 Please revert this commit.
I'm the only one to express some concerns about such change.
Se conversations here
https://github.com/apache/maven-build-cache-extension/pull/88#issuecomment-1694496822
On Sat, 26 Aug 2023 at 23:33, wrote:
>
> This is an automated email from the ASF dual-hosted git repository.
>
> elharo pushed a commit to branch master
> in repository
> https://gitbox.apache.org/repos/asf/maven-build-cache-extension.git
>
>
> The following commit(s) were added to refs/heads/master by this push:
> new 47f8404 remove unused logback dependency (#88)
> 47f8404 is described below
>
> commit 47f8404c256fa51ea2ce819eb782de88c36c2bd5
> Author: Elliotte Rusty Harold
> AuthorDate: Sat Aug 26 09:31:34 2023 -0400
>
> remove unused logback dependency (#88)
> ---
> pom.xml| 6 --
> src/test/resources/logback.xml | 40
> 2 files changed, 46 deletions(-)
>
> diff --git a/pom.xml b/pom.xml
> index 1c11381..8dc816c 100644
> --- a/pom.xml
> +++ b/pom.xml
> @@ -188,12 +188,6 @@ under the License.
>junit-jupiter
>test
>
> -
> - ch.qos.logback
> - logback-classic
> - 1.3.11
> - test
> -
>
>org.slf4j
>log4j-over-slf4j
> diff --git a/src/test/resources/logback.xml b/src/test/resources/logback.xml
> deleted file mode 100644
> index 88be419..000
> --- a/src/test/resources/logback.xml
> +++ /dev/null
> @@ -1,40 +0,0 @@
> -
> -
> -
> -
> - />
> -
> -
> -
> - %-4relative [%thread] %-5level %logger{64} - %msg %n
> -
> -
> -
> - name="org.apache.maven.buildcache.BuildCacheMojosExecutionStrategy"
> level="debug"/>
> -
> -
> -
> -
> -
> -
>
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
