Re: Maven 3.9.7 fails to activate profile?

[Tamás Cservenák]

In the mean time we got this issue as well:
https://issues.apache.org/jira/browse/MNG-8131

On Tue, May 28, 2024, 21:25 John Neffenger  wrote:

> On 5/28/24 7:52 AM, Tamás Cservenák wrote:
> > well, after a quite long investigation we came to several conclusions:
> > * 3.9.6 and before worked really "by chance", as
> > * the POM is invalid
>
> Thank you very much, Tamás and Romain. I really appreciate your help and
> expertise. I will report the issue to the OpenJFX project.
>
> > In fact, am unsure what produced this POM, as Maven cannot even grasp it
> > (refuses to load it even):
> > https://gist.github.com/cstamas/27b948306cddabd00105f747e744e2cd
>
> I recreated those errors now, too. Thanks for the evidence.
>
> John
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: Maven 3.9.7 fails to activate profile?

[John Neffenger]

On 5/28/24 7:52 AM, Tamás Cservenák wrote:

well, after a quite long investigation we came to several conclusions:
* 3.9.6 and before worked really "by chance", as
* the POM is invalid


Thank you very much, Tamás and Romain. I really appreciate your help and 
expertise. I will report the issue to the OpenJFX project.



In fact, am unsure what produced this POM, as Maven cannot even grasp it
(refuses to load it even):
https://gist.github.com/cstamas/27b948306cddabd00105f747e744e2cd


I recreated those errors now, too. Thanks for the evidence.

John

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

Re: [VOTE] Release Maven Shade Plugin 3.6.0

[Sylwester Lachiewicz]

+1

wt., 28 maj 2024 o 18:10 Romain Manni-Bucau 
napisał(a):

> +1, thanks
>
> (small request: can the title "Drop plugin cruft" be rewritten to describe
> the issue in the changelog on jira?)
>
> Romain Manni-Bucau
> @rmannibucau  |  Blog
>  | Old Blog
>  | Github <
> https://github.com/rmannibucau> |
> LinkedIn  | Book
> <
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> >
>
>
> Le mar. 28 mai 2024 à 17:21, Tamás Cservenák  a
> écrit :
>
> > Howdy,
> >
> > We solved 7 issues:
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317921=12354611
> >
> > There are still a couple of issues left in JIRA:
> > https://issues.apache.org/jira/projects/MSHADE/issues
> >
> > Staging repo:
> > https://repository.apache.org/content/repositories/maven-2134/
> >
> > Source release checksum(s) SHA-512 :
> >
> >
> b0a31f02918329c466abd9c7b0c01bc7baeb0fbf8ef084212800c24b937d01495614fde43771689daec9160ef43bcd93c2d87a12dfe9d4e0fd926e190f28f797
> >
> > 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
> >
>

Re: [DISCUSS] Removal of ineffective switch for Maven 4

[Guillaume Nodet]

Le mar. 28 mai 2024 à 20:23, Maarten Mulders  a
écrit :

> Yep, that commit was over 3 years ago... Yet Maven 3.8 and 3.9 have been
> released since that date, and both version series report having those
> options - although "ineffective".
>
>
Yes, that's because the 3.x branch has been created a long time ago.


>
> The good thing is that Maven 4 does not report them. So I'll leave it at
> that.
>
>
> Maarten
>
> On 25/05/2024 14:00, Guillaume Nodet wrote:
> > I think those have been removed  3 years ago...
> >   https://issues.apache.org/jira/browse/MNG-6888
> >
> > Le ven. 24 mai 2024 à 13:10, Maarten Mulders  a
> > écrit :
> >
> >> On 24/05/2024 09:43, Michael Osipov wrote:
> >>> On 2024/05/24 07:06:45 Maarten Mulders wrote:
>  Hi all,
> 
>  Today, I noticed Maven has an `-up` switch, for `--update-plugins`.
> The
>  help text says it's ineffective, only kept for backward compatibility.
> 
>  With the advent of Maven 4, would this be a good moment to remove this
>  switch?
> >>>
> >>> There much more of them to be killed, but before we do that we need to
> >> make sure that any of our plugins which invoke Maven never pass them,
> then
> >> we can discuss their removal.
> >>
> >> Just checked, and indeed, there are a few more listed explicitly as
> >> "ineffective":
> >>
> >> -cpu, --check-plugin-updates
> >> -npr, --no-plugin-registry
> >> -npu, --no-plugin-updates
> >> -up, --update-plugins
> >>
> >> My idea would then be to see if any of these four are used in our own
> >> code base (core as well as plugins). If there are usages, let's remove
> >> them. That should not be hard, as they don't trigger any behaviour
> >> anymore. After that, we can continue to drop them from the Maven CLI.
> >>
> >> Would that make sense?
> >>
> >>
> >> Maarten
> >>
> >> -
> >> 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
>
>

-- 

Guillaume Nodet

Re: [DISCUSS] Removal of ineffective switch for Maven 4

[Maarten Mulders]

Yep, that commit was over 3 years ago... Yet Maven 3.8 and 3.9 have been 
released since that date, and both version series report having those 
options - although "ineffective".



The good thing is that Maven 4 does not report them. So I'll leave it at 
that.



Maarten

On 25/05/2024 14:00, Guillaume Nodet wrote:

I think those have been removed  3 years ago...
  https://issues.apache.org/jira/browse/MNG-6888

Le ven. 24 mai 2024 à 13:10, Maarten Mulders  a
écrit :


On 24/05/2024 09:43, Michael Osipov wrote:

On 2024/05/24 07:06:45 Maarten Mulders wrote:

Hi all,

Today, I noticed Maven has an `-up` switch, for `--update-plugins`. The
help text says it's ineffective, only kept for backward compatibility.

With the advent of Maven 4, would this be a good moment to remove this
switch?


There much more of them to be killed, but before we do that we need to

make sure that any of our plugins which invoke Maven never pass them, then
we can discuss their removal.

Just checked, and indeed, there are a few more listed explicitly as
"ineffective":

-cpu, --check-plugin-updates
-npr, --no-plugin-registry
-npu, --no-plugin-updates
-up, --update-plugins

My idea would then be to see if any of these four are used in our own
code base (core as well as plugins). If there are usages, let's remove
them. That should not be hard, as they don't trigger any behaviour
anymore. After that, we can continue to drop them from the Maven CLI.

Would that make sense?


Maarten

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






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

Re: [VOTE] Release Maven Shade Plugin 3.6.0

[Romain Manni-Bucau]

+1, thanks

(small request: can the title "Drop plugin cruft" be rewritten to describe
the issue in the changelog on jira?)

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



Le mar. 28 mai 2024 à 17:21, Tamás Cservenák  a écrit :

> Howdy,
>
> We solved 7 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317921=12354611
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/projects/MSHADE/issues
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-2134/
>
> Source release checksum(s) SHA-512 :
>
> b0a31f02918329c466abd9c7b0c01bc7baeb0fbf8ef084212800c24b937d01495614fde43771689daec9160ef43bcd93c2d87a12dfe9d4e0fd926e190f28f797
>
> 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
>

[VOTE] Release Maven Shade Plugin 3.6.0

[Tamás Cservenák]

Howdy,

We solved 7 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317921=12354611

There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/projects/MSHADE/issues

Staging repo:
https://repository.apache.org/content/repositories/maven-2134/

Source release checksum(s) SHA-512 :
b0a31f02918329c466abd9c7b0c01bc7baeb0fbf8ef084212800c24b937d01495614fde43771689daec9160ef43bcd93c2d87a12dfe9d4e0fd926e190f28f797

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

Re: Maven 3.9.7 fails to activate profile?

[Romain Manni-Bucau]

you ask but you know it is gradle right ([1])? ;)

It is the risk to drive the build descriptors by code, you can get
conflicts using conventions not validating themselves in the build script.

[1] https://github.com/openjdk/jfx/blob/master/build.gradle#L1674

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



Le mar. 28 mai 2024 à 16:53, Tamás Cservenák  a écrit :

> Howdy,
>
> well, after a quite long investigation we came to several conclusions:
> * 3.9.6 and before worked really "by chance", as
> * the POM is invalid
>
> https://repo.maven.apache.org/maven2/org/openjfx/javafx/21.0.3/javafx-21.0.3.pom
>
> It uses _same profile IDs for conflicting profies_ (as one can expect,
> fields having "ID" in their name are supposed to be, well, "identifiers").
>
> In fact, am unsure what produced this POM, as Maven cannot even grasp it
> (refuses to load it even):
> https://gist.github.com/cstamas/27b948306cddabd00105f747e744e2cd
>
> Thanks
> T
>
>
> On Mon, May 27, 2024 at 11:43 PM John Neffenger  wrote:
>
> > Thank you for the quick response, Tamás.
> >
> > On 5/27/24 11:51 AM, Tamás Cservenák wrote:
> > > Can you create a small reproducer, ideally shared on github or similar
> > > service?
> >
> > This "Hello World" JavaFX project illustrates the problem for me:
> >
> >Hello JavaFX!
> >https://github.com/jgneff/hello-javafx
> >
> > Just clone and build with:
> >
> >$ git clone https://github.com/jgneff/hello-javafx.git
> >$ cd hello-javafx
> >$ mvn clean package
> >
> > Thanks,
> > John
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
> >
>

Re: Maven 3.9.7 fails to activate profile?

[Tamás Cservenák]

Howdy,

well, after a quite long investigation we came to several conclusions:
* 3.9.6 and before worked really "by chance", as
* the POM is invalid
https://repo.maven.apache.org/maven2/org/openjfx/javafx/21.0.3/javafx-21.0.3.pom

It uses _same profile IDs for conflicting profies_ (as one can expect,
fields having "ID" in their name are supposed to be, well, "identifiers").

In fact, am unsure what produced this POM, as Maven cannot even grasp it
(refuses to load it even):
https://gist.github.com/cstamas/27b948306cddabd00105f747e744e2cd

Thanks
T


On Mon, May 27, 2024 at 11:43 PM John Neffenger  wrote:

> Thank you for the quick response, Tamás.
>
> On 5/27/24 11:51 AM, Tamás Cservenák wrote:
> > Can you create a small reproducer, ideally shared on github or similar
> > service?
>
> This "Hello World" JavaFX project illustrates the problem for me:
>
>Hello JavaFX!
>https://github.com/jgneff/hello-javafx
>
> Just clone and build with:
>
>$ git clone https://github.com/jgneff/hello-javafx.git
>$ cd hello-javafx
>$ mvn clean package
>
> Thanks,
> John
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

[VOTE] Release Maven Plugin Tools version 3.13.1

[Michael Osipov]

Hi,

we solved 1 issue:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317820=12354759

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-2133/
https://repository.apache.org/content/repositories/maven-2133/org/apache/maven/plugin-tools/maven-plugin-tools/3.13.1/maven-plugin-tools-3.13.1-source-release.zip

Source release checksum(s):
maven-plugin-tools-3.13.1-source-release.zip
sha512: 
2464cd9e69eeaec410488228b9d1773e572ec6fbe339e745da591b2837e8ea806eaf2b57608662eee96c79a4f8f43cb4ebbcb087c2988e234ad144f08eb4c00f


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

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

Vote open for 72 hours.

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

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

[ANN] Apache Maven Reporting Exec 2.0.0-M14 released

[Michael Osipov]

The Apache Maven team is pleased to announce the release of the Maven 
Reporting Exec version 2.0.0-M14.


https://maven.apache.org/shared/maven-reporting-exec/


Release Notes - Maven Shared Components - Version 
maven-reporting-exec-2.0.0-M14


** Dependency upgrade
* [MSHARED-1392] - Upgrade to Parent 42 and Maven 3.6.3
* [MSHARED-1404] - Upgrade plugins and components (in ITs)


Enjoy,

-The Apache Maven team

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

[ANN] Apache Maven Reporting Impl 4.0.0-M15 released

[Michael Osipov]

The Apache Maven team is pleased to announce the release of the Maven 
Reporting Impl version 4.0.0-M15.


https://maven.apache.org/shared/maven-reporting-impl/


Release Notes - Maven Shared Components - Version 
maven-reporting-impl-4.0.0-M15


** Dependency upgrade
* [MSHARED-1392] - Upgrade to Parent 42 and Maven 3.6.3
* [MSHARED-1397] - Bump org.apache.maven:maven-archiver from 3.6.1 
to 3.6.2

* [MSHARED-1402] - Upgrade plugins and components (in ITs)


Enjoy,

-The Apache Maven team

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

[RESULT] [VOTE] Release Apache Maven Reporting Exec version 2.0.0-M14

[Michael Osipov]

Hi,

The vote has passed with the following result:

+1: Michael Osipov, Tamás Cservenák, Slawomir Jaranowski, Sylwester 
Lachiewicz


PMC quorum: reached

I will promote the artifacts to the central repo, the source release ZIP 
file and add this release the board report.

[RESULT] [VOTE] Release Apache Maven Reporting Impl version 4.0.0-M15

[Michael Osipov]

Hi,

The vote has passed with the following result:

+1: Michael Osipov, Tamás Cservenák, Slawomir Jaranowski, Sylwester 
Lachiewicz


PMC quorum: reached

I will promote the artifacts to the central repo, the source release ZIP 
file and add this release the board report.

Re: [VOTE] Release Apache Maven Dependency Tree version 3.3.0

[Michael Osipov]

On 2024/05/26 18:22:05 Michael Osipov wrote:
> Hi,
> 
> NOTE: This is expected to be the last release of this component.
> 
> we solved 5 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12348675
> 
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20maven-dependency-tree
> 
> Staging repo:
> https://repository.apache.org/content/repositories/maven-2132/
> https://repository.apache.org/content/repositories/maven-2132/org/apache/maven/shared/maven-dependency-tree/3.3.0/maven-dependency-tree-3.3.0-source-release.zip
> 
> Source release checksum(s):
> maven-dependency-tree-3.3.0-source-release.zip
> sha512: 
> b9e8c3cda43a0ad54ea80795cc265c49f4196fe23c0494a1abacb37ac424209c171b0c64da141302d4cf579a83ba92053ca00b5b6092817cd499abfe6c83cbb1
> 
> 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 72 hours.

+1

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

Re: [VOTE] Release Apache Maven Enforcer version 3.5.0

[Karl Heinz Marbaise]

Hi,

+1 from me.

Kind regards
Karl Heinz Marbaise
On 26.05.24 19:51, Slawomir Jaranowski wrote:

Hi,

We solved 9 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317520=12353621

There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MENFORCER%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC

Staging repo:
https://repository.apache.org/content/repositories/maven-2131/
https://repository.apache.org/content/repositories/maven-2131/org/apache/maven/enforcer/enforcer/3.5.0/enforcer-3.5.0-source-release.zip

Source release checksum(s):
enforcer-3.5.0-source-release.zip - SHA-512 :
a8d91fe9f0a47746af8c0a0c9287350750dc2fc342b73f14ff9d0f32cb2b4c1c9ba727d7a5924644cd22d12bbef70474c7404d5c06858585595af085e761d095

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




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