Re: [VOTE] Release Maven Deploy Plugin 3.1.2
+1 On Fri, Apr 26, 2024 at 12: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 > -- Arnaud Héritier Twitter/GitHub/... : aheritier
Re: [VOTE] Release Maven Resolver 1.9.20
+1 On Fri, Apr 26, 2024 at 1:01 PM 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 > -- Arnaud Héritier Twitter/GitHub/... : aheritier
Re: [VOTE] Release Maven Install Plugin 3.1.2
+1 On Fri, Apr 26, 2024 at 12:41 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 > -- Arnaud Héritier Twitter/GitHub/... : aheritier
Re: [VOTE] Require Java 17 for Maven 4
+1. It’s time to move on. Arnaud Héritier Twitter/GitHub/... : aheritier Le mer. 28 févr. 2024 à 08:31, Benjamin Marwell a écrit : > 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 > >
Re: [VOTE] Release Maven PMD Plugin version 3.21.2
+1 On Thu, Nov 2, 2023 at 7:43 PM Slawomir Jaranowski wrote: > +1 > > pon., 30 paź 2023, 22:11 użytkownik Michael Osipov > napisał: > > > Hi, > > > > we solved 6 issues: > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317621=12353789 > > > > There are still a couple of issues left in JIRA: > > > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MPMD%20AND%20resolution%20%3D%20Unresolved > > > > Staging repo: > > https://repository.apache.org/content/repositories/maven-2020/ > > > > > https://repository.apache.org/content/repositories/maven-2020/org/apache/maven/plugins/maven-pmd-plugin/3.21.2/maven-pmd-plugin-3.21.2-source-release.zip > > > > Source release checksum(s): > > maven-pmd-plugin-3.21.2-source-release.zip > > sha512: > > > > > deaa2e85cf14eca370b5fca81985c1ee897075e2e60a8c61f5a6743bec53f949d23b182174f47b8645c2b192c3105377ca56944f8ebbda506e73839d61a78ae7 > > > > Staging site: > > https://maven.apache.org/plugins-archives/maven-pmd-plugin-LATEST/ > > > > Guide to testing staged releases: > > https://maven.apache.org/guides/development/guide-testing-releases.html > > > > Vote open for 72 hours. > > > > [ ] +1 > > [ ] +0 > > [ ] -1 > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > -- Arnaud Héritier Twitter/GitHub/... : aheritier
Re: [VOTE] Release Apache Maven Daemon 1.0-m8
+1 On Thu, Nov 2, 2023 at 8:47 AM Slawomir Jaranowski wrote: > +1 > > czw., 26 paź 2023 o 08:44 Guillaume Nodet napisał(a): > > > I've staged a candidate release at > > https://dist.apache.org/repos/dist/dev/maven/mvnd/1.0-m8/ > > > > This release provides distributions based on Maven 3.9.5 and > > 4.0.0-alpha-8 releases. > > The release notes are available at : > > > > > https://github.com/apache/maven-mvnd/releases/tag/untagged-56be0cecfa7305fcd889 > > > > Please review and vote ! > > -- > > > > Guillaume Nodet > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > > -- > Sławomir Jaranowski > -- Arnaud Héritier Twitter/GitHub/... : aheritier
Re: [VOTE] Release Apache Maven 3.9.5
gt; > (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; > > > > > version=12353460> > > > > > > > There are still a couple of issues left in JIRA: > > > > > > > > > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20res > > > > > olution%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: > > > > > > > > > > > f1e7f36a6423c4f6d98e599120ede3a9f9f62448edeb2d49ffbdc05e36548190049bc83aae > > > > > 4f49e3305da1060d7b8e49477a55cb78b938951fd41ab3d360995f> > > > > > > > apache-maven-3.9.5-src.tar.gz sha512: > > > > > > > > > > > fd8f9c4f3c6af001d11146102ba491b248163cd45d8be16907f7dcdc763eef4a081a02286b > > > > > 28a74de7f48c3f377a0a4491d2fa9155c906466aa3c831a5b4ef8e> > > > > > > > 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 > > > > > > > > > > > - > > > > > 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 > > > > > > > > > > > -- > Sławomir Jaranowski > -- Arnaud Héritier Twitter/GitHub/... : aheritier
Re: [VOTE] Release Apache Maven 3.9.4 -- take two
+1 Le lun. 31 juil. 2023 à 12:29, Tamás Cservenák a écrit : > Howdy, > > We solved 3 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12353369 > > 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 (NEW, old was maven-1982): > https://repository.apache.org/content/repositories/maven-1983 > > Dev dist directory (binary bundles updated): > https://dist.apache.org/repos/dist/dev/maven/maven-3/3.9.4/ > > Source release checksums: > apache-maven-3.9.4-src.zip sha512 (UNCHANGED): > > 7a45cfd1f50e51246bbbeef769bf0c61ec08320ac260eed6b54ffce060a3186c99e902b3407ed9aa98fe02ad9b618b1bd2741275c05c7cdac24f0bc799d324e0 > > apache-maven-3.9.4-src.tar.gz sha512 (UNCHANGED): > > 7a77f7e19c5165be8dd886ae06a52c6d6a94b1419917d2e035e937114c7cff5aea19d8ea3614485c1876185e70f4fbdd80b673f56f7d344fae75e51d62f3100c > > Binary release checksums: > apache-maven-3.9.4-bin.tar.gz - SHA-512 : > > deaa39e16b2cf20f8cd7d232a1306344f04020e1f0fb28d35492606f647a60fe729cc40d3cba33e093a17aed41bd161fe1240556d0f1b80e773abd408686217e > > apache-maven-3.9.4-bin.zip - SHA-512 : > > 755e7b757ea011621d704b9d2bee8fc344b77c13117077caa71abea560f20926a2bc8c96f990ed298f2dfc14bdba376566ee11c66c547f2594579f9cb3c50e1c > > Staged site: > https://maven.apache.org/ref/3-LATEST/ > > Draft for release notes: > https://github.com/apache/maven-site/pull/442 > > Guide to testing staged releases: > http://maven.apache.org/guides/development/guide-testing-releases.html > > Vote open for 72h > > [ ] +1 > [ ] +0 > [ ] -1 > -- Arnaud Héritier Twitter/GitHub/... : aheritier
Re: [VOTE] Release Apache Maven 3.9.2
+1 On Tue, May 9, 2023 at 8:19 PM Sylwester Lachiewicz wrote: > +1 > > pon., 8 maj 2023 o 12:40 Tamás Cservenák napisał(a): > > > Howdy, > > > > We solved 12 issues: > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12352958 > > > > 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-1937 > > > > Dev dist directory: > > https://dist.apache.org/repos/dist/dev/maven/maven-3/3.9.2/ > > > > Source release checksums: > > apache-maven-3.9.2-src.zip sha512: > > > > > addd90f1521f5789dbeab4b0af5fd60cad3650cd51e175c25cfbc8f77c3c82ce5b4c4b7d5278691cb67225e59ee8b4b6d97cfd4cd9bd8913e79773e9cebf18c8 > > apache-maven-3.9.2-src.tar.gz sha512: > > > > > 977c0c56c570977567e63cd4d2e61d2645381e08713f0a8c73f22e6600cf31e1b5a360929fb08f28bb7329033eb5f9331b0dabdb32b2b9009650be5f48f6e6d1 > > > > Binary release checksums: > > apache-maven-3.9.2-bin.zip sha512: > > > > > f7296534ce624f688268e55544ffdf0b37562ac71dbcede4fe4f994b4e9487b7d66934849204373e127cfacc709cd5fd9152a53c06d778fc391aee84aa3364a3 > > apache-maven-3.9.2-bin.tar.gz sha512: > > > > > 900bdeeeae550d2d2b3920fe0e00e41b0069f32c019d566465015bdd1b3866395cbe016e22d95d25d51d3a5e614af2c83ec9b282d73309f644859bbad08b63db > > > > Staged site: > > https://maven.apache.org/ref/3-LATEST/ > > > > Draft for release notes: > > https://github.com/apache/maven-site/pull/414 > > > > Guide to testing staged releases: > > http://maven.apache.org/guides/development/guide-testing-releases.html > > > > Vote open for 72h > > > > [ ] +1 > > [ ] +0 > > [ ] -1 > > > -- Arnaud Héritier Twitter/GitHub/... : aheritier
Re: [VOTE] Release Apache Maven Remote Resources Plugin version 3.1.0
+1 On Tue, May 9, 2023 at 9:28 PM Sylwester Lachiewicz wrote: > +1 > > wt., 9 maj 2023 o 20:09 Delany napisał(a): > > > +1 > > > > On Tue, 9 May 2023 at 18:48, Slawomir Jaranowski > > > wrote: > > > > > Hi, > > > > > > We solved 13 issues: > > > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317825=12352115 > > > > > > There are still a couple of issues left in JIRA: > > > > > > > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRRESOURCES%20AND%20resolution%20%3D%20Unresolved > > > > > > Staging repo: > > > https://repository.apache.org/content/repositories/maven-1938/ > > > > > > > > > https://repository.apache.org/content/repositories/maven-1938/org/apache/maven/plugins/maven-remote-resources-plugin/3.1.0/maven-remote-resources-plugin-3.1.0-source-release.zip > > > > > > Source release checksum(s): > > > maven-remote-resources-plugin-3.1.0-source-release.zip - SHA-512 : > > > > > > > > > bb34a452e03c0c29a099c409f40130f362c89d5400a2841cb7909f44112d2d36569449be33704f6fe0e89da20a4d47b93a7e09f1870b6a911987b8d966b148ed > > > > > > Staging site: > > > > > > > > > https://maven.apache.org/plugins-archives/maven-remote-resources-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 > > > > > > -- Arnaud Héritier Twitter/GitHub/... : aheritier
Re: [VOTE] Release Apache Maven Daemon 1.0-m6
+1 Le jeu. 30 mars 2023 à 08:59, Slawomir Jaranowski a écrit : > +1 > > czw., 23 mar 2023 o 11:22 Guillaume Nodet napisał(a): > > > I've staged a candidate release at > > https://dist.apache.org/repos/dist/dev/maven/mvnd/1.0-m6/ > > > > This release provides distributions based on Maven 3.9.1 and > 4.0.0-alpha-4 > > releases. > > The release notes are available at : > > > > > > > https://github.com/apache/maven-mvnd/releases/tag/untagged-659daa4af1d963db7430 > > > > Please review and vote ! > > > > Cheers > > Guillaume Nodet > > > > > -- > Sławomir Jaranowski > -- Arnaud Héritier Twitter/GitHub/... : aheritier
Re: [VOTE] Release Apache Maven 4.0.0-alpha-5
+1 Le dim. 19 mars 2023 à 08:28, Slawomir Jaranowski a écrit : > +1 > > śr., 15 mar 2023 o 18:14 Guillaume Nodet napisał(a): > > > Hey > > > > We solved 26 issues: > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12352862=12316922 > > > > Staging repository: > > https://repository.apache.org/content/repositories/maven-1890 > > > > Dev dist directory: > > https://dist.apache.org/repos/dist/dev/maven/maven-4/4.0.0-alpha-5/ > > > > Staged site: > > https://maven.apache.org/ref/4-LATEST/ > > > > Guide to testing staged releases: > > http://maven.apache.org/guides/development/guide-testing-releases.html > > > > Please review and vote ! > > > > Cheers, > > Guillaume Nodet > > > > > -- > Sławomir Jaranowski > -- Arnaud Héritier Twitter/GitHub/... : aheritier
Re: [VOTE] Release Apache Maven 3.9.1
+1 On Wed, Mar 15, 2023 at 11:14 AM Tamás Cservenák wrote: > Howdy, > > We solved 29 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12352872 > > There are still 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-1888/ > > Dev dist directory: > https://dist.apache.org/repos/dist/dev/maven/maven-3/3.9.1/ > > Source release checksums: > apache-maven-3.9.1-src.zip sha512: > > 2b1f14d4d5fd4a9759ac2519dd8eb4fbfdec199a9fdc66b7995b606bb5548c4f10f431d02e725f10af4d89d55d575e6d8bc7c2e006bbfbbaa0f6349cfd699f9b > apache-maven-3.9.1-src.tar.gz sha512: > > 726679381d4660150f88a727e16005cecd0fee6c03748ae8db889cfe88a2da7ac378f0d221bf237953bba3c49542d2bd7233888eb549cf7c10dd4e2deb2a3828 > > Binary release checksums: > apache-maven-3.9.1-bin.zip sha512: > > 4ae5a0d17f9e6cbe57640c481f426a9184dfb451c2bb7cc7db324da095f616a14e7c482a79240e5286e241d8cd2805ea1cd9c95e38954101c2fa4088baad9a1a > apache-maven-3.9.1-bin.tar.gz sha512: > > d3be5956712d1c2cf7a6e4c3a2db1841aa971c6097c7a67f59493a5873ccf8c8b889cf988e4e9801390a2b1ae5a0669de07673acb090a083232dbd3faf82f3e3 > > Staged site: > https://maven.apache.org/ref/3-LATEST/ > > Draft for release notes: > https://github.com/apache/maven-site/pull/400 > > Guide to testing staged releases: > http://maven.apache.org/guides/development/guide-testing-releases.html > > Vote open for 72h > > [ ] +1 > [ ] +0 > [ ] -1 > -- Arnaud Héritier Twitter/GitHub/... : aheritier
Re: [VOTE] Release Apache Maven version 3.8.7
+1 On Sat, Dec 24, 2022 at 9:20 PM Michael Osipov wrote: > Hi, > > We solved 19 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12352690 > > There are still hundreds 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-1839/ > > Dev dist directory: > https://dist.apache.org/repos/dist/dev/maven/maven-3/3.8.7/ > > Source release checksums: > apache-maven-3.8.7-src.zip sha512: > > 7c5bbdfbd85711d11f93254208978b47e4dcf010f94a1b9f549c3040507d751dff10d99c5f3af5fa92fd44b4261fc950d69eac345736f62007416e1350319891 > apache-maven-3.8.7-src.tar.gz sha512: > > 99dc6a44811d945d2d9a9e88b32abde5a82e4a8fa202ff217a5e3106d7fc532f347cff01331f6c2c0d86b2cf67fc0d0ee609d0c7d39b352a9422b990e49a81eb > > Binary release checksums: > apache-maven-3.8.7-bin.zip sha512: > > c687fcdc3890bcf0f9f9dbc42ceded21dc80f0dcc5541c28912a99224694793f6e437998e46b5939bd314178865263c62a069c6c6f15d1d0541eea75748c46fd > apache-maven-3.8.7-bin.tar.gz sha512: > > 21c2be0a180a326353e8f6d12289f74bc7cd53080305f05358936f3a1b6dd4d91203f4cc799e81761cf5c53c5bbe9dcc13bdb27ec8f57ecf21b2f9ceec3c8d27 > > Draft for release notes: > https://github.com/apache/maven-site/pull/356 > > Guide to testing staged releases: > http://maven.apache.org/guides/development/guide-testing-releases.html > > Vote open until 2022-12-30T20:00Z > > [ ] +1 > [ ] +0 > [ ] -1 > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- Arnaud Héritier Twitter/GitHub/... : aheritier
Re: mvn install vs mvn verify
t; >> will > >> > be > >> > > deployed. Again, win-win. > >> > > > >> > > Finally, to me this feels like it is being pushed by people who > >> "stick" > >> > to > >> > > their local repository a bit too much :) For them, there is a "split > >> > local > >> > > repository" feature, where installed and cached stuff is clearly > >> > separated > >> > > (and hence, easy to nuke). > >> > > > >> > > Or in other words, I stick to the mantra "what is not in a (local or > >> > > remote) repo, does not exist (for Maven)". And most often you do > want > >> to > >> > > reuse (depend on) the project being built, hence "sharing" > (installing > >> > for > >> > > local dev or deploy for remote dev) is wanted. > >> > > > >> > > I see verify being better for trivial cases, like you work on a > simple > >> > > (single or multi module) project, with a trivial (known to behave) > >> set of > >> > > plugins. But in a moment when you work on two or more interconnected > >> > > projects, or non trivial projects, or just using some "nasty" plugin > >> that > >> > > for some reason tries to resolve things and is unaware of the > project, > >> > etc, > >> > > mvn verify quickly becomes a problem. > >> > > > >> > > WDYT? > >> > > > >> > > Thanks > >> > > T > >> > > >> > - > >> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > >> > For additional commands, e-mail: dev-h...@maven.apache.org > >> > > >> > > >> > > > -- Arnaud Héritier Twitter/GitHub/... : aheritier
Re: [DISCUSS] Raise minimum JDK requirements to 1.8 in parent pom
+1 Le sam. 22 oct. 2022 à 21:45, Guillaume Nodet a écrit : > Given maven and the resolver have upgraded their minimum JDK requirement to > 1.8, I think it makes sense to raise it globally in the parent pom. > > Any objections ? > > Cheers, > Guillaume Nodet > -- Arnaud Héritier Twitter/GitHub/... : aheritier
Re: [VOTE] Release Apache Maven 4.0.0-alpha-2
+1 Le sam. 22 oct. 2022 à 20:30, Maarten Mulders a écrit : > On 15/10/2022 02:18, Guillaume Nodet wrote: > > I've staged a release candidate at > >https://repository.apache.org/content/repositories/maven-1811 > > > > The binaries are available at: > > > > > https://repository.apache.org/service/local/repositories/maven-1811/content/org/apache/maven/apache-maven/4.0.0-alpha-2/ > > > > The tag is available at: > >https://github.com/apache/maven/tree/maven-4.0.0-alpha-2 > > > > Please review and vote ! > > > > Cheers, > > Guillaume Nodet > > > > > TL;DR: my vote is a +1. > > > First of all, thanks for creating this first alpha of Maven 4, > Guillaume! I've been using snapshots of Maven 4 for over two years now, > and they've proven to be quite reliable and stable. > > Given this is an alpha for a major release, I'm not concerned with > changes that break backward compatibility, as long as we properly > document those so our users know what they can expect. > > > Thanks, > > Maarten > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- Arnaud
Re: [DISCUSS] Change maven code style
+1.
If useful we can also add an editorconfig file to automatically configure
IDEs but it’s a bit redundant with checkstyle
Le mer. 12 oct. 2022 à 18:24, Guillaume Nodet a écrit :
> Related to the discussion about automatically formatting and sorting
> imports, I think it would be nice, given the big reformat commits if those
> PRs are to be merged, to eventually discuss some changes to those code
> style. In particular, I found out that the code is very sparse and my
> screen is more wide than height, which means I can usually only see 30-40
> lines of code, where sometime half of them do not really carry any semantic
> (open braces, or things like close brace + else + open brace on 3 lines).
> This makes me scroll a lot even on quite small methods to be able to read
> the full code, and that's a pain imho.
> So I'd like to propose the following changes that would make maven code
> more readable imho (and also closer to the usual java coding style) :
> * move open braces to the end of the previous line on all places
> * allow the else keyword to be directly following a closing brace to
> allow "} else {" to be on the same line
> * eventually relax a bit the checkstyle line length as described in
> https://github.com/gnodet/maven-shared-resources/pull/2. This has not
> much
> effect, as the formatter will automatically format the lines and wrap them
> at 120. However, in certain cases, the formatter can find in difficult to
> wrap the line (for example with a variable declaration and cast with a
> fully qualified name) and there is either a need to manually force the wrap
> (using an end of line comment for example) or disabling the check with a
> @SuppressWarning( "checkstyle:LineLength" ) annotation. This change only
> removes the checks so that in those rare cases, the formatter can be left
> without any need to force things.
>
> If this is to be accepted, I'd amend the PRs from the other thread to
> follow those changes.
>
> Cheers,
> Guillaume
>
--
Arnaud Héritier
Twitter/GitHub/... : aheritier
Re: Question - JDK Minimum of future Apache Maven 4.0.0
I would say java 11 for maven 4 and 17 for maven 5 with the hope that it won’t be here in many years Le jeu. 21 juil. 2022 à 18:53, Benjamin Marwell a écrit : > I was going to answer: go for 17. > > But running the tests on the same language level is really a good argument. > So much changed: HttpClient, TLS and cipher suites, DNS resolution > (starting with Java 18 it will be pluggable!) etc. > > Yes, in theory it should not fail. But this is (sadly) a strong argument > against using Java 11+. > > If it's just for language features, we could also use kotlin, groovy or > just a library like javaslang (now vavr.io) to receive some amount of what > you would like to see. Groovy is even an Apache project and kotlin has > excellent support. Both can mimic sealed classes, have advanced features > like traits etc. > > Not saying I'm a big fan of this myself, but it *might* be an option to > think about. > > Of course we could scare devs away or attract them. Who knows. > > So, I deeply regret it, but I'd say go for 8 and make an early Maven 5 > release with Java 17, then make all the major changes (new pom etc) in > Maven 6 instead of Maven 5. > > > On Wed, 20 Jul 2022, 17:08 Jorge Solórzano, wrote: > > > Yes, I agree with Romain (and also many others that have the same > > concerns), expecting that the behavior of testing with one JDK that > > targets a lower JDK will "just works" is naive. > > > > There are differences at bytecode level, just compile a class with > > JDK17 --release 11 and the same class with JDK11 --release 11 and then > > compare with diffoscope to see them, this is one of the reasons that > > you need to use the same major JDK version to get Reproducible Builds, > > you can't expect a build to be reproducible even if you target to the > > same release. > > > > I don't expect the bytecode differences to be a real issue, yet > > without proper testing (using the same runtime that you target) you > > can't be sure. > > > > The HttpClient is one example where you have things like this bug: > > https://bugs.java.com/bugdatabase/view_bug.do?bug_id=8245245, fixed > > only in Java 16+, meaning that while it *works* on Java 17, it will > > fail on Java 11. > > > > We all agree that Toolchains is the way to go for this kind of thing, > > but it's important to mention that Toolchains create some friction for > > end users and a more involved setup. > > > > And please don't get me wrong, I'm all for using JDK 17, but user > > experience is also important. > > > > On Wed, Jul 20, 2022 at 4:23 PM Romain Manni-Bucau > > wrote: > > > > > > Was more due to tests failling but there is no guarantee there is no > > > difference in the bytecode on one side and the most important IMHO is > the > > > fact the run behavior can be different so at the end of the day you > cant > > > assume that because your build with java17 -release 8 worked that it > will > > > run on your prod. > > > > > > Romain Manni-Bucau > > > @rmannibucau <https://twitter.com/rmannibucau> | Blog > > > <https://rmannibucau.metawerx.net/> | Old Blog > > > <http://rmannibucau.wordpress.com> | Github < > > https://github.com/rmannibucau> | > > > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book > > > < > > > https://www.packtpub.com/application-development/java-ee-8-high-performance > > > > > > > > > > > > Le mer. 20 juil. 2022 à 16:16, Tomo Suzuki > > > a > > > écrit : > > > > > > > Hi Romain, > > > > > > > > > the while loop was not exactly the same > > > > > > > > Did you observe the difference in the while loop bytecode cause an > > issue in > > > > Java 8 users? > > > > > > > > Regards, > > > > Tomo > > > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > -- Arnaud Héritier Twitter/GitHub/... : aheritier
Re: [VOTE] Maven Install Plugin 3.0.1
+1 Le ven. 22 juil. 2022 à 18:10, Slawomir Jaranowski a écrit : > +1 > > wt., 19 lip 2022 o 16:27 Tamás Cservenák napisał(a): > > > Howdy, > > > > We fixed one regression in install-file Mojo > > > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MINSTALL%20AND%20fixVersion%20%3D%203.0.1 > > > > Staged repository: > > https://repository.apache.org/content/repositories/maven-1784 > > > > Source release SHA512: > > > > > bb2b4216ba0da11f6de4a9c02921a92839a3e0eb11f6df3a3ed11275b2ee323f81341ab9de263cb043aaea73a4c749667bbc3cef7a2887b00f22135c75f6c2f4 > > > > Staged site: > > https://maven.apache.org/plugins-archives/maven-install-plugin-LATEST/ > > > > Vote open for 72h > > > > Thanks > > T > > > > > -- > Sławomir Jaranowski > -- Arnaud Héritier Twitter/GitHub/... : aheritier
Re: [VOTE] Release Apache Maven version 3.8.6
+1 On Thu, Jun 9, 2022 at 6:10 PM Grzegorz Grzybek wrote: > +1 (non-binding) > > tested on few projects and some extensions. > > regards > Grzegorz Grzybek > > czw., 9 cze 2022 o 17:59 Sylwester Lachiewicz > napisał(a): > > > +1 > > > > pon., 6 cze 2022, 19:18 użytkownik Michael Osipov > > napisał: > > > > > Hi, > > > > > > We solved 16 issues: > > > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12351556 > > > > > > There are still hundreds 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-1759/ > > > > > > Dev dist directory: > > > https://dist.apache.org/repos/dist/dev/maven/maven-3/3.8.6/ > > > > > > Source release checksums: > > > apache-maven-3.8.6-src.zip sha512: > > > > > > > > > cfa8b7e5f965d4da8d0e098889b98fccf3eec70ac500c452a5257ca9f8b5e75d200ba51d89c0be6e06072255b71d8a0c0f21ee3e3d4ba6152ea72007b497344a > > > apache-maven-3.8.6-src.tar.gz sha512: > > > > > > > > > 03366d0d34bba79ce6f0d5e88390e360fbf2f61c273bc18885a21a6d4dcdf5eca14fe4d902735e4fcb03db32327be086e3927d259c519aa790f42142cfcb > > > > > > Binary release checksums: > > > apache-maven-3.8.6-bin.zip sha512: > > > > > > > > > f92dbd90060c5fd422349f844ea904a0918c9c9392f3277543ce2bfb0aab941950bb4174d9b6e2ea84cd48d2940111b83ffcc2e3acf5a5b2004277105fd22be9 > > > apache-maven-3.8.6-bin.tar.gz sha512: > > > > > > > > > f790857f3b1f90ae8d16281f902c689e4f136ebe584aba45e4b1fa66c80cba826d3e0e52fdd04ed44b4c66f6d3fe3584a057c26dfcac544a60b301e6d0f91c26 > > > > > > Draft for release notes: > > > https://github.com/apache/maven-site/pull/303 > > > > > > > > > Guide to testing staged releases: > > > http://maven.apache.org/guides/development/guide-testing-releases.html > > > > > > Vote open until 2021-06-12T12:00Z > > > > > > [ ] +1 > > > [ ] +0 > > > [ ] -1 > > > > > > - > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > > > > > -- Arnaud Héritier Twitter/GitHub/... : aheritier
Re: Change of Chair
Thanks again for everything you did for several years Robert. And thanks Karl for taking the role. Hope to see you soon On Thu, Apr 21, 2022 at 4:57 PM Robert Scholte wrote: > Hi all, > > as of now, Karl Heinz is the new chairman of the Apache Maven project. > I've done it for quite some time with a lot of pleasure. > I will also reduce my activities on this project, but will still be > involved as PMC member. > > thanks, > Robert > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- Arnaud Héritier Twitter/GitHub/... : aheritier
Re: [VOTE] - Release Apache Maven Clean Plugin Version 3.2.0
+1 On Fri, Apr 1, 2022 at 11:31 PM Karl Heinz Marbaise wrote: > Hi, > > We solved 10 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12343770=Text=12317224 > > There are still one issue left in JIRA: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MCLEAN%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20ASC%2C%20priority%20DESC%2C%20updated%20DESC > > Staging repo: > https://repository.apache.org/content/repositories/maven-1733 > > > https://repository.apache.org/service/local/repositories/maven-1733/content/org/apache/maven/plugins/maven-clean-plugin/3.2.0/maven-clean-plugin-3.2.0-source-release.zip > > Source release checksum(s): > maven-clean-plugin-3.2.0-source-release.zip sha512: > > c0b28aa05009948f9dc65cb3e55e332c1c000f88e2f81de848611ac9f0d4b446a4c4afc6f86961a07d0f40d9862fb294c608a6aa12be316dc457ff76b80d0cf9 > > 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 > > Kind regards > Karl Heinz Marbaise > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- Arnaud Héritier Twitter/GitHub/... : aheritier
Re: [VOTE] Release Apache Maven Artifact Plugin version 3.3.0
+1 On Sun, Apr 3, 2022 at 5:36 PM Hervé BOUTEMY wrote: > Hi, > > We solved 2 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12324322=12350902=Text > > Staging repo: > https://repository.apache.org/content/repositories/maven-1734/ > > https://repository.apache.org/content/repositories/maven-1734/org/apache/maven/plugins/maven-artifact-plugin/3.3.0/maven-artifact-plugin-3.3.0-source-release.zip > > Source release checksum(s): > maven-artifact-plugin-3.3.0-source-release.zip sha512: > f8fb4239a33a3699b4902a161252855e0033a6635b4bece0d26f15243c2e96b905bde82e8c1d2e97dd7c757ae182c783d69e36f1332cd64954685c06d9d1a10f > > Staging site: > https://maven.apache.org/plugins-archives/maven-artifact-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 > > -- Arnaud Héritier Twitter/GitHub/... : aheritier
Re: [VOTE] Release Apache Maven Surefire Plugin version 3.0.0-M6
+1 Le jeu. 31 mars 2022 à 14:35, Tibor Digana a écrit : > Hi, > > We solved 111 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927=12344613 > > There are still a couple of issues left in JIRA: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20SUREFIRE%20AND%20status%20%3D%20Open%20ORDER%20BY%20priority%20DESC > > Staging repo: > https://repository.apache.org/content/repositories/maven-1731/ > > https://repository.apache.org/content/repositories/maven-1731/org/apache/maven/surefire/surefire/3.0.0-M6/surefire-3.0.0-M6-source-release.zip > > Source release checksum(s): > surefire-3.0.0-M6-source-release.zip sha512: > > 2ad963a52445100438c68ecc2d2eb3c3e2191a33494b255969d9ec37f1a418012b8cd71567201a87839f10a47a01d6b304a625a53d90237637755b06234f4bc7 > > Staging site: > http://maven.apache.org/surefire-archives/surefire-LATEST/ > > Guide to testing staged releases: > http://maven.apache.org/guides/development/guide-testing-releases.html > > Vote open for 72 hours. > > [ ] +1 > [ ] +0 > [ ] -1 > > Cheers > Tibor > -- Arnaud Héritier Twitter/GitHub/... : aheritier
Re: [VOTE] Release Apache Maven Verifier version 1.8.0
+1 On Sat, Mar 19, 2022 at 2:06 PM Slawomir Jaranowski wrote: > Hi, > > We solved 7 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12351428=Text=12317922 > > 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-verifier%20ORDER%20BY%20key%20DESC > > Staging repo: > https://repository.apache.org/content/repositories/maven-1728/ > > https://repository.apache.org/content/repositories/maven-1728/org/apache/maven/shared/maven-verifier/1.8.0/maven-verifier-1.8.0-source-release.zip > > Source release checksum(s): > maven-verifier-1.8.0-source-release.zip - SHA-512 : > > 3e82235ca54fdb1d96cc2f51873b4033ebe2deb3d23678e61a3b20f1ddf76683e09ccfacd51088fba81dc83a0ce48eccff811e86728c6a7ef85369b6ff3dd09a > > Staging site: > https://maven.apache.org/shared-archives/maven-verifier-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 > -- Arnaud Héritier Twitter/GitHub/... : aheritier
Re: [VOTE] Release Apache Maven Dependency Plugin version 3.3.0
+1 On Wed, Mar 9, 2022 at 8:27 AM Hervé BOUTEMY wrote: > +1 > > Reproducible Builds ok: reference done with JDK 8 on *nix > > Regards, > > Hervé > > Le dimanche 6 mars 2022, 03:47:22 CET Olivier Lamy a écrit : > > +1 > > > > On Sun, 6 Mar 2022 at 05:08, Slawomir Jaranowski > > > > > wrote: > > > Hi, > > > > > > We solved 24 issues: > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12340588 > > > yleName=Text=12317227 > > > > > > There are still a couple of issues left in JIRA: > > > > > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MDEP%20AND%20re > > > > solution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC > > > > > > Staging repo: > > > https://repository.apache.org/content/repositories/maven-1725/ > > > > > > > https://repository.apache.org/content/repositories/maven-1725/org/apache/m > > > > aven/plugins/maven-dependency-plugin/3.3.0/maven-dependency-plugin-3.3.0-s > > > ource-release.zip > > > > > > Source release checksum(s): > > > maven-dependency-plugin-3.3.0-source-release.zip - SHA-512 : > > > > > > > b0c650fa440078fcc63c7af70219e937be92ed16aeb6c12057e43c66e605c0d3c31f8f681b > > > 014fc0adffe1e20d5a73c5e4bbedc9c70d91637f7d85ea4d60c27c > > > > > > Staging site: > > > > https://maven.apache.org/plugins-archives/maven-dependency-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 > > -- Arnaud Héritier Twitter/GitHub/... : aheritier
Re: [VOTE] Apache Maven Compiler 3.10.1
+1 On Wed, Mar 9, 2022 at 8:18 AM Olivier Lamy wrote: > +1 > > On Tue, 8 Mar 2022 at 11:25, Olivier Lamy wrote: > > > Hi, > > I'd like to release Apache Maven Compiler 3.10.1. > > > > 3 issues solved: > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12351339=Text=12317225 > > > > Staging repository: > > https://repository.apache.org/content/repositories/maven-1726/ > > > > 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 > > > > cheers > > Olivier > > > -- Arnaud Héritier Twitter/GitHub/... : aheritier
Re: [VOTE] Release Apache Maven version 3.8.5
+1. Le sam. 5 mars 2022 à 17:47, Michael Osipov a écrit : > Hi, > > We solved 27 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12351105 > > There are still hundreds 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-1724/ > > Dev dist directory: > https://dist.apache.org/repos/dist/dev/maven/maven-3/3.8.5/ > > Source release checksums: > apache-maven-3.8.5-src.zip sha512: > > 7edb6864834a81c11cf9d22a8110abc3f5f96360bdbc4bc33ec0c98dc389dd9fc71465253a87729dbe7b8a011b2ec38afa0e011172657c3a97ef96fb6f40292b > apache-maven-3.8.5-src.tar.gz sha512: > > 1aa1b2dcba794b7e4cbc8e2ff9baf64283fb3883ae93efff26fe259578504b60a8b68404a074f4741922e462fa696cbbe71f9d74e4e6316ed0e389d25667 > > Binary release checksums: > apache-maven-3.8.5-bin.zip sha512: > > f9f838b4adaf23db0204a6cafa52bf1125bd2d649fd676843fd05e82866b596ec19c4f3de60d5e3ff17f10a63d96c141311ff9bc2bfa816eade7a5cbff2bd925 > apache-maven-3.8.5-bin.tar.gz sha512: > > 89ab8ece99292476447ef6a6800d9842bbb60787b9b8a45c103aa61d2f205a971d8c3ddfb8b03e514455b4173602bd015e82958c0b3ddc1728a57126f773c743 > > Draft for release notes: > https://github.com/apache/maven-site/pull/292 > > > Guide to testing staged releases: > http://maven.apache.org/guides/development/guide-testing-releases.html > > Vote open until 2021-03-13T12:00Z > > [ ] +1 > [ ] +0 > [ ] -1 > > --------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- Arnaud Héritier Twitter/GitHub/... : aheritier
Re: Switch to Matomo Tracking code
It’s around 40 to 50k active users per day (week days) Le sam. 5 mars 2022 à 13:41, Benjamin Marwell a écrit : > Hi everyone! > > The ASF now runs a public Matomo instance [1]. > They are open for more projects now. > > If it is okay with you, we could add a tracking code to our site.xml file > [2]. > It is an easy change, just add a body-head section [4]. > > Even if you do not agree to add Matomo, I will create a PR to remove > the Google Analytics tracking code, as it violates our privacy policy > [3] and is already illegal to use in some countries, e.g. France. > > Let me know what you think. > > - Ben > > PS: Someone with access to Google Analytics, please provide some rough > numbers (daily hits) to Martijn, who is CC'd. Thanks! > > [1]: https://matomo.privacy.apache.org/ > [2]: https://github.com/apache/maven-parent/blob/master/src/site/site.xml > [3]: > https://www.apache.org/foundation/policies/privacy.html#:~:text=We%20do%20not%20track%20or,for%20the%20purpose%20described%20above > . > [4]: > https://maven.apache.org/plugins/maven-site-plugin/examples/sitedescriptor.html#Inject_xhtml_into_.3Chead.3E > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- Arnaud Héritier Twitter/GitHub/... : aheritier
Re: [VOTE] Release Maven Plugin Tools version 3.6.4
+1 On Tue, Jan 11, 2022 at 11:28 AM Michael Osipov wrote: > Am 2022-01-11 um 00:35 schrieb Slawomir Jaranowski: > > Hi, > > > > We solved 5 issues: > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317820=12351222 > > > > 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-1697/ > > > https://repository.apache.org/content/repositories/maven-1697/org/apache/maven/plugin-tools/maven-plugin-tools/3.6.4/maven-plugin-tools-3.6.4-source-release.zip > > > > > > Source release checksum(s): > > maven-plugin-tools-3.6.4-SNAPSHOT-source-release.zip > > SHA-512 : > > > d6a9c46ad324d77258cb2ccdddf7d3673734f9412c2863d21cde10a3853c1bcd1d15427851b49660d19c2707e2116d10aace13876c656d23c178998717970c07 > > > > Staging site: > > > https://maven.apache.org/plugin-tools-archives/plugin-tools-LATEST/maven-plugin-plugin/ > > > > Guide to testing staged releases: > > https://maven.apache.org/guides/development/guide-testing-releases.html > > > > Vote open for at least 72 hours. > > +1 > > --------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- Arnaud Héritier Twitter/GitHub/... : aheritier
Re: [VOTE] Release Maven JAR Plugin version 3.2.2
+1 On Tue, Jan 11, 2022 at 8:09 PM Slawomir Jaranowski wrote: > +1 > > wt., 11 sty 2022 o 19:46 Sylwester Lachiewicz > napisał(a): > > > +1 > > > > wt., 11 sty 2022 o 18:51 Michael Osipov > napisał(a): > > > > > > Am 2022-01-08 um 22:26 schrieb Michael Osipov: > > > > Hi, > > > > > > > > We solved 2 issues: > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317526=12351215 > > > > > > > > > > > > There are still a couple of issues left in JIRA: > > > > > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%MJAR%20AND%20resolution%20%3D%20Unresolved > > > > > > > > > > > > Staging repo: > > > > https://repository.apache.org/content/repositories/maven-1695/ > > > > > > > https://repository.apache.org/content/repositories/maven-1695/org/apache/maven/plugins/maven-jar-plugin/3.2.2/maven-jar-plugin-3.2.2-source-release.zip > > > > > > > > > > > > Source release checksum(s): > > > > maven-jar-plugin-3.2.2-source-release.zip > > > > sha512: > > > > > > > c1dd89f6c7954197e4a571978698527730c136039ae47f3d3ba284e0cba06be91eb3ad1829a68d4603090bd14fd9e067c005569dff964bf84cb4f52e1b41fbf4 > > > > > > > > > > > > Staging site: > > > > http://maven.apache.org/plugins-archives/maven-jar-plugin-LATEST/ > > > > > > > > Guide to testing staged releases: > > > > > http://maven.apache.org/guides/development/guide-testing-releases.html > > > > > > > > Vote open for 72 hours. > > > > > > > > > +1 > > > > > > > > > Guys, I need one more vote! > > > > > > - > > > 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 > > > > > > -- > Sławomir Jaranowski > -- Arnaud Héritier Twitter/GitHub/... : aheritier
Re: [VOTE] Release Maven SCM version 2.0.0-M1
+1 On Tue, Jan 11, 2022 at 8:16 PM Slawomir Jaranowski wrote: > +1 > > niedz., 9 sty 2022 o 23:31 Herve Boutemy napisał(a): > > > +1 > > > > Reproducible Build checked: reference build was done with JDK 8 on > Windows > > > > Regards, > > > > Hervé > > > > > > On 2022/01/08 20:24:01 Michael Osipov wrote: > > > Hi, > > > > > > We solved 6 issues: > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317828=12350622 > > > > > > There are still a couple of issues left in JIRA: > > > https://issues.apache.org/jira/projects/SCM/issues > > > > > > Staging repo: > > > https://repository.apache.org/content/repositories/maven-1694/ > > > > > > https://repository.apache.org/content/repositories/maven-1694/org/apache/maven/scm/maven-scm/2.0.0-M1/maven-scm-2.0.0-M1-source-release.zip > > > > > > Source release checksum(s): > > > maven-scm-2.0.0-M1-source-release.zip > > > sha512: > > > > > > 5937012a1e7c2e43a10800ade13017bdf89655405b3aa7c1470e84c13e1cdfadd8c145ca9a29c58b77206a5e34362a663c9bcebe54b414a70bf6b50dd7d1b5fe > > > > > > Staging site: > > > https://maven.apache.org/scm-archives/scm-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 > > > > > > -- > Sławomir Jaranowski > -- Arnaud Héritier Twitter/GitHub/... : aheritier
Re: [VOTE] Release Maven Compiler Plugin version 3.9.0
+1 On Tue, Jan 11, 2022 at 8:25 PM Slawomir Jaranowski wrote: > The latest build on jenkis > > https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-compiler-plugin/job/master/93/ > is ok > > Build on mac Os, jdk 1.8, 17, Maven 3.8.4 also ok. > > +1 > > niedz., 9 sty 2022 o 20:01 Herve Boutemy napisał(a): > > > I rebuilt from current Git HEAD and got same result > > > > looking at ASF Jenkins, it seems 1 configuration has exactly the same > > issue than me: > > > > > https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-compiler-plugin/job/master/92/execution/node/249/log/ > > > > it's JDK 8 with Maven 3.2 on ASF Jenkins, with other Maven versions > working > > I'm testing locally with Maven 3.8.3, so I really doubt that Maven > version > > is really key > > > > it is strange... > > > > On 2022/01/09 17:20:08 Michael Osipov wrote: > > > Am 2022-01-09 um 17:56 schrieb Michael Osipov: > > > > Interesting, here it worked during release: > > > >> [INFO] [INFO] run post-build script verify.groovy > > > >> [INFO] [INFO] MCOMPILER-349_dependencyChanged\pom.xml > > > >> .. SUCCESS (8.7 s) > > > > > > > > I'll retry on FreeBSD, maybe this is an OS thing. > > > > > > Can't reproduce in 8, 11 and 17. Maybe an ephemeral issue? > > > > > > - > > > 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 > > > > > > -- > Sławomir Jaranowski > -- Arnaud Héritier Twitter/GitHub/... : aheritier
Re: [VOTE] Release Maven JAR Plugin version 3.2.1
+1 Le mer. 5 janv. 2022 à 19:29, Michael Osipov a écrit : > Hi, > > We solved 3 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317526=12348050 > > There are still a couple of issues left in JIRA: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%MJAR%20AND%20resolution%20%3D%20Unresolved > > Staging repo: > https://repository.apache.org/content/repositories/maven-1692/ > > https://repository.apache.org/content/repositories/maven-1692/org/apache/maven/plugins/maven-jar-plugin/3.2.1/maven-jar-plugin-3.2.1-source-release.zip > > Source release checksum(s): > maven-jar-plugin-3.2.1-source-release.zip > sha512: > > 0d89b58b65c6c5b5b5512eeeb2d88b2c077b94a08e7ef9356fa52e2bf0c46230289e7311e57c994296481c14d6c78c56b2daef28b3513c60f3ea00aebe3d77b9 > > Staging site: > http://maven.apache.org/plugins-archives/maven-jar-plugin-LATEST/ > > Guide to testing staged releases: > http://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 > > -- Arnaud Héritier Twitter/GitHub/... : aheritier
Re: [VOTE] Release Maven Release version 3.0.0-M5
+1 On Sun, Jan 2, 2022 at 11:41 AM Michael Osipov wrote: > Hi, > > We solved 9 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824=12346565 > > There are still a couple of issues left in JIRA: > https://issues.apache.org/jira/projects/MRELEASE/issues > > Staging repo: > https://repository.apache.org/content/repositories/maven-1690/ > > https://repository.apache.org/content/repositories/maven-1690/org/apache/maven/release/maven-release/3.0.0-M5/maven-release-3.0.0-M5-source-release.zip > > Source release checksum(s): > maven-release-3.0.0-M5-source-release.zip > > cbf9e5feec66d194022a0fa3088702e37b6a54d179b8dd836578601883a4d3583de7be136ca55ce29287417f43176a7e98f449da3abc6ef80d6d09a2701b1786 > > Staging site: > https://maven.apache.org/maven-release-archives/maven-release-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 > > -- Arnaud Héritier Twitter/GitHub/... : aheritier
Re: Maven Resolver + Wagon
Sorry I missed this interesting thread. I completely agree with your analysis. In 2022 I don’t think anyone consume its artifacts from another protocol than http(s) or file. It’s probably another story for the publication and in this area wagon is still making sense but for the resolver I don’t see any interest to keep it (especially if it can help to improve the performances and the reduction of layers can help to simplify and optimize more this part of maven) Le jeu. 23 déc. 2021 à 10:56, Tamás Cservenák a écrit : > Ping, no one else has any opinion on this? > > T > > On Wed, Dec 15, 2021 at 9:26 AM Tamás Cservenák > wrote: > > > Howdy, > > > > I'd like to pitch a topic about maven-resolver and usage of Wagon in it. > > As IMHO, Wagon use in maven-resolver is far from optimal (is very > > suboptimal). > > > > Typical example is this PR: > > https://github.com/apache/maven-resolver/pull/140 > > > > This PR _halves HTTP requests made by resolver_ against Maven Central (!) > > by utilizing hashes sent by Maven Central in HTTP response header. Hence, > > instead of doing GET /a.jar and then GET /a.jar.sha1 it does both at once > > with one HTTP request. IMHO, this is huge. But, this works only with > > maven-resolver-transport-http that is NOT used with Maven (as it uses > > maven-resolver-transport-wagon). Moreover, doing this in Wagon, that is > > layer by layer ... of abstractions is just very hard. > > > > IMHO, back in Maven2 times, when Wagon was conceived, the "transport > > agnosticism" and "universal transport" was really a life saver: back > then, > > people used sticks and duct-tapes to craft "repo solutions", hence access > > like SSHFS, Apache httpd + mod_dav and who knows what were common, and > > Wagon having supporting all these cases was really a cool thing to have. > > > > But fast forward 10+ years, there is really no reason to do this today, > as > > the landscape changed a LOT, there are MRMs on every corner popping up > like > > mushrooms. I don't really see use of maven-resolver (and maven's use of > > maven-resolver) that does not involve HTTP or FILE. > > > > In short, resolver NOT involving HTTP is something you will VERY RARELY > > see. Or in other words, maven-resolver concerning anything NOT HTTP (and > > FILE) is just sub optimal. > > > > So I propose to retarget maven-resolver (and it's use within maven) to > use > > maven-resolver-transport-http instead of Wagon. Wagon, similarly like > > Plexus, is there to stay in Maven, but it's use in maven-resolver is > really > > really suboptimal. > > > > > > WDYT? > > > > Tamas > > > > > -- Arnaud Héritier Twitter/GitHub/... : aheritier
Re: [VOTE] Release Maven Wagon version 3.5.0
+1 Le lun. 20 déc. 2021 à 17:48, Olivier Lamy a écrit : > +1 > > On Sun, 19 Dec 2021 at 19:46, Michael Osipov wrote: > > > Hi, > > > > We solved 5 issues: > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318122=12351097 > > > > There are still a couple of issues left in JIRA: > > > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20WAGON%20AND%20resolution%20%3D%20Unresolved > > > > Staging repo: > > https://repository.apache.org/content/repositories/maven-1680/ > > > > > https://repository.apache.org/content/repositories/maven-1680/org/apache/maven/wagon/wagon/3.5.0/wagon-3.5.0-source-release.zip > > > > Source release checksum(s): > > wagon-3.5.0-source-release.zip > > sha512: > > > > > c24c05c37b621c6ce160ef30675ca94c683b8581a2252a6b383d852d779816cbd80688f2e14d8eb1722e56984f97b301379762a9ebba77e9366ece03bef69d52 > > > > Staging site: > > https://maven.apache.org/wagon-archives/wagon-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 > > > > > -- Arnaud Héritier Twitter/GitHub/... : aheritier
Re: [VOTE] Release Apache Maven Wrapper version 3.1.0
+1 Le mer. 15 déc. 2021 à 19:38, Jason van zyl a écrit : > +1 > > jvz > > > On Dec 13, 2021, at 4:09 PM, Hervé BOUTEMY > wrote: > > > > Hi, > > > > We solved 18 issues: > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12323721=12350068=Text > > > > Staging repo: > > https://repository.apache.org/content/repositories/maven-1679/ > > > https://repository.apache.org/content/repositories/maven-1679/org/apache/maven/wrapper/maven-wrapper-parent/3.1.0/maven-wrapper-parent-3.1.0-source-release.zip > > > > Source release checksum(s): > > maven-wrapper-parent-3.1.0-source-release.zip sha512: > 9b7362c956cd24e21b46b290e154893ae35fd38431b6fe80f035cd17a97806e9221c71ac14975692f2a948ad25489f5b9d9bbb72441f9ab5eb541da0a86bdef9 > > > > 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 > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- Arnaud Héritier Twitter/GitHub/... : aheritier
Re: Welcome Sławomir Jaranowski as Maven Committer
Welcome Slawomir ! On Tue, Dec 14, 2021 at 2:23 PM Karl Heinz Marbaise wrote: > Hi to Sławomir, > > Welcome to the team. > > Glad to have you on board. > > Enjoy.. > > Kind regards > Karl Heinz Marbaise > On 14.12.21 11:10, Robert Scholte wrote: > > The Maven PMC invited Sławomir to become a committer and he has accepted > > it. > > > > Enjoy improving Apache Maven! > > > > thanks, > > Robert > > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- Arnaud Héritier Twitter/GitHub/... : aheritier
Re: [DISCUSS] Move maven caching to an external repository
+1 go for it !! On Fri, Dec 10, 2021 at 7:37 PM Michael Osipov wrote: > Am 2021-12-10 um 10:30 schrieb Guillaume Nodet: > > I've refactored the build to be a single-module build. > > I agree that maven-caching is not the most descriptive, I'd be pleased > with > >* maven-build-cache-extension* > > This sounds very promising. > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- Arnaud Héritier Twitter/GitHub/... : aheritier
Re: [DISCUSS] Move maven caching to an external repository
I agree that having a set of official extensions might be ideal. Today the most popular are still the Takari ones AFAIK but they aren't officially supported by our team and thus probably less used than they could/should. Due to the git organization @ASF I don't know what is easier between having 1 repo or several ones. In general I prefer to have 1 repo = 1 lifecycle (the opposite of monorepo) but maybe it could have some sense in the long term and some shared code ... not sure. On Tue, Dec 7, 2021 at 9:53 AM Tamás Cservenák wrote: > Howdy, > > I'd rather group ASF extensions (are there any existing ones aside of > caching?), > to be clear... so GH repo could be something like > apache/maven-caching-extension > apache/maven-foobar-extension > etc? > > T > > On Tue, Dec 7, 2021 at 9:48 AM Guillaume Nodet wrote: > > > Following the recent work done to integrate the maven caching / > incremental > > build system into maven, I think it's now time to discuss where we want > its > > long-term location to be. > > > > This extension was donated a few months ago and provides local and remote > > caching of maven project's output, based on computed hashes of the > inputs. > > It's defined as a maven extension and can be used as a core or build > > extension. This avoids building the project and speeds up builds a lot ! > > > > The current status of this work resides in 3 branches: > > * MNG-7129-3.8.x (PR at https://github.com/apache/maven/pull/622) > > * MNG-7129-master (PR at https://github.com/apache/maven/pull/607) > > * https://github.com/apache/maven/tree/MNG-7129-maven-caching > > The two first PRs include the required changes to integrate the extension > > in maven 3.8.x (or rather 3.9.x) and in master. The last branch is the > one > > that should be moved to a separate repository and contain the code for > the > > extension. The goal is to agree on the location and the final name for > the > > repository (it can't be changed easily). > > > > I propose maven-caching as the repository / subproject name, but any > better > > name is welcomed of course. > > > > -- > > > > Guillaume Nodet > > > -- Arnaud Héritier Twitter/GitHub/... : aheritier
Re: [VOTE] Release Apache Maven version 3.8.4
No regression found +1 On Sun, Nov 14, 2021 at 2:28 PM Michael Osipov wrote: > Hi, > > We solved 5 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12350685 > > 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%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC > > Staging repo: > https://repository.apache.org/content/repositories/maven-1669/ > > Dev dist directory: > https://dist.apache.org/repos/dist/dev/maven/maven-3/3.8.4/ > > Source release checksums: > apache-maven-3.8.4-src.zip sha512: > > 2f57dd7476ee1831867930dbe33ebe669b8fc0a9863586093a4eb2188745c5ddc2710beea1bf076263923ce38a487ef92d570bc752c77d0e0f1e3416b65bc785 > apache-maven-3.8.4-src.tar.gz sha512: > > ea4b5f2b29be45d22e716099d0ef87367c78766aade094e8d7f295fe3b2c98cba2bf0f214d3ed55e2c17d2f74c82352cf9dc83fa47ddc97a8d2b847315500431 > > Binary release checksums: > apache-maven-3.8.4-bin.zip sha512: > > bcd1e99548ac8a5b9ec159ee16c23d29d6799696c92140d583d25eb323433aadcc0b47c45b0b6bd9dbcf344bbba38b56dd056a9c49ae714cfc22dc06bb4a4230 > apache-maven-3.8.4-bin.tar.gz sha512: > > a9b2d825eacf2e771ed5d6b0e01398589ac1bfa4171f36154d1b5787879605507802f699da6f7cfc80732a5282fd31b28e4cd6052338cbef0fa1358b48a5e3c8 > > Draft for release notes: > https://github.com/apache/maven-site/pull/274 > > > Guide to testing staged releases: > http://maven.apache.org/guides/development/guide-testing-releases.html > > Vote open until 2021-11-19T18:00Z > > [ ] +1 > [ ] +0 > [ ] -1 > > ----- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- Arnaud Héritier Twitter/GitHub/... : aheritier
Re: [VOTE] Release Maven Resolver version 1.7.2
+1 On Wed, Sep 8, 2021 at 10:27 PM Michael Osipov wrote: > Hi, > > We solved 13 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=12344271 > > There are still a couple of issues left in JIRA: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOLVER%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20Resolver > > Staging repo: > https://repository.apache.org/content/repositories/maven-1664/ > > https://repository.apache.org/content/repositories/maven-1664/org/apache/maven/resolver/maven-resolver/1.7.2/maven-resolver-1.7.2-source-release.zip > > Source release checksum(s): > maven-resolver-1.7.2-source-release.zip > > 793ea97d055e9b9ce0555427985a0e3c04b0c68342d1b67c1f42cd8a42354f0736e02f312cb1622d489504767d45ddaef2bd3d4b9de161bb6d9ec78eac677b59 > > 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 > > -- Arnaud Héritier Twitter/GitHub/... : aheritier
Re: [VOTE] Release Maven SCM version 1.12.0
+1 On Mon, Sep 13, 2021 at 10:49 AM Michael Osipov wrote: > Hi, > > We solved 14 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317828=12350600 > > There are still a couple of issues left in JIRA: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20SCM%20AND%20resolution%20%3D%20Unresolved > > Staging repo: > https://repository.apache.org/content/repositories/maven-1666/ > > https://repository.apache.org/content/repositories/maven-1666/org/apache/maven/scm/maven-scm/1.12.0/maven-scm-1.12.0-source-release.zip > > Source release checksum(s): > maven-scm-1.12.0-source-release.zip > sha512: > > 8127cf2db7c5ef1f3884079d3336b3647ddac4cb16bdfb95b48553318ff7aae3079901c83e456043fc1f94aa9f73579264a099d6cc47f33106589265b56f0ad8 > > Staging site: > https://maven.apache.org/scm-archives/scm-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 > > -- Arnaud Héritier Twitter/GitHub/... : aheritier
Re: [VOTE] Release Apache Maven Shared Resources version 4
+1 On Sat, Oct 2, 2021 at 5:15 PM Sylwester Lachiewicz wrote: > Hi, > > We solved 1 issue: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12349555=Text=12317922 > > Dependency upgrade > [MSHARED-990] - Swap scope and exclude scope to access modifier in > the check JavadocMethodCheck. > > There are no 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-shared-resources > > Staging repo: > https://repository.apache.org/content/repositories/maven-1668/ > > https://repository.apache.org/content/repositories/maven-1668/org/apache/maven/shared/maven-shared-resources/4/maven-shared-resources-4-source-release.zip > > Source release checksum(s): > maven-shared-resources-4-source-release.zip sha512: > > 5792cecf4a644dfb050d03f32ad4b5718422cd51b10ccb4056c0b0fe9618c8fec615115dc932d75a5470888c16c02cb7987f61b18611f6119fc2d2d3cb679bf7 > > Staging site: > https://maven.apache.org/shared-archives/maven-shared-resources-LATEST/ > > Guide to testing staged releases: > https://maven.apache.org/guides/development/guide-testing-releases.html > > Vote open for at least 72 hours. > > [ ] +1 > [ ] +0 > [ ] -1 > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- Arnaud Héritier Twitter/GitHub/... : aheritier
Re: [VOTE] Release Apache Maven PMD Plugin version 3.15.0
+1 On Fri, Sep 10, 2021 at 7:37 AM Hervé BOUTEMY wrote: > +1 > > checked that I could reproduce the build: reference binaries were done > with > JDK 8 on some Unix > > Regards, > > Hervé > > Le lundi 6 septembre 2021, 20:56:25 CEST Andreas Dangel a écrit : > > Hi, > > > > We solved 14 issues: > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12349432 > > eName=Text=12317621 > > > > There are still a couple of issues left in JIRA: > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MPMD%20AND%20stat > > us%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC > > > > Staging repo: > > https://repository.apache.org/content/repositories/maven-1663/ > > > https://repository.apache.org/content/repositories/maven-1663/org/apache/mav > > > en/plugins/maven-pmd-plugin/3.15.0/maven-pmd-plugin-3.15.0-source-release.zi > > p > > > > Source release checksum(s): > > maven-pmd-plugin-3.15.0-source-release.zip sha512: > > > 8ce5f12e7bbdb69013e122ef525f20c9cb191c1fbaf29708800aa887d2782e4eedc7aab51a66 > > 3803e4c7d0f6005918836d5eb0a27bff35ffdf483194e32f7dc4 > > > > Staging site: > > https://maven.apache.org/plugins-archives/maven-pmd-plugin-LATEST/ > > > > Guide to testing staged releases: > > https://maven.apache.org/guides/development/guide-testing-releases.html > > > > Vote open for at least 72 hours. > > > > [ ] +1 > > [ ] +0 > > [ ] -1 > > > > > > Regards, > > Andreas > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- Arnaud Héritier Twitter/GitHub/... : aheritier
Re: [VOTE] Release Maven Resolver version 1.7.2
+1 On Fri, Sep 10, 2021 at 8:49 AM Tamás Cservenák wrote: > +1 > > On Wed, Sep 8, 2021, 22:27 Michael Osipov wrote: > > > Hi, > > > > We solved 13 issues: > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=12344271 > > > > There are still a couple of issues left in JIRA: > > > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOLVER%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20Resolver > > > > Staging repo: > > https://repository.apache.org/content/repositories/maven-1664/ > > > > > https://repository.apache.org/content/repositories/maven-1664/org/apache/maven/resolver/maven-resolver/1.7.2/maven-resolver-1.7.2-source-release.zip > > > > Source release checksum(s): > > maven-resolver-1.7.2-source-release.zip > > > > > 793ea97d055e9b9ce0555427985a0e3c04b0c68342d1b67c1f42cd8a42354f0736e02f312cb1622d489504767d45ddaef2bd3d4b9de161bb6d9ec78eac677b59 > > > > 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 > > > > > -- Arnaud Héritier Twitter/GitHub/... : aheritier
Re: [VOTE] Release Apache Maven WAR Plugin version 3.3.2
+1 On Sun, Sep 5, 2021 at 11:38 AM Hervé BOUTEMY wrote: > Hi, > > We solved 2 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318121=12348574=Text > > Staging repo: > https://repository.apache.org/content/repositories/maven-1661/ > > https://repository.apache.org/content/repositories/maven-1661/org/apache/maven/plugins/maven-war-plugin/3.3.2/maven-war-plugin-3.3.2-source-release.zip > > Source release checksum(s): > maven-war-plugin-3.3.2-source-release.zip sha512: > 368d1066d3aa429b3dc26b1e3a502fe56c4232fae13727c74d44015b160eec3753f28ff72e3a0f33f9dfa9d25e9912efb559d45cf41952151ecc88337203fc95 > > Staging site: > https://maven.apache.org/plugins-archives/maven-war-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 > > -- Arnaud Héritier Twitter/GitHub/... : aheritier
Re: [VOTE] Release Apache Maven Javadoc Plugin version 3.3.1
+1 On Sat, Sep 4, 2021 at 10:57 AM Robert Scholte wrote: > Hi, > > We solved 9 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317529=12347807=Text > > There are still a couple of issues left in JIRA: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317529%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC > > Staging repo: > https://repository.apache.org/content/repositories/maven-1660 > > https://repository.apache.org/content/repositories/maven-1660/org/apache/maven/plugins/maven-javadoc-plugin/3.3.1/maven-javadoc-plugin-3.3.1-source-release.zip > > Source release checksum(s): > maven-javadoc-plugin-3.3.1-source-release.zip sha512: > > b10de64f1389b04b6e4aace3045f77e90515448d91cbb4705a0805779b052bc76df695ad85bad55288f8bc66b9bced86baad11bbb40ef06e441e20700bb31746 > > 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 at least 72 hours. > > [ ] +1 > [ ] +0 > [ ] -1 > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- Arnaud Héritier Twitter/GitHub/... : aheritier
Re: [JENKINS] - New Maven Controller for the project
To close this thread, the disconnection of linux agents was a side effect of the kernel settings which were using a too long tcp timeout Gavin applied the settings recommended in this doc ( https://support.cloudbees.com/hc/en-us/articles/115001369667-Dedicated-SSH-agent-gets-disconnected ) and it solved this issue sysctl -w net.ipv4.tcp_keepalive_time=120 sysctl -w net.ipv4.tcp_keepalive_intvl=30 sysctl -w net.ipv4.tcp_keepalive_probes=8 sysctl -w net.ipv4.tcp_fin_timeout=30 Thanks a lot Gavin for your help On Tue, Jul 27, 2021 at 10:48 AM Arnaud Héritier wrote: > thanks > As discussed on Slack I will open.a support case on CloudBees side to > study the instability issue of linux agents. > I will verify that there is nothing wrong in the new setup (but I found > nothing bad personally which could create such issue) > The major change when we compare ci-builds and ci-maven environments is > that our agents are now running on Azure and sadly I heard about similar > issues in others communities using Azure like Jenkins > I will check if we can find a solution or if we can give enough details to > Gavin to open a case on Azure side too. > If we really don't find any solution with Azure we'll see with Gavin to > deploy our agents somewhere else (but let's try to give a chance to Azure > first) > > Cheers > > > > On Tue, Jul 27, 2021 at 10:37 AM Gavin McDonald > wrote: > >> On Tue, Jul 27, 2021 at 10:18 AM Arnaud Héritier >> wrote: >> >> > Gavin, these JDKs are only for build agents, right ? >> > Tibor was asking for the JVM used to host Tomcat/Jenkins. >> > (And I suppose that the controller part is templatised) >> > >> >> Oh right, sorry, yes the client controllers use a system openjdk 8 >> >> >> https://github.com/apache/infrastructure-p6/blob/production/modules/jenkins_client_master/manifests/init.pp >> >> >> > On Mon, Jul 26, 2021 at 1:06 PM Gavin McDonald >> > wrote: >> > >> >> There are MANY JDKS installed already. Oracle JDKs OpenJDKs >> AdoptOpenJDKs >> >> - they are all already there. >> >> >> >> >> https://cwiki.apache.org/confluence/display/INFRA/JDK+Installation+Matrix >> >> >> >> On Mon, Jul 26, 2021 at 11:47 AM Arnaud Héritier >> >> wrote: >> >> >> >> > It has to be discussed with infra. >> >> > I am not sure which distro is used. >> >> > It's a Private Build of openJDK 8 (today CloudBees CI doesn't support >> >> > something else than Java 8 - no comment) >> >> > I don't have the feeling for now (with the data I reviewed) that >> it's a >> >> > memory / GC issue (it could create disconnections under high load) >> >> > Here the stability issue occurs even when the controller does nothing >> >> (the >> >> > controller cannot ping the agent or vice and versa) and it seems to >> >> impact >> >> > more the linux agents than the windows ones (it's a pity) >> >> > >> >> > >> >> > >> >> > On Fri, Jul 23, 2021 at 12:06 AM Tibor Digana < >> tibordig...@apache.org> >> >> > wrote: >> >> > >> >> >> Can you install AdoptOpenJdk for the Jenkins controller? >> >> >> It contains Eclipse OpenJ9 Garbage Collector and it significantly >> >> >> decreases >> >> >> memory consumption of the application due to the meta space goes to >> the >> >> >> disk. >> >> >> You should save 40 - 75% out of 3GB. >> >> >> I used G1, Shenandoah, ZGC and Eclipse OpenJ9 which saved the most >> >> memory. >> >> >> >> >> >> On Thu, Jul 22, 2021 at 9:23 AM Arnaud Héritier < >> aherit...@gmail.com> >> >> >> wrote: >> >> >> >> >> >> > yes for the controller it depends of its size (number of jobs and >> >> types >> >> >> of >> >> >> > jobs) but here we are fine it seems with our 3Gb >> >> >> > >> >> >> > * Java >> >> >> > - Version: 1.8.0292 >> >> >> > - Maximum memory: 3.00 GB (3221225472) >> >> >> > - Allocated memory: 3.00 GB (3221225472) >> >> >> > - Free memory: 750.15 MB (786591664) >> >> >> > - In-use memory: 2.27 GB (2434633808) >> >> >> > - GC strategy: G1 >> >> >> > - Available CPUs: 2
Re: [VOTE] Release Apache Maven version 3.8.2
+1 Tested on several projects with no issue I agree that the performance is a bit degraded but nothing blocker compared the value of the fixes introduced here. On Sun, Aug 8, 2021 at 10:53 PM Sylwester Lachiewicz wrote: > +1 > > niedz., 8 sie 2021, 21:32 użytkownik Robert Scholte > napisał: > > > +1 > > On 4-8-2021 22:02:18, Michael Osipov wrote: > > Hi, > > > > We solved 68 issues: > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12349965 > > > > 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%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC > > > > Staging repo: > > https://repository.apache.org/content/repositories/maven-1657/ > > > > Dev dist directory: > > https://dist.apache.org/repos/dist/dev/maven/maven-3/3.8.2/ > > > > Source release checksums: > > apache-maven-3.8.2-src.zip sha512: > > > > > 228ae07dfd89f73cc7d0b10b60708db2730465dbe6022968bde6c5d7f0df9bcd7f460fe1d8012726a29f136486bdb63d1e1ba932e307380fe4c1f4db440407dd > > apache-maven-3.8.2-src.tar.gz sha512: > > > > > 617377ad85ced7961f972610ed88535fd3f1ab18e104556d8a3adee7769515ee67ee3cbaff50afcffd74a443b471b806acb1ae92f91a259bc8ccaab56795baf6 > > > > Binary release checksums: > > apache-maven-3.8.2-bin.zip sha512: > > > > > 59ad2cbd6b7abde34ebedda94ce5631256373718e71b55202035bd1190d0144f071433f78b99e16f1204413b3eb888659e5039009e1ad0106f16332e3c62bced > > apache-maven-3.8.2-bin.tar.gz sha512: > > > > > b0bf39460348b2d8eae1c861ced6c3e8a077b6e761fb3d4669be5de09490521a74db294cf031b0775b2dfcd57bd82246e42ce10904063ef8e3806222e686f222 > > > > Draft for release notes: > > https://github.com/apache/maven-site/pull/251 > > > > > > Guide to testing staged releases: > > http://maven.apache.org/guides/development/guide-testing-releases.html > > > > Vote open for at least 72 hours. > > > > [ ] +1 > > [ ] +0 > > [ ] -1 > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > -- Arnaud Héritier Twitter/GitHub/... : aheritier
Re: [VOTE] Release Apache Maven Enforcer Plugin / Extension version 3.0.0
+1 Le mar. 27 juil. 2021 à 19:32, Robert Scholte a écrit : > +1 > > On 26-7-2021 23:17:57, Robert Scholte wrote: > Hi, > > We solved 37 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317520=12346527=Text > > There are still a couple of issues left in JIRA: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317520%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC > > Staging repo: > https://repository.apache.org/content/repositories/maven-1656 > > https://repository.apache.org/content/repositories/maven-1656/org/apache/maven/enforcer/enforcer/3.0.0/enforcer-3.0.0-source-release.zip > > Source release checksum(s): > > enforcer-3.0.0-source-release.zip sha512: > 2916475006ee76223de1d2fc58129b42864275edcfcf14945bef7699fa29fb26e23f35532d54a83413f3ab1bfb84a05885418ce5aa3d6b25dad29299c5957523 > > 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 > -- Arnaud Héritier Twitter/Skype : aheritier
Re: [JENKINS] - New Maven Controller for the project
thanks As discussed on Slack I will open.a support case on CloudBees side to study the instability issue of linux agents. I will verify that there is nothing wrong in the new setup (but I found nothing bad personally which could create such issue) The major change when we compare ci-builds and ci-maven environments is that our agents are now running on Azure and sadly I heard about similar issues in others communities using Azure like Jenkins I will check if we can find a solution or if we can give enough details to Gavin to open a case on Azure side too. If we really don't find any solution with Azure we'll see with Gavin to deploy our agents somewhere else (but let's try to give a chance to Azure first) Cheers On Tue, Jul 27, 2021 at 10:37 AM Gavin McDonald wrote: > On Tue, Jul 27, 2021 at 10:18 AM Arnaud Héritier > wrote: > > > Gavin, these JDKs are only for build agents, right ? > > Tibor was asking for the JVM used to host Tomcat/Jenkins. > > (And I suppose that the controller part is templatised) > > > > Oh right, sorry, yes the client controllers use a system openjdk 8 > > > https://github.com/apache/infrastructure-p6/blob/production/modules/jenkins_client_master/manifests/init.pp > > > > On Mon, Jul 26, 2021 at 1:06 PM Gavin McDonald > > wrote: > > > >> There are MANY JDKS installed already. Oracle JDKs OpenJDKs > AdoptOpenJDKs > >> - they are all already there. > >> > >> > https://cwiki.apache.org/confluence/display/INFRA/JDK+Installation+Matrix > >> > >> On Mon, Jul 26, 2021 at 11:47 AM Arnaud Héritier > >> wrote: > >> > >> > It has to be discussed with infra. > >> > I am not sure which distro is used. > >> > It's a Private Build of openJDK 8 (today CloudBees CI doesn't support > >> > something else than Java 8 - no comment) > >> > I don't have the feeling for now (with the data I reviewed) that it's > a > >> > memory / GC issue (it could create disconnections under high load) > >> > Here the stability issue occurs even when the controller does nothing > >> (the > >> > controller cannot ping the agent or vice and versa) and it seems to > >> impact > >> > more the linux agents than the windows ones (it's a pity) > >> > > >> > > >> > > >> > On Fri, Jul 23, 2021 at 12:06 AM Tibor Digana > > >> > wrote: > >> > > >> >> Can you install AdoptOpenJdk for the Jenkins controller? > >> >> It contains Eclipse OpenJ9 Garbage Collector and it significantly > >> >> decreases > >> >> memory consumption of the application due to the meta space goes to > the > >> >> disk. > >> >> You should save 40 - 75% out of 3GB. > >> >> I used G1, Shenandoah, ZGC and Eclipse OpenJ9 which saved the most > >> memory. > >> >> > >> >> On Thu, Jul 22, 2021 at 9:23 AM Arnaud Héritier > > >> >> wrote: > >> >> > >> >> > yes for the controller it depends of its size (number of jobs and > >> types > >> >> of > >> >> > jobs) but here we are fine it seems with our 3Gb > >> >> > > >> >> > * Java > >> >> > - Version: 1.8.0292 > >> >> > - Maximum memory: 3.00 GB (3221225472) > >> >> > - Allocated memory: 3.00 GB (3221225472) > >> >> > - Free memory: 750.15 MB (786591664) > >> >> > - In-use memory: 2.27 GB (2434633808) > >> >> > - GC strategy: G1 > >> >> > - Available CPUs: 2 > >> >> > > >> >> > For agents I reduced the memory allocated to the agent process but > it > >> >> > doesn't help much (it seems - even if it is still a good thing to > do) > >> >> > > >> >> > What is strange is that I see our agents sometimes disconnected > even > >> >> when > >> >> > we have no activity on the jenkins controller > >> >> > > >> >> > Sadly jenkins is deployed on Apache Tomcat thus I cannot get access > >> to > >> >> its > >> >> > logs > >> >> > > >> >> > In general the connection lost is detected by what we call the > >> >> PingThread ( > >> >> > > >> >> > > >> >> > >> > https://www.jenkins.io/doc/book/system-administration/monitoring/#ping-thread > >> >> > ) bu
Re: [JENKINS] - New Maven Controller for the project
Gavin, these JDKs are only for build agents, right ? Tibor was asking for the JVM used to host Tomcat/Jenkins. (And I suppose that the controller part is templatised) On Mon, Jul 26, 2021 at 1:06 PM Gavin McDonald wrote: > There are MANY JDKS installed already. Oracle JDKs OpenJDKs AdoptOpenJDKs > - they are all already there. > > https://cwiki.apache.org/confluence/display/INFRA/JDK+Installation+Matrix > > On Mon, Jul 26, 2021 at 11:47 AM Arnaud Héritier > wrote: > > > It has to be discussed with infra. > > I am not sure which distro is used. > > It's a Private Build of openJDK 8 (today CloudBees CI doesn't support > > something else than Java 8 - no comment) > > I don't have the feeling for now (with the data I reviewed) that it's a > > memory / GC issue (it could create disconnections under high load) > > Here the stability issue occurs even when the controller does nothing > (the > > controller cannot ping the agent or vice and versa) and it seems to > impact > > more the linux agents than the windows ones (it's a pity) > > > > > > > > On Fri, Jul 23, 2021 at 12:06 AM Tibor Digana > > wrote: > > > >> Can you install AdoptOpenJdk for the Jenkins controller? > >> It contains Eclipse OpenJ9 Garbage Collector and it significantly > >> decreases > >> memory consumption of the application due to the meta space goes to the > >> disk. > >> You should save 40 - 75% out of 3GB. > >> I used G1, Shenandoah, ZGC and Eclipse OpenJ9 which saved the most > memory. > >> > >> On Thu, Jul 22, 2021 at 9:23 AM Arnaud Héritier > >> wrote: > >> > >> > yes for the controller it depends of its size (number of jobs and > types > >> of > >> > jobs) but here we are fine it seems with our 3Gb > >> > > >> > * Java > >> > - Version: 1.8.0292 > >> > - Maximum memory: 3.00 GB (3221225472) > >> > - Allocated memory: 3.00 GB (3221225472) > >> > - Free memory: 750.15 MB (786591664) > >> > - In-use memory: 2.27 GB (2434633808) > >> > - GC strategy: G1 > >> > - Available CPUs: 2 > >> > > >> > For agents I reduced the memory allocated to the agent process but it > >> > doesn't help much (it seems - even if it is still a good thing to do) > >> > > >> > What is strange is that I see our agents sometimes disconnected even > >> when > >> > we have no activity on the jenkins controller > >> > > >> > Sadly jenkins is deployed on Apache Tomcat thus I cannot get access to > >> its > >> > logs > >> > > >> > In general the connection lost is detected by what we call the > >> PingThread ( > >> > > >> > > >> > https://www.jenkins.io/doc/book/system-administration/monitoring/#ping-thread > >> > ) but not only > >> > > >> > https://ci-maven.apache.org/log/all > >> > > >> > For example it was few minutes ago we got 3 agents disconnected while > >> > nothing was running > >> > > >> > 2021-07-22 06:58:21.769+ [id=106291] INFO > >> > hudson.slaves.ChannelPinger$1#onDead: > >> > Ping failed. Terminating the channel maven4. > >> > java.util.concurrent.TimeoutException: Ping started at 1626936861769 > >> hasn't > >> > completed by 1626937101769 > >> > at hudson.remoting.PingThread.ping(PingThread.java:134) > >> > at hudson.remoting.PingThread.run(PingThread.java:90) > >> > 2021-07-22 06:58:21.778+ [id=106292] INFO > >> > hudson.slaves.ChannelPinger$1#onDead: > >> > Ping failed. Terminating the channel maven3. > >> > java.util.concurrent.TimeoutException: Ping started at 1626936861777 > >> hasn't > >> > completed by 1626937101778 > >> > at hudson.remoting.PingThread.ping(PingThread.java:134) > >> > at hudson.remoting.PingThread.run(PingThread.java:90) > >> > 2021-07-22 06:58:21.983+ [id=106295] INFO > >> > hudson.slaves.ChannelPinger$1#onDead: > >> > Ping failed. Terminating the channel maven5. > >> > java.util.concurrent.TimeoutException: Ping started at 1626936861982 > >> hasn't > >> > completed by 1626937101983 > >> > at hudson.remoting.PingThread.ping(PingThread.java:134) > >> > at hudson.remoting.PingThread.run(PingThread.java:90) > >> > > >> > @Gav
Re: [JENKINS] - New Maven Controller for the project
It has to be discussed with infra. I am not sure which distro is used. It's a Private Build of openJDK 8 (today CloudBees CI doesn't support something else than Java 8 - no comment) I don't have the feeling for now (with the data I reviewed) that it's a memory / GC issue (it could create disconnections under high load) Here the stability issue occurs even when the controller does nothing (the controller cannot ping the agent or vice and versa) and it seems to impact more the linux agents than the windows ones (it's a pity) On Fri, Jul 23, 2021 at 12:06 AM Tibor Digana wrote: > Can you install AdoptOpenJdk for the Jenkins controller? > It contains Eclipse OpenJ9 Garbage Collector and it significantly decreases > memory consumption of the application due to the meta space goes to the > disk. > You should save 40 - 75% out of 3GB. > I used G1, Shenandoah, ZGC and Eclipse OpenJ9 which saved the most memory. > > On Thu, Jul 22, 2021 at 9:23 AM Arnaud Héritier > wrote: > > > yes for the controller it depends of its size (number of jobs and types > of > > jobs) but here we are fine it seems with our 3Gb > > > > * Java > > - Version: 1.8.0292 > > - Maximum memory: 3.00 GB (3221225472) > > - Allocated memory: 3.00 GB (3221225472) > > - Free memory: 750.15 MB (786591664) > > - In-use memory: 2.27 GB (2434633808) > > - GC strategy: G1 > > - Available CPUs: 2 > > > > For agents I reduced the memory allocated to the agent process but it > > doesn't help much (it seems - even if it is still a good thing to do) > > > > What is strange is that I see our agents sometimes disconnected even when > > we have no activity on the jenkins controller > > > > Sadly jenkins is deployed on Apache Tomcat thus I cannot get access to > its > > logs > > > > In general the connection lost is detected by what we call the > PingThread ( > > > > > https://www.jenkins.io/doc/book/system-administration/monitoring/#ping-thread > > ) but not only > > > > https://ci-maven.apache.org/log/all > > > > For example it was few minutes ago we got 3 agents disconnected while > > nothing was running > > > > 2021-07-22 06:58:21.769+ [id=106291] INFO > > hudson.slaves.ChannelPinger$1#onDead: > > Ping failed. Terminating the channel maven4. > > java.util.concurrent.TimeoutException: Ping started at 1626936861769 > hasn't > > completed by 1626937101769 > > at hudson.remoting.PingThread.ping(PingThread.java:134) > > at hudson.remoting.PingThread.run(PingThread.java:90) > > 2021-07-22 06:58:21.778+ [id=106292] INFO > > hudson.slaves.ChannelPinger$1#onDead: > > Ping failed. Terminating the channel maven3. > > java.util.concurrent.TimeoutException: Ping started at 1626936861777 > hasn't > > completed by 1626937101778 > > at hudson.remoting.PingThread.ping(PingThread.java:134) > > at hudson.remoting.PingThread.run(PingThread.java:90) > > 2021-07-22 06:58:21.983+ [id=106295] INFO > > hudson.slaves.ChannelPinger$1#onDead: > > Ping failed. Terminating the channel maven5. > > java.util.concurrent.TimeoutException: Ping started at 1626936861982 > hasn't > > completed by 1626937101983 > > at hudson.remoting.PingThread.ping(PingThread.java:134) > > at hudson.remoting.PingThread.run(PingThread.java:90) > > > > @Gavin McDonald In terms of network, is it the > same > > environment we use today compared to the ci-builds.apache.org > environment > > ? > > > > > > On Wed, Jul 21, 2021 at 11:48 PM Tibor Digana > > wrote: > > > > > In my company, I also used 1GB for Xmx of Java Heap for the Jenkins JVM > > and > > > it was enough. > > > The subprocesses like Maven need to have much more memory to allocate > for > > > themself rather than Jenkins JVM. > > > T > > > > > > On Wed, Jul 21, 2021 at 6:38 PM Arnaud Héritier > > > wrote: > > > > > > > I am looking at our builds and I try to understand why our agents are > > > often > > > > disconnected during the builds. > > > > We have in general a stacktrace like > > > > > > > > maven6 was marked offline: Connection was broken: > java.io.IOException: > > > > Pipe closed after 0 cycles > > > > at > > > > > > > > > > org.apache.sshd.common.channel.ChannelPipedInputStream.read(ChannelPipedInputStream.java:118) > > > > at > > > > > > > > > > org.apache.sshd.common.channel.Chann
Re: Upcoming Maven 3.8.2
Awesome work. Well done team On Sat, Jul 3, 2021 at 4:31 PM Michael Osipov wrote: > Folks, > > I have ported approx. 50 non-invasive issues back to maven-3.8.x branch > and it is in a very good shape. > There are only two issues open (one blocker): > * https://issues.apache.org/jira/browse/MNG-7161 > * https://issues.apache.org/jira/browse/MNG-7034 > (https://github.com/apache/maven/pull/484) > > I kindly asked gnodet@ for help to resolve them. > > Do you see any other issues either from 4.0.0-alpha-1 or others which > need to be addressed in 3.8.2? > > M > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- Arnaud Héritier Twitter/Skype : aheritier
Re: [JENKINS] - New Maven Controller for the project
yes for the controller it depends of its size (number of jobs and types of jobs) but here we are fine it seems with our 3Gb * Java - Version: 1.8.0292 - Maximum memory: 3.00 GB (3221225472) - Allocated memory: 3.00 GB (3221225472) - Free memory: 750.15 MB (786591664) - In-use memory: 2.27 GB (2434633808) - GC strategy: G1 - Available CPUs: 2 For agents I reduced the memory allocated to the agent process but it doesn't help much (it seems - even if it is still a good thing to do) What is strange is that I see our agents sometimes disconnected even when we have no activity on the jenkins controller Sadly jenkins is deployed on Apache Tomcat thus I cannot get access to its logs In general the connection lost is detected by what we call the PingThread ( https://www.jenkins.io/doc/book/system-administration/monitoring/#ping-thread ) but not only https://ci-maven.apache.org/log/all For example it was few minutes ago we got 3 agents disconnected while nothing was running 2021-07-22 06:58:21.769+ [id=106291] INFO hudson.slaves.ChannelPinger$1#onDead: Ping failed. Terminating the channel maven4. java.util.concurrent.TimeoutException: Ping started at 1626936861769 hasn't completed by 1626937101769 at hudson.remoting.PingThread.ping(PingThread.java:134) at hudson.remoting.PingThread.run(PingThread.java:90) 2021-07-22 06:58:21.778+ [id=106292] INFO hudson.slaves.ChannelPinger$1#onDead: Ping failed. Terminating the channel maven3. java.util.concurrent.TimeoutException: Ping started at 1626936861777 hasn't completed by 1626937101778 at hudson.remoting.PingThread.ping(PingThread.java:134) at hudson.remoting.PingThread.run(PingThread.java:90) 2021-07-22 06:58:21.983+ [id=106295] INFO hudson.slaves.ChannelPinger$1#onDead: Ping failed. Terminating the channel maven5. java.util.concurrent.TimeoutException: Ping started at 1626936861982 hasn't completed by 1626937101983 at hudson.remoting.PingThread.ping(PingThread.java:134) at hudson.remoting.PingThread.run(PingThread.java:90) @Gavin McDonald In terms of network, is it the same environment we use today compared to the ci-builds.apache.org environment ? On Wed, Jul 21, 2021 at 11:48 PM Tibor Digana wrote: > In my company, I also used 1GB for Xmx of Java Heap for the Jenkins JVM and > it was enough. > The subprocesses like Maven need to have much more memory to allocate for > themself rather than Jenkins JVM. > T > > On Wed, Jul 21, 2021 at 6:38 PM Arnaud Héritier > wrote: > > > I am looking at our builds and I try to understand why our agents are > often > > disconnected during the builds. > > We have in general a stacktrace like > > > > maven6 was marked offline: Connection was broken: java.io.IOException: > > Pipe closed after 0 cycles > > at > > > org.apache.sshd.common.channel.ChannelPipedInputStream.read(ChannelPipedInputStream.java:118) > > at > > > org.apache.sshd.common.channel.ChannelPipedInputStream.read(ChannelPipedInputStream.java:101) > > at > > > hudson.remoting.FlightRecorderInputStream.read(FlightRecorderInputStream.java:92) > > at > > hudson.remoting.ChunkedInputStream.readHeader(ChunkedInputStream.java:73) > > at > > > hudson.remoting.ChunkedInputStream.readUntilBreak(ChunkedInputStream.java:103) > > at > > > hudson.remoting.ChunkedCommandTransport.readBlock(ChunkedCommandTransport.java:39) > > at > > > hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) > > at > > > hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:63) > > > > > > > > As far I can see we are using 16Gb "hosts" for linux agents > > > > Something very strange is that the jenkins agent (this small component > > doing the link between the build host and the controller) is configured > > with `-Xms8g -Xmx8g` thus we are reserving for it 50% of the server mem > > (even more because of the non-heap) > > This one in general should require in general really less. 1Gb is > already a > > lot from my exp. > > Due to this, the OS can see it has the biggest process on the host and > > decide to kill it when the rest of the memory is used by the build. > > I think we should decrease this value. > > (I can do it but I don't know how was configured the ci.apache.org > agents > > and I would like to not add more issue if this setting was here in the > past > > > > I don't think it is the root cause of our instabilities (at least all) > and > > there is something else I have to find but it's a cheap fix to try > > > > FYI our agents VMs are ~like this today: > > > > -
Re: [JENKINS] - New Maven Controller for the project
ok Gavin Thanks for your feedback It's what I wanted to be sure, I didn't want to break something you are maintaining On Wed, Jul 21, 2021 at 6:47 PM Gavin McDonald wrote: > Hi Arnaud > > Surem feel free to tweak the node configs directly, these configs are not > in version control or puppet. > > On Wed, Jul 21, 2021 at 6:38 PM Arnaud Héritier > wrote: > >> I am looking at our builds and I try to understand why our agents are >> often disconnected during the builds. >> We have in general a stacktrace like >> >> maven6 was marked offline: Connection was broken: java.io.IOException: Pipe >> closed after 0 cycles >> at >> org.apache.sshd.common.channel.ChannelPipedInputStream.read(ChannelPipedInputStream.java:118) >> at >> org.apache.sshd.common.channel.ChannelPipedInputStream.read(ChannelPipedInputStream.java:101) >> at >> hudson.remoting.FlightRecorderInputStream.read(FlightRecorderInputStream.java:92) >> at >> hudson.remoting.ChunkedInputStream.readHeader(ChunkedInputStream.java:73) >> at >> hudson.remoting.ChunkedInputStream.readUntilBreak(ChunkedInputStream.java:103) >> at >> hudson.remoting.ChunkedCommandTransport.readBlock(ChunkedCommandTransport.java:39) >> at >> hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) >> at >> hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:63) >> >> >> >> As far I can see we are using 16Gb "hosts" for linux agents >> >> Something very strange is that the jenkins agent (this small component >> doing the link between the build host and the controller) is configured >> with `-Xms8g -Xmx8g` thus we are reserving for it 50% of the server mem >> (even more because of the non-heap) >> This one in general should require in general really less. 1Gb is already >> a lot from my exp. >> Due to this, the OS can see it has the biggest process on the host and >> decide to kill it when the rest of the memory is used by the build. >> I think we should decrease this value. >> (I can do it but I don't know how was configured the ci.apache.org >> agents and I would like to not add more issue if this setting was here in >> the past >> >> I don't think it is the root cause of our instabilities (at least all) >> and there is something else I have to find but it's a cheap fix to try >> >> FYI our agents VMs are ~like this today: >> >> - Java >> + Home: `/usr/local/asfpackages/java/oraclejdk-1.8.0-291/jre` >> + Vendor: Oracle Corporation >> + Version: 1.8.0291 >> + Maximum memory: 7.67 GB (8232370176) >> + Allocated memory: 7.67 GB (8232370176) >> + Free memory: 6.03 GB (6470953760) >> + In-use memory: 1.64 GB (1761416416) >> + GC strategy: ParallelGC >> + Available CPUs: 4 >> >> 8Gb is reserved, 1Gb is used (because the GC does nothing as the Free mem >> is high) >> >> I would be in favor to try to launch them with -Xms128m >> -Xmx1g -XX:+UseG1GC -XX:+UseStringDeduplication >> >> I think it's enough customization to start with >> >> Cheers >> >> On Wed, Jul 21, 2021 at 1:28 PM Arnaud Héritier >> wrote: >> >>> I am not sure about the setup >>> AFAICS we don't use any JDK installer ( >>> https://ci-maven.apache.org/configureTools/ ) thus I suppose that the >>> different JDKs are supposed to be installed directly on the agent ? >>> I am not sure how it was done on the previous environment >>> >>> On Sun, Jul 18, 2021 at 5:30 PM Tibor Digana >>> wrote: >>> >>>> The new CI system has the following issue: >>>> >>>> /home/jenkins/tools/java/latest1.7/bin/java: not found >>>> >>>> >>>> https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-surefire/job/master/104/execution/node/183/log/ >>>> >>>> >>>> >>>> On Wed, Jun 30, 2021 at 8:03 PM Gavin McDonald >>>> wrote: >>>> >>>> > Hi Maven folks. >>>> > >>>> > Infra has decided to separate off the Maven build jobs from >>>> > ci-builds.apache.org over to its very own Jenkins Controller and >>>> Agents. >>>> > >>>> > This means that Maven now has a dedicated Jenkins environment for >>>> itself. >>>> > It >>>> > also means that no other projects build jobs can build on the
Re: [JENKINS] - New Maven Controller for the project
I am looking at our builds and I try to understand why our agents are often disconnected during the builds. We have in general a stacktrace like maven6 was marked offline: Connection was broken: java.io.IOException: Pipe closed after 0 cycles at org.apache.sshd.common.channel.ChannelPipedInputStream.read(ChannelPipedInputStream.java:118) at org.apache.sshd.common.channel.ChannelPipedInputStream.read(ChannelPipedInputStream.java:101) at hudson.remoting.FlightRecorderInputStream.read(FlightRecorderInputStream.java:92) at hudson.remoting.ChunkedInputStream.readHeader(ChunkedInputStream.java:73) at hudson.remoting.ChunkedInputStream.readUntilBreak(ChunkedInputStream.java:103) at hudson.remoting.ChunkedCommandTransport.readBlock(ChunkedCommandTransport.java:39) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:63) As far I can see we are using 16Gb "hosts" for linux agents Something very strange is that the jenkins agent (this small component doing the link between the build host and the controller) is configured with `-Xms8g -Xmx8g` thus we are reserving for it 50% of the server mem (even more because of the non-heap) This one in general should require in general really less. 1Gb is already a lot from my exp. Due to this, the OS can see it has the biggest process on the host and decide to kill it when the rest of the memory is used by the build. I think we should decrease this value. (I can do it but I don't know how was configured the ci.apache.org agents and I would like to not add more issue if this setting was here in the past I don't think it is the root cause of our instabilities (at least all) and there is something else I have to find but it's a cheap fix to try FYI our agents VMs are ~like this today: - Java + Home: `/usr/local/asfpackages/java/oraclejdk-1.8.0-291/jre` + Vendor: Oracle Corporation + Version: 1.8.0291 + Maximum memory: 7.67 GB (8232370176) + Allocated memory: 7.67 GB (8232370176) + Free memory: 6.03 GB (6470953760) + In-use memory: 1.64 GB (1761416416) + GC strategy: ParallelGC + Available CPUs: 4 8Gb is reserved, 1Gb is used (because the GC does nothing as the Free mem is high) I would be in favor to try to launch them with -Xms128m -Xmx1g -XX:+UseG1GC -XX:+UseStringDeduplication I think it's enough customization to start with Cheers On Wed, Jul 21, 2021 at 1:28 PM Arnaud Héritier wrote: > I am not sure about the setup > AFAICS we don't use any JDK installer ( > https://ci-maven.apache.org/configureTools/ ) thus I suppose that the > different JDKs are supposed to be installed directly on the agent ? > I am not sure how it was done on the previous environment > > On Sun, Jul 18, 2021 at 5:30 PM Tibor Digana > wrote: > >> The new CI system has the following issue: >> >> /home/jenkins/tools/java/latest1.7/bin/java: not found >> >> >> https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-surefire/job/master/104/execution/node/183/log/ >> >> >> >> On Wed, Jun 30, 2021 at 8:03 PM Gavin McDonald >> wrote: >> >> > Hi Maven folks. >> > >> > Infra has decided to separate off the Maven build jobs from >> > ci-builds.apache.org over to its very own Jenkins Controller and >> Agents. >> > >> > This means that Maven now has a dedicated Jenkins environment for >> itself. >> > It >> > also means that no other projects build jobs can build on the Maven >> nodes; >> > and >> > then Maven jobs will no longer be able to build on the ci-builds jobs. >> > >> > Your new Controller is set up as https://ci-maven.apache.org and all >> Maven >> > Committers >> > can login via LDAP and create jobs. >> > >> > At the time of writing, there is one node/agent attached but I am >> building >> > 4 more - all >> > Ubuntu 20.04 and based in our Azure account. >> > >> > We can automagically move all your jobs over from ci-builds to ci-maven >> - I >> > just need someone to tell me go ahead and do it. >> > >> > In the meantime, feel free to have a test. The remaining 4 agents will >> be >> > online >> > by tomorrow. We will review after a month if 5 is enough nodes. >> > >> > As with other projects having their own dedicated controller, who have >> > taken advantage >> > of this isolation by having some nodes/agents given to the project as a >> > 'targeted donation' >> > so someone here may know of a Company will to donate
Re: [JENKINS] - New Maven Controller for the project
I am not sure about the setup AFAICS we don't use any JDK installer ( https://ci-maven.apache.org/configureTools/ ) thus I suppose that the different JDKs are supposed to be installed directly on the agent ? I am not sure how it was done on the previous environment On Sun, Jul 18, 2021 at 5:30 PM Tibor Digana wrote: > The new CI system has the following issue: > > /home/jenkins/tools/java/latest1.7/bin/java: not found > > > https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-surefire/job/master/104/execution/node/183/log/ > > > > On Wed, Jun 30, 2021 at 8:03 PM Gavin McDonald > wrote: > > > Hi Maven folks. > > > > Infra has decided to separate off the Maven build jobs from > > ci-builds.apache.org over to its very own Jenkins Controller and Agents. > > > > This means that Maven now has a dedicated Jenkins environment for itself. > > It > > also means that no other projects build jobs can build on the Maven > nodes; > > and > > then Maven jobs will no longer be able to build on the ci-builds jobs. > > > > Your new Controller is set up as https://ci-maven.apache.org and all > Maven > > Committers > > can login via LDAP and create jobs. > > > > At the time of writing, there is one node/agent attached but I am > building > > 4 more - all > > Ubuntu 20.04 and based in our Azure account. > > > > We can automagically move all your jobs over from ci-builds to ci-maven > - I > > just need someone to tell me go ahead and do it. > > > > In the meantime, feel free to have a test. The remaining 4 agents will be > > online > > by tomorrow. We will review after a month if 5 is enough nodes. > > > > As with other projects having their own dedicated controller, who have > > taken advantage > > of this isolation by having some nodes/agents given to the project as a > > 'targeted donation' > > so someone here may know of a Company will to donate 5 - 10 or more nodes > > specifically > > for Maven Jenkins environment. Infra can afford to hand you over 5 right > > now. > > > > Let me know if you have any questions, otherwise let me know when I can > > make the > > transfer of your jobs. > > > > Thanks > > > > -- > > > > *Gavin McDonald* > > Systems Administrator > > ASF Infrastructure Team > > > -- Arnaud Héritier Twitter/Skype : aheritier
Re: [JENKINS] - New Maven Controller for the project
This one:
https://plugins.jenkins.io/ws-cleanup/
Do we (at least PMCs) have admin privileges on the controller? In such case
you can just add it from the plugins management admin panel.
You just search the missing keyword on jenkins.io to find the plugin
implementing the missing command.
We should probably document these needs somewhere.
Arnaud
Le ven. 16 juil. 2021 à 10:02, Robert Scholte a
écrit :
> Yes, that fixed the build generating pages like
>
> https://ci-maven.apache.org/job/Maven/job/dist-tool-plugin/job/master/site/dist-tool-master-jobs.html
>
>
> Most masters are broken, most likely all due to this error:"
> No such DSL method 'cleanWs'
>
>
> Looks like another plugin is missing.
>
> Robert
> On 16-7-2021 09:52:15, Gavin McDonald wrote:
> Thanks Robert,
>
> I believe those are a result of missing plugins Ansicolor and Timestamper.
>
> Both now installed
>
> HTH
>
> On Fri, Jul 16, 2021 at 9:31 AM Robert Scholte wrote:
>
> > Okay, that makes sense.
> > Jobs have been picked up, just required quite some hours to run
> everything.
> >
> > this morning I noticed some failed with the following message:
> >
> > org.codehaus.groovy.control.MultipleCompilationErrorsException: startup
> failed:
> > WorkflowScript: 54: Invalid option type "timestamps". Valid option
> types: [authorizationMatrix, buildDiscarder, catchError,
> checkoutToSubdirectory, datadog, disableConcurrentBuilds, disableResume,
> durabilityHint, newContainerPerStage, overrideIndexTriggers,
> parallelsAlwaysFailFast, preserveStashes, quietPeriod, rateLimitBuilds,
> retry, script, skipDefaultCheckout, skipStagesAfterUnstable, throttle,
> throttleJobProperty, timeout, waitUntil, warnError, withChecks,
> withContext, withCredentials, withEnv, wrap, ws] @ line 54, column 9.
> > timestamps()
> > ^
> >
> > WorkflowScript: 56: Invalid option type "ansiColor". Valid option types:
> [authorizationMatrix, buildDiscarder, catchError, checkoutToSubdirectory,
> datadog, disableConcurrentBuilds, disableResume, durabilityHint,
> newContainerPerStage, overrideIndexTriggers, parallelsAlwaysFailFast,
> preserveStashes, quietPeriod, rateLimitBuilds, retry, script,
> skipDefaultCheckout, skipStagesAfterUnstable, throttle,
> throttleJobProperty, timeout, waitUntil, warnError, withChecks,
> withContext, withCredentials, withEnv, wrap, ws] @ line 56, column 9.
> > ansiColor('xterm')
> > ^
> >
> > 2 errors
> >
> > at
> org.codehaus.groovy.control.ErrorCollector.failIfErrors(ErrorCollector.java:310)
> > at
> org.codehaus.groovy.control.CompilationUnit.applyToPrimaryClassNodes(CompilationUnit.java:1085)
> > at
> org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:603)
> > at
> org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(CompilationUnit.java:581)
> > at
> org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:558)
> > at groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:298)
> > at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:268)
> > at groovy.lang.GroovyShell.parseClass(GroovyShell.java:688)
> > at groovy.lang.GroovyShell.parse(GroovyShell.java:700)
> > at
> org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.doParse(CpsGroovyShell.java:142)
> > at
> org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.reparse(CpsGroovyShell.java:127)
> > at
> org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.parseScript(CpsFlowExecution.java:571)
> > at
> org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.start(CpsFlowExecution.java:523)
> > at
> org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:337)
> > at hudson.model.ResourceController.execute(ResourceController.java:97)
> > at hudson.model.Executor.run(Executor.java:429)
> > Finished: FAILURE
> >
> >
> >
> > I've looked into our Jenkins scripts and and can't find these options. So
> > I assume these are some globally defined scripts that needs to be
> repaired.
> >
> > thanks,
> > Robert
> >
> > On 15-7-2021 11:18:34, Gavin McDonald wrote:
> > Hi
> >
> > On Thu, Jul 15, 2021 at 11:08 AM Robert Scholte
> > wrote:
> >
> > > In case you haven't noticed: all Windows nodes are offline.
> > >
> > >
> > Yeah they are 'leased' nodes shared between all ci-* controllers and come
> > online
> > when in use.
> >
> >
> > Robert
> > > On 15-7-2021 10:29:31, Robert Scholte wrote:
> > > Our scripts use the labels ubuntu and Windows to distinguish the OS.
> > > Is it s
Re: [VOTE] Release Apache Maven Dependency Tree version 3.1.0
+1 Le sam. 10 juil. 2021 à 12:04, Tamás Cservenák a écrit : > +1 > > On Thu, Jul 8, 2021, 14:34 Robert Scholte wrote: > > > Hi, > > > > We solved 12 issues: > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12341375=Text > > > > There are no issues left in JIRA: > > > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20component%20%3D%20maven-dependency-tree%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC > > > > Staging repo: > > https://repository.apache.org/content/repositories/maven-1654 > > > > > https://repository.apache.org/content/repositories/maven-1654/org/apache/maven/shared/maven-dependency-tree/3.1.0/maven-dependency-tree-3.1.0-source-release.zip > > > > Source release checksum(s): > > > > maven-dependency-tree-3.1.0-source-release.zip sha512: > a34df4748ed28dcf0224abd1ff7c2ebe228c90e95afa01b0a9590770392a9642c3b716cd09847c30f6a58492b5e08015f2ffa0e498f0351a85a97c6dc089e6c4 > > > > Staging site: > > https://maven.apache.org/shared-archives\maven-dependency-tree-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 > > > -- Arnaud Héritier Twitter/Skype : aheritier
Re: [VOTE] Release Apache Parent POM version 24
+1 Le sam. 10 juil. 2021 à 11:56, Michael Osipov a écrit : > Am 2021-07-10 um 03:39 schrieb Hervé BOUTEMY: > > Hi, > > > > We solved 17 issues: > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250=12346845=Text > > > > > https://github.com/apache/maven-apache-parent/compare/apache-23...apache-24 > > > > Staging repo: > > https://repository.apache.org/content/repositories/orgapacheapache-1021/ > > > https://repository.apache.org/content/repositories/orgapacheapache-1021/org/apache/apache/24/apache-24-source-release.zip > > > > Source release checksum(s): > > apache-24-source-release.zip sha512: > 3c0667eee535523ba16309c991e5aed4ef59f48bae623eea6757762ff03ec3ef3ab51d11958a75c032efb95be491c2c8a367b46c7ca0104e6203a5003c878ad8 > > > > 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 > > > ----- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- Arnaud Héritier Twitter/Skype : aheritier
Re: [JENKINS] - New Maven Controller for the project
Hi Gavin Let’s go. I cannot test more than the authentication today but I can assist more later this month after my vacations. What is important is to move the shared libraries used by our jobs (I do not remember how they were configured). We will see if we need / have to find some sponsors to setup some additional build nodes. Thanks for your help. Le jeu. 8 juil. 2021 à 23:06, Enrico Olivelli a écrit : > Il giorno gio 8 lug 2021 alle ore 20:06 Gavin McDonald < > gmcdon...@apache.org> > ha scritto: > > > Hi All, > > > > With no more interest in this subject, and no willing testers, I'll be > > going ahead tomorrow and move all Maven jobs to ci-maven.apache.org. > > > > I have tested that I am able to login to ci-maven with my LDAP credentials > > Thanks > Enrico > > > > > > Feel free to check after the move and create INFRA jira ticket(s) for > > anything that breaks as a result. > > > > Gav... > > > > On 2021/06/30 18:23:54, Gavin McDonald wrote: > > > Hi Michael, > > > > > > On 2021/06/30 18:12:12, Michael Osipov wrote: > > > > Am 2021-06-30 um 20:03 schrieb Gavin McDonald: > > > > > Hi Maven folks. > > > > > > > > > > Infra has decided to separate off the Maven build jobs from > > > > > ci-builds.apache.org over to its very own Jenkins Controller and > > Agents. > > > > > > > > > > This means that Maven now has a dedicated Jenkins environment for > > itself. > > > > > It > > > > > also means that no other projects build jobs can build on the Maven > > nodes; > > > > > and > > > > > then Maven jobs will no longer be able to build on the ci-builds > > jobs. > > > > > > > > > > Your new Controller is set up as https://ci-maven.apache.org and > > all Maven > > > > > Committers > > > > > can login via LDAP and create jobs. > > > > > > > > > > At the time of writing, there is one node/agent attached but I am > > building > > > > > 4 more - all > > > > > Ubuntu 20.04 and based in our Azure account. > > > > > > > > Well, just Ubuntu? We actually need at least three different > operating > > > > systems to detect subtile bugs which I have found over time. > > > > Since this is on an Azure can you rather add at least one Windows and > > > > FreeBSD node to it? 4x Ubuntu won't really help. > > > > > > You are getting exactly as you have been using on ci-builds.a.o (and > > builds.a.o) before that. > > > There is no FreeBSD on any of our CI nor has there been for many years, > > we do not support > > > it. > > > > > > As for Windows nodes, you still have access to the same Windows nodes > as > > you always have, they are what are called floating agents available for > > lease by all Jenkins Controllers, so your access and availability to the > > Windows nodes will not change. We have 6 Windoes nodes currently and plan > > to add some more soon. > > > > > > If anyone were to donate any nodes to attach to ci-maven then we'd be > > happy to help add them on, including FreeBSD donated nodes, only > difference > > being that Infra would not manage them nor install any software on them, > > which would be up to the donator(s). > > > > > > HTH > > > > > > > > > > > Michael > > > > > > > > - > > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > > > > > > > > > > - > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > -- Arnaud Héritier Twitter/Skype : aheritier
Re: [VOTE] Release Apache Maven Doxia Sitetools version 1.10
+1 On Sat, Jun 26, 2021 at 3:55 PM Tamás Cservenák wrote: > +1 > > On Sat, Jun 26, 2021, 13:52 Michael Osipov wrote: > > > Hi, > > > > We solved 7 issues: > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317320=12347008 > > > > 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-1653 > > > > > https://repository.apache.org/content/repositories/maven-1653/org/apache/maven/doxia/doxia-sitetools/1.10/doxia-sitetools-1.10-source-release.zip > > > > Source release checksum(s): > > doxia-sitetools-1.10-source-release.zip > > sha512: > > > > > a4a627212d7fde967709d20114eedabfd499c3cb83ed253017211dfa9fdd881aa324117ea4aa09bfa4e7c9846b0041d6e0c0f4b95058c4d134be57a56ca4b844 > > > > 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 > > > > > -- Arnaud Héritier Twitter/Skype : aheritier
Re: [VOTE] Import mvndaemon/mvnd project @ Apache
+1 On Wed, Jun 16, 2021 at 8:50 AM Olivier Lamy wrote: > Hi > As already proposed by Guillaume, it looks to be a good idea to > import mvndaemon/mvnd here at Apache. > > I'd like to propose a vote for this. > +1: import the project here > 0 : no real idea > -1 : no (please explain why) > > cheers > -- > Olivier > PS: Actually I have no idea how binding works in such vote. > -- Arnaud Héritier Twitter/Skype : aheritier
Re: Welcome Guillaume Nodet as new Maven Committer
Welcome Guillaume !! Happy to see you here. Cheers On Tue, May 25, 2021 at 7:19 PM Robert Scholte wrote: > Hi, > > On behalf of the Apache Maven PMC I am pleased to announce that > Guillaume Nodet has been voted in as new Apache Maven committer > and he has accepted this invitation. > > Welcome on board and have a lot of fun! > > Thanks, > Robert Scholte > -- Arnaud Héritier Twitter/Skype : aheritier
Re: [VOTE] Release Apache Maven Javadoc Plugin version 3.3.0
+1 Le sam. 22 mai 2021 à 09:50, Frederik Boster a écrit : > +1 > > Works on Ubuntu 21.04 with Maven 3.6.3. > > Best Regards > Frederik Boster > > On Sat, May 22, 2021, 09:43 Robert Scholte wrote: > > > Dear all, > > > > I need some extra votes in order to release this. > > > > thanks, > > Robert > > On 18-5-2021 20:43:37, Robert Scholte wrote: > > Hi, > > > > We solved 28 issues: > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317529=12346637=Text > > > > There are still a couple of issues left in JIRA: > > > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317529%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC > > > > Staging repo: > > https://repository.apache.org/content/repositories/maven-1649 > > > > > https://repository.apache.org/content/repositories/maven-1649/org/apache/maven/plugins/maven-javadoc-plugin/3.3.0/maven-javadoc-plugin-3.3.0-source-release.zip > > > > Source release checksum(s): > > > > maven-javadoc-plugin-3.3.0-source-release.zip sha512: > 780e485ea5bb05a074089f243f6442ad43d9627e7a3805e5985dbda67751fcf140504e48b1e74596dc10d187cb6bb3d9a153f74dda3b733e2d8d3a42062d4794 > > > > 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 at least 72 hours. > > > > [ ] +1 > > [ ] +0 > > [ ] -1 > > > -- Arnaud Héritier Twitter/Skype : aheritier
Re: [VOTE] Release Apache Maven JXR Plugin version 3.1.1
+1 Le dim. 18 avr. 2021 à 21:12, Robert Scholte a écrit : > Hi, > > We solved 12 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317527=12344185=Text > > There are still a couple of issues left in JIRA: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317527%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC > > Staging repo: > https://repository.apache.org/content/repositories/maven-1640/ > > https://repository.apache.org/content/repositories/maven-1640/org/apache/maven/jxr/jxr/3.1.1/jxr-3.1.1-source-release.zip > > Source release checksum(s): > > jxr-3.1.1-source-release.zip sha512: > d7bdbedc72568192a9b63132a91852379ad542c606d222a87cf316e1cef8e60434c4b573b55d7e39c1159cb17728eb5ae5c1cb0922337bb5c06885805a36d76c > > Staging site: > https://maven.apache.org/jxr-archives/jxr-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 > -- Arnaud Héritier Twitter/Skype : aheritier
Re: [VOTE] Release Apache Maven Release Plugin version 3.0.0-M4
+1 On Thu, Apr 15, 2021 at 10:36 AM Sylwester Lachiewicz wrote: > +1 > Sylwester > > czw., 15 kwi 2021, 10:22 użytkownik Olivier Lamy > napisał: > > > +1 > > > > On Tue, 13 Apr 2021 at 3:31 am, Robert Scholte > > wrote: > > > > > Hi, > > > > > > We solved 5 issues: > > > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824=12348079=Text > > > > > > There are still a couple of issues left in JIRA: > > > > > > > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317824%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC > > > > > > Staging repo: > > > https://repository.apache.org/content/repositories/maven-1639 > > > > > > > > > https://repository.apache.org/content/repositories/maven-1639/org/apache/maven/release/maven-release/3.0.0-M4/maven-release-3.0.0-M4-source-release.zip > > > > > > Source release checksum(s): > > > > > > maven-release-3.0.0-M4-source-release.zip sha512: > > > 49ec8c495b11696671e83ccdeee3408223d0aef3cfd5f48e2a4afc66e225f550069a060702205152e3e59238f9db64efd85ac626b25b05596be3ef422b991895 > > > > > > Staging site: > > > https://maven.apache.org/maven-release-archives\maven-release-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 > > > > > -- > > Olivier Lamy > > http://twitter.com/olamy | http://linkedin.com/in/olamy > > > -- Arnaud Héritier Twitter/Skype : aheritier
Re: [VOTE] Release Apache Maven Wrapper Plugin version 3.0.2
+1 On Wed, Apr 7, 2021 at 11:26 PM Olivier Lamy wrote: > +1 > > On Wed, 7 Apr 2021 at 4:50 pm, Robert Scholte > wrote: > > > +1 > > > > On 5-4-2021 20:23:34, Maarten Mulders wrote: > > +1 > > > > Tested with Maven 3.8.1 on macOS. Plugin does not generate a wrapper for > > Maven 3.6.3, 3.7.0 or 3.8.1. > > > > > > Maarten > > > > On 05/04/2021 16:29, Robert Scholte wrote: > > > To: "Maven Developers List" > > > Subject: [VOTE] Release Apache Maven Wrapper Plugin version 3.0.2 > > > > > > Hi, > > > > > > We solved 2 issues: > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12323721=12348358=Text > > > > > > There are zero issues left in JIRA: > > > > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%2012323721%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC > > > > > > Staging repo: > > > https://repository.apache.org/content/repositories/maven-1637/ > > > > > > https://repository.apache.org/content/repositories/maven-1637/org/apache/maven/plugins/maven-wrapper-plugin/3.0.2/maven-wrapper-plugin-3.0.2-source-release.zip > > > > > > Source release checksum(s): > > > > > maven-wrapper-plugin-3.0.2-source-release.zip sha512: > 3b185d5486249f9ad4e0133462d294aeae05bc80fa3cbc7dd622c50689eb9316d5b260fa28a03e1922fe3e2ec1beb22f69c033c7f4894d90c4d874e1835089cc > > > > > > Staging site: > > > https://maven.apache.org/plugins-archives/maven-wrapper-plugin-LATEST/ > > > > > > Guide to testing staged releases: > > > > https://maven.apache.org/guides/development/guide-testing-releases.html > > > > > > Testing the plugin with Maven 3 will fail (see MWRAPPER-8) > > > To test the plugin with Maven 4, ensure to add the following > repository: > > > > > > > > > apache.snapshots > > > Apache Snapshot Repository > > > https://repository.apache.org/snapshots > > > > > > false > > > > > > > > > > > > > > > Vote open for at least 72 hours. > > > > > > [ ] +1 > > > [ ] +0 > > > [ ] -1 > > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > -- > Olivier Lamy > http://twitter.com/olamy | http://linkedin.com/in/olamy > -- Arnaud Héritier Twitter/Skype : aheritier
Re: [VOTE] Release Apache Maven version 3.8.1
ok, I think it makes sense then. +1 for me, all my tests are ok On Wed, Mar 31, 2021 at 10:11 AM wrote: > I had the same observation. I *think* it is caused by the fact that you > manually downloaded the ZIP archive - browsers on macOS set the > 'quarantine' flag on downloaded files. It also happens if I download > 3.6.3 manually (i.e., using Firefox). > > I think the Homebrew package manager for macOS doesn't have this issue. > At least, I cannot recall ever having seen that message for Maven > versions that I installed through Homebrew. > > Thanks, > > Maarten > > On March 31, 2021 at 09:38, Arnaud Héritier wrote: > > I have a problem on macos that I didn't have with 3.6.3, when I launch > > maven it I have this error: > > > > “libjansi.jnilib” cannot be opened because the developer cannot be > verified. > > macOS cannot verify that this app is free from malware. > > Brave downloaded this file today at 09:25. > > > > It's a popup window: > > > https://www.dropbox.com/s/tj0yp3hzuerm1ll/Screenshot%202021-03-31%20at%2009.29.06.png?dl=0 > > < > https://www.dropbox.com/s/tj0yp3hzuerm1ll/Screenshot%202021-03-31%20at%2009.29.06.png?dl=0 > > > > > > I manually installed Maven from the zip (in general I use ASDF). > > > > I can use the "Allow Anyway" in "Security & Privacy" settings but then I > > have another message: > > > https://www.dropbox.com/s/icgddpm7zfzvjx8/Screenshot%202021-03-31%20at%2009.37.14.png?dl=0 > > < > https://www.dropbox.com/s/icgddpm7zfzvjx8/Screenshot%202021-03-31%20at%2009.37.14.png?dl=0 > > > > > > macOS cannot verify the developer of “libjansi.jnilib”. Are you sure you > > want to open it? > > By opening this app, you will be overriding system security which can > > expose your computer and personal information to malware that may harm > > your Mac or compromise your privacy. > > Brave downloaded this file today at 09:25. > > > > > > After this last pop the problem disappears. > > > > Not a problem for me but I don't remember to have done this in the past > > for jansi. Did we change anything ? > > > > > > On Wed, Mar 31, 2021 at 8:46 AM Maarten Mulders > <mailto:mthmuld...@apache.org>> wrote: > > > > Retried the test that I did on 3.8.0, this time I observe the > desired / > > correct behaviour. > > > > > > +1 > > > > > > Maarten > > > > > > On March 31, 2021, at 01:46, Mark Derricutt wrote: > > > +1 non-binding > > > > > > - bistro zips are in the /dev/ tree > > > - my multi-repo osgi maven tiles weirdo build works fine. > > > > > > > > > > > > > > > From: Robert Scholte > <mailto:rfscho...@apache.org>> > <mailto:rfscho...@apache.org>> > > > Reply: Maven Developers List > <mailto:dev@maven.apache.org>> > <mailto:dev@maven.apache.org>> > > > Date: 31 March 2021 at 9:58:56 AM > > > To: dev@maven.apache.org <mailto:dev@maven.apache.org> > > mailto:dev@maven.apache.org>> > > mailto:dev@maven.apache.org>> > > > Subject: [VOTE] Release Apache Maven version 3.8.1 > > > > > > Hi, > > > > > > For the details about this release, please read > > > https://maven.apache.org/docs/3.8.1/release-notes.html > > <https://maven.apache.org/docs/3.8.1/release-notes.html> > > > Also please provide feedback on the release notes. (as you know, > > these are > > > published separately from the release, so it doesn't have to > > block the > > > release itself) > > > > > > We solved 6 issues: > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12350032=Text > > < > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12350032=Text > > > > > > > > Staging repo: > > > https://repository.apache.org/content/repositories/maven-1634/ > > <https://repository.apache.org/content/repositories/maven-1634/> > > > > > > https://dist.apache.org/repos/dist/dev/maven/maven-3/3.8.1/binaries/apache-maven-3.8.1-bin.zip > > < > https://dist.apache.org/repos/dist/dev/maven/maven-3/3.8.1/binaries/apache-maven-3.8.1-bin.zip > > > > > > > > https:/
Re: [VOTE] Release Apache Maven version 3.8.1
I have a problem on macos that I didn't have with 3.6.3, when I launch maven it I have this error: “libjansi.jnilib” cannot be opened because the developer cannot be verified. macOS cannot verify that this app is free from malware. Brave downloaded this file today at 09:25. It's a popup window: https://www.dropbox.com/s/tj0yp3hzuerm1ll/Screenshot%202021-03-31%20at%2009.29.06.png?dl=0 I manually installed Maven from the zip (in general I use ASDF). I can use the "Allow Anyway" in "Security & Privacy" settings but then I have another message: https://www.dropbox.com/s/icgddpm7zfzvjx8/Screenshot%202021-03-31%20at%2009.37.14.png?dl=0 macOS cannot verify the developer of “libjansi.jnilib”. Are you sure you want to open it? By opening this app, you will be overriding system security which can expose your computer and personal information to malware that may harm your Mac or compromise your privacy. Brave downloaded this file today at 09:25. After this last pop the problem disappears. Not a problem for me but I don't remember to have done this in the past for jansi. Did we change anything ? On Wed, Mar 31, 2021 at 8:46 AM Maarten Mulders wrote: > Retried the test that I did on 3.8.0, this time I observe the desired / > correct behaviour. > > > +1 > > > Maarten > > > On March 31, 2021, at 01:46, Mark Derricutt wrote: > > +1 non-binding > > > > - bistro zips are in the /dev/ tree > > - my multi-repo osgi maven tiles weirdo build works fine. > > > > > > > > > > From: Robert Scholte > > Reply: Maven Developers List < > dev@maven.apache.org> > > Date: 31 March 2021 at 9:58:56 AM > > To: dev@maven.apache.org > > Subject: [VOTE] Release Apache Maven version 3.8.1 > > > > Hi, > > > > For the details about this release, please read > > https://maven.apache.org/docs/3.8.1/release-notes.html > > Also please provide feedback on the release notes. (as you know, these > are > > published separately from the release, so it doesn't have to block the > > release itself) > > > > We solved 6 issues: > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12350032=Text > > > > Staging repo: > > https://repository.apache.org/content/repositories/maven-1634/ > > > https://dist.apache.org/repos/dist/dev/maven/maven-3/3.8.1/binaries/apache-maven-3.8.1-bin.zip > > > https://dist.apache.org/repos/dist/dev/maven/maven-3/3.8.1/source/apache-maven-3.8.1-src.zip > > > > Source release checksum(s): > > apache-maven-3.8.1-bin.zip sha512: > > > c585847bfbcf8647aeabfd3e8bf0ac3f67a037bd345545e274766f144c2b978b3457cbc3e31545e62c21ad69e732695de01ec96ea2580e5da67bd85df095c0f4 > > > > apache-maven-3.8.1-src.zip > > sha512: > 893988635349985074c88ce5ef27ac5ccb62fcdf58846209eee8a7ea5515238288b91c202347ca42e201ab336c14d83f3f5fd8194070e57b9366bcce2414614d > > > > > > Knows issues: > > When building with the sources with JDK-16 and above, the unittest > > MavenCliTest#testStyleColors will fail. This will be fix with > MNG-7127[1], > > but is left out to keep focus on the real purpose of this release. > > > > Staging site: > > https://maven.apache.org/ref/3-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 > > > > > > --- > > [1] https://issues.apache.org/jira/browse/MNG-7127 > > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- Arnaud Héritier Twitter/Skype : aheritier
Re: [DISCUSS] Next release version: 3.6.4, 3.7.0, 3.8.0 or other
Due to the distribution error, I agree that the next release can only be 3.8.1 today On Tue, Mar 30, 2021 at 6:39 PM TheCakeIsNaOH wrote: > Hi, > > I am the maintainer of the Maven Chocolatey package. > > Given that I uploaded a 3.8.0 package after seeing the binaries in the > release > download area, there are around ~2,400 users which downloaded that version > of the package. > > Therefore, on the Chocolatey side of things, it would be best if the next > version > is something greater than 3.8.0. That way, the people that downloaded the > 3.8.0 package would upgrade to the actual release, instead of having to > downgrade manually. > > Regards, TheCakeIsNaOH > > On 2021/03/28 09:47:11, Romain Manni-Bucau wrote: > > Hi all,> > > > > Before we reroll the failed 3.8.0 I'd like we discuss openly the next> > > versioning since it seems we didn't reach a consensus yet and trying to > not> > > create too much friction for users and in the community.> > > > > As a reminder the only feature the release will get is to prevent HTTP > repo> > > (in favor of HTTPS ones). In that regard it is a breaking change if > users> > > rely on HTTP repo but a security fix (I don't come back on the HTTP ->> > > HTTPS move IT ecosystem got recently here).> > > > > So it seems there are multiple versioning options:> > > > > 1. 3.6.4: seems natural since it is a security fix, enables companies to> > > get this fix respecting a project versioning policy without having to> > > upgrade and avoids us to have to maintain 3.6 + 3.7/3.8 and soon 4.x.> > > Indeed it requires a very well documented paragraph about this change > and> > > how to workaround it (local proxy/mirror is a trivial one for example) > but> > > it will be the case whatever version we pick anyway IMHO.> > > 2. 3.7.0: since it is a breaking change it can seem natural too (but has> > > the pitfall to likely require a backport in 3.6 anyway, due to the> > > versioning policies which can prevent some users to upgrade to a 3.7)> > > 3. 3.8.0: was the vote, seems the rational was that originally we> > > targetting mvnw in 3.7 and since we didn't make it 3.8 was used. Have to> > > admit I'm not sure of this reasoning more than that (cause for me if we> > > don't have a planned feature we can either try to push/wait for it or> > > postpone it but not skip a version due to that) so if anyone wants to> > > complete the reasoning here it would be great.> > > > > Indeed my preference is for 3.6.4 which has the most advantages for> > > everyone and no additional drawbacks compared to 3.7 or 3.8 options > until> > > we try to push to get mvnw in which would mean 3.7 becomes more natural> > > (and likely imply a 3.6.x maintenance version).> > > > > Goal of this thread is to feel the overall trend and see if we can > refine> > > the proposals (for example: can we drop 3.8 one and only keep 3.7 and > 3.6> > > or - best - can we refine it to a single version after some exchanges).> > > If we keep a few proposals after some days, what about a vote where the> > > majority wins - we would just need to define how we count,> > > bindings/committers/all (my preference being last one indeed)?> > > > > Romain Manni-Bucau> > > @rmannibucau <https://twitter.com/rmannibucau> | Blog> > > <https://rmannibucau.metawerx.net/> | Old Blog> > > <http://rmannibucau.wordpress.com> | Github < > https://github.com/rmannibucau> |> > > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book> > > < > https://www.packtpub.com/application-development/java-ee-8-high-performance > >> > > > > -- Arnaud Héritier Twitter/Skype : aheritier
Re: [VOTE] Release Apache Maven version 3.8.0
+1 On Sat, Mar 27, 2021 at 4:03 AM Mark Derricutt wrote: > Mostly reads good to me, only minor niggle to me is: > > Then once the vote passed, svn move to release > > which I think might be grammatically better: > > “Once the vote has passed, svn move to the release tree ” > > +1.5 non-binding :) > > > > > From: Hervé BOUTEMY > Reply: Maven Developers List > Date: 27 March 2021 at 2:19:48 PM > To: Maven Developers List > Subject: Re: [VOTE] Release Apache Maven version 3.8.0 > > first pass of documentation improvement done in > > github.com/apache/maven-site/commit/ec73b445adc7012e1384cf1b89af3f0a6f5eee17 > please all review and see if anything you read may be mis-interpreted when > reading fast > -- Arnaud Héritier Twitter/Skype : aheritier
Re: [VOTE] Release Apache Maven version 3.8.0
Well done team. Not yet tested, I'll vote later. About the release note the link to the Repository Order <https://maven.apache.org/docs/3.8.0/maven.apache.org/guides/mini/guide-multiple-repositories.html#repository-order> page is broken. I think it is because the link doesn't have the https:// prefix/protocol) About the content and especially MNG-7117 and MNG-7118 do we have an update of https://maven.apache.org/guides/mini/guide-mirror-settings.html ? I see the code changes but I don't find the doc update. The release note maybe perhaps simplified to just say that we added 2 new features in the mirror configuration (the blocked element and the matching rule for http protocol) and we had a link to a more detailed doc Elliotte I am not sure. I agree with you that nobody promised anything but if you google Maven 3.7.0 you can find many reference about the inclusion of the wrapper [1] or the build/consumer pom [2] In any case I don't think it will be clear for everyone. [1] https://www.infoq.com/news/2020/04/maven-wrapper/ [2] https://cwiki.apache.org/confluence/display/MAVEN/Build+vs+Consumer+POM Can be easily fixed. cheers On Mon, Mar 22, 2021 at 8:40 PM Robert Scholte wrote: > Hi, > > For the details about this release, please read > https://maven.apache.org/docs/3.8.0/release-notes.html > Also please provide feedback on the release notes. (as you know, these are > published separately from the release, so it doesn't have to block the > release itself) > > We solved 5 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12350003=Text > > There are still a couple of issues left in JIRA: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%2012316922%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC > > Staging repo: > https://repository.apache.org/content/repositories/maven-1633/ > > > https://dist.apache.org/repos/dist/release/maven/maven-3/3.8.0/binaries/apache-maven-3.8.0-bin.zip > > https://dist.apache.org/repos/dist/release/maven/maven-3/3.8.0/source/apache-maven-3.8.0-src.zip > > > Source release checksum(s): > > apache-maven-3.8.0-bin.zip sha512: > b56da9a0efa45e084e4882b795787fc7b61970d19835635b2db099b91a9854f14e3776a01d569e3f7af9db946a05af91abbfad41cdc5ac09e90df25077dec01e > > apache-maven-3.8.0-src.zip sha512: > 51a1570894e8fb1ef52cb19ce472866745ccae2720e45304edd3cabc212cdf105937c76502558fe87995aea81c41402d7f581cc8e9393af234b64696e9a45893 > > > Staging site: > https://maven.apache.org/ref/3-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 > -- Arnaud Héritier Twitter/Skype : aheritier
Re: [VOTE] Release Maven Resolver version 1.6.2
+1 On Wed, Mar 17, 2021 at 8:36 AM Olivier Lamy wrote: > +1 > > On Tue, 16 Mar 2021 at 08:53, Michael Osipov wrote: > > > Hi, > > > > We solved 2 issues: > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=1235 > > > > There are still a couple of issues left in JIRA: > > > > > https://issues.apache.org/jira/projects/MRESOLVER/issues?filter=allopenissues > > > > Staging repo: > > https://repository.apache.org/content/repositories/maven-1632/ > > > > > https://repository.apache.org/content/repositories/maven-1632/org/apache/maven/resolver/maven-resolver/1.6.2/maven-resolver-1.6.2-source-release.zip > > > > Source release checksum(s): > > maven-resolver-1.6.2-source-release.zip > > > > > 521529465c4cc29390aa125e8b5495cc1e26e54eefb11298beb4c15aa5b1fef43e965171eb45933a95478d387dff3e37c978168c2bc5c08c9863140624a2 > > > > 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 > > > > > > -- > Olivier Lamy > http://twitter.com/olamy | http://linkedin.com/in/olamy > -- Arnaud Héritier Twitter/Skype : aheritier
Re: Official Maven Github Actions
I am not an expert on GitHub actions but also saw this article from Andres which is useful to deploy to Maven Central using GitHub Actions : https://andresalmiray.com/publishing-to-maven-central-using-apache-maven/ (useful with the shutdown of JFrog's JCentral repo) I think it may be good for the community if we could provide some best practices / tools such a commonly used platform I am not sure about the "verified", when I look at the ruby one it doesn't look to be small thing to maintain and I am not sure our team will have such bandwidth ( https://github.com/ruby/setup-ruby ) On Fri, Feb 12, 2021 at 6:52 PM Cesar Hernandez wrote: > Hi, > > The problems: > > Currently, the official Github actions for building and testing Java with > Maven [1] don't offer a way to specify the Maven version a workflow can > use. > Adding this support seems to be out of the scope of the > current actions/checkout@v2. [2]. > > In the Github actions market are already a couple of alternatives to > perform this setup [3] but are non-verified third parties actions. > > Currently, in the Github actions market are cero verified Maven related > actions [5] but there are already a couple really useful maven related > actions beyond just the version settings [6] > > Since early 2021, Apache related projects allows only verified actions to > be used in workflows. > > > The opportunity: > Base on the interaction with the Actions team [2] it seems Actions > verification can be done if the actions are created as part of the official > projects. For example Ruby setup action [4]. > > Before brainstorming in solution, creating a JIRA or a PR with draft > implementation, I would like to know if there is any interest within the > Maven community to offer to users certified Maven Github actions? > > > [1] > > https://docs.github.com/en/actions/guides/building-and-testing-java-with-maven > [2] https://github.com/actions/setup-java/issues/40#issuecomment-778028611 > [3] https://github.com/stCarolas/setup-maven > [4] https://github.com/ruby/setup-ruby > [5] > > https://github.com/marketplace?query=maven=actions=verified > [6] https://github.com/marketplace?after=Y3Vyc29yOjIw=maven > -- > Atentamente: > César Hernández. > -- Arnaud Héritier Twitter/Skype : aheritier
Re: Apache Hosted Git Folder not scanned anymore
Robert shared with me that an issue we have is that when we update the shared library we are rebuilding all projects/branches. I understand how it can easily kill the instance. We can disable this option [image: Screenshot 2021-02-06 at 15.14.41.png] I don't think we really want to rebuild everything when the shared lib is updated. Having the updated version used for future builds is probably enough. We can disable this feature. We will sadly lose the inclusion of the shared lib changelogs which is controlled by the same option. On Sat, Feb 6, 2021 at 3:13 PM Sylwester Lachiewicz wrote: > Yes, because after pushing changes to master (or other branch) nothing has > happened, i manually requested to scan build. I also observe that > something happened recently. > > Sylwester > > sob., 6 lut 2021, 15:07 użytkownik Arnaud Héritier > napisał: > > > I had a look at it and I am not sure if the comment is recent or not > > The job wasn't disabled and the comment not visible without editing the > job > > because the HTML was invalid > > For sure something is not right and it seems that the repo events are > > automatically triggering the builds (or add/remove branches) > > > > The latest commit I see in my emails is: [maven-jxr] 01/01: WIP misc > > changes > > In the next branch of maven-jxr > > > > > https://gitbox.apache.org/repos/asf?p=maven-jxr.git;a=shortlog;h=refs/heads/next > > 37min > > < > https://gitbox.apache.org/repos/asf?p=maven-jxr.git;a=shortlog;h=refs/heads/next37min > > > > ago > > And this branch was effectively not here : > > https://builds.apache.org/job/Maven/job/maven-box/job/maven-jxr/ > > The indexation was triggered manually by Sylvester earlier today > > > > > https://builds.apache.org/job/Maven/job/maven-box/job/maven-jxr/indexing/console > > > > Started by user Sylwester Lachiewicz > > <https://builds.apache.org/user/slachiewicz> > > [Sat Feb 06 11:56:54 UTC 2021] Starting branch indexing... > > Listing remote references... > > Checking branches... > > Checking branch master > > ‘Jenkinsfile’ found > > Met criteria > > No changes detected: master (still at > > 6df9ba323e04ef7f7612a9ea1c9d64e3f8717cc0) > > Checking branch elharo-patch-2 > > ‘Jenkinsfile’ found > > Met criteria > > No changes detected: elharo-patch-2 (still at > > 87b2d6681022c5720d57c6803f4f708749cbf146) > > Checking branch JXR-154 > > ‘Jenkinsfile’ found > > Met criteria > > No changes detected: JXR-154 (still at > > 737fdbed58af9018ce2c096cea5aaf2d60dfe396) > > Checking branch JXR-145 > > ‘Jenkinsfile’ found > > Met criteria > > No changes detected: JXR-145 (still at > > 13fa0bf46a37e627a64eb1a1e6e9d3bca1f2793b) > > Processed 4 branches > > [Sat Feb 06 11:56:57 UTC 2021] Finished branch indexing. Indexing took > 2.7 > > sec > > Finished: SUCCESS > > > > > > But for now we see no recent event: > > > > > https://builds.apache.org/job/Maven/job/maven-box/job/maven-jxr/indexing/events > > > > I triggered the reindexation > > https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven-jxr/ > > 3 new branches added but for each of them we do 16 builds :-/ > > > > > > > https://ci-builds.apache.org/blue/organizations/jenkins/Maven%2Fmaven-box%2Fmaven-jxr/detail/unused/1/pipeline > > > > I understand we want to validate with various versions of maven / OS / > Java > > but on every branch it looks a lot (too much) > > > > > > On Sat, Feb 6, 2021 at 12:54 PM Robert Scholte > > wrote: > > > > > I see this line in the description: > > > > jobs > > > in the queue, please fix this before re-enabling > > > > > > On 6-2-2021 12:38:21, Arnaud Héritier wrote: > > > I do not have enough privilege to do anything on this instance but the > > scan > > > is configured to be done every week even if nothing happens > > > Nothing happens means that we got no new event and effectively there is > > > nothing on this page after Feb 2nd which is suspicious : > > > https://builds.apache.org/job/Maven/job/maven-box/computation/events > > > > > > On Sat, Feb 6, 2021 at 12:18 PM Robert Scholte wrote: > > > > > > > Most likely there has been an update at INFRA, which causes that > > commits > > > > aren't picked up automatically. > > > > Last scan details[1] > > > > [Thu Feb 04 20:27:32 UTC 2021] Finished organization scan. Scan took > 1 > > > min > > > > 31 sec > > > > > > > > Finished: SUCCESS > > > > > > > > Would be great if somebody could investigate this. > > > > > > > > thanks, > > > > Robert > > > > > > > > [1] > > > > > > > > > > https://builds.apache.org/job/Maven/job/maven-box/computation/consoleFull > > > > > > > > > > > > -- > > > Arnaud Héritier > > > Twitter/Skype : aheritier > > > > > > > > > -- > > Arnaud Héritier > > Twitter/Skype : aheritier > > > -- Arnaud Héritier Twitter/Skype : aheritier
Re: Apache Hosted Git Folder not scanned anymore
Not sure if we are losing some events or if the shared controller has too many events to process We can ask to INFRA if they are aware of such issue. If needed they can contact CloudBees' support to assist in the troubleshooting. I can be in the loop and assist if I can get more details from the system Maybe Stephen or someone else is admin otherwise ? On Sat, Feb 6, 2021 at 3:13 PM Sylwester Lachiewicz wrote: > Yes, because after pushing changes to master (or other branch) nothing has > happened, i manually requested to scan build. I also observe that > something happened recently. > > Sylwester > > sob., 6 lut 2021, 15:07 użytkownik Arnaud Héritier > napisał: > > > I had a look at it and I am not sure if the comment is recent or not > > The job wasn't disabled and the comment not visible without editing the > job > > because the HTML was invalid > > For sure something is not right and it seems that the repo events are > > automatically triggering the builds (or add/remove branches) > > > > The latest commit I see in my emails is: [maven-jxr] 01/01: WIP misc > > changes > > In the next branch of maven-jxr > > > > > https://gitbox.apache.org/repos/asf?p=maven-jxr.git;a=shortlog;h=refs/heads/next > > 37min > > < > https://gitbox.apache.org/repos/asf?p=maven-jxr.git;a=shortlog;h=refs/heads/next37min > > > > ago > > And this branch was effectively not here : > > https://builds.apache.org/job/Maven/job/maven-box/job/maven-jxr/ > > The indexation was triggered manually by Sylvester earlier today > > > > > https://builds.apache.org/job/Maven/job/maven-box/job/maven-jxr/indexing/console > > > > Started by user Sylwester Lachiewicz > > <https://builds.apache.org/user/slachiewicz> > > [Sat Feb 06 11:56:54 UTC 2021] Starting branch indexing... > > Listing remote references... > > Checking branches... > > Checking branch master > > ‘Jenkinsfile’ found > > Met criteria > > No changes detected: master (still at > > 6df9ba323e04ef7f7612a9ea1c9d64e3f8717cc0) > > Checking branch elharo-patch-2 > > ‘Jenkinsfile’ found > > Met criteria > > No changes detected: elharo-patch-2 (still at > > 87b2d6681022c5720d57c6803f4f708749cbf146) > > Checking branch JXR-154 > > ‘Jenkinsfile’ found > > Met criteria > > No changes detected: JXR-154 (still at > > 737fdbed58af9018ce2c096cea5aaf2d60dfe396) > > Checking branch JXR-145 > > ‘Jenkinsfile’ found > > Met criteria > > No changes detected: JXR-145 (still at > > 13fa0bf46a37e627a64eb1a1e6e9d3bca1f2793b) > > Processed 4 branches > > [Sat Feb 06 11:56:57 UTC 2021] Finished branch indexing. Indexing took > 2.7 > > sec > > Finished: SUCCESS > > > > > > But for now we see no recent event: > > > > > https://builds.apache.org/job/Maven/job/maven-box/job/maven-jxr/indexing/events > > > > I triggered the reindexation > > https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven-jxr/ > > 3 new branches added but for each of them we do 16 builds :-/ > > > > > > > https://ci-builds.apache.org/blue/organizations/jenkins/Maven%2Fmaven-box%2Fmaven-jxr/detail/unused/1/pipeline > > > > I understand we want to validate with various versions of maven / OS / > Java > > but on every branch it looks a lot (too much) > > > > > > On Sat, Feb 6, 2021 at 12:54 PM Robert Scholte > > wrote: > > > > > I see this line in the description: > > > > jobs > > > in the queue, please fix this before re-enabling > > > > > > On 6-2-2021 12:38:21, Arnaud Héritier wrote: > > > I do not have enough privilege to do anything on this instance but the > > scan > > > is configured to be done every week even if nothing happens > > > Nothing happens means that we got no new event and effectively there is > > > nothing on this page after Feb 2nd which is suspicious : > > > https://builds.apache.org/job/Maven/job/maven-box/computation/events > > > > > > On Sat, Feb 6, 2021 at 12:18 PM Robert Scholte wrote: > > > > > > > Most likely there has been an update at INFRA, which causes that > > commits > > > > aren't picked up automatically. > > > > Last scan details[1] > > > > [Thu Feb 04 20:27:32 UTC 2021] Finished organization scan. Scan took > 1 > > > min > > > > 31 sec > > > > > > > > Finished: SUCCESS > > > > > > > > Would be great if somebody could investigate this. > > > > > > > > thanks, > > > > Robert > > > > > > > > [1] > > > > > > > > > > https://builds.apache.org/job/Maven/job/maven-box/computation/consoleFull > > > > > > > > > > > > -- > > > Arnaud Héritier > > > Twitter/Skype : aheritier > > > > > > > > > -- > > Arnaud Héritier > > Twitter/Skype : aheritier > > > -- Arnaud Héritier Twitter/Skype : aheritier
Re: Apache Hosted Git Folder not scanned anymore
Because we have a lot of repos maybe we should have a dedicated CI infra. I know that it's possible to use a dedicated Jenkins controller (and associated agents) to avoid to use the shared resources of all other projects. On Sat, Feb 6, 2021 at 3:07 PM Arnaud Héritier wrote: > I had a look at it and I am not sure if the comment is recent or not > The job wasn't disabled and the comment not visible without editing the > job because the HTML was invalid > For sure something is not right and it seems that the repo events are > automatically triggering the builds (or add/remove branches) > > The latest commit I see in my emails is: [maven-jxr] 01/01: WIP misc > changes > In the next branch of maven-jxr > > https://gitbox.apache.org/repos/asf?p=maven-jxr.git;a=shortlog;h=refs/heads/next > 37min ago > And this branch was effectively not here : > https://builds.apache.org/job/Maven/job/maven-box/job/maven-jxr/ > The indexation was triggered manually by Sylvester earlier today > https://builds.apache.org/job/Maven/job/maven-box/job/maven-jxr/indexing/console > > Started by user Sylwester Lachiewicz > <https://builds.apache.org/user/slachiewicz> > [Sat Feb 06 11:56:54 UTC 2021] Starting branch indexing... > Listing remote references... > Checking branches... > Checking branch master > ‘Jenkinsfile’ found > Met criteria > No changes detected: master (still at > 6df9ba323e04ef7f7612a9ea1c9d64e3f8717cc0) > Checking branch elharo-patch-2 > ‘Jenkinsfile’ found > Met criteria > No changes detected: elharo-patch-2 (still at > 87b2d6681022c5720d57c6803f4f708749cbf146) > Checking branch JXR-154 > ‘Jenkinsfile’ found > Met criteria > No changes detected: JXR-154 (still at > 737fdbed58af9018ce2c096cea5aaf2d60dfe396) > Checking branch JXR-145 > ‘Jenkinsfile’ found > Met criteria > No changes detected: JXR-145 (still at > 13fa0bf46a37e627a64eb1a1e6e9d3bca1f2793b) > Processed 4 branches > [Sat Feb 06 11:56:57 UTC 2021] Finished branch indexing. Indexing took 2.7 sec > Finished: SUCCESS > > > But for now we see no recent event: > https://builds.apache.org/job/Maven/job/maven-box/job/maven-jxr/indexing/events > > I triggered the reindexation > https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven-jxr/ > 3 new branches added but for each of them we do 16 builds :-/ > > > https://ci-builds.apache.org/blue/organizations/jenkins/Maven%2Fmaven-box%2Fmaven-jxr/detail/unused/1/pipeline > > I understand we want to validate with various versions of maven / OS / > Java but on every branch it looks a lot (too much) > > > On Sat, Feb 6, 2021 at 12:54 PM Robert Scholte > wrote: > >> I see this line in the description: >> > jobs in the queue, please fix this before re-enabling >> >> On 6-2-2021 12:38:21, Arnaud Héritier wrote: >> I do not have enough privilege to do anything on this instance but the >> scan >> is configured to be done every week even if nothing happens >> Nothing happens means that we got no new event and effectively there is >> nothing on this page after Feb 2nd which is suspicious : >> https://builds.apache.org/job/Maven/job/maven-box/computation/events >> >> On Sat, Feb 6, 2021 at 12:18 PM Robert Scholte wrote: >> >> > Most likely there has been an update at INFRA, which causes that commits >> > aren't picked up automatically. >> > Last scan details[1] >> > [Thu Feb 04 20:27:32 UTC 2021] Finished organization scan. Scan took 1 >> min >> > 31 sec >> > >> > Finished: SUCCESS >> > >> > Would be great if somebody could investigate this. >> > >> > thanks, >> > Robert >> > >> > [1] >> > >> https://builds.apache.org/job/Maven/job/maven-box/computation/consoleFull >> >> >> >> -- >> Arnaud Héritier >> Twitter/Skype : aheritier >> > > > -- > Arnaud Héritier > Twitter/Skype : aheritier > -- Arnaud Héritier Twitter/Skype : aheritier
Re: Apache Hosted Git Folder not scanned anymore
I had a look at it and I am not sure if the comment is recent or not The job wasn't disabled and the comment not visible without editing the job because the HTML was invalid For sure something is not right and it seems that the repo events are automatically triggering the builds (or add/remove branches) The latest commit I see in my emails is: [maven-jxr] 01/01: WIP misc changes In the next branch of maven-jxr https://gitbox.apache.org/repos/asf?p=maven-jxr.git;a=shortlog;h=refs/heads/next 37min ago And this branch was effectively not here : https://builds.apache.org/job/Maven/job/maven-box/job/maven-jxr/ The indexation was triggered manually by Sylvester earlier today https://builds.apache.org/job/Maven/job/maven-box/job/maven-jxr/indexing/console Started by user Sylwester Lachiewicz <https://builds.apache.org/user/slachiewicz> [Sat Feb 06 11:56:54 UTC 2021] Starting branch indexing... Listing remote references... Checking branches... Checking branch master ‘Jenkinsfile’ found Met criteria No changes detected: master (still at 6df9ba323e04ef7f7612a9ea1c9d64e3f8717cc0) Checking branch elharo-patch-2 ‘Jenkinsfile’ found Met criteria No changes detected: elharo-patch-2 (still at 87b2d6681022c5720d57c6803f4f708749cbf146) Checking branch JXR-154 ‘Jenkinsfile’ found Met criteria No changes detected: JXR-154 (still at 737fdbed58af9018ce2c096cea5aaf2d60dfe396) Checking branch JXR-145 ‘Jenkinsfile’ found Met criteria No changes detected: JXR-145 (still at 13fa0bf46a37e627a64eb1a1e6e9d3bca1f2793b) Processed 4 branches [Sat Feb 06 11:56:57 UTC 2021] Finished branch indexing. Indexing took 2.7 sec Finished: SUCCESS But for now we see no recent event: https://builds.apache.org/job/Maven/job/maven-box/job/maven-jxr/indexing/events I triggered the reindexation https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven-jxr/ 3 new branches added but for each of them we do 16 builds :-/ https://ci-builds.apache.org/blue/organizations/jenkins/Maven%2Fmaven-box%2Fmaven-jxr/detail/unused/1/pipeline I understand we want to validate with various versions of maven / OS / Java but on every branch it looks a lot (too much) On Sat, Feb 6, 2021 at 12:54 PM Robert Scholte wrote: > I see this line in the description: > in the queue, please fix this before re-enabling > > On 6-2-2021 12:38:21, Arnaud Héritier wrote: > I do not have enough privilege to do anything on this instance but the scan > is configured to be done every week even if nothing happens > Nothing happens means that we got no new event and effectively there is > nothing on this page after Feb 2nd which is suspicious : > https://builds.apache.org/job/Maven/job/maven-box/computation/events > > On Sat, Feb 6, 2021 at 12:18 PM Robert Scholte wrote: > > > Most likely there has been an update at INFRA, which causes that commits > > aren't picked up automatically. > > Last scan details[1] > > [Thu Feb 04 20:27:32 UTC 2021] Finished organization scan. Scan took 1 > min > > 31 sec > > > > Finished: SUCCESS > > > > Would be great if somebody could investigate this. > > > > thanks, > > Robert > > > > [1] > > > https://builds.apache.org/job/Maven/job/maven-box/computation/consoleFull > > > > -- > Arnaud Héritier > Twitter/Skype : aheritier > -- Arnaud Héritier Twitter/Skype : aheritier
Re: Apache Hosted Git Folder not scanned anymore
I do not have enough privilege to do anything on this instance but the scan is configured to be done every week even if nothing happens Nothing happens means that we got no new event and effectively there is nothing on this page after Feb 2nd which is suspicious : https://builds.apache.org/job/Maven/job/maven-box/computation/events On Sat, Feb 6, 2021 at 12:18 PM Robert Scholte wrote: > Most likely there has been an update at INFRA, which causes that commits > aren't picked up automatically. > Last scan details[1] > [Thu Feb 04 20:27:32 UTC 2021] Finished organization scan. Scan took 1 min > 31 sec > > Finished: SUCCESS > > Would be great if somebody could investigate this. > > thanks, > Robert > > [1] > https://builds.apache.org/job/Maven/job/maven-box/computation/consoleFull -- Arnaud Héritier Twitter/Skype : aheritier
Re: [RESULT][DISCUSS] Make Jira issues viewable.
It's not a blocker if it works without the filter parameter but the behavior is strange (I never saw this myself) On Fri, Sep 11, 2020 at 12:25 PM Robert Scholte wrote: > Clear, it is not an issue, just a matter of using the correct URL. > > Robert > > On 11-9-2020 11:18:45, Enrico Olivelli wrote: > I agree with Bindul > > I have never seen such blocks > > Enrico > > Il Ven 11 Set 2020, 10:38 Bindul Bhowmik ha > scritto: > > > Hi, > > > > If I may chime in, the Maven (and most Apache) JIRA issues don't > > require a login to view. I believe the issue is that Amelia added a > > filter to the URL pasted in the tweet, and the filter requires a > > login. > > So: https://issues.apache.org/jira/browse/MNG-6928 is viewable without > > a login https://issues.apache.org/jira/browse/MNG-6928?filter=-2 is > > not. > > > > Bindul > > > > On Fri, Sep 11, 2020 at 12:54 AM Maarten Mulders > > wrote: > > > > > > Agreed. If there's anything that is too deliberate to discuss in the > > > open, there's the mailing list, direct email or what not. > > > > > > Maarten > > > > > > On 11/09/2020 09:51, Robert Scholte wrote: > > > > Based on the > > https://twitter.com/ameliaeiras/status/1303815661307613184 and the > > responses of Marten Deinum I agree that it makes sense to make issues > > viewable for all. > > > > > > > > If there is no strong reason to keep it as it is, I'll ask our Jira > > administrator if our scheme can be updated. > > > > (looks like the Maven projects are missing an explicit Issue Security > > scheme) > > > > > > > > thanks, > > > > Robert > > > > > > > > > > - > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > -- Arnaud Héritier Twitter/Skype : aheritier
Re: Fwd: Maven builds out of control
No I agree, it's a long term solution and orthogonal on cleaning our branches/builds and limiting our usages If these are static agents the best we could do at the CI level is to restrict the usage of our builds to a limited number of agents https://docs.cloudbees.com/docs/cloudbees-ci/latest/traditional-secure-guide/folders-plus#_controlled_agents On Mon, Aug 17, 2020 at 10:55 AM Olivier Lamy wrote: > traditional slaves > I have a goal to help moving to kubernetes but this will not fix this > problem :) > > > On Mon, 17 Aug 2020 at 16:46, Arnaud Héritier wrote: > > > Thanks for the feedback Gavin, it makes a lot of sense to me. > > The new infrastructure is a traditional one (ie not hosted on > Kubernetes) ? > > > > On Mon, Aug 17, 2020 at 10:44 AM Gavin McDonald > > wrote: > > > > > Hi, > > > > > > On Mon, Aug 17, 2020 at 10:35 AM Olivier Lamy > wrote: > > > > > > > +infra > > > > > > > > On Mon, 17 Aug 2020 at 4:23 pm, Arnaud Héritier > > > > > wrote: > > > > > > > >> If we are consuming too much resources couldn't we have a dedicated > > > >> Jenkins > > > >> > > > >> controller and/or limit our agents capacities to be the one ones to > be > > > >> > > > >> impacted by these problems instead of all the users or this Jenkins > > > >> > > > >> controller ? > > > >> > > > >> Beam, Cassandra, CouchDB and few more have a dedicated controller : > > > >> > > > >> https://jenkins-ccos.apache.org/job/masters/ > > > >> > > > >> What are the rules to have a dedicated one ? > > > >> > > > > > > > All of those projects got their own master as they are contributing > their > > > own nodes and not using the ASF provided ones > > > > > > HTH > > > > > > > > > > > > > >> > > > >> > > > >> On Mon, Aug 17, 2020 at 10:02 AM Michael Osipov < > micha...@apache.org> > > > >> wrote: > > > >> > > > >> > > > >> > > > >> > Am 2020-08-17 um 09:55 schrieb Olivier Lamy: > > > >> > > > >> > > Furthermore, we need to clean up unused branches. > > > >> > > > >> > > What about removing branches older than 1yo? > > > >> > > > >> > > Then older than 6months? > > > >> > > > >> > > > > >> > > > >> > I consider branches which have been merged obsolete, but there is > no > > > >> > > > >> > hard rule that an unmerged branch is obsolete. It may prepresent > an > > > >> > > > >> > unfished state or something which was not agreed on. Dropping work > > > does > > > >> > > > >> > not feel right. It needs to be decided on a case-by-case approach. > > > >> > > > >> > I have done this recently for Wagon and Resolver. > > > >> > > > >> > > > > >> > > > >> > Michael > > > >> > > > >> > > > > >> > > > >> > > > - > > > >> > > > >> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > > >> > > > >> > For additional commands, e-mail: dev-h...@maven.apache.org > > > >> > > > >> > > > > >> > > > >> > > > > >> > > > >> > > > >> > > > >> -- > > > >> > > > >> Arnaud Héritier > > > >> > > > >> Twitter/Skype : aheritier > > > >> > > > >> -- > > > > Olivier Lamy > > > > http://twitter.com/olamy | http://linkedin.com/in/olamy > > > > > > > > > > > > > -- > > > > > > *Gavin McDonald* > > > Systems Administrator > > > ASF Infrastructure Team > > > > > > > > > -- > > Arnaud Héritier > > Twitter/Skype : aheritier > > > > > -- > Olivier Lamy > http://twitter.com/olamy | http://linkedin.com/in/olamy > -- Arnaud Héritier Twitter/Skype : aheritier
Re: Fwd: Maven builds out of control
Thanks for the feedback Gavin, it makes a lot of sense to me. The new infrastructure is a traditional one (ie not hosted on Kubernetes) ? On Mon, Aug 17, 2020 at 10:44 AM Gavin McDonald wrote: > Hi, > > On Mon, Aug 17, 2020 at 10:35 AM Olivier Lamy wrote: > > > +infra > > > > On Mon, 17 Aug 2020 at 4:23 pm, Arnaud Héritier > > wrote: > > > >> If we are consuming too much resources couldn't we have a dedicated > >> Jenkins > >> > >> controller and/or limit our agents capacities to be the one ones to be > >> > >> impacted by these problems instead of all the users or this Jenkins > >> > >> controller ? > >> > >> Beam, Cassandra, CouchDB and few more have a dedicated controller : > >> > >> https://jenkins-ccos.apache.org/job/masters/ > >> > >> What are the rules to have a dedicated one ? > >> > > > All of those projects got their own master as they are contributing their > own nodes and not using the ASF provided ones > > HTH > > > > > >> > >> > >> On Mon, Aug 17, 2020 at 10:02 AM Michael Osipov > >> wrote: > >> > >> > >> > >> > Am 2020-08-17 um 09:55 schrieb Olivier Lamy: > >> > >> > > Furthermore, we need to clean up unused branches. > >> > >> > > What about removing branches older than 1yo? > >> > >> > > Then older than 6months? > >> > >> > > >> > >> > I consider branches which have been merged obsolete, but there is no > >> > >> > hard rule that an unmerged branch is obsolete. It may prepresent an > >> > >> > unfished state or something which was not agreed on. Dropping work > does > >> > >> > not feel right. It needs to be decided on a case-by-case approach. > >> > >> > I have done this recently for Wagon and Resolver. > >> > >> > > >> > >> > Michael > >> > >> > > >> > >> > - > >> > >> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > >> > >> > For additional commands, e-mail: dev-h...@maven.apache.org > >> > >> > > >> > >> > > >> > >> > >> > >> -- > >> > >> Arnaud Héritier > >> > >> Twitter/Skype : aheritier > >> > >> -- > > Olivier Lamy > > http://twitter.com/olamy | http://linkedin.com/in/olamy > > > > > -- > > *Gavin McDonald* > Systems Administrator > ASF Infrastructure Team > -- Arnaud Héritier Twitter/Skype : aheritier
Re: Fwd: Maven builds out of control
If we are consuming too much resources couldn't we have a dedicated Jenkins controller and/or limit our agents capacities to be the one ones to be impacted by these problems instead of all the users or this Jenkins controller ? Beam, Cassandra, CouchDB and few more have a dedicated controller : https://jenkins-ccos.apache.org/job/masters/ What are the rules to have a dedicated one ? On Mon, Aug 17, 2020 at 10:02 AM Michael Osipov wrote: > Am 2020-08-17 um 09:55 schrieb Olivier Lamy: > > Furthermore, we need to clean up unused branches. > > What about removing branches older than 1yo? > > Then older than 6months? > > I consider branches which have been merged obsolete, but there is no > hard rule that an unmerged branch is obsolete. It may prepresent an > unfished state or something which was not agreed on. Dropping work does > not feel right. It needs to be decided on a case-by-case approach. > I have done this recently for Wagon and Resolver. > > Michael > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- Arnaud Héritier Twitter/Skype : aheritier
Re: Welcome the new Maven committers: Maarten Mulders en Martin Kanters
Welcome in the team! Le ven. 10 juil. 2020 à 21:13, Robert Scholte a écrit : > Hi, > > On behalf of the Apache Maven PMC I am pleased to announce that > Maarten Mulders en Martin Kanters has been voted in as new Apache Maven > committers > and they've both accepted this invitation. > > Welcome on board and have a lot of fun! > > Thanks, > Robert Scholte > -- - Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier
Re: [VOTE] Release Apache Maven EJB Plugin version 3.1.0
+1 Le ven. 12 juin 2020 à 08:10, Hervé BOUTEMY a écrit : > Le mercredi 10 juin 2020, 07:35:51 CEST Hervé BOUTEMY a écrit : > > I need more votes, please > ping? > > > > > Regards, > > > > Hervé > > > > Le dimanche 7 juin 2020, 18:26:43 CEST Hervé BOUTEMY a écrit : > > > Hi, > > > > > > We solved 7 issues: > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317421; > > > ve rsion=12343161=Text > > > > > > Staging repo: > > > https://repository.apache.org/content/repositories/maven-1588/ > > > > https://repository.apache.org/content/repositories/maven-1588/org/apache/m > > > av > > > > en/plugins/maven-ejb-plugin/3.1.0/maven-ejb-plugin-3.1.0-source-release.z > > > ip > > > > > > Source release checksum(s): > > > maven-ejb-plugin-3.1.0-source-release.zip.sha512 sha512: > > > > c6f2de1f10222e50ebf1c4991d91aa468749727d1214024caaef21e3ca4bf42523450ebaa3 > > > c > > > bfe40ec1e948b68c1a1ecea484bb2d5ce979a61cbbae64e074698 > > > > > > Staging site: > > > https://maven.apache.org/plugins-archives/maven-ejb-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 > > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- - Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier
Re: Twitter handles of committers
We can create a public list of developers with the project account. Le dim. 24 mai 2020 à 19:44, Maarten Mulders a écrit : > Great initiative! > > Deeplinking to the profile would be nice, too, I guess. > I would start with Twitter and GitHub. GitLab makes less sense to me, > AFAIK there are no mirrors of Maven hosted at GitLab? > > May I also suggest to do it the other way round: a Twitter list [1] of > people who are Maven committer? Or maybe it already exists? > > Maarten > > [1] https://help.twitter.com/en/using-twitter/twitter-lists > > On May 24, 2020 at 19:40, Robert Scholte wrote: > > > Sure we could do that too. > > Would be nice to improve the team pages for well known properties, but > > at the moment there's a vote on the maven-project-info-reports-plugin. > > Maybe an up-for-grabs to include with the next release. > > > > Robert > > On 24-5-2020 19:27:08, Andres Almiray wrote: > > Good idea Robert! > > May I suggest adding GitHub account as well? Not everyone follows > > Twitter > > or has an account (shocking, I know) but they may have a Github account > > or > > consider browsing through an author's profile. > > > > And why stop with Github? Let's add Gitlab. > > I guess, s long as there's no "explicit" or "stardard" social media | > > social coding column team members are free to choose which accounts > > they'd > > like to link, right? > > > > Cheers, > > Andres > > > > --- > > Java Champion; Groovy Enthusiast > > http://andresalmiray.com > > http://www.linkedin.com/in/aalmiray > > -- > > What goes up, must come down. Ask any system administrator. > > There are 10 types of people in the world: Those who understand binary, > > and > > those who don't. > > To understand recursion, we must first understand recursion. > > > > On Sun, May 24, 2020 at 7:18 PM Robert Scholte wrote: > > > >> I had a chat with Chandra (@CGuntur) regarding exposure of Maven > >> committers. > >> My experience is that most Maven users just use it, without knowing > >> the > >> people behind and (yes, people, not a company). Twitter has been a > >> good way > >> to share information regarding Maven. > >> To get more attention, I've added a twitter-property to my profile in > >> the > >> maven parent pom. > >> After triggering the website the team-list[1] has been expanded with a > >> properties-column. > >> Not the nicest look and feel, but having my twitter handle here is > >> more > >> important to me. > >> > >> I could add all known twitter handles, but I leave it up to every > >> committer to add this property as well. > >> Simply update your profile in the maven-parent if you want. > >> > >> thanks, > >> Robert > >> > >> [1] https://maven.apache.org/team.html > >> > >> [2] https://github.com/apache/maven-parent/blob/master/pom.xml > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- - Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier
Re: second apache-maven-wrapper
ok no worries, it was a nice to have if it wasn't yet on master. On Sat, May 23, 2020 at 1:04 PM Karl Heinz Marbaise wrote: > > HI, > > On 23.05.20 12:51, Arnaud Héritier wrote: > > LGTM > > Rebasing the code could be great if not too difficult > > Unfortunately the code is already on master with all commits > > Kind regards > Karl Heinz Marbaise > > > > > On Sat, May 23, 2020 at 12:32 PM Enrico Olivelli > > wrote: > > > >> Approved on github > >> > >> +1 > >> I have run thru the diff. > >> It looks very well > >> > >> Longing for testing it on a real project > >> > >> The fact that you won't have to commit mave wrapper jar to local > sources is > >> great > >> > >> > >> Enrico > >> > >> Il Ven 22 Mag 2020, 22:56 Manfred Moser ha > >> scritto: > >> > >>> Awesome! +1 > >>> > >>> Robert Scholte wrote on 2020-05-22 13:36 (GMT -07:00): > >>> > >>>> I've reached the point where apache-maven-wrapper is ready to be > merged > >>> into > >>>> master. > >>>> The code contains all original commits and a few from me to get them > >>> step by > >>>> step into core. > >>>> > >>>> Related tickets: > >>>> https://issues.apache.org/jira/browse/MNG-5937 > >>>> > >>>> https://issues.apache.org/jira/browse/MNG-6914 > >>>> > >>>> > >>>> https://github.com/apache/maven/pull/349 > >>>> > >>>> https://github.com/apache/maven-integration-testing/pull/62 > >>>> > >>>> > >>>> thanks, > >>>> Robert > -- - Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier
Re: [VOTE] Release Maven Wagon version 3.4.1
LGTM +1 I did only a code review using https://github.com/apache/maven-wagon/compare/wagon-3.4.0...wagon-3.4.1 On Fri, May 22, 2020 at 9:45 PM Michael Osipov wrote: > Hi, > > We solved 6 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318122=12348210 > > There are still a couple of issues left in JIRA: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20WAGON%20AND%20resolution%20%3D%20Unresolved > > Staging repo: > https://repository.apache.org/content/repositories/maven-1576/ > > https://repository.apache.org/content/repositories/maven-1576/org/apache/maven/wagon/wagon/3.4.1/wagon-3.4.1-source-release.zip > > Source release checksum(s): > wagon-3.4.1-source-release.zip > sha512: > > 342d3ad88ba3535a0b6cafcfebd3f5b2e0fc6ac4022bebcea78a60703b0c611232e765ea87fb98ada0dc5daf1a9002e9bf7959571eebc4c974efda042246999c > > Staging site: > https://maven.apache.org/wagon-archives/wagon-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 > > -- - Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier
Re: second apache-maven-wrapper
LGTM Rebasing the code could be great if not too difficult On Sat, May 23, 2020 at 12:32 PM Enrico Olivelli wrote: > Approved on github > > +1 > I have run thru the diff. > It looks very well > > Longing for testing it on a real project > > The fact that you won't have to commit mave wrapper jar to local sources is > great > > > Enrico > > Il Ven 22 Mag 2020, 22:56 Manfred Moser ha > scritto: > > > Awesome! +1 > > > > Robert Scholte wrote on 2020-05-22 13:36 (GMT -07:00): > > > > > I've reached the point where apache-maven-wrapper is ready to be merged > > into > > > master. > > > The code contains all original commits and a few from me to get them > > step by > > > step into core. > > > > > > Related tickets: > > > https://issues.apache.org/jira/browse/MNG-5937 > > > > > > https://issues.apache.org/jira/browse/MNG-6914 > > > > > > > > > https://github.com/apache/maven/pull/349 > > > > > > https://github.com/apache/maven-integration-testing/pull/62 > > > > > > > > > thanks, > > > Robert > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > -- - Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier
Re: next level of compatibility (was Re: [maven-site] branch master updated: few precisions)
+1 On Sat, May 23, 2020 at 11:13 AM Enrico Olivelli wrote: > +1 > > Enrico > > Il Sab 23 Mag 2020, 09:40 Sylwester Lachiewicz ha > scritto: > > > +1 > > > > sob., 23 maj 2020, 09:22 użytkownik Hervé BOUTEMY > > > napisał: > > > > > Le vendredi 22 mai 2020, 02:13:16 CEST Olivier Lamy a écrit : > > > > > + * discussions on Maven > 3.0.x (3.1 or 3.2 or 3.3? details still > > > TDB) + > > > > > Java 8 prerequisites > > > > > > > > Don't be shy Hervé we can definitely says >= 3.3.9 (at least you will > > not > > > > hear any objections from me :) ) > > > > > > looking at our history https://maven.apache.org/docs/history.html, > there > > > is 1 > > > year between 3.1.max and 3.2.max then 1 year to 3.3.max: not so much > > > and AFAIK, many people went from 3.0 to 3.3+ > > > > > > looks a good idea to me: +1 > > > > > > any objection? > > > > > > Regards, > > > > > > Hervé > > > > > > > > > > > > - > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > > > > > -- - Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier
Re: [VOTE] Release Apache Maven Release Plugin version 3.0.0-M2
While I confirm MRELEASE-1038 fixed it seems that there is another problem related to it : https://issues.apache.org/jira/browse/MRELEASE-1042 For now -1 On Tue, Apr 7, 2020 at 8:48 PM Robert Scholte wrote: > Hi, > > We solved 8 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824=12348049=Text > > There are still a couple of issues left in JIRA: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317824%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC > > Staging repo: > https://repository.apache.org/content/repositories/maven-1560/ > > https://repository.apache.org/content/repositories/maven-1560/org/apache/maven/release/maven-release/3.0.0-M2/maven-release-3.0.0-M2-source-release.zip > > Source release checksum(s): > > maven-release-3.0.0-M2-source-release.zip sha512: > 7b10e9f809abcd0b24b54fed243e2a6bb45a577d2b45c9fadf800f99a5e7632999efbffb507b704cdcf382f693a30de473846c5673c335c34ddcb9e8e711ae5c > > Staging site: > https://maven.apache.org/maven-release-archives/maven-release-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 > -- - Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier
Re: [VOTE] Release Apache Maven Parent POMs version 34
+1 On Thu, Jan 30, 2020 at 8:49 AM Enrico Olivelli wrote: > +1 (non binding) > > Interesting https://issues.apache.org/jira/browse/MPOM-223 Introduce > parent > for extensions ! > > Enrico > > Il giorno gio 30 gen 2020 alle ore 08:20 Karl Heinz Marbaise < > khmarba...@gmx.de> ha scritto: > > > Hi, > > +1 from me. > > > > Kind regards > > Karl Heinz Marbaise > > On 26.01.20 10:16, Hervé BOUTEMY wrote: > > > Hi, > > > > > > We solved 9 issues: > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250=12344077=Text > > > > > > Changes since the last release: > > > > > > https://github.com/apache/maven-parent/compare/maven-parent-33...maven-parent-34#diff > > > > > > There are still a couple of issues left in JIRA: > > > > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MPOM%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC > > > > > > Staging repo: > > > https://repository.apache.org/content/repositories/maven-1548/ > > > > > > https://repository.apache.org/content/repositories/maven-1548/org/apache/maven/maven-parent/34/maven-parent-34-source-release.zip > > > > > > Source release checksum(s): > > > maven-parent-34-source-release.zip sha512: > > > caf523e3def4d414985b3f96ec6939a43a96d977510001e08f23aa3b44dd182b92ec7557204de649e63d6a5bc926042f62fde83406cd428ca710d62af7151b7a > > > > > > Staging site: > > > https://maven.apache.org/pom-archives/maven-LATEST/ > > > > > > Guide to testing staged releases: > > > > https://maven.apache.org/guides/development/guide-testing-releases.html > > > > > > Vote open for at least 72 hours. > > > > > > [ ] +1 > > > [ ] +0 > > > [ ] -1 > > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > -- - Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier
Re: [VOTE] Release Apache Maven PMD Plugin version 3.13.0
+1 On Sat, Feb 1, 2020 at 1:08 AM wrote: > +1 > > Regards, > > Hervé > > - Mail original - > De: "Karl Heinz Marbaise" > À: "Maven Developers List" , "Andreas Dangel" < > adan...@apache.org> > Envoyé: Lundi 27 Janvier 2020 10:49:32 > Objet: Re: [VOTE] Release Apache Maven PMD Plugin version 3.13.0 > > Hi, > > +1 from me. > > Kind regards > Karl Heinz Marbaise > On 25.01.20 12:04, Andreas Dangel wrote: > > Hi, > > > > We solved 12 issues: > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12345409=Text=12317621 > > > > There are still a couple of issues left in JIRA: > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MPMD%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC > > > > Staging repo: > > https://repository.apache.org/content/repositories/maven-1547/ > > > https://repository.apache.org/content/repositories/maven-1547/org/apache/maven/plugins/maven-pmd-plugin/3.13.0/maven-pmd-plugin-3.13.0-source-release.zip > > > > Source release checksum(s): > > maven-pmd-plugin-3.13.0-source-release.zip sha512: > > > 9b5238f49f5189a720d0f6b294bc2be715eddae51c84f3d498f091694cd98047eb548b09d705ac4823f2a8bd4716d6e48b77a650f35f15008ad12f2e8604 > > > > Staging site: > > https://maven.apache.org/plugins-archives/maven-pmd-plugin-LATEST/ > > > > Guide to testing staged releases: > > https://maven.apache.org/guides/development/guide-testing-releases.html > > > > Vote open for at least 72 hours. > > > > [ ] +1 > > [ ] +0 > > [ ] -1 > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- - Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier
Re: [VOTE] Release Apache Maven Checkstyle Plugin version 3.1.1
+1 On Tue, Feb 11, 2020 at 10:12 PM Romain Manni-Bucau wrote: > +1 (non binding) > > Le mar. 11 févr. 2020 à 20:04, Stephane Nicoll > a écrit : > > > +1 (non-binding anymore). > > > > Cheers, > > S. > > > > On Tue, Feb 11, 2020 at 1:47 PM Enrico Olivelli > > wrote: > > > > > Thank you Hervé > > > > > > I need two more binding +1 please > > > > > > Enrico > > > > > > Il Sab 8 Feb 2020, 21:43 Hervé BOUTEMY ha > > scritto: > > > > > > > +1 > > > > > > > > I was able to rebuild (with JDK 8) .jar, -sources.jar and > > > > -source-release.zip > > > > archives from source-release archive, deleting first DEPENDENCIES, > > > LICENSE > > > > and > > > > NOTICE > > > > > > > > Regards, > > > > > > > > Hervé > > > > > > > > Le samedi 8 février 2020, 10:11:29 CET Enrico Olivelli a écrit : > > > > > Hi, > > > > > > > > > > We solved 7 issues: > > > > > > > > > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317223 > > > > > rsion=12345558 > > > > > > > > > > In particular this release allows users to upgrade to latest and > > > > > greatest checkstyle version 8.29. > > > > > > > > > > There are still a couple of issues left in JIRA: > > > > > > > > > > > > > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MCHECKSTYLE%20AND > > > > > > > > > > > > > > > %20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC%2C%20updated > > > > > %20DESC > > > > > > > > > > Staging repo: > > > > > https://repository.apache.org/content/repositories/maven-1549/ > > > > > > > > > > > > > > > https://repository.apache.org/content/repositories/maven-1549/org/apache/mav > > > > > > > > > > > > > > > en/plugins/maven-checkstyle-plugin/3.1.1/maven-checkstyle-plugin-3.1.1-sourc > > > > > e-release.zip > > > > > > > > > > Source release checksum(s): > > > > > maven-checkstyle-plugin-3.1.1-source-release.zip sha512: > > > > > > > > > > > > > > > 753015ff86d22d840ffbcab81b8d5170e6db7a9dc21963686faa2a54d3232964dace2f7316ff > > > > > 84a27e06700cf32a57088d9bee5d51463d0f0b5c01e7f87a1268 > > > > > > > > > > Staging site: > > > > > > > > > > > > > > > https://maven.apache.org/plugins-archives/maven-checkstyle-plugin-LATEST/ > > > > > > > > > > Guide to testing staged releases: > > > > > > > > > https://maven.apache.org/guides/development/guide-testing-releases.html > > > > > > > > > > Vote open for at least 72 hours. > > > > > > > > > > [ ] +1 > > > > > [ ] +0 > > > > > [ ] -1 > > > > > > > > > > Enrico Olivelli > > > > > > > > > > > - > > > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > > > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > > > > > > > > > > > > > > > > > > > > - > > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > > > > > > > > > > -- - Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier
Re: [VOTE] Release Apache Maven Shade Plugin version 3.2.2
+1 On Wed, Feb 12, 2020 at 8:01 AM Olivier Lamy wrote: > +1 > > On Sun, 9 Feb 2020 at 19:25, Hervé BOUTEMY wrote: > > > Hi, > > > > We solved 28 issues: > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317921=1230=Text > > > > Staging repo: > > https://repository.apache.org/content/repositories/maven-1550/ > > > > > https://repository.apache.org/content/repositories/maven-1550/org/apache/maven/plugins/maven-shade-plugin/3.2.2/maven-shade-plugin-3.2.2-source-release.zip > > > > Source release checksum(s): > > maven-shade-plugin-3.2.2-source-release.zip sha512: > > > c9ecdf2003c5c983005e62ad4f0bcae408c25583496d32fc7c7912ba34060048f541cea135c3d308146f39c0cb17795124cf9e1d50f42373c9456f47d2d61830 > > > > Staging site: > > https://maven.apache.org/plugins-archives/maven-shade-plugin-LATEST/ > > > > Guide to testing staged releases: > > https://maven.apache.org/guides/development/guide-testing-releases.html > > > > Vote open for at least 72 hours. > > > > [ ] +1 > > [ ] +0 > > [ ] -1 > > > > > > > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > > -- > Olivier Lamy > http://twitter.com/olamy | http://linkedin.com/in/olamy > -- - Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier
