Re: [VOTE] Release Apache Maven JLink Plugin version 3.2.0

2024-01-29 Thread Romain Manni-Bucau 
+1

Le lun. 29 janv. 2024 à 23:41, Sylwester Lachiewicz 
a écrit :

> +1
>
> pon., 29 sty 2024 o 20:37 Benjamin Marwell 
> napisał(a):
>
> > Hi,
> >
> > We solved 6 issues:
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321432&version=12349496
> >
> > There are still two issues left in JIRA:
> > https://issues.apache.org/jira/projects/MJLINK/issues
> >
> > Staging repo:
> > https://repository.apache.org/content/repositories/maven-2064
> >
> >
> https://repository.apache.org/service/local/repositories/maven-2064/content/org/apache/maven/plugins/maven-jlink-plugin/3.2.0/maven-jlink-plugin-3.2.0-source-release.zip
> >
> > Source release checksum(s):
> > maven-jlink-plugin-3.2.0-source-release.zip sha512:
> >
> >
> 0cedc1a75b2ed7c085017ad65f18a10b2da4d06217dcb0eb6a1e6e22a8dadab2df4986b020392d15c7215e0b594f25e47d7341ed4e157a6b7e60be63158d008b%
> >
> > Staging site:
> > https://maven.apache.org/plugins-archives/maven-jlink-plugin-LATEST/
> >
> > Guide to testing staged releases:
> > https://maven.apache.org/guides/development/guide-testing-releases.html
> >
> > Vote open for at least 72 hours.
> >
> > [ ] +1
> > [ ] +0
> > [ ] -1
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
> >
>

Re: [VOTE] Release Apache Maven JLink Plugin version 3.2.0

2024-01-29 Thread Sylwester Lachiewicz 
+1

pon., 29 sty 2024 o 20:37 Benjamin Marwell  napisał(a):

> Hi,
>
> We solved 6 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321432&version=12349496
>
> There are still two issues left in JIRA:
> https://issues.apache.org/jira/projects/MJLINK/issues
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-2064
>
> https://repository.apache.org/service/local/repositories/maven-2064/content/org/apache/maven/plugins/maven-jlink-plugin/3.2.0/maven-jlink-plugin-3.2.0-source-release.zip
>
> Source release checksum(s):
> maven-jlink-plugin-3.2.0-source-release.zip sha512:
>
> 0cedc1a75b2ed7c085017ad65f18a10b2da4d06217dcb0eb6a1e6e22a8dadab2df4986b020392d15c7215e0b594f25e47d7341ed4e157a6b7e60be63158d008b%
>
> Staging site:
> https://maven.apache.org/plugins-archives/maven-jlink-plugin-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for at least 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: [MPH-183] effective-pom + verbose should show path to source

2024-01-29 Thread Maarten Mulders 
Sorry to reboot this really old thread, but I feel it's best to reply to 
this rather than creating a new one.


Unfortunately, I haven't found much time to work on this myself. But I'm 
happy to report that I did find two colleagues who are very eager to 
take on this challenge. I'm working closely with them to help them where 
necessary.



Thanks,

Maarten

On 14/09/2022 13:39, Maarten Mulders wrote:

On 08/06/2022 23:03, Robert Scholte wrote:
This is already a huge improvement as imported boms now hides this 
information.


Thanks!

I do see room for more improvements, though (even though they could be 
considering as minor as this already solves a critical issue)


  From another example I picked one of the longest lines:
2.16.1  


Suppose you want to use a different version of this zipkin dependency, 
what should you do? The first thing is to check is if you can upgrade 
spring-cloud-dependencies. The focus should be on that dependency.


Even though  io.zipkin.reporter2:zipkin-reporter-bom:2.16.1, line 149 
is the most exact location, what's probably more important from a 
developer perspective is the preferred location to make a change in 
your pom.
That would likely be 
org.springframework.cloud:spring-cloud-dependencies:2020.0.4.
IMO that should be the first part of the line (instead of scrolling to 
the right). This implies reverting the order, so instead of  .. from 
.. from .., I'd prefer .. to .. to ..


This should be a relatively simple task. I think we can isolate this in 
the M-H-P. I feel it should be part of the first release - reversing the 
display order later would be confusing to users.


Now that we know the 
org.springframework.cloud:spring-cloud-dependencies dependency needs 
to be updated, it would be great if it shows the linenumber in the pom.
We might run into problems if this was inherited via a parent pom, in 
which case we should make clear which parent shoould be changed.


Agreed - I haven't checked that use case yet, but I see how it could be 
relevant and useful. I think this could be postponed to a later release 
if it turns out to be hard to implement.


I'm already very pleased with the current results. If you agree with 
me you can make separate tasks of it and decide if they should be come 
part of the same release or not.
I consider it finetuning, although adjusting the order later might 
result in a huge shock as you suddenly need to read it the other way 
around.


Great minds... :-)


great work,


Thanks again!


Robert

-- Oorspronkelijke bericht --
Van "Maarten Mulders" 
Aan "Maven Developers List" 
Datum 7-6-2022 17:46:41
Onderwerp [MPH-183] effective-pom + verbose should show path to source


Hi all,

Over the past months, I have been working on an enhancement [1] for 
the Maven Help Plugin. The enhancement is about the effective-pom 
goal. If you pass it the 'verbose' parameter, it will include inline 
comments saying "this line of the effective pom is caused by this 
line in a different pom":



  org.example  
  mng-7344-dep-x  
  2  



This is not so useful when you have a long path of POMs referring to 
each other. It will only show the last POM of that trail, but not the 
intermediate POMs. This makes it hard for users to understand how 
their effective POM was constructed. In the enhanced version, 
help:effective-pom -Dverbose would show something like this:



  org.example  
  mng-7344-dep-x  
  2  




(I'm sorry, the output is hard to read in a plain-text email; a 
formatted version is available in the JIRA ticket [1].)



This enhancement requires changes in three projects:
1. Maven Help Plugin
2. Maven Core
3. Modello



Now that the proof of concept is there, I'd like to ask: is this an 
enhancement we want to incorporate into Maven? If so, I'll start by 
polishing the code a bit, and then open three separate merge 
requests. We can discuss the implementation there.


One particularly important thing to mention is that I did _not yet_ 
pay attention to backward compatibility of the Maven Help Plugin. I 
believe we can do this in a decent way - it wasn't the first priority 
for the proof of concept.



I'm looking forward to hearing your thoughts on this.


Thanks,


Maarten



[1] https://issues.apache.org/jira/browse/MPH-183

-
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




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

[VOTE] Release Apache Maven JLink Plugin version 3.2.0

2024-01-29 Thread Benjamin Marwell 
Hi,

We solved 6 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321432&version=12349496

There are still two issues left in JIRA:
https://issues.apache.org/jira/projects/MJLINK/issues

Staging repo:
https://repository.apache.org/content/repositories/maven-2064
https://repository.apache.org/service/local/repositories/maven-2064/content/org/apache/maven/plugins/maven-jlink-plugin/3.2.0/maven-jlink-plugin-3.2.0-source-release.zip

Source release checksum(s):
maven-jlink-plugin-3.2.0-source-release.zip sha512:
0cedc1a75b2ed7c085017ad65f18a10b2da4d06217dcb0eb6a1e6e22a8dadab2df4986b020392d15c7215e0b594f25e47d7341ed4e157a6b7e60be63158d008b%

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

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

Vote open for at least 72 hours.

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

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

[ANN] Apache Maven Resolver 2.0.0-alpha-7 released

2024-01-29 Thread Tamás Cservenák 
Howdy,

The Apache Maven team is pleased to announce the release of the
Maven Resolver 2.0.0-alpha-7.

https://maven.apache.org/resolver-archives/resolver-2.0.0-alpha-7/

This is a sixth *PREVIEW* (alpha-4 was scrubbed) release of upcoming Maven
Resolver 2.0.0 meant for users of Resolver to pick it up and adapt code if
needed. This alpha contains almost all of the planned features and
improvements, and for sure some unplanned bugs as well.

Release Notes - Maven Resolver - Version 2.0.0-alpha-7

** Bug
* [MRESOLVER-334] - Maven Resolver GenericVersionScheme diverges from
the spec
* [MRESOLVER-336] - Unexpected handling of qualifiers in
GenericVersionScheme
* [MRESOLVER-464] - JDK transport bug
** Improvement
* [MRESOLVER-264] - Make file-lock the default locking
* [MRESOLVER-463] - Ensure checksum record file (summary fie) is sorted
by artifact relative path and not checksum
* [MRESOLVER-465] - Make room for new version scheme implementations
* [MRESOLVER-467] - Pull out shared HTTP (Remote Included checksum) code
* [MRESOLVER-468] - Stabilize supplier binary and source compatibility
** Task
* [MRESOLVER-466] - Extend site documentation
* [MRESOLVER-470] - Prepare for new changes regarding Artifact
properties/scopes
* [MRESOLVER-471] - Resolver should be oblivious about scopes
** Dependency upgrade
* [MRESOLVER-469] - Upgrade to Maven 4.0.0-alpha-12
* [MRESOLVER-472] - Upgrade Jetty dependency to 10.0.19
* [MRESOLVER-473] - Upgrade slf4j to version 2.0.11 (align with Maven)
* [MRESOLVER-474] - Upgrade (build, not project) dependency
commons-lang to 3.14.0
* [MRESOLVER-475] - Upgrade Wagon transport dependency:
plexus-classworlds to 2.8.0
* [MRESOLVER-476] - Upgrade Wagon transport test dependency:
plexus-testing to 1.3.0
* [MRESOLVER-477] - Upgrade managed dependency: plexus-xml to 4.0.3
* [MRESOLVER-478] - Redisson named locks: upgrade to
org.redisson:redisson 3.26.0
* [MRESOLVER-479] - Hazelcast named locks: upgrade to
com.hazelcast:hazelcast 5.3.6

Have fun,
Maven Team

[RESULT] [VOTE] Release Maven Resolver 2.0.0-alpha-7

2024-01-29 Thread Tamás Cservenák 
Howdy,

The vote has passed with the following result:

+1: Sylwester, Slawomir, Romain, Olivier, Guillaume

PMC quorum: reached

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

Thanks
T

Re: [VOTE] Release Maven Resolver 2.0.0-alpha-7

2024-01-29 Thread Guillaume Nodet 
+1

Le jeu. 25 janv. 2024 à 19:58, Tamás Cservenák  a écrit :
>
> Howdy,
>
> Note: This is a sixth (alpha-4 was scrubbed) preview release of Resolver
> 2.0.0, that would allow any downstream consumers to try it out and adapt.
> The supplier is aligned with Maven 4.0.0-alpha-12. Delivered features are
> mostly smaller improvements, bug fixes and dependency updates. One notable
> change is that this release makes "file locking" enabled by default. This
> alpha contains pretty much every major feature we planned for 2.0.0. Of
> course, we do NOT exclude more issues to be added (most likely bugs) down
> the road, but the final 2.0.0 release is getting near.
>
> For configuration changes, see
> https://maven.apache.org/resolver-archives/resolver-LATEST/configuration.html
>
> IF the vote is successful, the staging site will NOT be moved to
> https://maven.apache.org/resolver/ but instead will be made reachable from
> https://maven.apache.org/resolver-archives/resolver-2.0.0-alpha-7/ only.
>
> The 1.9.18 is still the "latest stable" release of Maven Resolver.
>
> ===
>
> We solved 20 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628&version=12354065
>
> There are still some issues in JIRA:
> https://issues.apache.org/jira/projects/MRESOLVER/issues
>
> Staging repository:
> https://repository.apache.org/content/repositories/maven-2063
>
> Source release SHA512:
> af765437edad19adb5cca208841c431bafc983288f5fd6ea09f6446a8ad30bcb27e2c0b81e4652ab4a95ecc8ca95a03cbeb20e3283a3ff1ced40caf6c3dbcf1b
>
> Staging site:
> https://maven.apache.org/resolver-archives/resolver-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1



-- 

Guillaume Nodet

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

Re: Strange behavior using maven build-cache extension in maven-release-plugin goals

2024-01-29 Thread Javier Gómez 

Hi Olivier,

No, the maven deploy goal is not executed twice if I launch it directly. 
It only happens with therelease:perform goal (which has a deploy goal 
configured)



  org.apache.maven.plugins
  maven-release-plugin
  3.0.0
  
-DskipEnforceSnapshots -DskipITs -DskipTests 
-DskipUTs
deploy

On 25/1/24 9:13, Olivier Lamy wrote:

PRECAUCIÓN: Este mensaje es de un REMITENTE EXTERNO - sea CUIDADOSO, en 
particular con los enlaces y archivos adjuntos. / CAUTION: This message is from 
an EXTERNAL SENDER - be CAUTIOUS, particularly with links and attachments.

interesting.
is the deploy goal executed twice as well when you run "mvn deploy"?
(as you marked as it as alwaysRun)

On Sun, 21 Jan 2024 at 23:00, Javier Gómez  wrote:

Hi all,

We are starting to apply the build-cache maven extension in our local and CI 
environment,  and we have seen strange behavior in several maven projects, when 
using the release plugin in conjunction with build-cache, which we have been 
able to reproduce both locally and in CI.

Our usual release plugin configuration is:

 
   org.apache.maven.plugins
   maven-release-plugin
   3.0.0
   
 -DskipEnforceSnapshots -DskipITs -DskipTests 
-DskipUTs
 deploy
 
SemVerVersionPolicy
 GithubReleaseStrategy
 @{prefix} Prepare release 
@{releaseLabel}
 @{prefix} Prepare for next development 
iteration
 @{project.version}
   

When we add the build-cache extension to the project, and execute the release 
with: mvn release:prepare release:perform -DreleaseVersion=x.y.z we can observe 
a strange behavior when maven is launching the release:perform goal, we see 
that the deploy goal is executed 2 times for each artifact (in fact it seems 
that the maven lifecycle restarts, once it reaches the deploy and begins to 
execute the validate again) and when it reaches the 2nd execution of deploy, it 
fails (since the user we use do not have permissions to overwrite artifacts). 
Below I show an extract from the log:

...

[INFO] [INFO] 

[INFO] [INFO] Reactor Build Order:
[INFO] [INFO]
[INFO] [INFO] temp.mectagcore:mectagcore [pom]
[INFO] [INFO] temp.mectagcore:mectagcore-domain  [jar]
[INFO] [INFO] temp.mectagcore:mectagcore-boot[jar]
[INFO] [INFO] temp.mectagcore:jacoco-report-aggregate[pom]
[INFO] [INFO]
[INFO] [INFO] -< temp.mectagcore:mectagcore >-
[INFO] [INFO] Building temp.mectagcore:mectagcore 1.0.0  [1/9]
[INFO] [INFO]   from pom.xml
[INFO] [INFO] [ pom 
]-
[INFO] [INFO] Going to calculate checksum for project [groupId=temp.mectagcore, 
artifactId=mectagcore]
[INFO] [INFO] Project inputs calculated in 12 ms. SHA-256 checksum 
[16534757c14aae9b1ff1961664995f0e7e9396fb88309d207a8a23c080c7f661] calculated 
in 4 ms.
[INFO] [INFO] Attempting to restore project temp.mectagcore:mectagcore from 
build cache
[INFO] [INFO] Local build found by checksum 
16534757c14aae9b1ff1961664995f0e7e9396fb88309d207a8a23c080c7f661
[INFO] [INFO] Found cached build, restoring temp.mectagcore:mectagcore from 
cache by checksum 
16534757c14aae9b1ff1961664995f0e7e9396fb88309d207a8a23c080c7f661
[INFO] [INFO] Project temp.mectagcore:mectagcore restored partially. Highest 
cached goal: verify, requested: deploy
[INFO] role: 'org.apache.maven.plugin.Mojo', implementation: 
'org.apache.maven.plugin.failsafe.IntegrationTestMojo', role hint: 
'org.apache.maven.plugins:maven-failsafe-plugin:3.0.0:integration-test'
[INFO] role: 'org.apache.maven.plugin.Mojo', implementation: 
'org.apache.maven.plugin.failsafe.VerifyMojo', role hint: 
'org.apache.maven.plugins:maven-failsafe-plugin:3.0.0:verify'
[INFO] ---
[INFO] [INFO] Skipping plugin execution (cached): enforcer:enforce
[INFO] [INFO] Skipping plugin execution (cached): enforcer:enforce
[INFO] [INFO] Skipping plugin execution (cached): build-helper:add-source
[INFO] [INFO] Mojo execution is forced by project property: 
amiga-assembly:amiga-assembly
[INFO] [INFO]
[INFO] [INFO] --- amiga-assembly:5.5.0:amiga-assembly 
(amiga-assembly-execution) @ mectagcore ---
[INFO] [INFO] Mojo execution is forced by project property: source:jar-no-fork
[INFO] [INFO]
[INFO] [INFO] --- source:3.2.1:jar-no-fork (attach-sources) @ mectagcore ---
[INFO] [INFO] Skipping plugin execution (cached): failsafe:integration-test
[INFO] [INFO] Skipping plugin execution (cached): failsafe:verify
[INFO] [INFO]
[INFO] [INFO] --- install:3.1.1:install (default-install) @ mectagcore ---
[INFO] role: 'org.apache.maven.plugin.Mojo', implementation: 
'org.apache.maven.plugins.install.InstallMojo', role hint: 
'org.apache.maven.plugins:mave

Re: [VOTE] Release Maven Resolver 2.0.0-alpha-7

2024-01-29 Thread Olivier Lamy 
+1

On Fri, 26 Jan 2024 at 04:58, Tamás Cservenák  wrote:
>
> Howdy,
>
> Note: This is a sixth (alpha-4 was scrubbed) preview release of Resolver
> 2.0.0, that would allow any downstream consumers to try it out and adapt.
> The supplier is aligned with Maven 4.0.0-alpha-12. Delivered features are
> mostly smaller improvements, bug fixes and dependency updates. One notable
> change is that this release makes "file locking" enabled by default. This
> alpha contains pretty much every major feature we planned for 2.0.0. Of
> course, we do NOT exclude more issues to be added (most likely bugs) down
> the road, but the final 2.0.0 release is getting near.
>
> For configuration changes, see
> https://maven.apache.org/resolver-archives/resolver-LATEST/configuration.html
>
> IF the vote is successful, the staging site will NOT be moved to
> https://maven.apache.org/resolver/ but instead will be made reachable from
> https://maven.apache.org/resolver-archives/resolver-2.0.0-alpha-7/ only.
>
> The 1.9.18 is still the "latest stable" release of Maven Resolver.
>
> ===
>
> We solved 20 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628&version=12354065
>
> There are still some issues in JIRA:
> https://issues.apache.org/jira/projects/MRESOLVER/issues
>
> Staging repository:
> https://repository.apache.org/content/repositories/maven-2063
>
> Source release SHA512:
> af765437edad19adb5cca208841c431bafc983288f5fd6ea09f6446a8ad30bcb27e2c0b81e4652ab4a95ecc8ca95a03cbeb20e3283a3ff1ced40caf6c3dbcf1b
>
> Staging site:
> https://maven.apache.org/resolver-archives/resolver-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1

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

Re: [VOTE] Release Maven Resolver 2.0.0-alpha-7

2024-01-29 Thread Romain Manni-Bucau 
+1

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



Le dim. 28 janv. 2024 à 23:33, Slawomir Jaranowski 
a écrit :

> +1
>
> czw., 25 sty 2024, 19:58 użytkownik Tamás Cservenák 
> napisał:
>
> > Howdy,
> >
> > Note: This is a sixth (alpha-4 was scrubbed) preview release of Resolver
> > 2.0.0, that would allow any downstream consumers to try it out and adapt.
> > The supplier is aligned with Maven 4.0.0-alpha-12. Delivered features are
> > mostly smaller improvements, bug fixes and dependency updates. One
> notable
> > change is that this release makes "file locking" enabled by default. This
> > alpha contains pretty much every major feature we planned for 2.0.0. Of
> > course, we do NOT exclude more issues to be added (most likely bugs) down
> > the road, but the final 2.0.0 release is getting near.
> >
> > For configuration changes, see
> >
> >
> https://maven.apache.org/resolver-archives/resolver-LATEST/configuration.html
> >
> > IF the vote is successful, the staging site will NOT be moved to
> > https://maven.apache.org/resolver/ but instead will be made reachable
> from
> > https://maven.apache.org/resolver-archives/resolver-2.0.0-alpha-7/ only.
> >
> > The 1.9.18 is still the "latest stable" release of Maven Resolver.
> >
> > ===
> >
> > We solved 20 issues:
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628&version=12354065
> >
> > There are still some issues in JIRA:
> > https://issues.apache.org/jira/projects/MRESOLVER/issues
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/maven-2063
> >
> > Source release SHA512:
> >
> >
> af765437edad19adb5cca208841c431bafc983288f5fd6ea09f6446a8ad30bcb27e2c0b81e4652ab4a95ecc8ca95a03cbeb20e3283a3ff1ced40caf6c3dbcf1b
> >
> > Staging site:
> > https://maven.apache.org/resolver-archives/resolver-LATEST/
> >
> > Guide to testing staged releases:
> > https://maven.apache.org/guides/development/guide-testing-releases.html
> >
> > Vote open for 72 hours.
> >
> > [ ] +1
> > [ ] +0
> > [ ] -1
> >
>