Re: [VOTE] Release Apache Maven parent 40

2023-06-12 Thread Guillaume Nodet 
+1

Le lun. 12 juin 2023 à 20:07, Slawomir Jaranowski 
a écrit :

> Hi,
>
> For testing you need ASF parent 30 from the staging repository.
>
> We solved 15 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250=12352681
>
> Commits:
>
> https://github.com/apache/maven-parent/compare/maven-parent-39...maven-parent-40
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1956/
>
> https://repository.apache.org/content/repositories/maven-1956/org/apache/maven/maven-parent/40/maven-parent-40-source-release.zip
>
> Source release checksum(s):
> maven-parent-40-source-release.zip - SHA-512 :
>
> 8014f1b5b15b6e60d7d17077a3c853c40eff54385ab658ea102398129ad96fb1fc329c8b0130f52d7d05aff7a258e7d5cce0e02c9dfae40ed9427a8cb3ea7da1
>
> Staging site:
> https://maven.apache.org/pom-archives/maven-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for at least 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> --
> Sławomir Jaranowski
>


-- 

Guillaume Nodet

Re: [VOTE] Release Apache Maven parent 40

2023-06-12 Thread Jeremy Landis 
While it's setup to override it, I'd tend to agree on plexus 4.  It's a little 
aggressive and I've already experienced issues with 4.0.  I forget where but 
rolled back with assumption that's really for maven 4.

Sent from my Verizon, Samsung Galaxy smartphone
Get Outlook for Android

From: Elliotte Rusty Harold 
Sent: Monday, June 12, 2023 9:11:37 PM
To: Maven Developers List 
Subject: Re: [VOTE] Release Apache Maven parent 40

-1

https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fmaven-parent%2Fpull%2F123%2Ffiles=05%7C01%7C%7C0f7f40175e0b4265dad808db6bab5072%7C84df9e7fe9f640afb435%7C1%7C0%7C638222155762377214%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=uvgI%2FEE404giyBynD%2Bu0TGkvc5jTnVniaKK8P3boKx4%3D=0
 seems likely to
break projects that update to parent pom 40 without adding an extra
dependency on plexus-xml 4.0.0, and this breakage might be several
levels deep in the dependency tree so there's no guarantee it will be
caught in the project that pulls it in.

On Mon, Jun 12, 2023 at 6:08 PM Slawomir Jaranowski
 wrote:
>
> Hi,
>
> For testing you need ASF parent 30 from the staging repository.
>
> We solved 15 issues:
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fsecure%2FReleaseNote.jspa%3FprojectId%3D12311250%26version%3D12352681=05%7C01%7C%7C0f7f40175e0b4265dad808db6bab5072%7C84df9e7fe9f640afb435%7C1%7C0%7C638222155762377214%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=QDJFrVgzRRUQcJIOy%2B6VHIWjqVMB80zsbPxQJDgg6p4%3D=0
>
> Commits:
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fmaven-parent%2Fcompare%2Fmaven-parent-39...maven-parent-40=05%7C01%7C%7C0f7f40175e0b4265dad808db6bab5072%7C84df9e7fe9f640afb435%7C1%7C0%7C638222155762377214%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=0b2dJrEOlZvlcJz%2BTXecuKgD%2BdttBDQAXTEc7dYmsnI%3D=0
>
> Staging repo:
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fmaven-1956%2F=05%7C01%7C%7C0f7f40175e0b4265dad808db6bab5072%7C84df9e7fe9f640afb435%7C1%7C0%7C638222155762377214%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=4BYro3Ytz5Tc5cbzGGy36xImJR7Y2xPVHH6OCHrJM0E%3D=0
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fmaven-1956%2Forg%2Fapache%2Fmaven%2Fmaven-parent%2F40%2Fmaven-parent-40-source-release.zip=05%7C01%7C%7C0f7f40175e0b4265dad808db6bab5072%7C84df9e7fe9f640afb435%7C1%7C0%7C638222155762377214%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=UgyeTTPs7ZuYUNbqjBJPVaI61D%2BI02cSe9MEc7EYhZw%3D=0
>
> Source release checksum(s):
> maven-parent-40-source-release.zip - SHA-512 :
> 8014f1b5b15b6e60d7d17077a3c853c40eff54385ab658ea102398129ad96fb1fc329c8b0130f52d7d05aff7a258e7d5cce0e02c9dfae40ed9427a8cb3ea7da1
>
> Staging site:
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmaven.apache.org%2Fpom-archives%2Fmaven-LATEST%2F=05%7C01%7C%7C0f7f40175e0b4265dad808db6bab5072%7C84df9e7fe9f640afb435%7C1%7C0%7C638222155762377214%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=rxg8UHiXhLbAZzfwPLBabq7ylL2AJcRramZ57Wl5EV4%3D=0
>
> Guide to testing staged releases:
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmaven.apache.org%2Fguides%2Fdevelopment%2Fguide-testing-releases.html=05%7C01%7C%7C0f7f40175e0b4265dad808db6bab5072%7C84df9e7fe9f640afb435%7C1%7C0%7C638222155762377214%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=FIJBVyAzMoR8UdslU6Jla%2FSVEpqf8pe0gF6sr6jTqVk%3D=0
>
> Vote open for at least 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> --
> Sławomir Jaranowski



--
Elliotte Rusty Harold
elh...@ibiblio.org

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Release Apache Maven parent 40

2023-06-12 Thread Guillaume Nodet 
Note that those classes classes in plexus-xml are always exported by the
maven-core classloader at runtime [1], so this could have an effect on unit
tests, but it should not have much at runtime (at least for plugins or
components used by plugins).

Fwiw, all the code I've migrated to those new plexus usually break very
fast when they need xml.  So I don't think that's a big problem.  Also, I
think the parent is for maven consumption, so we can pay attention to that
when we upgrade. Anyway, if you have a better idea, we could improve
obviously.

[1]
https://github.com/apache/maven/blob/f0cc176b338822ff95b7a9046d6483bb1afb950b/maven-core/src/main/resources/META-INF/maven/extension.xml#L86-L90

Le mar. 13 juin 2023 à 03:12, Elliotte Rusty Harold  a
écrit :

> -1
>
> https://github.com/apache/maven-parent/pull/123/files seems likely to
> break projects that update to parent pom 40 without adding an extra
> dependency on plexus-xml 4.0.0, and this breakage might be several
> levels deep in the dependency tree so there's no guarantee it will be
> caught in the project that pulls it in.
>
> On Mon, Jun 12, 2023 at 6:08 PM Slawomir Jaranowski
>  wrote:
> >
> > Hi,
> >
> > For testing you need ASF parent 30 from the staging repository.
> >
> > We solved 15 issues:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250=12352681
> >
> > Commits:
> >
> https://github.com/apache/maven-parent/compare/maven-parent-39...maven-parent-40
> >
> > Staging repo:
> > https://repository.apache.org/content/repositories/maven-1956/
> >
> https://repository.apache.org/content/repositories/maven-1956/org/apache/maven/maven-parent/40/maven-parent-40-source-release.zip
> >
> > Source release checksum(s):
> > maven-parent-40-source-release.zip - SHA-512 :
> >
> 8014f1b5b15b6e60d7d17077a3c853c40eff54385ab658ea102398129ad96fb1fc329c8b0130f52d7d05aff7a258e7d5cce0e02c9dfae40ed9427a8cb3ea7da1
> >
> > Staging site:
> > https://maven.apache.org/pom-archives/maven-LATEST/
> >
> > Guide to testing staged releases:
> > https://maven.apache.org/guides/development/guide-testing-releases.html
> >
> > Vote open for at least 72 hours.
> >
> > [ ] +1
> > [ ] +0
> > [ ] -1
> >
> > --
> > Sławomir Jaranowski
>
>
>
> --
> Elliotte Rusty Harold
> elh...@ibiblio.org
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

-- 

Guillaume Nodet

Re: [VOTE] Release Apache Maven parent 40

2023-06-12 Thread Elliotte Rusty Harold 
-1

https://github.com/apache/maven-parent/pull/123/files seems likely to
break projects that update to parent pom 40 without adding an extra
dependency on plexus-xml 4.0.0, and this breakage might be several
levels deep in the dependency tree so there's no guarantee it will be
caught in the project that pulls it in.

On Mon, Jun 12, 2023 at 6:08 PM Slawomir Jaranowski
 wrote:
>
> Hi,
>
> For testing you need ASF parent 30 from the staging repository.
>
> We solved 15 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250=12352681
>
> Commits:
> https://github.com/apache/maven-parent/compare/maven-parent-39...maven-parent-40
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1956/
> https://repository.apache.org/content/repositories/maven-1956/org/apache/maven/maven-parent/40/maven-parent-40-source-release.zip
>
> Source release checksum(s):
> maven-parent-40-source-release.zip - SHA-512 :
> 8014f1b5b15b6e60d7d17077a3c853c40eff54385ab658ea102398129ad96fb1fc329c8b0130f52d7d05aff7a258e7d5cce0e02c9dfae40ed9427a8cb3ea7da1
>
> Staging site:
> https://maven.apache.org/pom-archives/maven-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for at least 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> --
> Sławomir Jaranowski



-- 
Elliotte Rusty Harold
elh...@ibiblio.org

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Release Apache Maven parent 40

2023-06-12 Thread Sylwester Lachiewicz 
+1

pon., 12 cze 2023, 20:07 użytkownik Slawomir Jaranowski <
s.jaranow...@gmail.com> napisał:

> Hi,
>
> For testing you need ASF parent 30 from the staging repository.
>
> We solved 15 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250=12352681
>
> Commits:
>
> https://github.com/apache/maven-parent/compare/maven-parent-39...maven-parent-40
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1956/
>
> https://repository.apache.org/content/repositories/maven-1956/org/apache/maven/maven-parent/40/maven-parent-40-source-release.zip
>
> Source release checksum(s):
> maven-parent-40-source-release.zip - SHA-512 :
>
> 8014f1b5b15b6e60d7d17077a3c853c40eff54385ab658ea102398129ad96fb1fc329c8b0130f52d7d05aff7a258e7d5cce0e02c9dfae40ed9427a8cb3ea7da1
>
> Staging site:
> https://maven.apache.org/pom-archives/maven-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for at least 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> --
> Sławomir Jaranowski
>

Re: [VOTE] Release Apache Maven parent 40

2023-06-12 Thread Tamás Cservenák 
+1

On Mon, Jun 12, 2023 at 8:07 PM Slawomir Jaranowski 
wrote:

> Hi,
>
> For testing you need ASF parent 30 from the staging repository.
>
> We solved 15 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250=12352681
>
> Commits:
>
> https://github.com/apache/maven-parent/compare/maven-parent-39...maven-parent-40
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1956/
>
> https://repository.apache.org/content/repositories/maven-1956/org/apache/maven/maven-parent/40/maven-parent-40-source-release.zip
>
> Source release checksum(s):
> maven-parent-40-source-release.zip - SHA-512 :
>
> 8014f1b5b15b6e60d7d17077a3c853c40eff54385ab658ea102398129ad96fb1fc329c8b0130f52d7d05aff7a258e7d5cce0e02c9dfae40ed9427a8cb3ea7da1
>
> Staging site:
> https://maven.apache.org/pom-archives/maven-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for at least 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> --
> Sławomir Jaranowski
>

[VOTE] Release Apache Maven parent 40

2023-06-12 Thread Slawomir Jaranowski 
Hi,

For testing you need ASF parent 30 from the staging repository.

We solved 15 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250=12352681

Commits:
https://github.com/apache/maven-parent/compare/maven-parent-39...maven-parent-40

Staging repo:
https://repository.apache.org/content/repositories/maven-1956/
https://repository.apache.org/content/repositories/maven-1956/org/apache/maven/maven-parent/40/maven-parent-40-source-release.zip

Source release checksum(s):
maven-parent-40-source-release.zip - SHA-512 :
8014f1b5b15b6e60d7d17077a3c853c40eff54385ab658ea102398129ad96fb1fc329c8b0130f52d7d05aff7a258e7d5cce0e02c9dfae40ed9427a8cb3ea7da1

Staging site:
https://maven.apache.org/pom-archives/maven-LATEST/

Guide to testing staged releases:
https://maven.apache.org/guides/development/guide-testing-releases.html

Vote open for at least 72 hours.

[ ] +1
[ ] +0
[ ] -1

-- 
Sławomir Jaranowski

Re: [VOTE] Release Apache ASF parent 30

2023-06-12 Thread Slawomir Jaranowski 
pon., 12 cze 2023 o 17:06 Guillaume Nodet  napisał(a):

> Thx !
> Quick question, you haven't released maven-parent 40 at the same time, do
> you plan to release it soon, after this release is closed, and not planning
> yet ?
>

I have a plan to release Maven parent 40 today.


> Guillaume
>
> Le dim. 11 juin 2023 à 19:02, Slawomir Jaranowski 
> a écrit :
>
>> Hi,
>>
>> We solved 25 issues:
>>
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250=12352680
>>
>> Commits:
>>
>> https://github.com/apache/maven-apache-parent/compare/apache-29...apache-30
>>
>> Staging repo:
>> https://repository.apache.org/content/repositories/orgapacheapache-1035/
>>
>> https://repository.apache.org/content/repositories/orgapacheapache-1035/org/apache/apache/30/apache-30-source-release.zip
>>
>> Source release checksum(s):
>> apache-30-source-release.zip - SHA-512 :
>>
>> 3c2557de0d8b1a1bfb36d67e7e17cdf338f9812ccb9fd030eedb3ff4693fbac38980bfe022dc033fe454b28f2e49ddedb768c52a62c83b82e1ad0041b5ff9ac7
>>
>> Staging site:
>> https://maven.apache.org/pom-archives/asf-LATEST/
>>
>> Guide to testing staged releases:
>> https://maven.apache.org/guides/development/guide-testing-releases.html
>>
>> Vote open for at least 72 hours.
>>
>> [ ] +1
>> [ ] +0
>> [ ] -1
>>
>> --
>> Sławomir Jaranowski
>>
>
>
> --
> 
> Guillaume Nodet
>
>

-- 
Sławomir Jaranowski

Re: [VOTE] Release Apache ASF parent 30

2023-06-12 Thread Guillaume Nodet 
Thx !
Quick question, you haven't released maven-parent 40 at the same time, do
you plan to release it soon, after this release is closed, and not planning
yet ?

Guillaume

Le dim. 11 juin 2023 à 19:02, Slawomir Jaranowski 
a écrit :

> Hi,
>
> We solved 25 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250=12352680
>
> Commits:
> https://github.com/apache/maven-apache-parent/compare/apache-29...apache-30
>
> Staging repo:
> https://repository.apache.org/content/repositories/orgapacheapache-1035/
>
> https://repository.apache.org/content/repositories/orgapacheapache-1035/org/apache/apache/30/apache-30-source-release.zip
>
> Source release checksum(s):
> apache-30-source-release.zip - SHA-512 :
>
> 3c2557de0d8b1a1bfb36d67e7e17cdf338f9812ccb9fd030eedb3ff4693fbac38980bfe022dc033fe454b28f2e49ddedb768c52a62c83b82e1ad0041b5ff9ac7
>
> Staging site:
> https://maven.apache.org/pom-archives/asf-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for at least 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> --
> Sławomir Jaranowski
>


-- 

Guillaume Nodet

Re: [VOTE] Release Maven WAR Plugin version 3.4.0

2023-06-12 Thread Romain Manni-Bucau 
+1

Romain Manni-Bucau
@rmannibucau  |  Blog
 | Old Blog
 | Github  |
LinkedIn  | Book



Le lun. 12 juin 2023 à 10:08, Guillaume Nodet  a écrit :

> +1
>
> Le dim. 11 juin 2023 à 22:15, Michael Osipov  a
> écrit :
>
> > Hi,
> >
> > we solved 17 issues:
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318121=12350597
> >
> > There are still a couple of issues left in JIRA:
> > https://issues.apache.org/jira/projects/MWAR/issues
> >
> > Staging repo:
> > https://repository.apache.org/content/repositories/maven-1955/
> >
> >
> https://repository.apache.org/content/repositories/maven-1955/org/apache/maven/plugins/maven-war-plugin/3.4.0/maven-war-plugin-3.4.0-source-release.zip
> >
> > Source release checksum(s):
> > maven-war-plugin-3.4.0-source-release.zip
> > sha512:
> >
> >
> ef7b2621697024570522a778318106f1e5ca18bf6944cb9e43e693e8c37312af272036f517d03b3555622f9bad695217ececa078affda6442d76063b5153f998
> >
> > 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 72 hours.
> >
> > [ ] +1
> > [ ] +0
> > [ ] -1
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
> >
>
> --
> 
> Guillaume Nodet
>

Re: [VOTE] Release Maven Invoker Plugin version 3.6.0

2023-06-12 Thread Tamás Cservenák 
+1

On Sun, Jun 11, 2023 at 7:34 PM Michael Osipov  wrote:

> Hi,
>
> we solved 8 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317525=12353076
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MINVOKER%20AND%20resolution%20%3D%20Unresolved
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1954/
>
> https://repository.apache.org/content/repositories/maven-1954/org/apache/maven/plugins/maven-invoker-plugin/3.6.0/maven-invoker-plugin-3.6.0-source-release.zip
>
> Source release checksum(s):
> maven-invoker-plugin-3.6.0-source-release.zip
> sha512:
>
> ed73a73536577de505c2c09b09ad644dcd4e1b957c785dc48d3481c67ba5f598ba5095d125d3d54414fde02226fb638536e1bcdc7618b23515d224184af3fdf2
>
> Staging site:
> https://maven.apache.org/plugins-archives/maven-invoker-plugin-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: [VOTE] Release Maven WAR Plugin version 3.4.0

2023-06-12 Thread Guillaume Nodet 
+1

Le dim. 11 juin 2023 à 22:15, Michael Osipov  a écrit :

> Hi,
>
> we solved 17 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318121=12350597
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/projects/MWAR/issues
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1955/
>
> https://repository.apache.org/content/repositories/maven-1955/org/apache/maven/plugins/maven-war-plugin/3.4.0/maven-war-plugin-3.4.0-source-release.zip
>
> Source release checksum(s):
> maven-war-plugin-3.4.0-source-release.zip
> sha512:
>
> ef7b2621697024570522a778318106f1e5ca18bf6944cb9e43e693e8c37312af272036f517d03b3555622f9bad695217ececa078affda6442d76063b5153f998
>
> 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 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

-- 

Guillaume Nodet

Re: [VOTE] Release Maven Invoker Plugin version 3.6.0

2023-06-12 Thread Guillaume Nodet 
+1

Le dim. 11 juin 2023 à 19:35, Michael Osipov  a écrit :

> Hi,
>
> we solved 8 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317525=12353076
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MINVOKER%20AND%20resolution%20%3D%20Unresolved
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1954/
>
> https://repository.apache.org/content/repositories/maven-1954/org/apache/maven/plugins/maven-invoker-plugin/3.6.0/maven-invoker-plugin-3.6.0-source-release.zip
>
> Source release checksum(s):
> maven-invoker-plugin-3.6.0-source-release.zip
> sha512:
>
> ed73a73536577de505c2c09b09ad644dcd4e1b957c785dc48d3481c67ba5f598ba5095d125d3d54414fde02226fb638536e1bcdc7618b23515d224184af3fdf2
>
> Staging site:
> https://maven.apache.org/plugins-archives/maven-invoker-plugin-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

-- 

Guillaume Nodet

Re: [VOTE] Release Maven Invoker Plugin version 3.6.0

2023-06-12 Thread Sylwester Lachiewicz 
+1

pon., 12 cze 2023, 09:21 użytkownik Slawomir Jaranowski <
s.jaranow...@gmail.com> napisał:

> +1
>
> niedz., 11 cze 2023 o 19:34 Michael Osipov 
> napisał(a):
>
> > Hi,
> >
> > we solved 8 issues:
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317525=12353076
> >
> > There are still a couple of issues left in JIRA:
> >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MINVOKER%20AND%20resolution%20%3D%20Unresolved
> >
> > Staging repo:
> > https://repository.apache.org/content/repositories/maven-1954/
> >
> >
> https://repository.apache.org/content/repositories/maven-1954/org/apache/maven/plugins/maven-invoker-plugin/3.6.0/maven-invoker-plugin-3.6.0-source-release.zip
> >
> > Source release checksum(s):
> > maven-invoker-plugin-3.6.0-source-release.zip
> > sha512:
> >
> >
> ed73a73536577de505c2c09b09ad644dcd4e1b957c785dc48d3481c67ba5f598ba5095d125d3d54414fde02226fb638536e1bcdc7618b23515d224184af3fdf2
> >
> > Staging site:
> > https://maven.apache.org/plugins-archives/maven-invoker-plugin-LATEST/
> >
> > Guide to testing staged releases:
> > https://maven.apache.org/guides/development/guide-testing-releases.html
> >
> > Vote open for 72 hours.
> >
> > [ ] +1
> > [ ] +0
> > [ ] -1
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
> >
>
> --
> Sławomir Jaranowski
>

Re: [VOTE] Release Maven WAR Plugin version 3.4.0

2023-06-12 Thread Slawomir Jaranowski 
+1

niedz., 11 cze 2023 o 22:14 Michael Osipov  napisał(a):

> Hi,
>
> we solved 17 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318121=12350597
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/projects/MWAR/issues
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1955/
>
> https://repository.apache.org/content/repositories/maven-1955/org/apache/maven/plugins/maven-war-plugin/3.4.0/maven-war-plugin-3.4.0-source-release.zip
>
> Source release checksum(s):
> maven-war-plugin-3.4.0-source-release.zip
> sha512:
>
> ef7b2621697024570522a778318106f1e5ca18bf6944cb9e43e693e8c37312af272036f517d03b3555622f9bad695217ececa078affda6442d76063b5153f998
>
> 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 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

-- 
Sławomir Jaranowski

Re: [VOTE] Release Maven Invoker Plugin version 3.6.0

2023-06-12 Thread Slawomir Jaranowski 
+1

niedz., 11 cze 2023 o 19:34 Michael Osipov  napisał(a):

> Hi,
>
> we solved 8 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317525=12353076
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MINVOKER%20AND%20resolution%20%3D%20Unresolved
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1954/
>
> https://repository.apache.org/content/repositories/maven-1954/org/apache/maven/plugins/maven-invoker-plugin/3.6.0/maven-invoker-plugin-3.6.0-source-release.zip
>
> Source release checksum(s):
> maven-invoker-plugin-3.6.0-source-release.zip
> sha512:
>
> ed73a73536577de505c2c09b09ad644dcd4e1b957c785dc48d3481c67ba5f598ba5095d125d3d54414fde02226fb638536e1bcdc7618b23515d224184af3fdf2
>
> Staging site:
> https://maven.apache.org/plugins-archives/maven-invoker-plugin-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

-- 
Sławomir Jaranowski

Re: Build POM and consumer POM (was Re: [DISCUSS] POM model version

2023-06-12 Thread Romain Manni-Bucau 
Le lun. 12 juin 2023 à 01:36, Guillaume Nodet  a écrit :

> Le dim. 11 juin 2023 à 23:12, Romain Manni-Bucau  a
> écrit :
>
> >
> >
> > Le dim. 11 juin 2023 à 22:28, Guillaume Nodet  a
> > écrit :
> >
> >> Those are actually two different questions, but I'd like to raise those
> >> together, since they do affect the same feature.
> >>
> >> 1/ We currently don't have an XML schema for the build POM.  One
> >> possibility would be to relax a bit the constraints on the main POM
> >> schema (
> >> http://maven.apache.org/xsd/maven-4.0.0.xsd) so that some elements are
> >> not
> >> mandatory in the xml.  By not modifying the validation rules, those
> >> elements will have to be present in the object model, so that should be
> >> safe.   Another option would be to have a separate schema, but given the
> >> small set of changes on the build pom on the current constraints, i
> >> think the first solution would be better.  As a reminder, the build pom
> >> supports: inferring version for artifacts that are part of the reactor
> >> (that's usually done using managedVersion), inferring the relativePath
> >> element, ci friendly interpolation for the version.
> >>
> >
> > +1 to relax
> >
> >>
> >> 2/ the consumer POM could be streamlined much more using the same
> >> techniques than used in the flatten-maven-plugin. Currently, we're only
> >> removing the  element, but we could remove the full build
> >> section,
> >> flatten dependencies, etc...  Packaged artifacts (i.e. with a non pom
> >> packaging), can only be used as dependencies, so I think the whole
> >> flattening process could make sense.  Is there any drawback in doing so
> ?
> >> Any particular reason the consumer POM support is limited to removing
> >> modules and does not go further ?  I can see some discussion in
> >> https://cwiki.apache.org/confluence/display/MAVEN/Build+vs+Consumer+POM
> >> but
> >> those do not seem to be settled.
> >>
> >
> > Doesnt flattening break transitive dep resolution since depth changes?
> >
> > Also drops some build meta which cant be resoled anymore portably like
> > compiler setup, which graalvm version was used and lastly would need to
> > drop or not props not used elsewhere.
> > Think staying as close as possible of the source is overall good to
> > consume as intended (build control) until the transformer is fully
> > configurable (never hopefully since it sounds overcomplicated).
> >
>
> All those properties, plugin config, etc... are completely irrelevant for
> jars or any other packaged artifact.  The only way those can actually have
> an impact is when you use the pom as a parent.  That's because when you
> inherit from a project, it has to have the "pom" packaging.  Dependency
> management is used when importing BOMs, but all other usages are afaik
> limited to declaring dependencies or plugins, and in those cases, the only
> interesting bits are dependencies, dependencyManagement, parents and
> properties (+ repositories).  The flatten-m-p does merge those 4 pieces
> into a single list of dependencies (which has the benefit of simplifying
> the consumption of the artifact).  We may not want to do that, but still
> the build section is completely irrelevant.
>

Do you assume people only use pom as a dependencies source? it is used for
way more than that IMHO.
While I agree how plugins are executed is not important, how they are
configured is used and adds value to consumers.
A simple example (but trust me I saw some more complex in companie$) is to
check compiler configs to ensure the assumed based runtime will work,
indeed it is part of a static analyzis (and rarely the build) but the used
source is the deployed pom and I strongly think it is an important metadata.
Indeed you can say all that must be replaced by some metadata files but, as
of today,  the pom gives that quite easily and pseudo portably (you just
compensate artifacts not using maven with explicit meta but it is a few
compared to dropping it globally).


>
> To recap, we have 3 different usages of the POM:
>   * the build pom on the file system read by maven when running
>   * the consumer pom on a repository which is used when consuming a
> dependency/plugin jar or any other kind of packaging
>   * the build pom with a pom packaging which can be uploaded to central and
> used as a parent by another project
>

Agree


>
> I do somewhat understand the will to keep the pom schema for artifacts
> uploaded in central.  When consuming those jars (as dependencies or
> plugins), there's definitely very little need to actually make any change
> to the POM schema that they are using (even though I'm not really buying
> the fact that it has to be set in "amber").  Maven already supports any new
> element/attribute and other tools could adapt as well.
> However, there are clear needs to improve the build side POM.  The
> build/pom consumer has done some improvement here, but it's not finished,
> and the pain point has not been addressed in any doc/wiki page