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

[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.Install

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

[Olivier Lamy]

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

On Sun, 21 Jan 2024 at 23:00, Javier Gómez  wrote:
>
> Hi all,
>
> We are starting to apply the build-cache maven extension in our local and CI 
> environment,  and we have seen strange behavior in several maven projects, 
> when using the release plugin in conjunction with build-cache, which we have 
> been able to reproduce both locally and in CI.
>
> Our usual release plugin configuration is:
>
> 
>       org.apache.maven.plugins
>   maven-release-plugin
>   3.0.0
>   
> -DskipEnforceSnapshots -DskipITs -DskipTests 
> -DskipUTs
> deploy
> 
> SemVerVersionPolicy
> GithubReleaseStrategy
> @{prefix} Prepare release 
> @{releaseLabel}
> @{prefix} Prepare for next 
> development iteration
> @{project.version}
>   
>
> When we add the build-cache extension to the project, and execute the release 
> with: mvn release:prepare release:perform -DreleaseVersion=x.y.z we can 
> observe a strange behavior when maven is launching the release:perform goal, 
> we see that the deploy goal is executed 2 times for each artifact (in fact it 
> seems that the maven lifecycle restarts, once it reaches the deploy and 
> begins to execute the validate again) and when it reaches the 2nd execution 
> of deploy, it fails (since the user we use do not have permissions to 
> overwrite artifacts). Below I show an extract from the log:
>
> ...
>
> [INFO] [INFO] 
> 
> [INFO] [INFO] Reactor Build Order:
> [INFO] [INFO]
> [INFO] [INFO] temp.mectagcore:mectagcore [pom]
> [INFO] [INFO] temp.mectagcore:mectagcore-domain  [jar]
> [INFO] [INFO] temp.mectagcore:mectagcore-boot[jar]
> [INFO] [INFO] temp.mectagcore:jacoco-report-aggregate[pom]
> [INFO] [INFO]
> [INFO] [INFO] -< temp.mectagcore:mectagcore >-
> [INFO] [INFO] Building temp.mectagcore:mectagcore 1.0.0  [1/9]
> [INFO] [INFO]   from pom.xml
> [INFO] [INFO] [ pom 
> ]-
> [INFO] [INFO] Going to calculate checksum for project 
> [groupId=temp.mectagcore, artifactId=mectagcore]
> [INFO] [INFO] Project inputs calculated in 12 ms. SHA-256 checksum 
> [16534757c14aae9b1ff1961664995f0e7e9396fb88309d207a8a23c080c7f661] calculated 
> in 4 ms.
> [INFO] [INFO] Attempting to restore project temp.mectagcore:mectagcore from 
> build cache
> [INFO] [INFO] Local build found by checksum 
> 16534757c14aae9b1ff1961664995f0e7e9396fb88309d207a8a23c080c7f661
> [INFO] [INFO] Found cached build, restoring temp.mectagcore:mectagcore from 
> cache by checksum 
> 16534757c14aae9b1ff1961664995f0e7e9396fb88309d207a8a23c080c7f661
> [INFO] [INFO] Project temp.mectagcore:mectagcore restored partially. Highest 
> cached goal: verify, requested: deploy
> [INFO] role: 'org.apache.maven.plugin.Mojo', implementation: 
> 'org.apache.maven.plugin.failsafe.IntegrationTestMojo', role hint: 
> 'org.apache.maven.plugins:maven-failsafe-plugin:3.0.0:integration-test'
> [INFO] role: 'org.apache.maven.plugin.Mojo', implementation: 
> 'org.apache.maven.plugin.failsafe.VerifyMojo', role hint: 
> 'org.apache.maven.plugins:maven-failsafe-plugin:3.0.0:verify'
> [INFO] ---
> [INFO] [INFO] Skipping plugin execution (cached): enforcer:enforce
> [INFO] [INFO] Skipping plugin execution (cached): enforcer:enforce
> [INFO] [INFO] Skipping plugin execution (cached): build-helper:add-source
> [INFO] [INFO] Mojo execution is forced by project property: 
> amiga-assembly:amiga-assembly
> [INFO] [INFO]
> [INFO] [INFO] --- amiga-assembly:5.5.0:amiga-assembly 
> (amiga-assembly-execution) @ mectagcore ---
> [INFO] [INFO] Mojo execution is forced by project property: source:jar-no-fork
> [INFO] [INFO]
> [INFO] [INFO] --- source:3.2.1:jar-no-fork (attach-sources) @ mectagcore ---
> [INFO] [INFO] Skipping plugin execution (cached): failsafe:integration-test
> [INFO] [INFO] Skipping plugin execution (cached): failsafe:verify
> [INFO] [INFO]
> [INFO] [INFO] --- install:3.1.1:install (default-install) @ mectagcore ---
> [INFO] role: 'org.apache.maven.plugin.Mojo', implementation: 
> 'org.apache.maven.plugins.install.InstallMojo', role hint: 
> 'org.apache.maven.plugins:maven-install-plugin:3.1.1:install'
> [INFO] role: 'org.apache.maven.plugin.Mojo', implementation: 
> 'org.apache.maven.plugins.install.InstallFileMojo', role hint: 
> '

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

[Javier Gómez]

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.zwe can observe a strange behavior when maven is 
launching the release:perform goal, we see that the deploy goal is 
executed 2 times for each artifact (in fact it seems that the maven 
lifecycle restarts, once it reaches the deploy and begins to execute the 
validate again) and when it reaches the 2nd execution of deploy, it 
fails (since the user we use do not have permissions to overwrite 
artifacts). Below I show an extract from the log:


...

[INFO] [INFO] 


[INFO] [INFO] Reactor Build Order:
[INFO] [INFO]
[INFO] [INFO] temp.mectagcore:mectagcore [pom]
[INFO] [INFO] temp.mectagcore:mectagcore-domain [jar]
[INFO] [INFO] temp.mectagcore:mectagcore-boot [jar]
[INFO] [INFO] temp.mectagcore:jacoco-report-aggregate [pom]
[INFO] [INFO]
[INFO] [INFO] -< temp.mectagcore:mectagcore 
>-
[INFO] [INFO] Building temp.mectagcore:mectagcore 1.0.0  
[1/9]

[INFO] [INFO]   from pom.xml
[INFO] [INFO] [ pom 
]-
[INFO] [INFO] Going to calculate checksum for project 
[groupId=temp.mectagcore, artifactId=mectagcore]
[INFO] [INFO] Project inputs calculated in 12 ms. SHA-256 checksum 
[16534757c14aae9b1ff1961664995f0e7e9396fb88309d207a8a23c080c7f661] 
calculated in 4 ms.
[INFO] [INFO] Attempting to restore project temp.mectagcore:mectagcore 
from build cache
[INFO] [INFO] Local build found by checksum 
16534757c14aae9b1ff1961664995f0e7e9396fb88309d207a8a23c080c7f661
[INFO] [INFO] Found cached build, restoring temp.mectagcore:mectagcore 
from cache by checksum 
16534757c14aae9b1ff1961664995f0e7e9396fb88309d207a8a23c080c7f661
[INFO] [INFO] Project temp.mectagcore:mectagcore restored partially. 
Highest cached goal: verify, requested: deploy
[INFO] role: 'org.apache.maven.plugin.Mojo', implementation: 
'org.apache.maven.plugin.failsafe.IntegrationTestMojo', role hint: 
'org.apache.maven.plugins:maven-failsafe-plugin:3.0.0:integration-test'
[INFO] role: 'org.apache.maven.plugin.Mojo', implementation: 
'org.apache.maven.plugin.failsafe.VerifyMojo', role hint: 
'org.apache.maven.plugins:maven-failsafe-plugin:3.0.0:verify'

[INFO] ---
[INFO] [INFO] Skipping plugin execution (cached): enforcer:enforce
[INFO] [INFO] Skipping plugin execution (cached): enforcer:enforce
[INFO] [INFO] Skipping plugin execution (cached): build-helper:add-source
[INFO] [INFO] Mojo execution is forced by project property: 
amiga-assembly:amiga-assembly

[INFO] [INFO]
[INFO] [INFO] --- amiga-assembly:5.5.0:amiga-assembly 
(amiga-assembly-execution) @ mectagcore ---
[INFO] [INFO] Mojo execution is forced by project property: 
source:jar-no-fork

[INFO] [INFO]
[INFO] [INFO] --- source:3.2.1:jar-no-fork (attach-sources) @ mectagcore ---
[INFO] [INFO] Skipping plugin execution (cached): failsafe:integration-test
[INFO] [INFO] Skipping plugin execution (cached): failsafe:verify
[INFO] [INFO]
[INFO] [INFO] --- install:3.1.1:install (default-install) @ mectagcore ---
[INFO] role: 'org.apache.maven.plugin.Mojo', implementation: 
'org.apache.maven.plugins.install.InstallMojo', role hint: 
'org.apache.maven.plugins:maven-install-plugin:3.1.1:install'
[INFO] role: 'org.apache.maven.plugin.Mojo', implementation: 
'org.apache.maven.plugins.install.InstallFileMojo', role hint: 
'org.apache.maven.plugins:maven-install-plugin:3.1.1:install-file'

[INFO] ---
[INFO] [INFO] Installing 
/tmp/mic-mectagcore/code/target/checkout/code/pom.xml to 
/home/alambike/.m2/repository/temp/mectagcore/mectagcore/1.0.0/mectagcore-1.0.0.pom

[INFO] [INFO]
[INFO] [INFO] --- deploy:3.1.1:deploy (default-deploy) @ mectagcore ---
[INFO] role: 'org.apache.maven.plugin.Mojo', implementation: 
'org.apache.maven.plugins.deploy.DeployFileMojo', role hint: 
'org.apache.maven.plugins:maven-deploy-plugin:3.1.1:deploy-file'
[INFO] role: 'org.apache.maven.plugin.Mojo', implementation: 
'org.apache.maven.plugins.maven_deploy_plugin.HelpMojo', role hint: 
'org.apache.maven.plugins:maven-deploy-plugin:3.1.1:help'

[INFO] ---
[INFO] [INFO] Uploading to maven-artifacts: 
https://xxx.jf

ANN] Apache Maven Release Plugin 3.0.1 Released

[Slawomir Jaranowski]

The Apache Maven team is pleased to announce the release of the Apache
Maven Release Plugin, version 3.0.1

https://maven.apache.org/maven-release/maven-release-plugin/

You should specify the version in your project's plugin configuration:


  org.apache.maven.plugins
  maven-release-plugin
  3.0.1


You can download the appropriate sources etc. from the download page:

https://maven.apache.org/maven-release/download.html

Release Notes - Maven Release Plugin - Version 3.0.1

** Bug
* [MRELEASE-851] - javaHome parameter is ignored and inherited
unexpectedly
* [MRELEASE-1103] - Decryption of server password in settings.xml
failed (works with 2.5.3)
* [MRELEASE-1114] - Broken interaction of maven-gpg-plugin with Gpg4win
Kleopatra since 3.0.0-M6
* [MRELEASE-1123] - Maven Release plugin doesn't work in maven 4

** Improvement
* [MRELEASE-1120] - Upgrade surefire version to 3.0.0
* [MRELEASE-1122] - add plugin's system requirements history

** Task
* [MRELEASE-1127] - Refresh download page

** Dependency upgrade
* [MRELEASE-1121] - Bump maven-shared-utils from 3.3.4 to 3.4.2

Enjoy,

-The Apache Maven team

[RSEULT] [VOTE] Release Apache Maven Release Plugin version 3.0.1

[Slawomir Jaranowski]

Hi,

The vote has passed with the following result:

+1: Herve Boutemy, Sylwester Lachiewicz, Maarten Mulders, Tamás Cservenák,
Guillaume Nodet, Olivier Lamy, Karl Heinz Marbaise

PMC quorum: reached

I will promote the source release zip file to Apache distribution area and
the artifacts to the central repo.

-- 
Sławomir Jaranowski

Re: [VOTE] Release Apache Maven Release Plugin version 3.0.1

[Karl Heinz Marbaise]

Hi,

+1 from me,

Kind regards
Karl Heinz Marbaisew
On 30.05.23 23:34, Slawomir Jaranowski wrote:

Hi,

We solved 8 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824=12353136

There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRELEASE%20AND%20resolution%20%3D%20Unresolved


Staging repo:
https://repository.apache.org/content/repositories/maven-1950/
https://repository.apache.org/content/repositories/maven-1950/org/apache/maven/release/maven-release/3.0.1/maven-release-3.0.1-source-release.zip

Source release checksum(s):
maven-release-3.0.1-source-release.zip - SHA-512:
e59018a70e67f8af38f4d02bc28703f54ec01d032bd9d21972d087bb196ed8997040da0600a687d5604ebed794ab444d67b697ae17f793f0e8908a4ca0a37f69


Staging site:
https://maven.apache.org/components/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



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

Re: [VOTE] Release Apache Maven Release Plugin version 3.0.1

[Olivier Lamy]

+1

On Wed, 31 May 2023 at 07:35, Slawomir Jaranowski
 wrote:
>
> Hi,
>
> We solved 8 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824=12353136
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRELEASE%20AND%20resolution%20%3D%20Unresolved
>
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1950/
> https://repository.apache.org/content/repositories/maven-1950/org/apache/maven/release/maven-release/3.0.1/maven-release-3.0.1-source-release.zip
>
> Source release checksum(s):
> maven-release-3.0.1-source-release.zip - SHA-512:
> e59018a70e67f8af38f4d02bc28703f54ec01d032bd9d21972d087bb196ed8997040da0600a687d5604ebed794ab444d67b697ae17f793f0e8908a4ca0a37f69
>
>
> Staging site:
> https://maven.apache.org/components/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
>
> --
> Sławomir Jaranowski

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

Re: [VOTE] Release Apache Maven Release Plugin version 3.0.1

[Guillaume Nodet]

+1

Le mar. 30 mai 2023 à 23:35, Slawomir Jaranowski  a
écrit :

> Hi,
>
> We solved 8 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824=12353136
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRELEASE%20AND%20resolution%20%3D%20Unresolved
>
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1950/
>
> https://repository.apache.org/content/repositories/maven-1950/org/apache/maven/release/maven-release/3.0.1/maven-release-3.0.1-source-release.zip
>
> Source release checksum(s):
> maven-release-3.0.1-source-release.zip - SHA-512:
>
> e59018a70e67f8af38f4d02bc28703f54ec01d032bd9d21972d087bb196ed8997040da0600a687d5604ebed794ab444d67b697ae17f793f0e8908a4ca0a37f69
>
>
> Staging site:
>
> https://maven.apache.org/components/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
>
> --
> Sławomir Jaranowski
>


-- 

Guillaume Nodet

Re: [VOTE] Release Apache Maven Release Plugin version 3.0.1

[Jeremy Landis]

Renovate is a better alternative to dependabot and usually finds items deeper 
in builds such as IT tests with basically zero config and a nice issue tracker 
right on github showing full content of repo, anything team declined, etc.  If 
you happen to check out mybatis repos, you can see it in action.  Dependabot 
for security alerts will still work behind scenes otherwise.

Sent from my Verizon, Samsung Galaxy smartphone
Get Outlook for Android<https://aka.ms/AAb9ysg>

From: Elliotte Rusty Harold 
Sent: Wednesday, May 31, 2023 7:33:47 AM
To: Maven Developers List 
Subject: Re: [VOTE] Release Apache Maven Release Plugin version 3.0.1

FYI, there seem to be some issues with dependabot configs. It's useful
when it fires, but it doesn't always, and sometimes it closes update
PRs for no valid reason I can discern.

And of course there are the more complex updates that can require more
than a simple number change in a pom.xml like
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fmaven-surefire%2Fpull%2F652=05%7C01%7C%7C3a3db68483ab49c23c2908db61cb1b66%7C84df9e7fe9f640afb435%7C1%7C0%7C638211297190092716%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=AQO3sJzqStxUXB8SyqhxQQRoWoFxoDur46p0TpynxOo%3D=0<https://github.com/apache/maven-surefire/pull/652>
 which I still
haven't fully debugged

On Wed, May 31, 2023 at 11:25 AM Jeremy Landis  wrote:
>
> Common thread I keep seeing.  Update all the libraries!  ...the common 
> thread..   No concern on this one but maven does still release vulnerable 
> plugin usage especially around transient commons collections.  We keep 
> patching so it's also frustrating the speed of plugin releases that are not 
> accounting for already available pull requests only to see core team make 
> this argument each release recently...
>
> I think in general, same I tell my devs. Review the bot pull requests and 
> incorporate all the ones possible before any release.
>
> Sent from my Verizon, Samsung Galaxy smartphone
> Get Outlook for 
> Android<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Faka.ms%2FAAb9ysg=05%7C01%7C%7C3a3db68483ab49c23c2908db61cb1b66%7C84df9e7fe9f640afb435%7C1%7C0%7C638211297190092716%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=4E9vKXjn4Lcb7bg3v9lJp%2BZj3nzRDunBQ%2B0H%2FeOY3ZY%3D=0<https://aka.ms/AAb9ysg>>
> 
> From: Elliotte Rusty Harold 
> Sent: Wednesday, May 31, 2023 7:09:22 AM
> To: Maven Developers List 
> Subject: Re: [VOTE] Release Apache Maven Release Plugin version 3.0.1
>
> One minor dependency update to maven-scm:
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fmaven-release%2Fpull%2F192=05%7C01%7C%7C3a3db68483ab49c23c2908db61cb1b66%7C84df9e7fe9f640afb435%7C1%7C0%7C638211297190092716%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=bYhPHbuMm%2BtJho7sSqf0ce4fB0N%2Bc%2Bn8ngEFSs2PEHY%3D=0<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fmaven-release%2Fpull%2F192=05%7C01%7C%7C3a3db68483ab49c23c2908db61cb1b66%7C84df9e7fe9f640afb435%7C1%7C0%7C638211297190092716%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=bYhPHbuMm%2BtJho7sSqf0ce4fB0N%2Bc%2Bn8ngEFSs2PEHY%3D=0><https://github.com/apache/maven-release/pull/192>
>
> Otherwise, looks good.
>
> On Tue, May 30, 2023 at 9:35 PM Slawomir Jaranowski
>  wrote:
> >
> > Hi,
> >
> > We solved 8 issues:
> > https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fsecure%2FReleaseNote.jspa%3FprojectId%3D12317824%26version%3D12353136=05%7C01%7C%7C3a3db68483ab49c23c2908db61cb1b66%7C84df9e7fe9f640afb435%7C1%7C0%7C638211297190092716%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=J8pRnyjaXcpmbcIS4ESCKc5OR%2FBWUSOEIEIPBaFbFFU%3D=0<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fsecure%2FReleaseNote.jspa%3FprojectId%3D12317824%26version%3D12353136=05%7C01%7C%7C3a3db68483ab49c23c2908db61cb1b66%7C84df9e7fe9f640afb435%7C1%7C0%7C638211297190092716%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=J8pRnyjaXcpmbcIS4ESCKc5OR%2FBWUSOEIEIPBaFbFFU%3D=0><https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824=12353136>
> >
> > There are still a couple of issues left in JIRA:
> > https://na01.safelinks.protection.outlook.com/?url=https%

Re: [VOTE] Release Apache Maven Release Plugin version 3.0.1

[Elliotte Rusty Harold]

FYI, there seem to be some issues with dependabot configs. It's useful
when it fires, but it doesn't always, and sometimes it closes update
PRs for no valid reason I can discern.

And of course there are the more complex updates that can require more
than a simple number change in a pom.xml like
https://github.com/apache/maven-surefire/pull/652 which I still
haven't fully debugged

On Wed, May 31, 2023 at 11:25 AM Jeremy Landis  wrote:
>
> Common thread I keep seeing.  Update all the libraries!  ...the common 
> thread..   No concern on this one but maven does still release vulnerable 
> plugin usage especially around transient commons collections.  We keep 
> patching so it's also frustrating the speed of plugin releases that are not 
> accounting for already available pull requests only to see core team make 
> this argument each release recently...
>
> I think in general, same I tell my devs. Review the bot pull requests and 
> incorporate all the ones possible before any release.
>
> Sent from my Verizon, Samsung Galaxy smartphone
> Get Outlook for Android<https://aka.ms/AAb9ysg>
> 
> From: Elliotte Rusty Harold 
> Sent: Wednesday, May 31, 2023 7:09:22 AM
> To: Maven Developers List 
> Subject: Re: [VOTE] Release Apache Maven Release Plugin version 3.0.1
>
> One minor dependency update to maven-scm:
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fmaven-release%2Fpull%2F192=05%7C01%7C%7Cd62172d30703417bea4008db61c7aba5%7C84df9e7fe9f640afb435%7C1%7C0%7C638211282439154797%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=N%2B3ESphp2RdNQUw0Lmr1s41MrdDcFVth7rpvJJCVxjM%3D=0<https://github.com/apache/maven-release/pull/192>
>
> Otherwise, looks good.
>
> On Tue, May 30, 2023 at 9:35 PM Slawomir Jaranowski
>  wrote:
> >
> > Hi,
> >
> > We solved 8 issues:
> > https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fsecure%2FReleaseNote.jspa%3FprojectId%3D12317824%26version%3D12353136=05%7C01%7C%7Cd62172d30703417bea4008db61c7aba5%7C84df9e7fe9f640afb435%7C1%7C0%7C638211282439154797%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=K0PqT3u1i%2BnCyjtXTFaeS5B%2Bf%2FkYtZbCuQGaZLHIANY%3D=0<https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824=12353136>
> >
> > There are still a couple of issues left in JIRA:
> > https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fissues%2F%3Fjql%3Dproject%2520%253D%2520MRELEASE%2520AND%2520resolution%2520%253D%2520Unresolved=05%7C01%7C%7Cd62172d30703417bea4008db61c7aba5%7C84df9e7fe9f640afb435%7C1%7C0%7C638211282439154797%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=oWlIcdjMAesuCqZJji1g38cVL8mo8rTo47TjNZrdzQw%3D=0<https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRELEASE%20AND%20resolution%20%3D%20Unresolved>
> >
> >
> > Staging repo:
> > https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fmaven-1950%2F=05%7C01%7C%7Cd62172d30703417bea4008db61c7aba5%7C84df9e7fe9f640afb435%7C1%7C0%7C638211282439154797%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=lvgqlqCAjzalGHn96QSFkchLbh5MyTU9c8Cyo4B%2BN08%3D=0<https://repository.apache.org/content/repositories/maven-1950/>
> > https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fmaven-1950%2Forg%2Fapache%2Fmaven%2Frelease%2Fmaven-release%2F3.0.1%2Fmaven-release-3.0.1-source-release.zip=05%7C01%7C%7Cd62172d30703417bea4008db61c7aba5%7C84df9e7fe9f640afb435%7C1%7C0%7C638211282439154797%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=YTkPBYdoTpceNk8Zxy296APUndozmceHfzQ7NwzcThg%3D=0<https://repository.apache.org/content/repositories/maven-1950/org/apache/maven/release/maven-release/3.0.1/maven-release-3.0.1-source-release.zip>
> >
> > Source release checksum(s):
> > maven-release-3.0.1-source-release.zip - SHA-512:
> > e59018a70e67f8af38f4d02bc28703f54ec01d032bd9d21972d087bb196ed8997040da0600a687d5604ebed794ab444d67b697ae17f793f0e8908a4ca0a37f69
> >
> >
> > Staging site:
> > https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmaven.apache.org%2Fcomponents%2Fmaven-release-archives%2Fmaven-release-LATEST=05%7C01%7C%7Cd62172d30703417bea4008db61c7aba5%7C84df9e7fe9f640afb435%7C1%7C0%7C638211282439154797%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoi

Re: [VOTE] Release Apache Maven Release Plugin version 3.0.1

[Jeremy Landis]

Common thread I keep seeing.  Update all the libraries!  ...the common thread.. 
  No concern on this one but maven does still release vulnerable plugin usage 
especially around transient commons collections.  We keep patching so it's also 
frustrating the speed of plugin releases that are not accounting for already 
available pull requests only to see core team make this argument each release 
recently...

I think in general, same I tell my devs. Review the bot pull requests and 
incorporate all the ones possible before any release.

Sent from my Verizon, Samsung Galaxy smartphone
Get Outlook for Android<https://aka.ms/AAb9ysg>

From: Elliotte Rusty Harold 
Sent: Wednesday, May 31, 2023 7:09:22 AM
To: Maven Developers List 
Subject: Re: [VOTE] Release Apache Maven Release Plugin version 3.0.1

One minor dependency update to maven-scm:
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fmaven-release%2Fpull%2F192=05%7C01%7C%7Cd62172d30703417bea4008db61c7aba5%7C84df9e7fe9f640afb435%7C1%7C0%7C638211282439154797%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=N%2B3ESphp2RdNQUw0Lmr1s41MrdDcFVth7rpvJJCVxjM%3D=0<https://github.com/apache/maven-release/pull/192>

Otherwise, looks good.

On Tue, May 30, 2023 at 9:35 PM Slawomir Jaranowski
 wrote:
>
> Hi,
>
> We solved 8 issues:
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fsecure%2FReleaseNote.jspa%3FprojectId%3D12317824%26version%3D12353136=05%7C01%7C%7Cd62172d30703417bea4008db61c7aba5%7C84df9e7fe9f640afb435%7C1%7C0%7C638211282439154797%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=K0PqT3u1i%2BnCyjtXTFaeS5B%2Bf%2FkYtZbCuQGaZLHIANY%3D=0<https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824=12353136>
>
> There are still a couple of issues left in JIRA:
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fissues%2F%3Fjql%3Dproject%2520%253D%2520MRELEASE%2520AND%2520resolution%2520%253D%2520Unresolved=05%7C01%7C%7Cd62172d30703417bea4008db61c7aba5%7C84df9e7fe9f640afb435%7C1%7C0%7C638211282439154797%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=oWlIcdjMAesuCqZJji1g38cVL8mo8rTo47TjNZrdzQw%3D=0<https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRELEASE%20AND%20resolution%20%3D%20Unresolved>
>
>
> Staging repo:
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fmaven-1950%2F=05%7C01%7C%7Cd62172d30703417bea4008db61c7aba5%7C84df9e7fe9f640afb435%7C1%7C0%7C638211282439154797%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=lvgqlqCAjzalGHn96QSFkchLbh5MyTU9c8Cyo4B%2BN08%3D=0<https://repository.apache.org/content/repositories/maven-1950/>
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Fmaven-1950%2Forg%2Fapache%2Fmaven%2Frelease%2Fmaven-release%2F3.0.1%2Fmaven-release-3.0.1-source-release.zip=05%7C01%7C%7Cd62172d30703417bea4008db61c7aba5%7C84df9e7fe9f640afb435%7C1%7C0%7C638211282439154797%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=YTkPBYdoTpceNk8Zxy296APUndozmceHfzQ7NwzcThg%3D=0<https://repository.apache.org/content/repositories/maven-1950/org/apache/maven/release/maven-release/3.0.1/maven-release-3.0.1-source-release.zip>
>
> Source release checksum(s):
> maven-release-3.0.1-source-release.zip - SHA-512:
> e59018a70e67f8af38f4d02bc28703f54ec01d032bd9d21972d087bb196ed8997040da0600a687d5604ebed794ab444d67b697ae17f793f0e8908a4ca0a37f69
>
>
> Staging site:
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmaven.apache.org%2Fcomponents%2Fmaven-release-archives%2Fmaven-release-LATEST=05%7C01%7C%7Cd62172d30703417bea4008db61c7aba5%7C84df9e7fe9f640afb435%7C1%7C0%7C638211282439154797%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=cJSBpS5K1UcmitC%2BlKYuqZpDjOGm%2F4LJ5bc8Fi9tb20%3D=0<https://maven.apache.org/components/maven-release-archives/maven-release-LATEST>
>
> 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%7Cd62172d30703417bea4008db61c7aba5%7C84df9e7fe9f640afb435%7C1%7C0%7C638211282439154797%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=UQgW4ZDiIOZp16XxdvpWvoYu4eBXRxbTOLH4ZcYRQnQ%3D=0<https://maven.apache.

Re: [VOTE] Release Apache Maven Release Plugin version 3.0.1

[Elliotte Rusty Harold]

One minor dependency update to maven-scm:
https://github.com/apache/maven-release/pull/192

Otherwise, looks good.

On Tue, May 30, 2023 at 9:35 PM Slawomir Jaranowski
 wrote:
>
> Hi,
>
> We solved 8 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824=12353136
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRELEASE%20AND%20resolution%20%3D%20Unresolved
>
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1950/
> https://repository.apache.org/content/repositories/maven-1950/org/apache/maven/release/maven-release/3.0.1/maven-release-3.0.1-source-release.zip
>
> Source release checksum(s):
> maven-release-3.0.1-source-release.zip - SHA-512:
> e59018a70e67f8af38f4d02bc28703f54ec01d032bd9d21972d087bb196ed8997040da0600a687d5604ebed794ab444d67b697ae17f793f0e8908a4ca0a37f69
>
>
> Staging site:
> https://maven.apache.org/components/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
>
> --
> 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 Release Plugin version 3.0.1

[Tamás Cservenák]

+1

On Tue, May 30, 2023 at 11:35 PM Slawomir Jaranowski 
wrote:

> Hi,
>
> We solved 8 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824=12353136
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRELEASE%20AND%20resolution%20%3D%20Unresolved
>
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1950/
>
> https://repository.apache.org/content/repositories/maven-1950/org/apache/maven/release/maven-release/3.0.1/maven-release-3.0.1-source-release.zip
>
> Source release checksum(s):
> maven-release-3.0.1-source-release.zip - SHA-512:
>
> e59018a70e67f8af38f4d02bc28703f54ec01d032bd9d21972d087bb196ed8997040da0600a687d5604ebed794ab444d67b697ae17f793f0e8908a4ca0a37f69
>
>
> Staging site:
>
> https://maven.apache.org/components/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
>
> --
> Sławomir Jaranowski
>

Re: [VOTE] Release Apache Maven Release Plugin version 3.0.1

[Maarten Mulders]

+1 - tested on macOS using Maven 3.9.2 with a custom release strategy.


Maarten

On 30/05/2023 23:34, Slawomir Jaranowski wrote:

Hi,

We solved 8 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824=12353136

There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRELEASE%20AND%20resolution%20%3D%20Unresolved


Staging repo:
https://repository.apache.org/content/repositories/maven-1950/
https://repository.apache.org/content/repositories/maven-1950/org/apache/maven/release/maven-release/3.0.1/maven-release-3.0.1-source-release.zip

Source release checksum(s):
maven-release-3.0.1-source-release.zip - SHA-512:
e59018a70e67f8af38f4d02bc28703f54ec01d032bd9d21972d087bb196ed8997040da0600a687d5604ebed794ab444d67b697ae17f793f0e8908a4ca0a37f69


Staging site:
https://maven.apache.org/components/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



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

Re: [VOTE] Release Apache Maven Release Plugin version 3.0.1

[Sylwester Lachiewicz]

+1

wt., 30 maj 2023, 23:35 użytkownik Slawomir Jaranowski <
s.jaranow...@gmail.com> napisał:

> Hi,
>
> We solved 8 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824=12353136
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRELEASE%20AND%20resolution%20%3D%20Unresolved
>
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1950/
>
> https://repository.apache.org/content/repositories/maven-1950/org/apache/maven/release/maven-release/3.0.1/maven-release-3.0.1-source-release.zip
>
> Source release checksum(s):
> maven-release-3.0.1-source-release.zip - SHA-512:
>
> e59018a70e67f8af38f4d02bc28703f54ec01d032bd9d21972d087bb196ed8997040da0600a687d5604ebed794ab444d67b697ae17f793f0e8908a4ca0a37f69
>
>
> Staging site:
>
> https://maven.apache.org/components/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
>
> --
> Sławomir Jaranowski
>

Re: [VOTE] Release Apache Maven Release Plugin version 3.0.1

[Herve Boutemy]

+1

Reproducible Builds ok: reference build done with JDK 17 on *nix

Regards,

Hervé

On 2023/05/30 21:34:37 Slawomir Jaranowski wrote:
> Hi,
> 
> We solved 8 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824=12353136
> 
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRELEASE%20AND%20resolution%20%3D%20Unresolved
> 
> 
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1950/
> https://repository.apache.org/content/repositories/maven-1950/org/apache/maven/release/maven-release/3.0.1/maven-release-3.0.1-source-release.zip
> 
> Source release checksum(s):
> maven-release-3.0.1-source-release.zip - SHA-512:
> e59018a70e67f8af38f4d02bc28703f54ec01d032bd9d21972d087bb196ed8997040da0600a687d5604ebed794ab444d67b697ae17f793f0e8908a4ca0a37f69
> 
> 
> Staging site:
> https://maven.apache.org/components/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
> 
> -- 
> Sławomir Jaranowski
> 

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

[VOTE] Release Apache Maven Release Plugin version 3.0.1

[Slawomir Jaranowski]

Hi,

We solved 8 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824=12353136

There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRELEASE%20AND%20resolution%20%3D%20Unresolved


Staging repo:
https://repository.apache.org/content/repositories/maven-1950/
https://repository.apache.org/content/repositories/maven-1950/org/apache/maven/release/maven-release/3.0.1/maven-release-3.0.1-source-release.zip

Source release checksum(s):
maven-release-3.0.1-source-release.zip - SHA-512:
e59018a70e67f8af38f4d02bc28703f54ec01d032bd9d21972d087bb196ed8997040da0600a687d5604ebed794ab444d67b697ae17f793f0e8908a4ca0a37f69


Staging site:
https://maven.apache.org/components/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

-- 
Sławomir Jaranowski

Re: Maven Release Plugin - Reopen MRELEASE-282

[Slawomir Jaranowski]

Hi,

Reopened. PR are welcome.

pt., 17 cze 2022 o 18:08 Pablo Caraballo Llorente 
napisał(a):

> Hello.
>
> As a user of the maven-release-plugin, I find that the issue MRELEASE-282
> <https://issues.apache.org/jira/browse/MRELEASE-282> is an improvement
> that
> would be useful to improve the configuration of the prepare and perform
> goals.
>
> In my specific case, I cannot configure different arguments for each goal
> given that both share the same property, and that the 1st one generates a
> release.properties file that overrides the configuration set in the pom
> file. Even more specifically, I would like to skip the tests compilation
> and execution during the perform goal, as this job is already done in the
> preparation, and adds a lot of overhead to the release pipeline
> (configuring the specific goals to run in the perform isn't suitable, as
> they may vary at any point).
>
> If you are aware of a better way of doing this rather than implementing the
> feature, please let me know. If that is the case, maybe it's worth
> mentioning it in the documentation site.
>
> Thanks and sorry for the noise.
>


-- 
Sławomir Jaranowski

Maven Release Plugin - Reopen MRELEASE-282

[Pablo Caraballo Llorente]

Hello.

As a user of the maven-release-plugin, I find that the issue MRELEASE-282
<https://issues.apache.org/jira/browse/MRELEASE-282> is an improvement that
would be useful to improve the configuration of the prepare and perform
goals.

In my specific case, I cannot configure different arguments for each goal
given that both share the same property, and that the 1st one generates a
release.properties file that overrides the configuration set in the pom
file. Even more specifically, I would like to skip the tests compilation
and execution during the perform goal, as this job is already done in the
preparation, and adds a lot of overhead to the release pipeline
(configuring the specific goals to run in the perform isn't suitable, as
they may vary at any point).

If you are aware of a better way of doing this rather than implementing the
feature, please let me know. If that is the case, maybe it's worth
mentioning it in the documentation site.

Thanks and sorry for the noise.

Re: Maven Release Plugin 3.0.0-M6

[Michael Osipov]

Guys,

let me know when you are done with all issues for M6, I will happily do 
the release for the community.


M

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

Re: Maven Release Plugin 3.0.0-M6

[Hervé BOUTEMY]

MRELEASE-1087 is a massive cleanup in terms of quantity of code, but it's not 
really functional changes: just get rid of old Plexus APIs and associated 
tricks to make our life easier. I'm confident our ITs would catch issues at 
that level.

on my own side, having feedback on 
https://maven.apache.org/maven-release-archives/maven-release-LATEST/maven-release-plugin/upgrade.html
 would be nice

yes, let's focus and do the release soon

Le vendredi 6 mai 2022, 04:05:15 CEST Olivier Lamy a écrit :
> Nice it looks like the call for release suddenly generates a lot of
> activity for this plugin :)
> but how long will it take to get all those issues done?
> Because at the start it was just a bug fix release and now we have a lot of
> changes coming.
> Can we just cut a release and then look after all of those other changes?
> because this one looks very massive change...
> https://issues.apache.org/jira/browse/MRELEASE-1087
> 
> On Thu, 5 May 2022 at 20:56, Karl Heinz Marbaise  wrote:
> > Hi,
> > 
> > I would like to enhance the list with this one:
> > 
> > https://issues.apache.org/jira/browse/MRELEASE-1079
> > 
> > Kind regards
> > Karl Heinz Marbaise
> > 
> > On 05.05.22 08:37, Hervé BOUTEMY wrote:
> > > https://issues.apache.org/jira/projects/MRELEASE/versions/12351336
> > > 3 issues to finish:
> > > https://issues.apache.org/jira/browse/MRELEASE-955
> > > https://issues.apache.org/jira/browse/MRELEASE-1084
> > > https://issues.apache.org/jira/browse/MRELEASE-1087
> > > 
> > > Le mercredi 4 mai 2022, 14:51:21 CEST Samuel Le Berrigaud a écrit :
> > >> Hello,
> > >> 
> > >> any news on this? Without putting any pressure, I'd just like to be
> > >> able to tell whether I should wait a few days or whether I should plan
> > >> around having an M6.
> > >> 
> > >> Thanks,
> > >> SaM
> > >> 
> > >> On Tue, Apr 26, 2022 at 2:36 PM Olivier Lamy  wrote:
> > >>> Hi
> > >>> It looks there is a plan for early (ish) next week
> > >>> 
> > >>> cheers
> > >>> Olivier
> > >>> 
> > >>> On Tue, 26 Apr 2022 at 9:48 pm, Samuel Le Berrigaud <
> > 
> > s...@leberrigaud.org>
> > 
> > >>> wrote:
> > >>>> Hello devs,
> > >>>> 
> > >>>> I'd just like to get an idea of when a potential 3.0.0-M6 of the
> > >>>> maven-release-plugin might happen.
> > >>>> 
> > >>>> I've managed to contribute a bug fix MRELEASE-1022 (1). Thanks for
> > >>>> the
> > >>>> quick PR & merge. And now, obviously, I would love to be able to use
> > >>>> a
> > >>>> regular build of the plugin.
> > >>>> 
> > >>>> Thanks for your help,
> > >>>> SaM
> > >>>> 
> > >>>> (1) https://issues.apache.org/jira/browse/MRELEASE-1022
> > >>>> 
> > >>>> -
> > >>>> 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 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: Maven Release Plugin 3.0.0-M6

[Olivier Lamy]

Nice it looks like the call for release suddenly generates a lot of
activity for this plugin :)
but how long will it take to get all those issues done?
Because at the start it was just a bug fix release and now we have a lot of
changes coming.
Can we just cut a release and then look after all of those other changes?
because this one looks very massive change...
https://issues.apache.org/jira/browse/MRELEASE-1087


On Thu, 5 May 2022 at 20:56, Karl Heinz Marbaise  wrote:

> Hi,
>
> I would like to enhance the list with this one:
>
> https://issues.apache.org/jira/browse/MRELEASE-1079
>
> Kind regards
> Karl Heinz Marbaise
>
> On 05.05.22 08:37, Hervé BOUTEMY wrote:
> > https://issues.apache.org/jira/projects/MRELEASE/versions/12351336
> > 3 issues to finish:
> > https://issues.apache.org/jira/browse/MRELEASE-955
> > https://issues.apache.org/jira/browse/MRELEASE-1084
> > https://issues.apache.org/jira/browse/MRELEASE-1087
> >
> > Le mercredi 4 mai 2022, 14:51:21 CEST Samuel Le Berrigaud a écrit :
> >> Hello,
> >>
> >> any news on this? Without putting any pressure, I'd just like to be
> >> able to tell whether I should wait a few days or whether I should plan
> >> around having an M6.
> >>
> >> Thanks,
> >> SaM
> >>
> >> On Tue, Apr 26, 2022 at 2:36 PM Olivier Lamy  wrote:
> >>> Hi
> >>> It looks there is a plan for early (ish) next week
> >>>
> >>> cheers
> >>> Olivier
> >>>
> >>> On Tue, 26 Apr 2022 at 9:48 pm, Samuel Le Berrigaud <
> s...@leberrigaud.org>
> >>>
> >>> wrote:
> >>>> Hello devs,
> >>>>
> >>>> I'd just like to get an idea of when a potential 3.0.0-M6 of the
> >>>> maven-release-plugin might happen.
> >>>>
> >>>> I've managed to contribute a bug fix MRELEASE-1022 (1). Thanks for the
> >>>> quick PR & merge. And now, obviously, I would love to be able to use a
> >>>> regular build of the plugin.
> >>>>
> >>>> Thanks for your help,
> >>>> SaM
> >>>>
> >>>> (1) https://issues.apache.org/jira/browse/MRELEASE-1022
> >>>>
> >>>> -
> >>>> 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 commands, e-mail: dev-h...@maven.apache.org
>
>

Re: Maven Release Plugin 3.0.0-M6

[Karl Heinz Marbaise]

Hi,

I would like to enhance the list with this one:

https://issues.apache.org/jira/browse/MRELEASE-1079

Kind regards
Karl Heinz Marbaise

On 05.05.22 08:37, Hervé BOUTEMY wrote:

https://issues.apache.org/jira/projects/MRELEASE/versions/12351336
3 issues to finish:
https://issues.apache.org/jira/browse/MRELEASE-955
https://issues.apache.org/jira/browse/MRELEASE-1084
https://issues.apache.org/jira/browse/MRELEASE-1087

Le mercredi 4 mai 2022, 14:51:21 CEST Samuel Le Berrigaud a écrit :

Hello,

any news on this? Without putting any pressure, I'd just like to be
able to tell whether I should wait a few days or whether I should plan
around having an M6.

Thanks,
SaM

On Tue, Apr 26, 2022 at 2:36 PM Olivier Lamy  wrote:

Hi
It looks there is a plan for early (ish) next week

cheers
Olivier

On Tue, 26 Apr 2022 at 9:48 pm, Samuel Le Berrigaud 

wrote:

Hello devs,

I'd just like to get an idea of when a potential 3.0.0-M6 of the
maven-release-plugin might happen.

I've managed to contribute a bug fix MRELEASE-1022 (1). Thanks for the
quick PR & merge. And now, obviously, I would love to be able to use a
regular build of the plugin.

Thanks for your help,
SaM

(1) https://issues.apache.org/jira/browse/MRELEASE-1022

-
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 commands, e-mail: dev-h...@maven.apache.org

Re: Maven Release Plugin 3.0.0-M6

[Hervé BOUTEMY]

https://issues.apache.org/jira/projects/MRELEASE/versions/12351336
3 issues to finish:
https://issues.apache.org/jira/browse/MRELEASE-955
https://issues.apache.org/jira/browse/MRELEASE-1084
https://issues.apache.org/jira/browse/MRELEASE-1087

Le mercredi 4 mai 2022, 14:51:21 CEST Samuel Le Berrigaud a écrit :
> Hello,
> 
> any news on this? Without putting any pressure, I'd just like to be
> able to tell whether I should wait a few days or whether I should plan
> around having an M6.
> 
> Thanks,
> SaM
> 
> On Tue, Apr 26, 2022 at 2:36 PM Olivier Lamy  wrote:
> > Hi
> > It looks there is a plan for early (ish) next week
> > 
> > cheers
> > Olivier
> > 
> > On Tue, 26 Apr 2022 at 9:48 pm, Samuel Le Berrigaud 
> > 
> > wrote:
> > > Hello devs,
> > > 
> > > I'd just like to get an idea of when a potential 3.0.0-M6 of the
> > > maven-release-plugin might happen.
> > > 
> > > I've managed to contribute a bug fix MRELEASE-1022 (1). Thanks for the
> > > quick PR & merge. And now, obviously, I would love to be able to use a
> > > regular build of the plugin.
> > > 
> > > Thanks for your help,
> > > SaM
> > > 
> > > (1) https://issues.apache.org/jira/browse/MRELEASE-1022
> > > 
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > > For additional commands, e-mail: dev-h...@maven.apache.org
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org





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

Re: Maven Release Plugin 3.0.0-M6

[Samuel Le Berrigaud]

Hello,

any news on this? Without putting any pressure, I'd just like to be
able to tell whether I should wait a few days or whether I should plan
around having an M6.

Thanks,
SaM

On Tue, Apr 26, 2022 at 2:36 PM Olivier Lamy  wrote:
>
> Hi
> It looks there is a plan for early (ish) next week
>
> cheers
> Olivier
>
> On Tue, 26 Apr 2022 at 9:48 pm, Samuel Le Berrigaud 
> wrote:
>
> > Hello devs,
> >
> > I'd just like to get an idea of when a potential 3.0.0-M6 of the
> > maven-release-plugin might happen.
> >
> > I've managed to contribute a bug fix MRELEASE-1022 (1). Thanks for the
> > quick PR & merge. And now, obviously, I would love to be able to use a
> > regular build of the plugin.
> >
> > Thanks for your help,
> > SaM
> >
> > (1) https://issues.apache.org/jira/browse/MRELEASE-1022
> >
> > -
> > 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: Maven Release Plugin 3.0.0-M6

[Hervé BOUTEMY]

IIUC, the key aspect we need to solve to remove that milestone aspect is
https://issues.apache.org/jira/browse/MRELEASE-955 (and relatives)

if someone else knows other topics, please share, so we can focus

Regards,

Hervé

Le mardi 26 avril 2022, 21:14:39 CEST Jeff Jensen a écrit :
> M is for Milestone, an incremental release towards the eventual final
> release considered early production ready but incomplete for full planned
> features and implementation.
> 
> On Tue, Apr 26, 2022 at 2:10 PM Gary Gregory  wrote:
> > Can someone explain the M release meaning? Is it an alpha release? A beta
> > version? Is it production ready? Does it depend on the plugin (please say
> > no)?
> > 
> > Gary
> > 
> > On Tue, Apr 26, 2022, 07:49 Samuel Le Berrigaud 
> > 
> > wrote:
> > > Hello devs,
> > > 
> > > I'd just like to get an idea of when a potential 3.0.0-M6 of the
> > > maven-release-plugin might happen.
> > > 
> > > I've managed to contribute a bug fix MRELEASE-1022 (1). Thanks for the
> > > quick PR & merge. And now, obviously, I would love to be able to use a
> > > regular build of the plugin.
> > > 
> > > Thanks for your help,
> > > SaM
> > > 
> > > (1) https://issues.apache.org/jira/browse/MRELEASE-1022
> > > 
> > > -
> > > 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: Maven Release Plugin 3.0.0-M6

[Michael Osipov]

Am 2022-04-26 um 21:14 schrieb Jeff Jensen:

M is for Milestone, an incremental release towards the eventual final
release considered early production ready but incomplete for full planned
features and implementation.


To the point!

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

Re: Maven Release Plugin 3.0.0-M6

[Jeff Jensen]

M is for Milestone, an incremental release towards the eventual final
release considered early production ready but incomplete for full planned
features and implementation.


On Tue, Apr 26, 2022 at 2:10 PM Gary Gregory  wrote:

> Can someone explain the M release meaning? Is it an alpha release? A beta
> version? Is it production ready? Does it depend on the plugin (please say
> no)?
>
> Gary
>
> On Tue, Apr 26, 2022, 07:49 Samuel Le Berrigaud 
> wrote:
>
> > Hello devs,
> >
> > I'd just like to get an idea of when a potential 3.0.0-M6 of the
> > maven-release-plugin might happen.
> >
> > I've managed to contribute a bug fix MRELEASE-1022 (1). Thanks for the
> > quick PR & merge. And now, obviously, I would love to be able to use a
> > regular build of the plugin.
> >
> > Thanks for your help,
> > SaM
> >
> > (1) https://issues.apache.org/jira/browse/MRELEASE-1022
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
> >
>

Re: Maven Release Plugin 3.0.0-M6

[Gary Gregory]

Can someone explain the M release meaning? Is it an alpha release? A beta
version? Is it production ready? Does it depend on the plugin (please say
no)?

Gary

On Tue, Apr 26, 2022, 07:49 Samuel Le Berrigaud  wrote:

> Hello devs,
>
> I'd just like to get an idea of when a potential 3.0.0-M6 of the
> maven-release-plugin might happen.
>
> I've managed to contribute a bug fix MRELEASE-1022 (1). Thanks for the
> quick PR & merge. And now, obviously, I would love to be able to use a
> regular build of the plugin.
>
> Thanks for your help,
> SaM
>
> (1) https://issues.apache.org/jira/browse/MRELEASE-1022
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: Maven Release Plugin 3.0.0-M6

[Olivier Lamy]

Hi
It looks there is a plan for early (ish) next week

cheers
Olivier

On Tue, 26 Apr 2022 at 9:48 pm, Samuel Le Berrigaud 
wrote:

> Hello devs,
>
> I'd just like to get an idea of when a potential 3.0.0-M6 of the
> maven-release-plugin might happen.
>
> I've managed to contribute a bug fix MRELEASE-1022 (1). Thanks for the
> quick PR & merge. And now, obviously, I would love to be able to use a
> regular build of the plugin.
>
> Thanks for your help,
> SaM
>
> (1) https://issues.apache.org/jira/browse/MRELEASE-1022
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Maven Release Plugin 3.0.0-M6

[Samuel Le Berrigaud]

Hello devs,

I'd just like to get an idea of when a potential 3.0.0-M6 of the
maven-release-plugin might happen.

I've managed to contribute a bug fix MRELEASE-1022 (1). Thanks for the
quick PR & merge. And now, obviously, I would love to be able to use a
regular build of the plugin.

Thanks for your help,
SaM

(1) https://issues.apache.org/jira/browse/MRELEASE-1022

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

Re: Conventional Commits with the maven-release-plugin

[Niels Basjes]

Yes ofcourse.

I have created the appropriate tickets and pull requests:

https://issues.apache.org/jira/browse/SCM-977
https://github.com/apache/maven-scm/pull/135

and

https://issues.apache.org/jira/browse/MRELEASE-1078
https://github.com/apache/maven-release/pull/104

This second pull request still has some rough edges:
- The config is not as clean as I would have liked it to be. I would have
liked to extend the XML schema for the configuration but because this is
really a plugin for a maven plugin I have not yet been able to figure out
how to do this.
- Some of the IT tests fail at this point.
- I would like to provide documentation for the web site.

The custom config allows you to have
- a custom format of the SCM tag and the system can still find and parse it.
- a custom set of patterns to look for in the commit messages to determine
if a patch/minor/major update is needed. The default rules assume the tag
to be just the version (i.e. "1.2.3") and the patterns to follow my
understanding of https://www.conventionalcommits.org/en/v1.0.0/

A "full" example (copied from the IT test I created):


  org.apache.maven.plugins
  maven-release-plugin
  @project.version@
  
true
true

false
false

ci(Release): 
ci(Release): Version
@{releaseLabel}
v@{project.version}
CCSemVerVersionPolicy










  


  
  

  org.apache.maven.its.release
  maven-scm-provider-dummy
  1.0


  org.apache.maven.release
  maven-release-ccsemver-policy
  @project.version@

  






I'm looking forward to your feedback.

Niels

On Tue, Feb 15, 2022 at 10:00 PM Olivier Lamy  wrote:

> sounds an interesting idea.
> would you mind having this as PRs to ease code review?
>
> On Tue, 15 Feb 2022 at 03:00, Niels Basjes  wrote:
>
> > Hi,
> >
> > I would like to use the ideas from the Conventional Commits to
> > automatically determine the next version for my release when releasing
> with
> > the maven-release-plugin.
> >
> > Since this is not yet a part of the current version of the release
> plugin I
> > decided to give it a go myself.
> >
> > So far I have succeeded in creating a new VersionPolicy that does this
> and
> > I'm wondering if the committers would consider including this idea or
> not.
> > I expect my code will need some more cleanups and changes on my end
> before
> > it can be included.
> >
> > Summary of what I had to change to make this work:
> > In maven-scm (
> > https://github.com/nielsbasjes/maven-scm/tree/SCM-xxx-ChangelogTags )
> > - I had to add the functionality that a ChangeSet could contain the tags
> > present on the commits as well.
> >   It is generic and I've added this functionality for gitexe and jgit.
> >   For gitexe I had to change the command used by the changelog command to
> > get the tags.
> >
> > In maven-release (
> > https://github.com/nielsbasjes/maven-release/tree/MRELEASE-xxx-CCSEMVER
> )
> > - I extended the VersionPolicyRequest to include the connection to the
> SCM
> > and a config parameter (right now a String) to configure the patterns to
> > look for in the pom.xml of the project that is to be released.
> > - I created a new VersionPolicy that examines the tags and commit
> messages
> > and from this computes if a patch, minor or major version update is
> needed.
> >
> > To check it actually works I created a dummy test project that has this
> > plugin:
> > https://github.com/nielsbasjes/releasetester/blob/main/pom.xml#L94
> >
> > So simply put: Should I file two jira tickets and put up the pull
> requests
> > so you can review my ideas ?
> >
> > --
> > Best regards / Met vriendelijke groeten,
> >
> > Niels Basjes
> >
>


-- 
Best regards / Met vriendelijke groeten,

Niels Basjes

Re: Conventional Commits with the maven-release-plugin

[Olivier Lamy]

sounds an interesting idea.
would you mind having this as PRs to ease code review?

On Tue, 15 Feb 2022 at 03:00, Niels Basjes  wrote:

> Hi,
>
> I would like to use the ideas from the Conventional Commits to
> automatically determine the next version for my release when releasing with
> the maven-release-plugin.
>
> Since this is not yet a part of the current version of the release plugin I
> decided to give it a go myself.
>
> So far I have succeeded in creating a new VersionPolicy that does this and
> I'm wondering if the committers would consider including this idea or not.
> I expect my code will need some more cleanups and changes on my end before
> it can be included.
>
> Summary of what I had to change to make this work:
> In maven-scm (
> https://github.com/nielsbasjes/maven-scm/tree/SCM-xxx-ChangelogTags )
> - I had to add the functionality that a ChangeSet could contain the tags
> present on the commits as well.
>   It is generic and I've added this functionality for gitexe and jgit.
>   For gitexe I had to change the command used by the changelog command to
> get the tags.
>
> In maven-release (
> https://github.com/nielsbasjes/maven-release/tree/MRELEASE-xxx-CCSEMVER )
> - I extended the VersionPolicyRequest to include the connection to the SCM
> and a config parameter (right now a String) to configure the patterns to
> look for in the pom.xml of the project that is to be released.
> - I created a new VersionPolicy that examines the tags and commit messages
> and from this computes if a patch, minor or major version update is needed.
>
> To check it actually works I created a dummy test project that has this
> plugin:
> https://github.com/nielsbasjes/releasetester/blob/main/pom.xml#L94
>
> So simply put: Should I file two jira tickets and put up the pull requests
> so you can review my ideas ?
>
> --
> Best regards / Met vriendelijke groeten,
>
> Niels Basjes
>

Conventional Commits with the maven-release-plugin

[Niels Basjes]

Hi,

I would like to use the ideas from the Conventional Commits to
automatically determine the next version for my release when releasing with
the maven-release-plugin.

Since this is not yet a part of the current version of the release plugin I
decided to give it a go myself.

So far I have succeeded in creating a new VersionPolicy that does this and
I'm wondering if the committers would consider including this idea or not.
I expect my code will need some more cleanups and changes on my end before
it can be included.

Summary of what I had to change to make this work:
In maven-scm (
https://github.com/nielsbasjes/maven-scm/tree/SCM-xxx-ChangelogTags )
- I had to add the functionality that a ChangeSet could contain the tags
present on the commits as well.
  It is generic and I've added this functionality for gitexe and jgit.
  For gitexe I had to change the command used by the changelog command to
get the tags.

In maven-release (
https://github.com/nielsbasjes/maven-release/tree/MRELEASE-xxx-CCSEMVER )
- I extended the VersionPolicyRequest to include the connection to the SCM
and a config parameter (right now a String) to configure the patterns to
look for in the pom.xml of the project that is to be released.
- I created a new VersionPolicy that examines the tags and commit messages
and from this computes if a patch, minor or major version update is needed.

To check it actually works I created a dummy test project that has this
plugin:  https://github.com/nielsbasjes/releasetester/blob/main/pom.xml#L94

So simply put: Should I file two jira tickets and put up the pull requests
so you can review my ideas ?

-- 
Best regards / Met vriendelijke groeten,

Niels Basjes

[RESULT] [VOTE] Release Apache Maven Release Plugin version 3.0.0-M4

[Robert Scholte]

Hi,

The vote has passed with the following result:

+1 : Tibor Digana, Hervé BOUTEMY, Olivier Lamy, Sylwester Lachiewicz, Arnaud 
Héritier, Robert Scholte

PMC quorum: reached

I will promote the artifacts to the central repo.

On 12-4-2021 19:31:13, 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

Re: [VOTE] Release Apache Maven Release Plugin version 3.0.0-M4

[Rémy Sanlaville]

Great, thank you Hervé!

Regards,
Rémy

On Fri, Apr 16, 2021 at 7:25 AM Hervé BOUTEMY  wrote:

> thank you Remi
>
> PR merged and current release HTML tweaked [1] to benefit from the
> documentation  just now
>
> Regards,
>
> Hervé
>
>
> https://maven.apache.org/maven-release-archives/maven-release-LATEST/maven-release-plugin/examples/rollback-release.html
>
> Le jeudi 15 avril 2021, 22:38:05 CEST Rémy Sanlaville a écrit :
> > Hi Hervé,
> >
> > PR created (cf. https://github.com/apache/maven-release/pulls)
> >
> > Regards,
> > Rémy
> >
> > On Wed, Apr 14, 2021 at 1:28 PM Hervé BOUTEMY 
> wrote:
> > > please create the PR to have it merged
> > >
> > > and given it's documentation, we can eventually modify HTML by hand to
> > > have
> > > this nice little improvement in the current release documentation...
> > >
> > > Le mercredi 14 avril 2021, 09:36:52 CEST Rémy Sanlaville a écrit :
> > > > Hi Robert,
> > > >
> > > > I understand. I wasn't aware about
> > > > https://github.com/apache/maven-release/pulls
> > > >
> > > > I was just aware to edit the page as you asked me
> > > >
> > > > > There's an edit-button on the page (upper left in nav bar) that
> links
> > >
> > > to
> > >
> > >
> https://github.com/apache/maven-release/blob/maven-release-3.0.0-M1/maven
> > >
> > > > > -release-plugin/src/site/apt/examples/rollback-release.apt Would be
> > >
> > > great
> > >
> > > > > if you could help updating this page.
> > > > >
> > > > > Cf.
> > >
> > >
> https://mail-archives.apache.org/mod_mbox/maven-dev/202006.mbox/%3CMailbir
> > > d-> 3058d9d5-b625-4621-bd90-e20080d523ce%40apache.org%3E
> > >
> > > > Rémy
> > > >
> > > > On Tue, Apr 13, 2021 at 5:49 PM Robert Scholte  >
> > >
> > > wrote:
> > > > > Hi Rémy
> > > > >
> > > > > I don't see it as PR under
> > >
> > > https://github.com/apache/maven-release/pulls
> > >
> > > > > I did a quick scan over this list and the open Jira issues and
> decided
> > >
> > > not
> > >
> > > > > to add more to this milestone release.
> > > > >
> > > > > Robert
> > > > > On 13-4-2021 09:09:21, Rémy Sanlaville 
> > >
> > > wrote:
> > > > > Hi Robert,
> > > > >
> > > > > What about
> > >
> > >
> https://github.com/apache/maven-release/compare/master...sanlaville:patch-
> > > >
> > >
> > > > 1
> > > >
> > > > > ?
> > > > >
> > > > > Cf.
> > >
> > >
> https://mail-archives.apache.org/mod_mbox/maven-dev/202006.mbox/%3CCAK8JC1
> > >
> > > > > TqE3CAQbD%3DAC6p9%2BXtO9uk1kjRsVY9YctdVSmPeB7YWQ%40mail.gmail.com
> %3E
> > >
> > >
> https://mail-archives.apache.org/mod_mbox/maven-dev/202006.mbox/%3CMailbir
> > >
> > > > > d-3058d9d5-b625-4621-bd90-e20080d523ce%40apache.org%3E
> > > > >
> > > > > Rémy
> > > > >
> > > > > On Mon, Apr 12, 2021 at 7:31 PM Robert Scholte wrote:
> > > > > > Hi,
> > >
> > > > > > We solved 5 issues:
> > >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824;
> > >
> > > > > version=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%20
> > >
> > > > > DESC>
> > > > >
> > > > > > Staging repo:
> > > > > > https://repository.apache.org/content/repositories/maven-1639
> > >
> > >
> https://repository.apache.org/content/repositories/maven-1639/org/apache/m
> > >
> > >
> aven/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:
> > >
> 49ec8c495b11696671e83ccdeee3408223d0aef3cfd5f48e2a4afc66e225f550069a060702
> > >
> > > > > 205152e3e59238f9db64efd85ac626b25b05596be3ef422b991895>
> > > > >
> > > > > > 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
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > > For additional commands, e-mail: dev-h...@maven.apache.org
>
>
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: [VOTE] Release Apache Maven Release Plugin version 3.0.0-M4

[Hervé BOUTEMY]

thank you Remi

PR merged and current release HTML tweaked [1] to benefit from the 
documentation  just now

Regards,

Hervé

https://maven.apache.org/maven-release-archives/maven-release-LATEST/maven-release-plugin/examples/rollback-release.html

Le jeudi 15 avril 2021, 22:38:05 CEST Rémy Sanlaville a écrit :
> Hi Hervé,
> 
> PR created (cf. https://github.com/apache/maven-release/pulls)
> 
> Regards,
> Rémy
> 
> On Wed, Apr 14, 2021 at 1:28 PM Hervé BOUTEMY  wrote:
> > please create the PR to have it merged
> > 
> > and given it's documentation, we can eventually modify HTML by hand to
> > have
> > this nice little improvement in the current release documentation...
> > 
> > Le mercredi 14 avril 2021, 09:36:52 CEST Rémy Sanlaville a écrit :
> > > Hi Robert,
> > > 
> > > I understand. I wasn't aware about
> > > https://github.com/apache/maven-release/pulls
> > > 
> > > I was just aware to edit the page as you asked me
> > > 
> > > > There's an edit-button on the page (upper left in nav bar) that links
> > 
> > to
> > 
> > https://github.com/apache/maven-release/blob/maven-release-3.0.0-M1/maven
> > 
> > > > -release-plugin/src/site/apt/examples/rollback-release.apt Would be
> > 
> > great
> > 
> > > > if you could help updating this page.
> > > > 
> > > > Cf.
> > 
> > https://mail-archives.apache.org/mod_mbox/maven-dev/202006.mbox/%3CMailbir
> > d-> 3058d9d5-b625-4621-bd90-e20080d523ce%40apache.org%3E
> > 
> > > Rémy
> > > 
> > > On Tue, Apr 13, 2021 at 5:49 PM Robert Scholte 
> > 
> > wrote:
> > > > Hi Rémy
> > > > 
> > > > I don't see it as PR under
> > 
> > https://github.com/apache/maven-release/pulls
> > 
> > > > I did a quick scan over this list and the open Jira issues and decided
> > 
> > not
> > 
> > > > to add more to this milestone release.
> > > > 
> > > > Robert
> > > > On 13-4-2021 09:09:21, Rémy Sanlaville 
> > 
> > wrote:
> > > > Hi Robert,
> > > > 
> > > > What about
> > 
> > https://github.com/apache/maven-release/compare/master...sanlaville:patch-
> > >
> > 
> > > 1
> > > 
> > > > ?
> > > > 
> > > > Cf.
> > 
> > https://mail-archives.apache.org/mod_mbox/maven-dev/202006.mbox/%3CCAK8JC1
> > 
> > > > TqE3CAQbD%3DAC6p9%2BXtO9uk1kjRsVY9YctdVSmPeB7YWQ%40mail.gmail.com%3E
> > 
> > https://mail-archives.apache.org/mod_mbox/maven-dev/202006.mbox/%3CMailbir
> > 
> > > > d-3058d9d5-b625-4621-bd90-e20080d523ce%40apache.org%3E
> > > > 
> > > > Rémy
> > > > 
> > > > On Mon, Apr 12, 2021 at 7:31 PM Robert Scholte wrote:
> > > > > Hi,
> > 
> > > > > We solved 5 issues:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824;
> > 
> > > > version=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%20
> > 
> > > > DESC>
> > > > 
> > > > > Staging repo:
> > > > > https://repository.apache.org/content/repositories/maven-1639
> > 
> > https://repository.apache.org/content/repositories/maven-1639/org/apache/m
> > 
> > aven/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:
> > 49ec8c495b11696671e83ccdeee3408223d0aef3cfd5f48e2a4afc66e225f550069a060702
> > 
> > > > 205152e3e59238f9db64efd85ac626b25b05596be3ef422b991895>
> > > > 
> > > > > 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
> > 
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org





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

Re: [VOTE] Release Apache Maven Release Plugin version 3.0.0-M4

[Rémy Sanlaville]

Hi Hervé,

PR created (cf. https://github.com/apache/maven-release/pulls)

Regards,
Rémy

On Wed, Apr 14, 2021 at 1:28 PM Hervé BOUTEMY  wrote:

> please create the PR to have it merged
>
> and given it's documentation, we can eventually modify HTML by hand to
> have
> this nice little improvement in the current release documentation...
>
> Le mercredi 14 avril 2021, 09:36:52 CEST Rémy Sanlaville a écrit :
> > Hi Robert,
> >
> > I understand. I wasn't aware about
> > https://github.com/apache/maven-release/pulls
> >
> > I was just aware to edit the page as you asked me
> >
> > > There's an edit-button on the page (upper left in nav bar) that links
> to
> > >
> https://github.com/apache/maven-release/blob/maven-release-3.0.0-M1/maven
> > > -release-plugin/src/site/apt/examples/rollback-release.apt Would be
> great
> > > if you could help updating this page.
> > >
> > > Cf.
> >
> >
> https://mail-archives.apache.org/mod_mbox/maven-dev/202006.mbox/%3CMailbird->
> 3058d9d5-b625-4621-bd90-e20080d523ce%40apache.org%3E
> >
> > Rémy
> >
> > On Tue, Apr 13, 2021 at 5:49 PM Robert Scholte 
> wrote:
> > > Hi Rémy
> > >
> > > I don't see it as PR under
> https://github.com/apache/maven-release/pulls
> > > I did a quick scan over this list and the open Jira issues and decided
> not
> > > to add more to this milestone release.
> > >
> > > Robert
> > > On 13-4-2021 09:09:21, Rémy Sanlaville 
> wrote:
> > > Hi Robert,
> > >
> > > What about
> > >
> https://github.com/apache/maven-release/compare/master...sanlaville:patch->
> > 1
> > > ?
> > >
> > > Cf.
> > >
> > >
> https://mail-archives.apache.org/mod_mbox/maven-dev/202006.mbox/%3CCAK8JC1
> > > TqE3CAQbD%3DAC6p9%2BXtO9uk1kjRsVY9YctdVSmPeB7YWQ%40mail.gmail.com%3E
> > >
> > >
> https://mail-archives.apache.org/mod_mbox/maven-dev/202006.mbox/%3CMailbir
> > > d-3058d9d5-b625-4621-bd90-e20080d523ce%40apache.org%3E
> > >
> > > Rémy
> > >
> > > On Mon, Apr 12, 2021 at 7:31 PM Robert Scholte wrote:
> > > > Hi,
> > >
> > > > We solved 5 issues:
> > >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824;
> > > version=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%20
> > > DESC>
> > > > Staging repo:
> > > > https://repository.apache.org/content/repositories/maven-1639
> > >
> > >
> https://repository.apache.org/content/repositories/maven-1639/org/apache/m
> > >
> aven/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:
> > >
> 49ec8c495b11696671e83ccdeee3408223d0aef3cfd5f48e2a4afc66e225f550069a060702
> > > 205152e3e59238f9db64efd85ac626b25b05596be3ef422b991895>
> > > > 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
>
>
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: [VOTE] Release Apache Maven Release Plugin version 3.0.0-M4

[Robert Scholte]

+1
On 12-4-2021 19:31:13, 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

Re: [VOTE] Release Apache Maven Release Plugin version 3.0.0-M4

[Arnaud Héritier]

+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 Release Plugin version 3.0.0-M4

[Sylwester Lachiewicz]

+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
>

Re: [VOTE] Release Apache Maven Release Plugin version 3.0.0-M4

[Olivier Lamy]

+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

Re: [VOTE] Release Apache Maven Release Plugin version 3.0.0-M4

[Hervé BOUTEMY]

+1

checked that the build was reproducible: ok with JDK 8 on Windows

regards,

Hervé

Le lundi 12 avril 2021, 19:31:13 CEST Robert Scholte a écrit :
> Hi,
> 
> We solved 5 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824
> rsion=12348079=Text
> 
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317824%20AND%20
> resolution%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/mav
> en/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: 49ec8c495b11696671e83ccdee
> e3408223d0aef3cfd5f48e2a4afc66e225f550069a060702205152e3e59238f9db64efd85ac6
> 26b25b05596be3ef422b991895
> 
> 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





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

Re: [VOTE] Release Apache Maven Release Plugin version 3.0.0-M4

[Hervé BOUTEMY]

please create the PR to have it merged

and given it's documentation, we can eventually modify HTML by hand to have 
this nice little improvement in the current release documentation...

Le mercredi 14 avril 2021, 09:36:52 CEST Rémy Sanlaville a écrit :
> Hi Robert,
> 
> I understand. I wasn't aware about
> https://github.com/apache/maven-release/pulls
> 
> I was just aware to edit the page as you asked me
> 
> > There's an edit-button on the page (upper left in nav bar) that links to
> > https://github.com/apache/maven-release/blob/maven-release-3.0.0-M1/maven
> > -release-plugin/src/site/apt/examples/rollback-release.apt Would be great
> > if you could help updating this page.
> > 
> > Cf.
> 
> https://mail-archives.apache.org/mod_mbox/maven-dev/202006.mbox/%3CMailbird-> 
> 3058d9d5-b625-4621-bd90-e20080d523ce%40apache.org%3E
> 
> Rémy
> 
> On Tue, Apr 13, 2021 at 5:49 PM Robert Scholte  wrote:
> > Hi Rémy
> > 
> > I don't see it as PR under https://github.com/apache/maven-release/pulls
> > I did a quick scan over this list and the open Jira issues and decided not
> > to add more to this milestone release.
> > 
> > Robert
> > On 13-4-2021 09:09:21, Rémy Sanlaville  wrote:
> > Hi Robert,
> > 
> > What about
> > https://github.com/apache/maven-release/compare/master...sanlaville:patch-> 
> > > 1
> > ?
> > 
> > Cf.
> > 
> > https://mail-archives.apache.org/mod_mbox/maven-dev/202006.mbox/%3CCAK8JC1
> > TqE3CAQbD%3DAC6p9%2BXtO9uk1kjRsVY9YctdVSmPeB7YWQ%40mail.gmail.com%3E
> > 
> > https://mail-archives.apache.org/mod_mbox/maven-dev/202006.mbox/%3CMailbir
> > d-3058d9d5-b625-4621-bd90-e20080d523ce%40apache.org%3E
> > 
> > Rémy
> > 
> > On Mon, Apr 12, 2021 at 7:31 PM Robert Scholte wrote:
> > > Hi,
> > 
> > > We solved 5 issues:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824;
> > version=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%20
> > DESC> 
> > > Staging repo:
> > > https://repository.apache.org/content/repositories/maven-1639
> > 
> > https://repository.apache.org/content/repositories/maven-1639/org/apache/m
> > aven/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:
> > 49ec8c495b11696671e83ccdeee3408223d0aef3cfd5f48e2a4afc66e225f550069a060702
> > 205152e3e59238f9db64efd85ac626b25b05596be3ef422b991895> 
> > > 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





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

Re: [VOTE] Release Apache Maven Release Plugin version 3.0.0-M4

[Tibor Digana]

+1

On Mon, Apr 12, 2021 at 7:31 PM 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
>

Re: [VOTE] Release Apache Maven Release Plugin version 3.0.0-M4

[Rémy Sanlaville]

Hi Robert,

I understand. I wasn't aware about
https://github.com/apache/maven-release/pulls

I was just aware to edit the page as you asked me

> There's an edit-button on the page (upper left in nav bar) that links to 
> https://github.com/apache/maven-release/blob/maven-release-3.0.0-M1/maven-release-plugin/src/site/apt/examples/rollback-release.apt
> Would be great if you could help updating this page.
>
> Cf.
https://mail-archives.apache.org/mod_mbox/maven-dev/202006.mbox/%3CMailbird-3058d9d5-b625-4621-bd90-e20080d523ce%40apache.org%3E

Rémy

On Tue, Apr 13, 2021 at 5:49 PM Robert Scholte  wrote:

> Hi Rémy
>
> I don't see it as PR under https://github.com/apache/maven-release/pulls
> I did a quick scan over this list and the open Jira issues and decided not
> to add more to this milestone release.
>
> Robert
> On 13-4-2021 09:09:21, Rémy Sanlaville  wrote:
> Hi Robert,
>
> What about
> https://github.com/apache/maven-release/compare/master...sanlaville:patch-1
> ?
>
> Cf.
>
> https://mail-archives.apache.org/mod_mbox/maven-dev/202006.mbox/%3CCAK8JC1TqE3CAQbD%3DAC6p9%2BXtO9uk1kjRsVY9YctdVSmPeB7YWQ%40mail.gmail.com%3E
>
> https://mail-archives.apache.org/mod_mbox/maven-dev/202006.mbox/%3CMailbird-3058d9d5-b625-4621-bd90-e20080d523ce%40apache.org%3E
>
> Rémy
>
> On Mon, Apr 12, 2021 at 7:31 PM 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
> >
>

Re: [VOTE] Release Apache Maven Release Plugin version 3.0.0-M4

[Robert Scholte]

Hi Rémy

I don't see it as PR under https://github.com/apache/maven-release/pulls
I did a quick scan over this list and the open Jira issues and decided not to 
add more to this milestone release.

Robert
On 13-4-2021 09:09:21, Rémy Sanlaville  wrote:
Hi Robert,

What about
https://github.com/apache/maven-release/compare/master...sanlaville:patch-1
?

Cf.
https://mail-archives.apache.org/mod_mbox/maven-dev/202006.mbox/%3CCAK8JC1TqE3CAQbD%3DAC6p9%2BXtO9uk1kjRsVY9YctdVSmPeB7YWQ%40mail.gmail.com%3E
https://mail-archives.apache.org/mod_mbox/maven-dev/202006.mbox/%3CMailbird-3058d9d5-b625-4621-bd90-e20080d523ce%40apache.org%3E

Rémy

On Mon, Apr 12, 2021 at 7:31 PM 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
>

Re: [VOTE] Release Apache Maven Release Plugin version 3.0.0-M4

[Rémy Sanlaville]

Hi Robert,

What about
https://github.com/apache/maven-release/compare/master...sanlaville:patch-1
?

Cf.
https://mail-archives.apache.org/mod_mbox/maven-dev/202006.mbox/%3CCAK8JC1TqE3CAQbD%3DAC6p9%2BXtO9uk1kjRsVY9YctdVSmPeB7YWQ%40mail.gmail.com%3E
https://mail-archives.apache.org/mod_mbox/maven-dev/202006.mbox/%3CMailbird-3058d9d5-b625-4621-bd90-e20080d523ce%40apache.org%3E

Rémy

On Mon, Apr 12, 2021 at 7:31 PM 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
>

[VOTE] Release Apache Maven Release Plugin version 3.0.0-M4

[Robert Scholte]

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

Re: [ANN] Apache Maven Release Plugin 3.0.0-M1 Released

[Rémy Sanlaville]

Hello Robert,

I wasn't aware of this possibility.
Done on branch master :
https://github.com/apache/maven-release/compare/master...sanlaville:patch-1

Regards,
Rémy

On Wed, Jun 17, 2020 at 6:08 PM Robert Scholte  wrote:

> There's an edit-button on the page (upper left in nav bar) that links to
> https://github.com/apache/maven-release/blob/maven-release-3.0.0-M1/maven-release-plugin/src/site/apt/examples/rollback-release.apt
> Would be great if you could help updating this page.
>
> thanks,
> Robert
>
>

Re: [ANN] Apache Maven Release Plugin 3.0.0-M1 Released

[Robert Scholte]

There's an edit-button on the page (upper left in nav bar) that links to 
https://github.com/apache/maven-release/blob/maven-release-3.0.0-M1/maven-release-plugin/src/site/apt/examples/rollback-release.apt
Would be great if you could help updating this page.

thanks,
Robert
On 17-6-2020 13:45:09, Rémy Sanlaville  wrote:
Hello,

FYI, it seems that the page rollback-release.html

was not updated with the release 3.0.0-M1:
- RELEASE-229 was fixed by
3.0.0-M1 release
- the JIRA link is wrong : http://jira.codehaus.org/browse/MRELEASE-229
should be replace by https://issues.apache.org/jira/browse/MRELEASE-229

Thanks for having fixing MRELEASE-229


Rémy

On Mon, Dec 16, 2019 at 9:02 AM Hervé Boutemy wrote:

> The Apache Maven team is pleased to announce the release of the Apache
> Maven Release Plugin, version 3.0.0-M1.
>
> This plugin is used to release a project with Maven, saving a lot of
> repetitive, manual work. Releasing a project is made in two steps: prepare
> and perform.
>
> https://maven.apache.org/plugins/maven-release-plugin/
>
> You should specify the version in your project's plugin configuration:
>
>
> org.apache.maven.plugins
> maven-release-plugin
> 3.0.0-M1
>
>
> You can download the appropriate sources etc. from the download page:
>
> https://maven.apache.org/plugins/maven-release-plugin/download.cgi
>
>
> Release Notes - Maven Release Plugin - Version 3.0.0-M1
>
> ** Bug
> * [MRELEASE-229] - release:rollback is missing remove tag
> implementation
> * [MRELEASE-601] - The Maven 2 release plugin modifies CDATA elements
> in pom.xml files.
> * [MRELEASE-694] - -SNAPSHOT is unexpectedly appended to version in
> branched pom.xml
> * [MRELEASE-908] - Git HTTP authentication failing if there are spaces
> in the password
> * [MRELEASE-928] - exposing the password for SCM URL if build failed
> to commit files to SCM
> * [MRELEASE-947] - Wiki page URL for maven-release-plugin is wrong -
> post Codehaus termination
> * [MRELEASE-964] - Error injecting:
> org.apache.maven.shared.release.phase.RewritePomsForReleasePhase
> * [MRELEASE-966] - release plugin does not respect "mvn -f"
> * [MRELEASE-968] - Maven release plugin missing plexus-cipher
> dependency
> * [MRELEASE-975] - NPE when using an unknown project versionpolicy id
> * [MRELEASE-997] - Unable to release:perform on windows if a file name
> contains spaces on windows
> * [MRELEASE-1009] - Compilation failure when using Java 10
> * [MRELEASE-1034] - Remove SCM tag blocks rollback in some situations
>
> ** New Feature
> * [MRELEASE-956] - Release Strategy Interface
> * [MRELEASE-980] - Provide the ability to control commit messages
> * [MRELEASE-985] - Override SNAPSHOT dependencies from command line
> * [MRELEASE-998] - Add ability to create custom phases
> * [MRELEASE-1029] - update project.build.outputTimestamp property on
> prepare
> * [MRELEASE-1031] - display release phases to give insight on what's
> going on during release
>
> ** Improvement
> * [MRELEASE-703] - [PATCH] Migration from obsolete plexus-maven-plugin
> to plexus-containers-component-metadata
> * [MRELEASE-873] - Remove possibly confusing non-standard goals from
> example
> * [MRELEASE-896] - Disable by default and deprecate useReleaseProfile
> parameter
> * [MRELEASE-909] - Add workItem/task support for scm deliver
> * [MRELEASE-958] - Using three digit version number (semver)
> * [MRELEASE-976] - release:branch should also support project version
> policies
> * [MRELEASE-977] - release:branch should prompt for branch name if
> none is given
> * [MRELEASE-979] - Support NamingPolicies to manage Branch and Tag
> names
> * [MRELEASE-992] - Deprecated maven flag --no-plugin-updates shows
> warnings in the console output
> * [MRELEASE-993] - Use shallow checkout per default (git scm)
> * [MRELEASE-994] - Drop Maven2 support
> * [MRELEASE-1005] - Extract ResourceGenerator from ReleasePhase
> * [MRELEASE-1007] - Rework usage workingDirectory and commonBasedir
> * [MRELEASE-1023] - Minor code cleanups
> * [MRELEASE-1032] - add https://m.a.o/xsd/maven-4.0.0.xsd schema
> instead of http://m.a.o/maven-v4_0_0.xsd
>
> ** Task
> * [MRELEASE-356] - Deprecate the automated release profile
> * [MRELEASE-990] - switch to Git
> * [MRELEASE-1027] - New Release
> * [MRELEASE-1033] - Site: Dead link to wiki
>
> ** Dependency upgrade
> * [MRELEASE-952] - Replace JDom as XML transformer
> * [MRELEASE-1010] - Upgrade maven-plugins parent to version 32
> * [MRELEASE-1024] - Upgrade to SCM 1.11.2
>
> Enjoy,
>
> -The Apache Maven team
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: [ANN] Apache Maven Release Plugin 3.0.0-M1 Released

[Rémy Sanlaville]

Hello,

FYI, it seems that the page rollback-release.html
<https://maven.apache.org/maven-release/maven-release-plugin/examples/rollback-release.html>
was not updated with the release 3.0.0-M1:
  - RELEASE-229 <http://jira.codehaus.org/browse/MRELEASE-229> was fixed by
3.0.0-M1 release
  - the JIRA link is wrong : http://jira.codehaus.org/browse/MRELEASE-229
should be replace by https://issues.apache.org/jira/browse/MRELEASE-229

Thanks for having fixing MRELEASE-229
<https://issues.apache.org/jira/browse/MRELEASE-229>

Rémy

On Mon, Dec 16, 2019 at 9:02 AM Hervé Boutemy  wrote:

> The Apache Maven team is pleased to announce the release of the Apache
> Maven Release Plugin, version 3.0.0-M1.
>
> This plugin is used to release a project with Maven, saving a lot of
> repetitive, manual work. Releasing a project is made in two steps: prepare
> and perform.
>
> https://maven.apache.org/plugins/maven-release-plugin/
>
> You should specify the version in your project's plugin configuration:
>
> 
>   org.apache.maven.plugins
>   maven-release-plugin
>   3.0.0-M1
> 
>
> You can download the appropriate sources etc. from the download page:
>
> https://maven.apache.org/plugins/maven-release-plugin/download.cgi
>
>
> Release Notes - Maven Release Plugin - Version 3.0.0-M1
>
> ** Bug
> * [MRELEASE-229] - release:rollback is missing remove tag
> implementation
> * [MRELEASE-601] - The Maven 2 release plugin modifies CDATA elements
> in pom.xml files.
> * [MRELEASE-694] - -SNAPSHOT is unexpectedly appended to version in
> branched pom.xml
> * [MRELEASE-908] - Git HTTP authentication failing if there are spaces
> in the password
> * [MRELEASE-928] - exposing the password for SCM URL if build failed
> to commit files to SCM
> * [MRELEASE-947] - Wiki page URL for maven-release-plugin is wrong -
> post Codehaus termination
> * [MRELEASE-964] - Error injecting:
> org.apache.maven.shared.release.phase.RewritePomsForReleasePhase
> * [MRELEASE-966] - release plugin does not respect "mvn -f"
> * [MRELEASE-968] - Maven release plugin missing plexus-cipher
> dependency
> * [MRELEASE-975] - NPE when using an unknown project versionpolicy id
> * [MRELEASE-997] - Unable to release:perform on windows if a file name
> contains spaces on windows
> * [MRELEASE-1009] - Compilation failure when using Java 10
> * [MRELEASE-1034] - Remove SCM tag blocks rollback in some situations
>
> ** New Feature
> * [MRELEASE-956] - Release Strategy Interface
> * [MRELEASE-980] - Provide the ability to control commit messages
> * [MRELEASE-985] - Override SNAPSHOT dependencies from command line
> * [MRELEASE-998] - Add ability to create custom phases
> * [MRELEASE-1029] - update project.build.outputTimestamp property on
> prepare
> * [MRELEASE-1031] - display release phases to give insight on what's
> going on during release
>
> ** Improvement
> * [MRELEASE-703] - [PATCH] Migration from obsolete plexus-maven-plugin
> to plexus-containers-component-metadata
> * [MRELEASE-873] - Remove possibly confusing non-standard goals from
> example
> * [MRELEASE-896] - Disable by default and deprecate useReleaseProfile
> parameter
> * [MRELEASE-909] - Add workItem/task support for scm deliver
> * [MRELEASE-958] - Using three digit version number (semver)
> * [MRELEASE-976] - release:branch should also support project version
> policies
> * [MRELEASE-977] - release:branch should prompt for branch name if
> none is given
> * [MRELEASE-979] - Support NamingPolicies to manage Branch and Tag
> names
> * [MRELEASE-992] - Deprecated maven flag --no-plugin-updates shows
> warnings in the console output
> * [MRELEASE-993] - Use shallow checkout per default (git scm)
> * [MRELEASE-994] - Drop Maven2 support
> * [MRELEASE-1005] - Extract ResourceGenerator from ReleasePhase
> * [MRELEASE-1007] - Rework usage workingDirectory and commonBasedir
> * [MRELEASE-1023] - Minor code cleanups
> * [MRELEASE-1032] - add https://m.a.o/xsd/maven-4.0.0.xsd schema
> instead of http://m.a.o/maven-v4_0_0.xsd
>
> ** Task
> * [MRELEASE-356] - Deprecate the automated release profile
> * [MRELEASE-990] - switch to Git
> * [MRELEASE-1027] - New Release
> * [MRELEASE-1033] - Site: Dead link to wiki
>
> ** Dependency upgrade
> * [MRELEASE-952] - Replace JDom as XML transformer
> * [MRELEASE-1010] - Upgrade maven-plugins parent to version 32
> * [MRELEASE-1024] - Upgrade to SCM 1.11.2
>
> Enjoy,
>
> -The Apache Maven team
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

[CANCELLED][VOTE] Release Apache Maven Release Plugin version 3.0.0-M2

[Robert Scholte]

Cancelled due to MRELEASE-1042[1]

I'll drop this release

thanks,
Robert

[1] https://issues.apache.org/jira/browse/MRELEASE-1042

On 7-4-2020 20:48:42, 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

Re: [VOTE] Release Apache Maven Release Plugin version 3.0.0-M2

[Arnaud Héritier]

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 Release Plugin version 3.0.0-M2

[Maarten Mulders]

Tested with a custom release strategy, no findings.

+1 from me.

Maarten

On 07/04/2020 20:48, 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
> 

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

Re: [VOTE] Release Apache Maven Release Plugin version 3.0.0-M2

[Elliotte Rusty Harold]

I see this in the pom.xml:




maven-source-plugin
3.2.0


The parent plugin is now 34. I'm not sure exactly what this refers to.
The version numbers of the plugins perhaps? Or the
maven-source-plugin? Or all the following plugins?



On Tue, Apr 7, 2020 at 2: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



-- 
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

[VOTE] Release Apache Maven Release Plugin version 3.0.0-M2

[Robert Scholte]

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

Re: Prevent maven-release-plugin from reformatting attributes on project element

[Bernd Eckenfels]

For the declaration element we took the easy route and use the single line 
element as it gets regenerated by the release.

 This is actually a good thing it contains absolutely nothing of value, so 
wasting only one line is ok (you just must get over the need of printing it on 
paper ,)


--
http://bernd.eckenfels.net

Von: Eric Lilja 
Gesendet: Tuesday, February 4, 2020 7:35:01 PM
An: Maven Developers List 
Betreff: Re: Prevent maven-release-plugin from reformatting attributes on 
project element

Sure! Today I did a release in a single module project. The unwanted diff
was that the release plugin changed


http://maven.apache.org/POM/4.0.0; xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance;
 xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd;>

to


http://maven.apache.org/POM/4.0.0; xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation="
http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd;>

So it discarded our formatting (which had a linebreak after the
xmlns:xsi-attribute and aligned xsi:schemaLocation-attribute, column-wise,
with the xmlns-attribute, in case formatting is lost in the email) and put
all attributes on the same line as its containing element (element
"project", in this case).

I don't know if it happens only for this element or not, in our pom-files,
that is usually the only element that has so many attributes that our
formatter line splits it.

We're trying to make sure formatting is always correct in our code-base, to
get rid of unwanted noise in git diffs to make reviews smaller, that's why
this is a slight nuisance to us.

The release was done on Linux machine. All files have unix-style line
breaks, indentation is four spaces.

- Eric L

On Tue, Feb 4, 2020 at 6:47 PM Hervé BOUTEMY  wrote:

> can you provide an example of reformatting, please?
>
> in every case I saw until now, there is no reformatting, so I suppose
> you're
> in a case I did not expect
>
> Regards,
>
> Hervé
>
> Le mardi 4 février 2020, 16:24:54 CET Eric Lilja a écrit :
> > > I see.
> > > I am not aware of any such feature.
> > > If you have some tool that pretty prints XML according to your
> > > comporate rules you could invoke it in completionGoals [1]
> >
> > That could be a workaround for now. Thanks!
> >
> > - Eric L
> >
> > > Enrico
> > >
> > > [1]
> > >
> http://maven.apache.org/maven-release/maven-release-plugin/prepare-mojo.ht
> > > ml#completionGoals
>
>
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: Prevent maven-release-plugin from reformatting attributes on project element

[Bernd Eckenfels]

It is quite likely that it was fixed/changed and we never fixed the broken 
indentions in existing poms, that's why I am still reminded of it :) I will 
test later.


--
http://bernd.eckenfels.net

Von: Eric Lilja 
Gesendet: Tuesday, February 4, 2020 8:41:03 PM
An: Maven Developers List 
Betreff: Re: Prevent maven-release-plugin from reformatting attributes on 
project element

Ah, yes, I do remember the changed indentation of the tag element in the
past, put I don't recall seeing that lately. Have to check tomorrow when I
get to the office.

Bernd: Which version of the maven-release-plugin did you use?

- Eric L

On Tue, Feb 4, 2020 at 8:30 PM Bernd Eckenfels 
wrote:

> Hm, for me it keeps the line breaks, it does however change the intention
> for the tag element. I thought this was configurable, but can't find it at
> the moment.
>
> Anyway this is an open (and rejected) issue:
> https://issues.apache.org/jira/browse/MRELEASE-1008
>
> Gruss
> Bernd
> --
> http://bernd.eckenfels.net
> 
> Von: Eric Lilja 
> Gesendet: Tuesday, February 4, 2020 3:21:51 PM
> An: Maven Developers List 
> Betreff: Prevent maven-release-plugin from reformatting attributes on
> project element
>
> Hi, we noticed that maven-release-plugin changes formatting of the project
> element, it writes the element as a single line, removing existing line
> breaks on attributes. Is it possible to make it preserve original
> formatting?
>
> We're using maven-release-plugin version 3.0.0-M1
>
> - Eric L
>

Re: Prevent maven-release-plugin from reformatting attributes on project element

[Eric Lilja]

Ah, yes, I do remember the changed indentation of the tag element in the
past, put I don't recall seeing that lately. Have to check tomorrow when I
get to the office.

Bernd: Which version of the maven-release-plugin did you use?

- Eric L

On Tue, Feb 4, 2020 at 8:30 PM Bernd Eckenfels 
wrote:

> Hm, for me it keeps the line breaks, it does however change the intention
> for the tag element. I thought this was configurable, but can't find it at
> the moment.
>
> Anyway this is an open (and rejected) issue:
> https://issues.apache.org/jira/browse/MRELEASE-1008
>
> Gruss
> Bernd
> --
> http://bernd.eckenfels.net
> 
> Von: Eric Lilja 
> Gesendet: Tuesday, February 4, 2020 3:21:51 PM
> An: Maven Developers List 
> Betreff: Prevent maven-release-plugin from reformatting attributes on
> project element
>
> Hi, we noticed that maven-release-plugin changes formatting of the project
> element, it writes the element as a single line, removing existing line
> breaks on attributes. Is it possible to make it preserve original
> formatting?
>
> We're using maven-release-plugin version 3.0.0-M1
>
> - Eric L
>

Re: Prevent maven-release-plugin from reformatting attributes on project element

[Bernd Eckenfels]

Hm, for me it keeps the line breaks, it does however change the intention for 
the tag element. I thought this was configurable, but can't find it at the 
moment.

Anyway this is an open (and rejected) issue: 
https://issues.apache.org/jira/browse/MRELEASE-1008

Gruss
Bernd
--
http://bernd.eckenfels.net

Von: Eric Lilja 
Gesendet: Tuesday, February 4, 2020 3:21:51 PM
An: Maven Developers List 
Betreff: Prevent maven-release-plugin from reformatting attributes on project 
element

Hi, we noticed that maven-release-plugin changes formatting of the project
element, it writes the element as a single line, removing existing line
breaks on attributes. Is it possible to make it preserve original
formatting?

We're using maven-release-plugin version 3.0.0-M1

- Eric L

Re: Prevent maven-release-plugin from reformatting attributes on project element

[Robert Scholte]

The transformation is triggered by one of the subclasses of 
AbstractRewritePomsPhase[1]
In 2.5.3[2] the plugin was relying on JDOM with quite some hacks to make it 
work. This is now extracted so it is possible to switch to a different parser 
(JDom is not an active project anymore).
Here's where you need to find the cause and solution.

thanks,
Robert

[1] 
https://github.com/apache/maven-release/blob/master/maven-release-manager/src/main/java/org/apache/maven/shared/release/phase/AbstractRewritePomsPhase.java
[2] 
https://github.com/apache/maven-release/blob/maven-release-2.5.3/maven-release-manager/src/main/java/org/apache/maven/shared/release/phase/AbstractRewritePomsPhase.java
On 4-2-2020 19:35:27, Eric Lilja  wrote:
Sure! Today I did a release in a single module project. The unwanted diff
was that the release plugin changed



xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd;>

to




So it discarded our formatting (which had a linebreak after the
xmlns:xsi-attribute and aligned xsi:schemaLocation-attribute, column-wise,
with the xmlns-attribute, in case formatting is lost in the email) and put
all attributes on the same line as its containing element (element
"project", in this case).

I don't know if it happens only for this element or not, in our pom-files,
that is usually the only element that has so many attributes that our
formatter line splits it.

We're trying to make sure formatting is always correct in our code-base, to
get rid of unwanted noise in git diffs to make reviews smaller, that's why
this is a slight nuisance to us.

The release was done on Linux machine. All files have unix-style line
breaks, indentation is four spaces.

- Eric L

On Tue, Feb 4, 2020 at 6:47 PM Hervé BOUTEMY wrote:

> can you provide an example of reformatting, please?
>
> in every case I saw until now, there is no reformatting, so I suppose
> you're
> in a case I did not expect
>
> Regards,
>
> Hervé
>
> Le mardi 4 février 2020, 16:24:54 CET Eric Lilja a écrit :
> > > I see.
> > > I am not aware of any such feature.
> > > If you have some tool that pretty prints XML according to your
> > > comporate rules you could invoke it in completionGoals [1]
> >
> > That could be a workaround for now. Thanks!
> >
> > - Eric L
> >
> > > Enrico
> > >
> > > [1]
> > >
> http://maven.apache.org/maven-release/maven-release-plugin/prepare-mojo.ht
> > > ml#completionGoals
>
>
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: Prevent maven-release-plugin from reformatting attributes on project element

[Eric Lilja]

Sure! Today I did a release in a single module project. The unwanted diff
was that the release plugin changed


http://maven.apache.org/POM/4.0.0; xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance;
 xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd;>

to


http://maven.apache.org/POM/4.0.0; xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation="
http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd;>

So it discarded our formatting (which had a linebreak after the
xmlns:xsi-attribute and aligned xsi:schemaLocation-attribute, column-wise,
with the xmlns-attribute, in case formatting is lost in the email) and put
all attributes on the same line as its containing element (element
"project", in this case).

I don't know if it happens only for this element or not, in our pom-files,
that is usually the only element that has so many attributes that our
formatter line splits it.

We're trying to make sure formatting is always correct in our code-base, to
get rid of unwanted noise in git diffs to make reviews smaller, that's why
this is a slight nuisance to us.

The release was done on Linux machine. All files have unix-style line
breaks, indentation is four spaces.

- Eric L

On Tue, Feb 4, 2020 at 6:47 PM Hervé BOUTEMY  wrote:

> can you provide an example of reformatting, please?
>
> in every case I saw until now, there is no reformatting, so I suppose
> you're
> in a case I did not expect
>
> Regards,
>
> Hervé
>
> Le mardi 4 février 2020, 16:24:54 CET Eric Lilja a écrit :
> > > I see.
> > > I am not aware of any such feature.
> > > If you have some tool that pretty prints XML according to your
> > > comporate rules you could invoke it in completionGoals [1]
> >
> > That could be a workaround for now. Thanks!
> >
> > - Eric L
> >
> > > Enrico
> > >
> > > [1]
> > >
> http://maven.apache.org/maven-release/maven-release-plugin/prepare-mojo.ht
> > > ml#completionGoals
>
>
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: Prevent maven-release-plugin from reformatting attributes on project element

[Hervé BOUTEMY]

can you provide an example of reformatting, please?

in every case I saw until now, there is no reformatting, so I suppose you're 
in a case I did not expect

Regards,

Hervé

Le mardi 4 février 2020, 16:24:54 CET Eric Lilja a écrit :
> > I see.
> > I am not aware of any such feature.
> > If you have some tool that pretty prints XML according to your
> > comporate rules you could invoke it in completionGoals [1]
> 
> That could be a workaround for now. Thanks!
> 
> - Eric L
> 
> > Enrico
> > 
> > [1]
> > http://maven.apache.org/maven-release/maven-release-plugin/prepare-mojo.ht
> > ml#completionGoals





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

Re: Prevent maven-release-plugin from reformatting attributes on project element

[Eric Lilja]

>
> I see.
> I am not aware of any such feature.
> If you have some tool that pretty prints XML according to your
> comporate rules you could invoke it in completionGoals [1]
>

That could be a workaround for now. Thanks!

- Eric L


>
> Enrico
>
> [1]
> http://maven.apache.org/maven-release/maven-release-plugin/prepare-mojo.html#completionGoals
>

Re: Prevent maven-release-plugin from reformatting attributes on project element

[Enrico Olivelli]

Il giorno mar 4 feb 2020 alle ore 16:17 Eric Lilja
 ha scritto:
>
> I didn't say the generated xml was invalid. It's a nuisance for us since
> the formatting conflicts with our corporate settings, so we are seeing
> unwelcome noise git diffs after releases.

I see.
I am not aware of any such feature.
If you have some tool that pretty prints XML according to your
comporate rules you could invoke it in completionGoals [1]

Enrico

[1] 
http://maven.apache.org/maven-release/maven-release-plugin/prepare-mojo.html#completionGoals
>
> - Eric L
>
> On Tue, Feb 4, 2020 at 4:08 PM Enrico Olivelli  wrote:
>
> > Eric
> > What's your use case?
> > As far as it creates a valid XML with the same meaning this should not be a
> > problem
> >
> > Enrico
> >
> > Il Mar 4 Feb 2020, 15:22 Eric Lilja  ha scritto:
> >
> > > Hi, we noticed that maven-release-plugin changes formatting of the
> > project
> > > element, it writes the element as a single line, removing existing line
> > > breaks on attributes. Is it possible to make it preserve original
> > > formatting?
> > >
> > > We're using maven-release-plugin version 3.0.0-M1
> > >
> > > - Eric L
> > >
> >

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

Re: Prevent maven-release-plugin from reformatting attributes on project element

[Eric Lilja]

I didn't say the generated xml was invalid. It's a nuisance for us since
the formatting conflicts with our corporate settings, so we are seeing
unwelcome noise git diffs after releases.

- Eric L

On Tue, Feb 4, 2020 at 4:08 PM Enrico Olivelli  wrote:

> Eric
> What's your use case?
> As far as it creates a valid XML with the same meaning this should not be a
> problem
>
> Enrico
>
> Il Mar 4 Feb 2020, 15:22 Eric Lilja  ha scritto:
>
> > Hi, we noticed that maven-release-plugin changes formatting of the
> project
> > element, it writes the element as a single line, removing existing line
> > breaks on attributes. Is it possible to make it preserve original
> > formatting?
> >
> > We're using maven-release-plugin version 3.0.0-M1
> >
> > - Eric L
> >
>

Re: Prevent maven-release-plugin from reformatting attributes on project element

[Enrico Olivelli]

Eric
What's your use case?
As far as it creates a valid XML with the same meaning this should not be a
problem

Enrico

Il Mar 4 Feb 2020, 15:22 Eric Lilja  ha scritto:

> Hi, we noticed that maven-release-plugin changes formatting of the project
> element, it writes the element as a single line, removing existing line
> breaks on attributes. Is it possible to make it preserve original
> formatting?
>
> We're using maven-release-plugin version 3.0.0-M1
>
> - Eric L
>

Prevent maven-release-plugin from reformatting attributes on project element

[Eric Lilja]

Hi, we noticed that maven-release-plugin changes formatting of the project
element, it writes the element as a single line, removing existing line
breaks on attributes. Is it possible to make it preserve original
formatting?

We're using maven-release-plugin version 3.0.0-M1

- Eric L

Re: [ANN] Apache Maven Release Plugin 3.0.0-M1 Released

[Robert Scholte]

Hi Mark,

Based on the exception you're missing maven-release-api (or this file is 
corrupt).
There's no documentation regarding MRELEASE-956 (yet), but it shouldn't effect 
the default (2.5.3) behavior of the plugin.

thanks,
Robert

On 18-12-2019 22:40:36, Mark Derricutt  wrote:
On 16 Dec 2019, at 21:02, Hervé Boutemy wrote:

org.apache.maven.plugins
maven-release-plugin
3.0.0-M1

Him, updating my projects to use this and got:
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-release-plugin:3.0.0-M1:prepare (default-cli) on 
project smx3.bill-of-materials: Execution default-cli of goal 
org.apache.maven.plugins:maven-release-plugin:3.0.0-M1:prepare failed: A 
required class was missing while executing 
org.apache.maven.plugins:maven-release-plugin:3.0.0-M1:prepare: 
org/apache/maven/shared/release/env/ReleaseEnvironment
This is configured in an import tile from out tiles project configured as:
 default 
 ...  org.apache.maven.plugins 
maven-release-plugin 2.5.3 
  clean reproducible:apply sortpom:sort 
tidy:pom rangeresolver:lock-deps install  
deploy  reproducible:clear sortpom:sort 
tidy:pom  
${projectVersionPolicyId} 
true 
false true 
   com.smxemail 
qualified-version-policy 1.0.2 
  
We do have a custom projectVersionPolicy that we configure, defaulting to 
'default'.
I note in the changeling:
* [MRELEASE-975] - NPE when using an unknown project versionpolicy id * 
[MRELEASE-956] - Release Strategy Interface
Is there a documented set of changes? MRELEASE-956 seems to imply the the 
current API is still there?
Mark
"The ease with which a change can be implemented has no relevance at all to 
whether it is the right change for the (Java) Platform for all time." — Mark 
Reinhold.
Mark Derricutt
http://www.theoryinpractice.net [http://www.theoryinpractice.net]
http://www.chaliceofblood.net [http://www.chaliceofblood.net]
http://plus.google.com/+MarkDerricutt [http://plus.google.com/+MarkDerricutt]
http://twitter.com/talios [http://twitter.com/talios]
http://facebook.com/mderricutt [http://facebook.com/mderricutt]

Re: [ANN] Apache Maven Release Plugin 3.0.0-M1 Released

[Mark Derricutt]

On 16 Dec 2019, at 21:02, Hervé Boutemy wrote:

> 
>   org.apache.maven.plugins
>   maven-release-plugin
>   3.0.0-M1
> 

Him, updating my projects to use this and got:

[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-release-plugin:3.0.0-M1:prepare (default-cli) on 
project smx3.bill-of-materials: Execution default-cli of goal 
org.apache.maven.plugins:maven-release-plugin:3.0.0-M1:prepare failed: A 
required class was missing while executing 
org.apache.maven.plugins:maven-release-plugin:3.0.0-M1:prepare: 
org/apache/maven/shared/release/env/ReleaseEnvironment

This is configured in an import tile from out tiles project configured as:

  
default
  
  ...
  
org.apache.maven.plugins
    maven-release-plugin
2.5.3

  
clean
reproducible:apply
sortpom:sort
tidy:pom
rangeresolver:lock-deps
install
  
  deploy
  
reproducible:clear
sortpom:sort
tidy:pom
  
  
${projectVersionPolicyId}
  true
  false
  true


  
com.smxemail
qualified-version-policy
1.0.2
  

  

We do have a custom projectVersionPolicy that we configure, defaulting to 
'default'.

I note in the changeling:

* [MRELEASE-975] - NPE when using an unknown project versionpolicy id
* [MRELEASE-956] - Release Strategy Interface

Is there a documented set of changes? MRELEASE-956 seems to imply the the 
current API is still there?

Mark





---
"The ease with which a change can be implemented has no relevance at all to 
whether it is the right change for the (Java) Platform for all time."  
Mark Reinhold.

Mark Derricutt
http://www.theoryinpractice.net
http://www.chaliceofblood.net
http://plus.google.com/+MarkDerricutt
http://twitter.com/talios
http://facebook.com/mderricutt


signature.asc
Description: OpenPGP digital signature

[ANN] Apache Maven Release Plugin 3.0.0-M1 Released

[Hervé Boutemy]

The Apache Maven team is pleased to announce the release of the Apache Maven 
Release Plugin, version 3.0.0-M1.
 
This plugin is used to release a project with Maven, saving a lot of 
repetitive, manual work. Releasing a project is made in two steps: prepare and 
perform.
 
https://maven.apache.org/plugins/maven-release-plugin/
 
You should specify the version in your project's plugin configuration:
 

  org.apache.maven.plugins
  maven-release-plugin
  3.0.0-M1

 
You can download the appropriate sources etc. from the download page:

https://maven.apache.org/plugins/maven-release-plugin/download.cgi
 

Release Notes - Maven Release Plugin - Version 3.0.0-M1

** Bug
* [MRELEASE-229] - release:rollback is missing remove tag implementation
* [MRELEASE-601] - The Maven 2 release plugin modifies CDATA elements in 
pom.xml files.
* [MRELEASE-694] - -SNAPSHOT is unexpectedly appended to version in 
branched pom.xml
* [MRELEASE-908] - Git HTTP authentication failing if there are spaces in 
the password
* [MRELEASE-928] - exposing the password for SCM URL if build failed to 
commit files to SCM
* [MRELEASE-947] - Wiki page URL for maven-release-plugin is wrong - post 
Codehaus termination
* [MRELEASE-964] - Error injecting: 
org.apache.maven.shared.release.phase.RewritePomsForReleasePhase
* [MRELEASE-966] - release plugin does not respect "mvn -f"
* [MRELEASE-968] - Maven release plugin missing plexus-cipher dependency
* [MRELEASE-975] - NPE when using an unknown project versionpolicy id
* [MRELEASE-997] - Unable to release:perform on windows if a file name 
contains spaces on windows
* [MRELEASE-1009] - Compilation failure when using Java 10
* [MRELEASE-1034] - Remove SCM tag blocks rollback in some situations

** New Feature
* [MRELEASE-956] - Release Strategy Interface
* [MRELEASE-980] - Provide the ability to control commit messages
* [MRELEASE-985] - Override SNAPSHOT dependencies from command line
* [MRELEASE-998] - Add ability to create custom phases
* [MRELEASE-1029] - update project.build.outputTimestamp property on prepare
* [MRELEASE-1031] - display release phases to give insight on what's going 
on during release

** Improvement
* [MRELEASE-703] - [PATCH] Migration from obsolete plexus-maven-plugin to 
plexus-containers-component-metadata
* [MRELEASE-873] - Remove possibly confusing non-standard goals from example
* [MRELEASE-896] - Disable by default and deprecate useReleaseProfile 
parameter
* [MRELEASE-909] - Add workItem/task support for scm deliver
* [MRELEASE-958] - Using three digit version number (semver)
* [MRELEASE-976] - release:branch should also support project version 
policies
* [MRELEASE-977] - release:branch should prompt for branch name if none is 
given
* [MRELEASE-979] - Support NamingPolicies to manage Branch and Tag names
* [MRELEASE-992] - Deprecated maven flag --no-plugin-updates shows warnings 
in the console output
* [MRELEASE-993] - Use shallow checkout per default (git scm)
* [MRELEASE-994] - Drop Maven2 support
* [MRELEASE-1005] - Extract ResourceGenerator from ReleasePhase
* [MRELEASE-1007] - Rework usage workingDirectory and commonBasedir
* [MRELEASE-1023] - Minor code cleanups
* [MRELEASE-1032] - add https://m.a.o/xsd/maven-4.0.0.xsd schema instead of 
http://m.a.o/maven-v4_0_0.xsd

** Task
* [MRELEASE-356] - Deprecate the automated release profile
* [MRELEASE-990] - switch to Git
* [MRELEASE-1027] - New Release
* [MRELEASE-1033] - Site: Dead link to wiki

** Dependency upgrade
* [MRELEASE-952] - Replace JDom as XML transformer
* [MRELEASE-1010] - Upgrade maven-plugins parent to version 32
* [MRELEASE-1024] - Upgrade to SCM 1.11.2
 
Enjoy,
 
-The Apache Maven team



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

Re: [VOTE] Release Apache Maven Release Plugin version 3.0.0-M1

[Hervé BOUTEMY]

Le jeudi 12 décembre 2019, 01:48:53 CET Olivier Lamy a écrit :
> +1
> 
> Nice to see you doing some archeology :P
you're right, fixing little reproducibility issues is a little bit like 
archeology :)
but at least, there are efficient tools to quickly pin issues:
- maven-buildinfo-plugin to easily get the checksum of every artifacts (and 
I'll probably add a few other goals given experience on this vote)
- diffoscope to dig into differences
In the near future, with experience of a few releases, I really hope that the 
check will be an easy "ok, got the same checksums in buildinfo", avoiding the 
investigation on little differences...

Regards,

Hervé

> 
> On Thu, 12 Dec 2019 at 09:42,  wrote:
> > Here is my +1
> > 
> > On reproducibility test, I took time to install a JDK 7 on my Mac and
> > test, and the results are not as good as expected:
> > - sources.jar are all different, because of a different order of
> > META-INF/LICENSE DEPENDENCIES and NOTICE
> > - maven-release-plugin-3.0.0-M1.jar is different, just because I forgot to
> > upgrade maven-plugin-tools (using version 3.2 which puts a date in
> > generated xml)
> > - maven-release-manager-3.0.0-M1.jar is different because I forgot to
> > upgrade plexus-components-metadata
> > Then 2 stupid plugins upgrade forgotten and one issue to dig into
> > regarding the files in META-INF
> > But this is going in the right direction
> > 
> > Regards,
> > 
> > Hervé
> > 
> > - Mail original -
> > De: "Enrico Olivelli" 
> > À: "Maven Developers List" 
> > Envoyé: Mercredi 11 Décembre 2019 16:59:31
> > Objet: Re: [VOTE] Release Apache Maven Release Plugin version 3.0.0-M1
> > 
> > +1 (non binding)
> > 
> > Only tested on Mac with JDK12.
> > 
> > Java version: 12.0.2, vendor: AdoptOpenJDK, runtime:
> > /Users/enrico.olivelli/dev/jdk-12
> > 
> > Default locale: it_IT, platform encoding: UTF-8
> > 
> > mvn clean install -Prun-its
> > 
> > INFO] Reactor Summary for Maven Release 3.0.0-M1:
> > 
> > [INFO]
> > 
> > [INFO] Maven Release .. SUCCESS [
> > 3.639
> > s]
> > 
> > [INFO] Maven Release APIs . SUCCESS [
> > 2.492
> > s]
> > 
> > [INFO] Maven Release Manager .. SUCCESS [01:38
> > min]
> > 
> > [INFO] Maven Release Plugin ... SUCCESS [04:36
> > min]
> > 
> > [INFO] Maven Release Odd-Even Policy .. SUCCESS [
> > 2.171
> > s]
> > 
> > [INFO] Maven Release SemVer Policy  SUCCESS [
> > 3.798
> > s]
> > 
> > [INFO]
> > 
> > 
> > [INFO] BUILD SUCCESS
> > 
> > [INFO]
> > 
> > 
> > [INFO] Total time:  06:27 min
> > 
> > [INFO] Finished at: 2019-12-11T17:58:08+01:00
> > 
> > All its run without problems.
> > 
> > Enrico
> > 
> > Il giorno mer 11 dic 2019 alle ore 17:35 Herve Boutemy <
> > hbout...@apache.org>
> > 
> > ha scritto:
> > > nobody interested? Or I was too hard on testing reproducibility with JDK
> > 
> > 7?
> > 
> > > This reproducibility test is just an option, don't hesitate to not test
> > > On next vote, I'll do the release with JDK 8, which will be easier for
> > > everyone to have on his computer...
> > > 
> > > Regards,
> > > 
> > > Hervé
> > > 
> > > On 2019/12/08 23:35:03, Hervé BOUTEMY  wrote:
> > > > Hi,
> > 
> > > > We solved 41 issues:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824;
> > version=12331214=Text> 
> > > > Staging repo:
> > > > https://repository.apache.org/content/repositories/maven-1544/
> > 
> > https://repository.apache.org/content/repositories/maven-1544/org/apache/m
> > aven/release/maven-release/3.0.0-M1/maven-release-3.0.0-M1-source-release.
> > zip> 
> > > > Source release checksum(s):
> > 
> > > > maven-release-3.0.0-M1-source-release.zip sha512:
> > e4eb349406bf1c823a68c83af77084f4838d0b32a05aeae178c3cda5442baef69f9cf1704b
> > 19ca32daac68decaafdc86a661e767074315a1f0ac0b8e4633b853> 
> > > > Staging site:
> > https://maven.apache.org/maven-release-archives/maven-release-LATEST/maven
&

[RESULT] [VOTE] Release Apache Maven Release Plugin version 3.0.0-M1

[Hervé BOUTEMY]

Hi,

The vote has passed with the following result:

+1 : Enrico Olivelli, Olivier Lamy, Robert Scholte, Hervé Boutemy

PMC quorum reached

I will promote the artifacts to the central repo.



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

Re: [VOTE] Release Apache Maven Release Plugin version 3.0.0-M1

[Olivier Lamy]

+1

Nice to see you doing some archeology :P

On Thu, 12 Dec 2019 at 09:42,  wrote:

> Here is my +1
>
> On reproducibility test, I took time to install a JDK 7 on my Mac and
> test, and the results are not as good as expected:
> - sources.jar are all different, because of a different order of
> META-INF/LICENSE DEPENDENCIES and NOTICE
> - maven-release-plugin-3.0.0-M1.jar is different, just because I forgot to
> upgrade maven-plugin-tools (using version 3.2 which puts a date in
> generated xml)
> - maven-release-manager-3.0.0-M1.jar is different because I forgot to
> upgrade plexus-components-metadata
> Then 2 stupid plugins upgrade forgotten and one issue to dig into
> regarding the files in META-INF
> But this is going in the right direction
>
> Regards,
>
> Hervé
>
> - Mail original -
> De: "Enrico Olivelli" 
> À: "Maven Developers List" 
> Envoyé: Mercredi 11 Décembre 2019 16:59:31
> Objet: Re: [VOTE] Release Apache Maven Release Plugin version 3.0.0-M1
>
> +1 (non binding)
>
> Only tested on Mac with JDK12.
>
> Java version: 12.0.2, vendor: AdoptOpenJDK, runtime:
> /Users/enrico.olivelli/dev/jdk-12
>
> Default locale: it_IT, platform encoding: UTF-8
>
> mvn clean install -Prun-its
>
> INFO] Reactor Summary for Maven Release 3.0.0-M1:
>
> [INFO]
>
> [INFO] Maven Release .. SUCCESS [
> 3.639
> s]
>
> [INFO] Maven Release APIs ......... SUCCESS [
> 2.492
> s]
>
> [INFO] Maven Release Manager .. SUCCESS [01:38
> min]
>
> [INFO] Maven Release Plugin ... SUCCESS [04:36
> min]
>
> [INFO] Maven Release Odd-Even Policy .. SUCCESS [
> 2.171
> s]
>
> [INFO] Maven Release SemVer Policy  SUCCESS [
> 3.798
> s]
>
> [INFO]
> 
>
> [INFO] BUILD SUCCESS
>
> [INFO]
> 
>
> [INFO] Total time:  06:27 min
>
> [INFO] Finished at: 2019-12-11T17:58:08+01:00
>
> All its run without problems.
>
> Enrico
>
> Il giorno mer 11 dic 2019 alle ore 17:35 Herve Boutemy <
> hbout...@apache.org>
> ha scritto:
>
> > nobody interested? Or I was too hard on testing reproducibility with JDK
> 7?
> > This reproducibility test is just an option, don't hesitate to not test
> > On next vote, I'll do the release with JDK 8, which will be easier for
> > everyone to have on his computer...
> >
> > Regards,
> >
> > Hervé
> >
> > On 2019/12/08 23:35:03, Hervé BOUTEMY  wrote:
> > > Hi,
> > >
> > > We solved 41 issues:
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824=12331214=Text
> > >
> > > Staging repo:
> > > https://repository.apache.org/content/repositories/maven-1544/
> > >
> >
> https://repository.apache.org/content/repositories/maven-1544/org/apache/maven/release/maven-release/3.0.0-M1/maven-release-3.0.0-M1-source-release.zip
> > >
> > > Source release checksum(s):
> > > maven-release-3.0.0-M1-source-release.zip sha512:
> >
> e4eb349406bf1c823a68c83af77084f4838d0b32a05aeae178c3cda5442baef69f9cf1704b19ca32daac68decaafdc86a661e767074315a1f0ac0b8e4633b853
> > >
> > > Staging site:
> > >
> >
> https://maven.apache.org/maven-release-archives/maven-release-LATEST/maven-release-plugin/
> > > 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
> > >
> > > In addition to these instructions, I'd like voters to check
> Reproducible
> > Build and report: to do so
> > > 1. please install locally maven-buildinfo-plugin
> > https://github.com/apache/maven-studies/tree/maven-buildinfo-plugin
> > > 2. use JDK 7 and any Unix and build with "mvn -Papache-release,run-its
> > -Dgpg.skip verify buildinfo:save"
> > > If you are building on Windows, please add "-Dline.separator="\n""...
> > > 3. check the content of
> >
> maven-release-policies/maven-release-semver-policy/target/aggregate.buildinfo
> > against reference in attachment
> > > Your should get the same sha512, even if you don't have exactly the
> same
> > OS or JDK version.
> > > Please share your results
> > >
> > >
> > > 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
>
>

-- 
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy

Re: [VOTE] Release Apache Maven Release Plugin version 3.0.0-M1

[herve . boutemy]

Here is my +1

On reproducibility test, I took time to install a JDK 7 on my Mac and test, and 
the results are not as good as expected:
- sources.jar are all different, because of a different order of 
META-INF/LICENSE DEPENDENCIES and NOTICE
- maven-release-plugin-3.0.0-M1.jar is different, just because I forgot to 
upgrade maven-plugin-tools (using version 3.2 which puts a date in generated 
xml)
- maven-release-manager-3.0.0-M1.jar is different because I forgot to upgrade 
plexus-components-metadata
Then 2 stupid plugins upgrade forgotten and one issue to dig into regarding the 
files in META-INF
But this is going in the right direction

Regards,

Hervé

- Mail original -
De: "Enrico Olivelli" 
À: "Maven Developers List" 
Envoyé: Mercredi 11 Décembre 2019 16:59:31
Objet: Re: [VOTE] Release Apache Maven Release Plugin version 3.0.0-M1

+1 (non binding)

Only tested on Mac with JDK12.

Java version: 12.0.2, vendor: AdoptOpenJDK, runtime:
/Users/enrico.olivelli/dev/jdk-12

Default locale: it_IT, platform encoding: UTF-8

mvn clean install -Prun-its

INFO] Reactor Summary for Maven Release 3.0.0-M1:

[INFO]

[INFO] Maven Release .. SUCCESS [  3.639
s]

[INFO] Maven Release APIs . SUCCESS [  2.492
s]

[INFO] Maven Release Manager .. SUCCESS [01:38
min]

[INFO] Maven Release Plugin ... SUCCESS [04:36
min]

[INFO] Maven Release Odd-Even Policy .. SUCCESS [  2.171
s]

[INFO] Maven Release SemVer Policy  SUCCESS [  3.798
s]

[INFO]


[INFO] BUILD SUCCESS

[INFO]


[INFO] Total time:  06:27 min

[INFO] Finished at: 2019-12-11T17:58:08+01:00

All its run without problems.

Enrico

Il giorno mer 11 dic 2019 alle ore 17:35 Herve Boutemy 
ha scritto:

> nobody interested? Or I was too hard on testing reproducibility with JDK 7?
> This reproducibility test is just an option, don't hesitate to not test
> On next vote, I'll do the release with JDK 8, which will be easier for
> everyone to have on his computer...
>
> Regards,
>
> Hervé
>
> On 2019/12/08 23:35:03, Hervé BOUTEMY  wrote:
> > Hi,
> >
> > We solved 41 issues:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824=12331214=Text
> >
> > Staging repo:
> > https://repository.apache.org/content/repositories/maven-1544/
> >
> https://repository.apache.org/content/repositories/maven-1544/org/apache/maven/release/maven-release/3.0.0-M1/maven-release-3.0.0-M1-source-release.zip
> >
> > Source release checksum(s):
> > maven-release-3.0.0-M1-source-release.zip sha512:
> e4eb349406bf1c823a68c83af77084f4838d0b32a05aeae178c3cda5442baef69f9cf1704b19ca32daac68decaafdc86a661e767074315a1f0ac0b8e4633b853
> >
> > Staging site:
> >
> https://maven.apache.org/maven-release-archives/maven-release-LATEST/maven-release-plugin/
> > 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
> >
> > In addition to these instructions, I'd like voters to check Reproducible
> Build and report: to do so
> > 1. please install locally maven-buildinfo-plugin
> https://github.com/apache/maven-studies/tree/maven-buildinfo-plugin
> > 2. use JDK 7 and any Unix and build with "mvn -Papache-release,run-its
> -Dgpg.skip verify buildinfo:save"
> > If you are building on Windows, please add "-Dline.separator="\n""...
> > 3. check the content of
> maven-release-policies/maven-release-semver-policy/target/aggregate.buildinfo
> against reference in attachment
> > Your should get the same sha512, even if you don't have exactly the same
> OS or JDK version.
> > Please share your results
> >
> >
> > Vote open for at least 72 hours.
> >
> > [ ] +1
> > [ ] +0
> > [ ] -1
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

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

Re: [VOTE] Release Apache Maven Release Plugin version 3.0.0-M1

[Robert Scholte]

+1
On 9-12-2019 00:35:11, Hervé BOUTEMY  wrote:
Hi,

We solved 41 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824=12331214=Text

Staging repo:
https://repository.apache.org/content/repositories/maven-1544/
https://repository.apache.org/content/repositories/maven-1544/org/apache/maven/release/maven-release/3.0.0-M1/maven-release-3.0.0-M1-source-release.zip

Source release checksum(s):
maven-release-3.0.0-M1-source-release.zip sha512: 
e4eb349406bf1c823a68c83af77084f4838d0b32a05aeae178c3cda5442baef69f9cf1704b19ca32daac68decaafdc86a661e767074315a1f0ac0b8e4633b853

Staging site:
https://maven.apache.org/maven-release-archives/maven-release-LATEST/maven-release-plugin/
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

In addition to these instructions, I'd like voters to check Reproducible Build 
and report: to do so
1. please install locally maven-buildinfo-plugin 
https://github.com/apache/maven-studies/tree/maven-buildinfo-plugin
2. use JDK 7 and any Unix and build with "mvn -Papache-release,run-its 
-Dgpg.skip verify buildinfo:save"
If you are building on Windows, please add "-Dline.separator="\n""...
3. check the content of 
maven-release-policies/maven-release-semver-policy/target/aggregate.buildinfo 
against reference in attachment
Your should get the same sha512, even if you don't have exactly the same OS or 
JDK version.
Please share your results


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 Release Plugin version 3.0.0-M1

[Enrico Olivelli]

+1 (non binding)

Only tested on Mac with JDK12.

Java version: 12.0.2, vendor: AdoptOpenJDK, runtime:
/Users/enrico.olivelli/dev/jdk-12

Default locale: it_IT, platform encoding: UTF-8

mvn clean install -Prun-its

INFO] Reactor Summary for Maven Release 3.0.0-M1:

[INFO]

[INFO] Maven Release .. SUCCESS [  3.639
s]

[INFO] Maven Release APIs . SUCCESS [  2.492
s]

[INFO] Maven Release Manager .. SUCCESS [01:38
min]

[INFO] Maven Release Plugin ... SUCCESS [04:36
min]

[INFO] Maven Release Odd-Even Policy .. SUCCESS [  2.171
s]

[INFO] Maven Release SemVer Policy  SUCCESS [  3.798
s]

[INFO]


[INFO] BUILD SUCCESS

[INFO]


[INFO] Total time:  06:27 min

[INFO] Finished at: 2019-12-11T17:58:08+01:00

All its run without problems.

Enrico

Il giorno mer 11 dic 2019 alle ore 17:35 Herve Boutemy 
ha scritto:

> nobody interested? Or I was too hard on testing reproducibility with JDK 7?
> This reproducibility test is just an option, don't hesitate to not test
> On next vote, I'll do the release with JDK 8, which will be easier for
> everyone to have on his computer...
>
> Regards,
>
> Hervé
>
> On 2019/12/08 23:35:03, Hervé BOUTEMY  wrote:
> > Hi,
> >
> > We solved 41 issues:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824=12331214=Text
> >
> > Staging repo:
> > https://repository.apache.org/content/repositories/maven-1544/
> >
> https://repository.apache.org/content/repositories/maven-1544/org/apache/maven/release/maven-release/3.0.0-M1/maven-release-3.0.0-M1-source-release.zip
> >
> > Source release checksum(s):
> > maven-release-3.0.0-M1-source-release.zip sha512:
> e4eb349406bf1c823a68c83af77084f4838d0b32a05aeae178c3cda5442baef69f9cf1704b19ca32daac68decaafdc86a661e767074315a1f0ac0b8e4633b853
> >
> > Staging site:
> >
> https://maven.apache.org/maven-release-archives/maven-release-LATEST/maven-release-plugin/
> > 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
> >
> > In addition to these instructions, I'd like voters to check Reproducible
> Build and report: to do so
> > 1. please install locally maven-buildinfo-plugin
> https://github.com/apache/maven-studies/tree/maven-buildinfo-plugin
> > 2. use JDK 7 and any Unix and build with "mvn -Papache-release,run-its
> -Dgpg.skip verify buildinfo:save"
> > If you are building on Windows, please add "-Dline.separator="\n""...
> > 3. check the content of
> maven-release-policies/maven-release-semver-policy/target/aggregate.buildinfo
> against reference in attachment
> > Your should get the same sha512, even if you don't have exactly the same
> OS or JDK version.
> > Please share your results
> >
> >
> > 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 Release Plugin version 3.0.0-M1

[Herve Boutemy]

nobody interested? Or I was too hard on testing reproducibility with JDK 7?
This reproducibility test is just an option, don't hesitate to not test
On next vote, I'll do the release with JDK 8, which will be easier for everyone 
to have on his computer...

Regards,

Hervé

On 2019/12/08 23:35:03, Hervé BOUTEMY  wrote: 
> Hi,
> 
> We solved 41 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824=12331214=Text
> 
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1544/
> https://repository.apache.org/content/repositories/maven-1544/org/apache/maven/release/maven-release/3.0.0-M1/maven-release-3.0.0-M1-source-release.zip
> 
> Source release checksum(s):
> maven-release-3.0.0-M1-source-release.zip sha512: 
> e4eb349406bf1c823a68c83af77084f4838d0b32a05aeae178c3cda5442baef69f9cf1704b19ca32daac68decaafdc86a661e767074315a1f0ac0b8e4633b853
> 
> Staging site:
> https://maven.apache.org/maven-release-archives/maven-release-LATEST/maven-release-plugin/
> 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
> 
> In addition to these instructions, I'd like voters to check Reproducible 
> Build and report: to do so
> 1. please install locally maven-buildinfo-plugin 
> https://github.com/apache/maven-studies/tree/maven-buildinfo-plugin
> 2. use JDK 7 and any Unix and build with "mvn -Papache-release,run-its 
> -Dgpg.skip verify buildinfo:save"
> If you are building on Windows, please add "-Dline.separator="\n""...
> 3. check the content of 
> maven-release-policies/maven-release-semver-policy/target/aggregate.buildinfo 
> against reference in attachment
> Your should get the same sha512, even if you don't have exactly the same OS 
> or JDK version.
> Please share your results
> 
> 
> Vote open for at least 72 hours.
> 
> [ ] +1
> [ ] +0
> [ ] -1

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

[VOTE] Release Apache Maven Release Plugin version 3.0.0-M1

[Hervé BOUTEMY]

Hi,

We solved 41 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824=12331214=Text

Staging repo:
https://repository.apache.org/content/repositories/maven-1544/
https://repository.apache.org/content/repositories/maven-1544/org/apache/maven/release/maven-release/3.0.0-M1/maven-release-3.0.0-M1-source-release.zip

Source release checksum(s):
maven-release-3.0.0-M1-source-release.zip sha512: 
e4eb349406bf1c823a68c83af77084f4838d0b32a05aeae178c3cda5442baef69f9cf1704b19ca32daac68decaafdc86a661e767074315a1f0ac0b8e4633b853

Staging site:
https://maven.apache.org/maven-release-archives/maven-release-LATEST/maven-release-plugin/
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

In addition to these instructions, I'd like voters to check Reproducible Build 
and report: to do so
1. please install locally maven-buildinfo-plugin 
https://github.com/apache/maven-studies/tree/maven-buildinfo-plugin
2. use JDK 7 and any Unix and build with "mvn -Papache-release,run-its 
-Dgpg.skip verify buildinfo:save"
If you are building on Windows, please add "-Dline.separator="\n""...
3. check the content of 
maven-release-policies/maven-release-semver-policy/target/aggregate.buildinfo 
against reference in attachment
Your should get the same sha512, even if you don't have exactly the same OS or 
JDK version.
Please share your results


Vote open for at least 72 hours.

[ ] +1
[ ] +0
[ ] -1buildinfo.version=1.0-SNAPSHOT

name=Maven Release
group-id=org.apache.maven.release
artifact-id=maven-release
version=3.0.0-M1

# source information
# TBD source.* artifact, url should be parameters
source.scm.uri=scm:git:https://gitbox.apache.org/repos/asf/maven-release.git
source.scm.tag=maven-release-3.0.0-M1

# build instructions
build-tool=mvn

# effective build environment information
java.version=1.7.0_161
java.vendor=Oracle Corporation
os.name=Linux

# Maven rebuild instructions and effective environment
mvn.rebuild-args=-DskipTests verify
mvn.version=Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
mvn.aggregate-buildinfo=org.apache.maven.release:maven-release-semver-policy:3.0.0-M1
mvn.build-root=org.apache.maven.release:maven-release:3.0.0-M1

# 1/6 org.apache.maven.release:maven-release
outputs.0.filename=maven-release-3.0.0-M1-site.xml
outputs.0.length=1435
outputs.0.checksums.sha512=ce15a8de4ac0e248119723ca493c6ef506c61aeb40cdc273ea1113a24d988b549f41fc7376371dbc6a47513de9d8e2132dcecec58e0645524ec0df63f94b28c6
outputs.1.filename=maven-release-3.0.0-M1-source-release.zip
outputs.1.length=1732665
outputs.1.checksums.sha512=e4eb349406bf1c823a68c83af77084f4838d0b32a05aeae178c3cda5442baef69f9cf1704b19ca32daac68decaafdc86a661e767074315a1f0ac0b8e4633b853

# 2/6 org.apache.maven.release:maven-release-api
outputs.0.filename=maven-release-api-3.0.0-M1.jar
outputs.0.length=26215
outputs.0.checksums.sha512=eecd5094383ec170c9a07228baa712e61245268a175df27958ffcc7146a72c93639a4c959f494e4f88b2e8adac8598ba238fd56318491a7ca443f3757cf4f25f
outputs.1.filename=maven-release-api-3.0.0-M1-sources.jar
outputs.1.length=33344
outputs.1.checksums.sha512=0d30b8e62b159f320fd8a05ad30d8c212b1e6c8dee0c0eb28da42776c5381c043665b7be2e12ba45ac412d0b93522bc14e38cf1ca8cef625d189473bdc0ea59d

# 3/6 org.apache.maven.release:maven-release-manager
outputs.0.filename=maven-release-manager-3.0.0-M1.jar
outputs.0.length=229959
outputs.0.checksums.sha512=289ef0aab61cf8c262f940d3d4240d8fcc45420084e80760b15d1690b11b3044da0b83e462fbe029c2af85da7817f2137ae8ee627d41770cb19be117717ea1d4
outputs.1.filename=maven-release-manager-3.0.0-M1-sources.jar
outputs.1.length=193052
outputs.1.checksums.sha512=71e14fb9fd3102d49493587c1814833a9083e18203fce0095ab9fa2dcd35d82dafb51fa56c0e10e5afa060e9d0daf338eb2965cf9569cd96f7dea32c78b83d4a

# 4/6 org.apache.maven.plugins:maven-release-plugin
outputs.0.filename=maven-release-plugin-3.0.0-M1.jar
outputs.0.length=58794
outputs.0.checksums.sha512=127a317b29821e51b2985c257c44e14b8f9bc4464c5628abf5b9035dc502df38805ee8e160a98666e33e38fee116930d3e65067dd78b6e4e9d89f68cd0498e58
outputs.1.filename=maven-release-plugin-3.0.0-M1-sources.jar
outputs.1.length=36952
outputs.1.checksums.sha512=42f46213dd3e199a0e1fdc28ff1ddde6a8777c74ba0429af71f8a7903df75d021f998d33b1082673a2f948ebd5fcd03076f1bc0a7b5662e4f8e0261403eb26a5

# 5/6 org.apache.maven.release:maven-release-oddeven-policy
outputs.0.filename=maven-release-oddeven-policy-3.0.0-M1.jar
outputs.0.length=11303
outputs.0.checksums.sha512=1f1abf53543f6faf88a26ccfe1f25a3f9b33a07675ad1d70413f702416d18c4fe0464284f4cc4ba499ed3a25c75538df0cac9c950dde85f9fb1016d74d17060c
outputs.1.filename=maven-release-oddeven-policy-3.0.0-M1-sources.jar
outputs.1.length=11202
outputs.1.checksums.sha512=3c964158f1b1f4d655657b8d8158cbbb1551f2b0c0f0e3ac6ef3a3d8e4e8c062a09b468f355773545e59ac6f53dd3b7b5ed36615568656849c1f9a256de6cea9

# 6/6 

Re: releasing Maven Release Plugin 3.0.0-M1

[Clemens Quoss]

Hi Hervé,

testing remove-scm-tag at our site (we use a customized version of 
maven-release where I already merged the code), i found this:


https://issues.apache.org/jira/browse/MRELEASE-1034

This is something between blocker and critical and i would like to have 
it in 3.0.0-M1.


When i provide the fix, will you pull it in?

I am not sure if i am able to provide an IT showing the issue, though, 
since i have only this week to provide the fix and haven't written ITs 
before.


Regards

Clemens

Am 01.12.2019 um 08:15 schrieb Hervé BOUTEMY:

merged, thank you for the PR

I'll do the release next week-end: if anybody wants to update something, you
have one week

here is the current state of the reference documentation:
https://maven.apache.org/maven-release-archives/maven-release-LATEST/

Regards,

Hervé

Le dimanche 24 novembre 2019, 16:16:44 CET Clemens Quoss a écrit :

Hi,

how about throwing in MRELEASE-229 as well?

Regards

Clemens

Am 24.11.2019 um 15:52 schrieb Hervé BOUTEMY:

Hi,

I fixed MRELEASE-1029 [1] for Reproducible Builds automatic update of
project.build.outputTimestamp property

I'd like to release maven-release-plugin.

But there are a few open Jira issues assigned to the release:
MRELEASE-973,
MRELEASE-955, MRELEASE-980, MRELEASE-993

Can everyone check if these issues can be fixed soon or if they should be
post- poned, please?

Regards,

Hervé


[1] https://issues.apache.org/jira/browse/MRELEASE-1029



-
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: releasing Maven Release Plugin 3.0.0-M1

[Tibor Digana]

guys, great job!
Finally, we will have a chance to check it out on GitBox in our releases.

On Sun, Dec 1, 2019 at 8:52 AM Enrico Olivelli  wrote:

> I would like to update the docs about preparationGoals, adding
> completionGoals and example about how to 'git add' files
>
> Not blocker
>
>
> Enrico
>
> Il dom 1 dic 2019, 08:15 Hervé BOUTEMY  ha scritto:
>
> > merged, thank you for the PR
> >
> > I'll do the release next week-end: if anybody wants to update something,
> > you
> > have one week
> >
> > here is the current state of the reference documentation:
> > https://maven.apache.org/maven-release-archives/maven-release-LATEST/
> >
> > Regards,
> >
> > Hervé
> >
> > Le dimanche 24 novembre 2019, 16:16:44 CET Clemens Quoss a écrit :
> > > Hi,
> > >
> > > how about throwing in MRELEASE-229 as well?
> > >
> > > Regards
> > >
> > > Clemens
> > >
> > > Am 24.11.2019 um 15:52 schrieb Hervé BOUTEMY:
> > > > Hi,
> > > >
> > > > I fixed MRELEASE-1029 [1] for Reproducible Builds automatic update of
> > > > project.build.outputTimestamp property
> > > >
> > > > I'd like to release maven-release-plugin.
> > > >
> > > > But there are a few open Jira issues assigned to the release:
> > > > MRELEASE-973,
> > > > MRELEASE-955, MRELEASE-980, MRELEASE-993
> > > >
> > > > Can everyone check if these issues can be fixed soon or if they
> should
> > be
> > > > post- poned, please?
> > > >
> > > > Regards,
> > > >
> > > > Hervé
> > > >
> > > >
> > > > [1] https://issues.apache.org/jira/browse/MRELEASE-1029
> > > >
> > > >
> > > >
> > > > -
> > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > > > For additional commands, e-mail: dev-h...@maven.apache.org
> >
> >
> >
> >
> >
>

Re: releasing Maven Release Plugin 3.0.0-M1

[Enrico Olivelli]

I would like to update the docs about preparationGoals, adding
completionGoals and example about how to 'git add' files

Not blocker


Enrico

Il dom 1 dic 2019, 08:15 Hervé BOUTEMY  ha scritto:

> merged, thank you for the PR
>
> I'll do the release next week-end: if anybody wants to update something,
> you
> have one week
>
> here is the current state of the reference documentation:
> https://maven.apache.org/maven-release-archives/maven-release-LATEST/
>
> Regards,
>
> Hervé
>
> Le dimanche 24 novembre 2019, 16:16:44 CET Clemens Quoss a écrit :
> > Hi,
> >
> > how about throwing in MRELEASE-229 as well?
> >
> > Regards
> >
> > Clemens
> >
> > Am 24.11.2019 um 15:52 schrieb Hervé BOUTEMY:
> > > Hi,
> > >
> > > I fixed MRELEASE-1029 [1] for Reproducible Builds automatic update of
> > > project.build.outputTimestamp property
> > >
> > > I'd like to release maven-release-plugin.
> > >
> > > But there are a few open Jira issues assigned to the release:
> > > MRELEASE-973,
> > > MRELEASE-955, MRELEASE-980, MRELEASE-993
> > >
> > > Can everyone check if these issues can be fixed soon or if they should
> be
> > > post- poned, please?
> > >
> > > Regards,
> > >
> > > Hervé
> > >
> > >
> > > [1] https://issues.apache.org/jira/browse/MRELEASE-1029
> > >
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > > For additional commands, e-mail: dev-h...@maven.apache.org
>
>
>
>
>

Re: releasing Maven Release Plugin 3.0.0-M1

[Hervé BOUTEMY]

merged, thank you for the PR

I'll do the release next week-end: if anybody wants to update something, you 
have one week

here is the current state of the reference documentation:
https://maven.apache.org/maven-release-archives/maven-release-LATEST/

Regards,

Hervé

Le dimanche 24 novembre 2019, 16:16:44 CET Clemens Quoss a écrit :
> Hi,
> 
> how about throwing in MRELEASE-229 as well?
> 
> Regards
> 
> Clemens
> 
> Am 24.11.2019 um 15:52 schrieb Hervé BOUTEMY:
> > Hi,
> > 
> > I fixed MRELEASE-1029 [1] for Reproducible Builds automatic update of
> > project.build.outputTimestamp property
> > 
> > I'd like to release maven-release-plugin.
> > 
> > But there are a few open Jira issues assigned to the release:
> > MRELEASE-973,
> > MRELEASE-955, MRELEASE-980, MRELEASE-993
> > 
> > Can everyone check if these issues can be fixed soon or if they should be
> > post- poned, please?
> > 
> > Regards,
> > 
> > Hervé
> > 
> > 
> > [1] https://issues.apache.org/jira/browse/MRELEASE-1029
> > 
> > 
> > 
> > -
> > 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: releasing Maven Release Plugin 3.0.0-M1

[Clemens Quoss]

Hi,

how about throwing in MRELEASE-229 as well?

Regards

Clemens

Am 24.11.2019 um 15:52 schrieb Hervé BOUTEMY:

Hi,

I fixed MRELEASE-1029 [1] for Reproducible Builds automatic update of
project.build.outputTimestamp property

I'd like to release maven-release-plugin.

But there are a few open Jira issues assigned to the release: MRELEASE-973,
MRELEASE-955, MRELEASE-980, MRELEASE-993

Can everyone check if these issues can be fixed soon or if they should be post-
poned, please?

Regards,

Hervé


[1] https://issues.apache.org/jira/browse/MRELEASE-1029



-
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

releasing Maven Release Plugin 3.0.0-M1

[Hervé BOUTEMY]

Hi,

I fixed MRELEASE-1029 [1] for Reproducible Builds automatic update of 
project.build.outputTimestamp property

I'd like to release maven-release-plugin.

But there are a few open Jira issues assigned to the release: MRELEASE-973, 
MRELEASE-955, MRELEASE-980, MRELEASE-993

Can everyone check if these issues can be fixed soon or if they should be post-
poned, please?

Regards,

Hervé


[1] https://issues.apache.org/jira/browse/MRELEASE-1029



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

Maven release plugin Xmx Xms environment variables

[Petar Tahchiev]

Hi all,

just a quick question. I have a project that I'm releasing using the
maven-release-plugin, but every time I call release:prepare the build fails
with OutofMemoryError. I tried setting the MAVEN_OPTS to "-Xmx2G" but
honestly I don't think it has any effect because after the build ends I get
this file

-rw---  1 tomcat tomcat 3.3G Oct  1 09:59 java_pid15462.hprof

which clearly is 3.3G

I was looking at the code of the maven-release-plugin and I don't see a way
to specify the java memory options of the forked process. Is this a missing
feature? Or have I missed something? How can one specify the jvmArgs of the
forked process?

Thank you.
-- 
Regards, Petar!
Karlovo, Bulgaria.
---
Public PGP Key at:
http://pgp.mit.edu:11371/pks/lookup?op=get=0x19658550C3110611
Key Fingerprint: A369 A7EE 61BC 93A3 CDFF  55A5 1965 8550 C311 0611

Re: [maven-parent] 02/02: [maven-release-plugin] rollback the release of maven-parent-TEST-34

[Hervé BOUTEMY]

sorry, I completely did fail my tests, which should never had been pushed to 
Apache master...
:(

Regards,

Hervé

Le dimanche 11 novembre 2018, 20:36:43 CET hbout...@apache.org a écrit :
> This is an automated email from the ASF dual-hosted git repository.
> 
> hboutemy pushed a commit to branch master
> in repository https://gitbox.apache.org/repos/asf/maven-parent.git
> 
> commit 9782eabad3cc07473924723d9ecfdc8b821b01a9
> Author: Hervé Boutemy 
> AuthorDate: Sun Nov 11 20:36:40 2018 +0100
> 
> [maven-release-plugin] rollback the release of maven-parent-TEST-34
> ---
>  apache-resource-bundles/pom.xml | 2 +-
>  doxia-tools/pom.xml | 2 +-
>  maven-plugins/pom.xml   | 2 +-
>  maven-shared-components/pom.xml | 2 +-
>  maven-skins/pom.xml | 2 +-
>  pom.xml | 8 
>  6 files changed, 9 insertions(+), 9 deletions(-)
> 
> diff --git a/apache-resource-bundles/pom.xml
> b/apache-resource-bundles/pom.xml index cd3e116..cb4aa0d 100644
> --- a/apache-resource-bundles/pom.xml
> +++ b/apache-resource-bundles/pom.xml
> @@ -25,7 +25,7 @@
>
>  org.apache.maven
>  maven-parent
> -TEST-35-SNAPSHOT
> +34-SNAPSHOT
>  ../pom.xml
>
> 
> diff --git a/doxia-tools/pom.xml b/doxia-tools/pom.xml
> index 7218ca9..145cd95 100644
> --- a/doxia-tools/pom.xml
> +++ b/doxia-tools/pom.xml
> @@ -25,7 +25,7 @@ under the License.
>
>  org.apache.maven
>  maven-parent
> -TEST-35-SNAPSHOT
> +34-SNAPSHOT
>  ../pom.xml
>
> 
> diff --git a/maven-plugins/pom.xml b/maven-plugins/pom.xml
> index 8d1c687..b224c86 100644
> --- a/maven-plugins/pom.xml
> +++ b/maven-plugins/pom.xml
> @@ -24,7 +24,7 @@ under the License.
>
>  org.apache.maven
>  maven-parent
> -TEST-35-SNAPSHOT
> +34-SNAPSHOT
>  ../pom.xml
>
> 
> diff --git a/maven-shared-components/pom.xml
> b/maven-shared-components/pom.xml index cfd3245..d96a5a5 100644
> --- a/maven-shared-components/pom.xml
> +++ b/maven-shared-components/pom.xml
> @@ -25,7 +25,7 @@ under the License.
>
>  org.apache.maven
>  maven-parent
> -TEST-35-SNAPSHOT
> +34-SNAPSHOT
>  ../pom.xml
>
> 
> diff --git a/maven-skins/pom.xml b/maven-skins/pom.xml
> index fd0df50..1ec4d66 100644
> --- a/maven-skins/pom.xml
> +++ b/maven-skins/pom.xml
> @@ -25,7 +25,7 @@ under the License.
>
>  org.apache.maven
>  maven-parent
> -TEST-35-SNAPSHOT
> +34-SNAPSHOT
>  ../pom.xml
>
> 
> diff --git a/pom.xml b/pom.xml
> index 19dd2f3..454f589 100644
> --- a/pom.xml
> +++ b/pom.xml
> @@ -32,7 +32,7 @@ under the License.
> 
>org.apache.maven
>maven-parent
> -  TEST-35-SNAPSHOT
> +  34-SNAPSHOT
>pom
> 
>Apache Maven
> @@ -847,9 +847,9 @@ under the License.
>
> 
>
> -   
> scm:git:https://github.com/hboutemy/maven-parent.git n> -   
> scm:git:https://github.com/hboutemy/maven-parent.git developerConnection> -   
> https://github.com/hboutemy/maven-parent/tree/${project.scm.tag}
> +   
> scm:git:https://gitbox.apache.org/repos/asf/maven-parent.git onnection> +   
> scm:git:https://gitbox.apache.org/repos/asf/maven-pare
> nt.git +   
> https://github.com/apache/maven-parent/tree/${project.scm.tag}
> HEAD
>





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

[maven-release-plugin] Passing additional parameters

[Naveen Swamy]

Hello there,

I have a question regarding maven release plugin. We use codehaus
native-plugin to build jni, I want to pass the cflags during release phase.
However I see that I am unable to pass any of the arguments through release
plugin. Any experience or pointers would help
this is mvn command which we call through a makefile similar to
https://github.com/apache/incubator-mxnet/blob/48d60908a1fa42364a829ac90133d28dd0998219/Makefile#L579
```
scalareleasedryrun:
(cd $(ROOTDIR)/scala-package; \
mvn -X release:prepare -DdryRun=true -DautoVersionSubmodules=true \
-P$(SCALA_PKG_PROFILE),$(SCALA_VERSION_PROFILE) \
-Darguments=-DskipTests -Dcxx="$(CXX)" \
-Drelease.cflags="$(CFLAGS)" -Dldflags="$(LDFLAGS)" \
-Dlddeps="$(LIB_DEP) $(ROOTDIR)/lib/libmxnet.a")
```
The parent pom file is here
https://github.com/apache/incubator-mxnet/blob/master/scala-package/pom.xml
and the pom file to compile native code is here
https://github.com/apache/incubator-mxnet/blob/master/scala-package/init-native/osx-x86_64/pom.xml#L59

I see that cflags variable used in the native pom.xml is coming as null
```
[INFO] [INFO] --- native-maven-plugin:1.0-alpha-9:compile (default-compile)
@ libmxnet-init-scala-osx-x86_64 ---
[INFO] [DEBUG] Configuring mojo
org.codehaus.mojo:native-maven-plugin:1.0-alpha-9:compile from plugin realm
ClassRealm[extension>org.codehaus.mojo:native-maven-plugin:1.0-alpha-9,
parent: sun.misc.Launcher$AppClassLoader@42a57993]
[INFO] [DEBUG] Configuring mojo
'org.codehaus.mojo:native-maven-plugin:1.0-alpha-9:compile' with basic
configurator -->
[INFO] [DEBUG]   (f) compilerEndOptions = [-I../../../include, null]
[INFO] [DEBUG]   (f) compilerOutputDirectory =
/Users/wamy/nswamy/deepengine/workspace/incubator-mxnet/scala-package/init-native/osx-x86_64/target/objs
[INFO] [DEBUG]   (f) compilerProvider = generic-classic
[INFO] [DEBUG]   (f) compilerStartOptions = [-std=c++0x]
[INFO] [DEBUG]   (f) dependencyIncludeDirectory =
/Users/wamy/nswamy/deepengine/workspace/incubator-mxnet/scala-package/init-native/osx-x86_64/target/native/include
[INFO] [DEBUG]   (f) javahOS = darwin
[INFO] [DEBUG]   (f) jdkIncludePath =
/Library/Java/JavaVirtualMachines/jdk1.8.0_171.jdk/Contents/Home/jre/../include
[INFO] [DEBUG]   (f) numberOfConcurrentCompilation = 1
[INFO] [DEBUG]   (f) project = MavenProject:
org.apache.mxnet:libmxnet-init-scala-osx-x86_64:1.2.0-SNAPSHOT @
/Users/wamy/nswamy/deepengine/workspace/incubator-mxnet/scala-package/init-native/osx-x86_64/pom.xml
[INFO] [DEBUG]   (s) directory =
/Users/wamy/nswamy/deepengine/workspace/incubator-mxnet/scala-package/init-native/src/main/native
[INFO] [DEBUG]   (s) fileNames = [org_apache_mxnet_init_native_c_api.cc]
[INFO] [DEBUG]   (f) sources =
[org.codehaus.mojo.natives.NativeSources@1e01b195]
[INFO] [DEBUG]   (f) workingDirectory =
/Users/wamy/nswamy/deepengine/workspace/incubator-mxnet/scala-package/init-native/osx-x86_64

```

I have already tried pass with -Darguments, create properties corresponding
to the flags, etc.,


Appreciate pointers and advise?

-Naveen

Re: Maven release plugin

[Robert Scholte]

My current proposal:

the start situation is a folder containing several checked out projects.
the folder contains an aggregator pom, which is NOT under version control.

release:prepare should start as normal, but it should end with a  
commit+tag+commit on every checked out folder.


release:perform uses target/checkout, where you copy the aggregator-pom.
And you also check out the projects by tag. Ensure they're using the same  
directory-name.


That should be about it. The wording is probably easier compared to the  
implementation.


Have a look at project-utils[1]. It should help with determining what kind  
of project every pom is.
It hasn't been released yet, but it was written to help the  
maven-release-plugin


I hope this makes sense,
Robert

[1] http://svn.apache.org/repos/asf/maven/shared/trunk/maven-project-utils/

On Tue, 21 Nov 2017 10:31:07 +0100, Petar Tahchiev <paranoia...@gmail.com>  
wrote:



Hi Robert,
i'll give it a try. Can you please summarize what needs to be done, or
perhaps point me the right direction?

2017-11-20 21:32 GMT+02:00 Robert Scholte <rfscho...@apache.org>:


Hi Petar,

would be great if you could pick this up.
There's enough work I want to finish first, maven-release-plugin is not
one of them right now.

thanks,
Robert


On Mon, 20 Nov 2017 18:38:56 +0100, Petar Tahchiev  
<paranoia...@gmail.com>

wrote:

Hi Robert,


any updates on the release-aggregator? Is there anything I can do to  
help?


2017-06-27 22:43 GMT+03:00 Robert Scholte <rfscho...@apache.org>:

Hi Petar,


This is a clear sign that ${project} should not be used to resolve  
this.
Instead the pom should be analyzed again and if there's a system  
property

matching the parent, it should be replaced before loading the parent.
That'll require quite some new lines of code :)
The suggested release-aggregator will require this same feature, so
sooner
or later this must be fixed.

Robert


On Tue, 27 Jun 2017 09:50:37 +0200, Petar Tahchiev <
paranoia...@gmail.com>
wrote:

Hey guys,



my pull-request worked fine to not show the prompt to specify a  
version.

However, it fails to update snapshot dependency versions when you
resolve
the parent to a concrete version.
Particularly in my case:


[BOM]
 /\
 [PLATFORM]  [DEMO_STORE]
   -module1 - platform:module1
   -module2 - platform:module2
     .
   - moduleN- platform:moduleN

The [BOM] defines in dependencyManagement section all the versions of
the
modules of the [PLATFORM]. Then the [DEMO_STORE] can reference them
without
specifying a version. During release what I do is I first release the
[BOM], then release the [PLATFORM] and up to here I see no problems.  
But
then I try to release the DEMO_STORE] and even though I specify on  
the

command line the version of the parent [BOM]:

-Ddependency.com.nemesis:bom.release=1.5.2.RELEASE
-Ddependency.com.nemesis:bom.development=1.5.3.BUILD-SNAPSHOT


it still asks me for versions of dependencies which are specified in  
the
released [BOM]. I tried patching the code and specifying a new  
version

of
the parent

project.getParentArtifact().setVersion("1.5.2.RELEASE")

just to see if it works, but the problem is that the dependencies in  
the

project are already resolved: when I call project.getDependencies() I
get
the SNAPSHOT versions.

Is there any way to reload the project model after I specify a new
parentVersion()? So that It understands the [BOM] is no longer a
snapshot
version.

Thanks

2017-06-25 12:11 GMT+03:00 Robert Scholte <rfscho...@apache.org>:

MRELEASE-362[1] is probably the matching issue.


Be aware that some are talking about tagging every module. In most
situations I don't like that. If the structure is hierarchical and  
the

root
is tagged, then all the modules are already tagged. All tags must be
checked out during release:perform, keep that in mind.
I see options with a flat structure and with the release-aggregator.

Robert

[1] https://issues.apache.org/jira/browse/MRELEASE-362


On Sat, 24 Jun 2017 22:59:48 +0200, Petar Tahchiev <
paranoia...@gmail.com>
wrote:

Hi Paul,



I think you misunderstood. The [BOM] is a separate project and the
[PLATFORM] and [DEMO_STORE] are also separate projects, both of  
which

declare as their parent the [BOM].

@Robert: I have added the test-case:
https://github.com/apache/maven-release/pull/18/commits/
Release-aggregator is exactly what's missing. Is there an issue I  
can

subscribe and track?


2017-06-24 14:15 GMT+03:00 Robert Scholte <rfscho...@apache.org>:

What we're still missing is a release-aggregator, which can release

multiple release-roots at once. That would probably be the  
preferred

fix,
the suggested patch is just an easy work-around.
It is still on my todo-list.

Robert


On Sat, 24

Re: Maven release plugin

[Petar Tahchiev]

Hi Robert,
i'll give it a try. Can you please summarize what needs to be done, or
perhaps point me the right direction?

2017-11-20 21:32 GMT+02:00 Robert Scholte <rfscho...@apache.org>:

> Hi Petar,
>
> would be great if you could pick this up.
> There's enough work I want to finish first, maven-release-plugin is not
> one of them right now.
>
> thanks,
> Robert
>
>
> On Mon, 20 Nov 2017 18:38:56 +0100, Petar Tahchiev <paranoia...@gmail.com>
> wrote:
>
> Hi Robert,
>>
>> any updates on the release-aggregator? Is there anything I can do to help?
>>
>> 2017-06-27 22:43 GMT+03:00 Robert Scholte <rfscho...@apache.org>:
>>
>> Hi Petar,
>>>
>>> This is a clear sign that ${project} should not be used to resolve this.
>>> Instead the pom should be analyzed again and if there's a system property
>>> matching the parent, it should be replaced before loading the parent.
>>> That'll require quite some new lines of code :)
>>> The suggested release-aggregator will require this same feature, so
>>> sooner
>>> or later this must be fixed.
>>>
>>> Robert
>>>
>>>
>>> On Tue, 27 Jun 2017 09:50:37 +0200, Petar Tahchiev <
>>> paranoia...@gmail.com>
>>> wrote:
>>>
>>> Hey guys,
>>>
>>>>
>>>> my pull-request worked fine to not show the prompt to specify a version.
>>>> However, it fails to update snapshot dependency versions when you
>>>> resolve
>>>> the parent to a concrete version.
>>>> Particularly in my case:
>>>>
>>>>
>>>> [BOM]
>>>>  /\
>>>>  [PLATFORM]  [DEMO_STORE]
>>>>-module1 - platform:module1
>>>>-module2 - platform:module2
>>>>  .
>>>>- moduleN- platform:moduleN
>>>>
>>>> The [BOM] defines in dependencyManagement section all the versions of
>>>> the
>>>> modules of the [PLATFORM]. Then the [DEMO_STORE] can reference them
>>>> without
>>>> specifying a version. During release what I do is I first release the
>>>> [BOM], then release the [PLATFORM] and up to here I see no problems. But
>>>> then I try to release the DEMO_STORE] and even though I specify on the
>>>> command line the version of the parent [BOM]:
>>>>
>>>> -Ddependency.com.nemesis:bom.release=1.5.2.RELEASE
>>>> -Ddependency.com.nemesis:bom.development=1.5.3.BUILD-SNAPSHOT
>>>>
>>>>
>>>> it still asks me for versions of dependencies which are specified in the
>>>> released [BOM]. I tried patching the code and specifying a new version
>>>> of
>>>> the parent
>>>>
>>>> project.getParentArtifact().setVersion("1.5.2.RELEASE")
>>>>
>>>> just to see if it works, but the problem is that the dependencies in the
>>>> project are already resolved: when I call project.getDependencies() I
>>>> get
>>>> the SNAPSHOT versions.
>>>>
>>>> Is there any way to reload the project model after I specify a new
>>>> parentVersion()? So that It understands the [BOM] is no longer a
>>>> snapshot
>>>> version.
>>>>
>>>> Thanks
>>>>
>>>> 2017-06-25 12:11 GMT+03:00 Robert Scholte <rfscho...@apache.org>:
>>>>
>>>> MRELEASE-362[1] is probably the matching issue.
>>>>
>>>>> Be aware that some are talking about tagging every module. In most
>>>>> situations I don't like that. If the structure is hierarchical and the
>>>>> root
>>>>> is tagged, then all the modules are already tagged. All tags must be
>>>>> checked out during release:perform, keep that in mind.
>>>>> I see options with a flat structure and with the release-aggregator.
>>>>>
>>>>> Robert
>>>>>
>>>>> [1] https://issues.apache.org/jira/browse/MRELEASE-362
>>>>>
>>>>>
>>>>> On Sat, 24 Jun 2017 22:59:48 +0200, Petar Tahchiev <
>>>>> paranoia...@gmail.com>
>>>>> wrote:
>>>>>
>>>>> Hi Paul,
>>>>>
>>>>>
>>>>>> I think you misunderstood. T

Re: Maven release plugin

[Robert Scholte]

Hi Petar,

would be great if you could pick this up.
There's enough work I want to finish first, maven-release-plugin is not  
one of them right now.


thanks,
Robert

On Mon, 20 Nov 2017 18:38:56 +0100, Petar Tahchiev <paranoia...@gmail.com>  
wrote:



Hi Robert,

any updates on the release-aggregator? Is there anything I can do to  
help?


2017-06-27 22:43 GMT+03:00 Robert Scholte <rfscho...@apache.org>:


Hi Petar,

This is a clear sign that ${project} should not be used to resolve this.
Instead the pom should be analyzed again and if there's a system  
property

matching the parent, it should be replaced before loading the parent.
That'll require quite some new lines of code :)
The suggested release-aggregator will require this same feature, so  
sooner

or later this must be fixed.

Robert


On Tue, 27 Jun 2017 09:50:37 +0200, Petar Tahchiev  
<paranoia...@gmail.com>

wrote:

Hey guys,


my pull-request worked fine to not show the prompt to specify a  
version.
However, it fails to update snapshot dependency versions when you  
resolve

the parent to a concrete version.
Particularly in my case:


[BOM]
 /\
 [PLATFORM]  [DEMO_STORE]
   -module1 - platform:module1
   -module2 - platform:module2
     .
   - moduleN- platform:moduleN

The [BOM] defines in dependencyManagement section all the versions of  
the

modules of the [PLATFORM]. Then the [DEMO_STORE] can reference them
without
specifying a version. During release what I do is I first release the
[BOM], then release the [PLATFORM] and up to here I see no problems.  
But

then I try to release the DEMO_STORE] and even though I specify on the
command line the version of the parent [BOM]:

-Ddependency.com.nemesis:bom.release=1.5.2.RELEASE
-Ddependency.com.nemesis:bom.development=1.5.3.BUILD-SNAPSHOT


it still asks me for versions of dependencies which are specified in  
the
released [BOM]. I tried patching the code and specifying a new version  
of

the parent

project.getParentArtifact().setVersion("1.5.2.RELEASE")

just to see if it works, but the problem is that the dependencies in  
the
project are already resolved: when I call project.getDependencies() I  
get

the SNAPSHOT versions.

Is there any way to reload the project model after I specify a new
parentVersion()? So that It understands the [BOM] is no longer a  
snapshot

version.

Thanks

2017-06-25 12:11 GMT+03:00 Robert Scholte <rfscho...@apache.org>:

MRELEASE-362[1] is probably the matching issue.

Be aware that some are talking about tagging every module. In most
situations I don't like that. If the structure is hierarchical and the
root
is tagged, then all the modules are already tagged. All tags must be
checked out during release:perform, keep that in mind.
I see options with a flat structure and with the release-aggregator.

Robert

[1] https://issues.apache.org/jira/browse/MRELEASE-362


On Sat, 24 Jun 2017 22:59:48 +0200, Petar Tahchiev <
paranoia...@gmail.com>
wrote:

Hi Paul,



I think you misunderstood. The [BOM] is a separate project and the
[PLATFORM] and [DEMO_STORE] are also separate projects, both of which
declare as their parent the [BOM].

@Robert: I have added the test-case:
https://github.com/apache/maven-release/pull/18/commits/
Release-aggregator is exactly what's missing. Is there an issue I can
subscribe and track?


2017-06-24 14:15 GMT+03:00 Robert Scholte <rfscho...@apache.org>:

What we're still missing is a release-aggregator, which can release


multiple release-roots at once. That would probably be the preferred
fix,
the suggested patch is just an easy work-around.
It is still on my todo-list.

Robert


On Sat, 24 Jun 2017 12:42:22 +0200, Paul Hammant <p...@hammant.org>
wrote:

Easy to fix.  Have a profile 'platformOnly' in the root module (I'm  
not


sure if 'BOM' should mean anything to me) that includes only  
'platform'

as
a child module.

   mvn release:prepare -PplatformOnly # etc

Later when you're ready to do the demo store release, use another
(from
root):

   mvn release:prepare -PdemoOnly # etc

Of course, you man not need to stuff demo in your
Artifactory/Nexus/etc
in
which case just do your deploy fu after an 'install' w/o the  
release

plugin
involved or that second profile.

- Paul


On Sat, Jun 24, 2017 at 2:58 AM, Petar Tahchiev <
paranoia...@gmail.com>
wrote:

Hey guys,



I'm facing a number of challenges when I release the project at my
company.
Here's my setup:

[BOM]
 /\
 [PLATFORM]  [DEMO_STORE]

I have a master BOM project which holds all the version as defined
properties. This BOM is the parent to two other projects -  
[PLATFORM]

and
[DEMO_STORE], The [PLATFORM] is a project with more than 60  
modules

inside,
and

Re: Maven release plugin

[Petar Tahchiev]

Hi Robert,

any updates on the release-aggregator? Is there anything I can do to help?

2017-06-27 22:43 GMT+03:00 Robert Scholte :

> Hi Petar,
>
> This is a clear sign that ${project} should not be used to resolve this.
> Instead the pom should be analyzed again and if there's a system property
> matching the parent, it should be replaced before loading the parent.
> That'll require quite some new lines of code :)
> The suggested release-aggregator will require this same feature, so sooner
> or later this must be fixed.
>
> Robert
>
>
> On Tue, 27 Jun 2017 09:50:37 +0200, Petar Tahchiev 
> wrote:
>
> Hey guys,
>>
>> my pull-request worked fine to not show the prompt to specify a version.
>> However, it fails to update snapshot dependency versions when you resolve
>> the parent to a concrete version.
>> Particularly in my case:
>>
>>
>> [BOM]
>>  /\
>>  [PLATFORM]  [DEMO_STORE]
>>-module1 - platform:module1
>>-module2 - platform:module2
>>  .
>>- moduleN- platform:moduleN
>>
>> The [BOM] defines in dependencyManagement section all the versions of the
>> modules of the [PLATFORM]. Then the [DEMO_STORE] can reference them
>> without
>> specifying a version. During release what I do is I first release the
>> [BOM], then release the [PLATFORM] and up to here I see no problems. But
>> then I try to release the DEMO_STORE] and even though I specify on the
>> command line the version of the parent [BOM]:
>>
>> -Ddependency.com.nemesis:bom.release=1.5.2.RELEASE
>> -Ddependency.com.nemesis:bom.development=1.5.3.BUILD-SNAPSHOT
>>
>>
>> it still asks me for versions of dependencies which are specified in the
>> released [BOM]. I tried patching the code and specifying a new version of
>> the parent
>>
>> project.getParentArtifact().setVersion("1.5.2.RELEASE")
>>
>> just to see if it works, but the problem is that the dependencies in the
>> project are already resolved: when I call project.getDependencies() I get
>> the SNAPSHOT versions.
>>
>> Is there any way to reload the project model after I specify a new
>> parentVersion()? So that It understands the [BOM] is no longer a snapshot
>> version.
>>
>> Thanks
>>
>> 2017-06-25 12:11 GMT+03:00 Robert Scholte :
>>
>> MRELEASE-362[1] is probably the matching issue.
>>> Be aware that some are talking about tagging every module. In most
>>> situations I don't like that. If the structure is hierarchical and the
>>> root
>>> is tagged, then all the modules are already tagged. All tags must be
>>> checked out during release:perform, keep that in mind.
>>> I see options with a flat structure and with the release-aggregator.
>>>
>>> Robert
>>>
>>> [1] https://issues.apache.org/jira/browse/MRELEASE-362
>>>
>>>
>>> On Sat, 24 Jun 2017 22:59:48 +0200, Petar Tahchiev <
>>> paranoia...@gmail.com>
>>> wrote:
>>>
>>> Hi Paul,
>>>

 I think you misunderstood. The [BOM] is a separate project and the
 [PLATFORM] and [DEMO_STORE] are also separate projects, both of which
 declare as their parent the [BOM].

 @Robert: I have added the test-case:
 https://github.com/apache/maven-release/pull/18/commits/
 Release-aggregator is exactly what's missing. Is there an issue I can
 subscribe and track?


 2017-06-24 14:15 GMT+03:00 Robert Scholte :

 What we're still missing is a release-aggregator, which can release

> multiple release-roots at once. That would probably be the preferred
> fix,
> the suggested patch is just an easy work-around.
> It is still on my todo-list.
>
> Robert
>
>
> On Sat, 24 Jun 2017 12:42:22 +0200, Paul Hammant 
> wrote:
>
> Easy to fix.  Have a profile 'platformOnly' in the root module (I'm not
>
> sure if 'BOM' should mean anything to me) that includes only 'platform'
>> as
>> a child module.
>>
>>mvn release:prepare -PplatformOnly # etc
>>
>> Later when you're ready to do the demo store release, use another
>> (from
>> root):
>>
>>mvn release:prepare -PdemoOnly # etc
>>
>> Of course, you man not need to stuff demo in your
>> Artifactory/Nexus/etc
>> in
>> which case just do your deploy fu after an 'install' w/o the release
>> plugin
>> involved or that second profile.
>>
>> - Paul
>>
>>
>> On Sat, Jun 24, 2017 at 2:58 AM, Petar Tahchiev <
>> paranoia...@gmail.com>
>> wrote:
>>
>> Hey guys,
>>
>>
>>> I'm facing a number of challenges when I release the project at my
>>> company.
>>> Here's my setup:
>>>
>>> [BOM]
>>>  /\
>>>  [PLATFORM] 

Re: maven-release-plugin and signing artifacts

[Robert Scholte]

On Sat, 05 Aug 2017 22:05:22 +0200, Karl Heinz Marbaise  
<khmarba...@gmx.de> wrote:



Hi Robert,

On 04/08/17 10:55, Robert Scholte wrote:

Hi Karl Heinz,
 this can happen when the plugin configuration contains a fixed value  
for arguments, i.e

-Dkey=value
 If you want arguments to be extended via commandline argument, you  
need to do this:

 -Dkey=value ${arguments}
 




Thanks for your explanations...

So that means the configuration for the maven-release-plugin must be  
done before to support expanding the arguments like I expected..


So on the other hand the maven-release-plugin documentation for the  
arguments property:

http://maven.apache.org/maven-release/maven-release-plugin/prepare-mojo.html

say only: "Additional arguments to pass to the Maven executions,  
separated by spaces.".


So I have expected to simply set the arguments property and the  
additional parameters would have been added to the Maven invocation..


So this looks like a documentation issue from my point of view...what do  
you think ?


This has nothing to do with the maven-release-plugin, this is how  
parameter resolution works in general.

I think you've been fooled by plexus-utils release compared to asf, see:

https://github.com/apache/maven-pom/blob/trunk/asf/pom.xml#L89
https://github.com/apache/maven-pom/blob/trunk/asf/pom.xml#L212

Robert



Kind regards
Karl Heinz Marbaise




 Robert
 On Thu, 03 Aug 2017 19:57:10 +0200, Karl Heinz Marbaise  
<khmarba...@gmx.de> wrote:



Hi,

I have tried to make a release of the plexus-utils and was faced with  
a problem...which I currently don't understand...


I have started the release with:

mvn -Darguments='-Dgpg.keyname=kama' release:prepare release:perform


So I thought the gpg.keyname property will be given to the called  
maven process which will run the part in prepare...but based on my  
tests it looks like it is not the case...cause the given "arguments"  
not transfered or added to the Maven sub process...(Ok I though might  
be caused by an older maven-release-plugin so I tested the same with  
the newest 2.5.3 but the result keeps the same)..


Has someone being faced with the same situation or Am I doing  
something wrong / Or misunderstand a thing here?


A work a round at the moment is to use:

mvn -DpreparationGoals='-Dgpg.keyname=kama clean verify'  
release:prepare release:perform


instead...but from my point of view this does not feel right...


Kind regards
Karl Heinz Marbaise


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


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

Re: maven-release-plugin and signing artifacts

[Karl Heinz Marbaise]

Hi Robert,

On 04/08/17 10:55, Robert Scholte wrote:

Hi Karl Heinz,

this can happen when the plugin configuration contains a fixed value for 
arguments, i.e

-Dkey=value

If you want arguments to be extended via commandline argument, you need 
to do this:


-Dkey=value ${arguments}






Thanks for your explanations...

So that means the configuration for the maven-release-plugin must be 
done before to support expanding the arguments like I expected..


So on the other hand the maven-release-plugin documentation for the 
arguments property:

http://maven.apache.org/maven-release/maven-release-plugin/prepare-mojo.html

say only: "Additional arguments to pass to the Maven executions, 
separated by spaces.".


So I have expected to simply set the arguments property and the 
additional parameters would have been added to the Maven invocation..


So this looks like a documentation issue from my point of view...what do 
you think ?


Kind regards
Karl Heinz Marbaise





Robert

On Thu, 03 Aug 2017 19:57:10 +0200, Karl Heinz Marbaise 
<khmarba...@gmx.de> wrote:



Hi,

I have tried to make a release of the plexus-utils and was faced with 
a problem...which I currently don't understand...


I have started the release with:

mvn -Darguments='-Dgpg.keyname=kama' release:prepare release:perform


So I thought the gpg.keyname property will be given to the called 
maven process which will run the part in prepare...but based on my 
tests it looks like it is not the case...cause the given "arguments" 
not transfered or added to the Maven sub process...(Ok I though might 
be caused by an older maven-release-plugin so I tested the same with 
the newest 2.5.3 but the result keeps the same)..


Has someone being faced with the same situation or Am I doing 
something wrong / Or misunderstand a thing here?


A work a round at the moment is to use:

mvn -DpreparationGoals='-Dgpg.keyname=kama clean verify' 
release:prepare release:perform


instead...but from my point of view this does not feel right...


Kind regards
Karl Heinz Marbaise


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

Re: maven-release-plugin and signing artifacts

[Robert Scholte]

Hi Karl Heinz,

this can happen when the plugin configuration contains a fixed value for  
arguments, i.e

-Dkey=value

If you want arguments to be extended via commandline argument, you need to  
do this:


-Dkey=value ${arguments}


   


Robert

On Thu, 03 Aug 2017 19:57:10 +0200, Karl Heinz Marbaise  
<khmarba...@gmx.de> wrote:



Hi,

I have tried to make a release of the plexus-utils and was faced with a  
problem...which I currently don't understand...


I have started the release with:

mvn -Darguments='-Dgpg.keyname=kama' release:prepare release:perform


So I thought the gpg.keyname property will be given to the called maven  
process which will run the part in prepare...but based on my tests it  
looks like it is not the case...cause the given "arguments" not  
transfered or added to the Maven sub process...(Ok I though might be  
caused by an older maven-release-plugin so I tested the same with the  
newest 2.5.3 but the result keeps the same)..


Has someone being faced with the same situation or Am I doing something  
wrong / Or misunderstand a thing here?


A work a round at the moment is to use:

mvn -DpreparationGoals='-Dgpg.keyname=kama clean verify' release:prepare  
release:perform


instead...but from my point of view this does not feel right...


Kind regards
Karl Heinz Marbaise

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


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

maven-release-plugin and signing artifacts

[Karl Heinz Marbaise]

Hi,

I have tried to make a release of the plexus-utils and was faced with a 
problem...which I currently don't understand...


I have started the release with:

mvn -Darguments='-Dgpg.keyname=kama' release:prepare release:perform


So I thought the gpg.keyname property will be given to the called maven 
process which will run the part in prepare...but based on my tests it 
looks like it is not the case...cause the given "arguments" not 
transfered or added to the Maven sub process...(Ok I though might be 
caused by an older maven-release-plugin so I tested the same with the 
newest 2.5.3 but the result keeps the same)..


Has someone being faced with the same situation or Am I doing something 
wrong / Or misunderstand a thing here?


A work a round at the moment is to use:

mvn -DpreparationGoals='-Dgpg.keyname=kama clean verify' release:prepare 
release:perform


instead...but from my point of view this does not feel right...


Kind regards
Karl Heinz Marbaise

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

Re: Maven release plugin

[Robert Scholte]

Hi Petar,

This is a clear sign that ${project} should not be used to resolve this.
Instead the pom should be analyzed again and if there's a system property  
matching the parent, it should be replaced before loading the parent.  
That'll require quite some new lines of code :)
The suggested release-aggregator will require this same feature, so sooner  
or later this must be fixed.


Robert

On Tue, 27 Jun 2017 09:50:37 +0200, Petar Tahchiev   
wrote:



Hey guys,

my pull-request worked fine to not show the prompt to specify a version.
However, it fails to update snapshot dependency versions when you resolve
the parent to a concrete version.
Particularly in my case:


[BOM]
 /\
 [PLATFORM]  [DEMO_STORE]
   -module1 - platform:module1
   -module2 - platform:module2
     .
   - moduleN- platform:moduleN

The [BOM] defines in dependencyManagement section all the versions of the
modules of the [PLATFORM]. Then the [DEMO_STORE] can reference them  
without

specifying a version. During release what I do is I first release the
[BOM], then release the [PLATFORM] and up to here I see no problems. But
then I try to release the DEMO_STORE] and even though I specify on the
command line the version of the parent [BOM]:

-Ddependency.com.nemesis:bom.release=1.5.2.RELEASE
-Ddependency.com.nemesis:bom.development=1.5.3.BUILD-SNAPSHOT


it still asks me for versions of dependencies which are specified in the
released [BOM]. I tried patching the code and specifying a new version of
the parent

project.getParentArtifact().setVersion("1.5.2.RELEASE")

just to see if it works, but the problem is that the dependencies in the
project are already resolved: when I call project.getDependencies() I get
the SNAPSHOT versions.

Is there any way to reload the project model after I specify a new
parentVersion()? So that It understands the [BOM] is no longer a snapshot
version.

Thanks

2017-06-25 12:11 GMT+03:00 Robert Scholte :


MRELEASE-362[1] is probably the matching issue.
Be aware that some are talking about tagging every module. In most
situations I don't like that. If the structure is hierarchical and the  
root

is tagged, then all the modules are already tagged. All tags must be
checked out during release:perform, keep that in mind.
I see options with a flat structure and with the release-aggregator.

Robert

[1] https://issues.apache.org/jira/browse/MRELEASE-362


On Sat, 24 Jun 2017 22:59:48 +0200, Petar Tahchiev  


wrote:

Hi Paul,


I think you misunderstood. The [BOM] is a separate project and the
[PLATFORM] and [DEMO_STORE] are also separate projects, both of which
declare as their parent the [BOM].

@Robert: I have added the test-case:
https://github.com/apache/maven-release/pull/18/commits/
Release-aggregator is exactly what's missing. Is there an issue I can
subscribe and track?


2017-06-24 14:15 GMT+03:00 Robert Scholte :

What we're still missing is a release-aggregator, which can release
multiple release-roots at once. That would probably be the preferred  
fix,

the suggested patch is just an easy work-around.
It is still on my todo-list.

Robert


On Sat, 24 Jun 2017 12:42:22 +0200, Paul Hammant 
wrote:

Easy to fix.  Have a profile 'platformOnly' in the root module (I'm  
not


sure if 'BOM' should mean anything to me) that includes only  
'platform'

as
a child module.

   mvn release:prepare -PplatformOnly # etc

Later when you're ready to do the demo store release, use another  
(from

root):

   mvn release:prepare -PdemoOnly # etc

Of course, you man not need to stuff demo in your  
Artifactory/Nexus/etc

in
which case just do your deploy fu after an 'install' w/o the release
plugin
involved or that second profile.

- Paul


On Sat, Jun 24, 2017 at 2:58 AM, Petar Tahchiev  


wrote:

Hey guys,



I'm facing a number of challenges when I release the project at my
company.
Here's my setup:

[BOM]
 /\
 [PLATFORM]  [DEMO_STORE]

I have a master BOM project which holds all the version as defined
properties. This BOM is the parent to two other projects -  
[PLATFORM]

and
[DEMO_STORE], The [PLATFORM] is a project with more than 60 modules
inside,
and the [DEMO_STORE] is a project that declares those modules as
dependencies.

Now what I want is to release all three from Jenkins. I can release  
the
[BOM] with no problems, then I start release of the [PLATFORM] and  
all

of a
sudden Jenkins blocks because Maven asks me on the command line if I
want
to resolve the SNAPSHOT dependencies (remember the parent of the
[PLATFORM]
is the [BOM] SNAPSHOT version).

So I created this issue https://issues.apache.org/jira

Re: Maven release plugin

[Jörg Schaible]

Petar Tahchiev wrote:

> Hey guys,
> 
> my pull-request worked fine to not show the prompt to specify a version.
> However, it fails to update snapshot dependency versions when you resolve
> the parent to a concrete version.
> Particularly in my case:
> 
> 
> [BOM]
>  /\
>  [PLATFORM]  [DEMO_STORE]
>-module1 - platform:module1
>-module2 - platform:module2
>  .
>- moduleN- platform:moduleN
> 
> The [BOM] defines in dependencyManagement section all the versions of the
> modules of the [PLATFORM]. Then the [DEMO_STORE] can reference them
> without specifying a version. During release what I do is I first release
> the
> [BOM], then release the [PLATFORM] and up to here I see no problems. But
> then I try to release the DEMO_STORE] and even though I specify on the
> command line the version of the parent [BOM]:
> 
> -Ddependency.com.nemesis:bom.release=1.5.2.RELEASE
> -Ddependency.com.nemesis:bom.development=1.5.3.BUILD-SNAPSHOT
> 
> 
> it still asks me for versions of dependencies which are specified in the
> released [BOM].

What you can do as workaround is to add an empty relativePath element to the 
[DEMO_STORE] as a temporary modification just for the release. Annoying, but 
that should limit the multi-project to the subtree.

> I tried patching the code and specifying a new version of
> the parent
> 
> project.getParentArtifact().setVersion("1.5.2.RELEASE")
> 
> just to see if it works, but the problem is that the dependencies in the
> project are already resolved: when I call project.getDependencies() I get
> the SNAPSHOT versions.
> 
> Is there any way to reload the project model after I specify a new
> parentVersion()? So that It understands the [BOM] is no longer a snapshot
> version.

Dependency resolution is too early for such modifications.

Cheers,
Jörg


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

Re: Maven release plugin

[Petar Tahchiev]

Hey guys,

my pull-request worked fine to not show the prompt to specify a version.
However, it fails to update snapshot dependency versions when you resolve
the parent to a concrete version.
Particularly in my case:


[BOM]
 /\
 [PLATFORM]  [DEMO_STORE]
   -module1 - platform:module1
   -module2 - platform:module2
     .
   - moduleN- platform:moduleN

The [BOM] defines in dependencyManagement section all the versions of the
modules of the [PLATFORM]. Then the [DEMO_STORE] can reference them without
specifying a version. During release what I do is I first release the
[BOM], then release the [PLATFORM] and up to here I see no problems. But
then I try to release the DEMO_STORE] and even though I specify on the
command line the version of the parent [BOM]:

-Ddependency.com.nemesis:bom.release=1.5.2.RELEASE
-Ddependency.com.nemesis:bom.development=1.5.3.BUILD-SNAPSHOT


it still asks me for versions of dependencies which are specified in the
released [BOM]. I tried patching the code and specifying a new version of
the parent

project.getParentArtifact().setVersion("1.5.2.RELEASE")

just to see if it works, but the problem is that the dependencies in the
project are already resolved: when I call project.getDependencies() I get
the SNAPSHOT versions.

Is there any way to reload the project model after I specify a new
parentVersion()? So that It understands the [BOM] is no longer a snapshot
version.

Thanks

2017-06-25 12:11 GMT+03:00 Robert Scholte :

> MRELEASE-362[1] is probably the matching issue.
> Be aware that some are talking about tagging every module. In most
> situations I don't like that. If the structure is hierarchical and the root
> is tagged, then all the modules are already tagged. All tags must be
> checked out during release:perform, keep that in mind.
> I see options with a flat structure and with the release-aggregator.
>
> Robert
>
> [1] https://issues.apache.org/jira/browse/MRELEASE-362
>
>
> On Sat, 24 Jun 2017 22:59:48 +0200, Petar Tahchiev 
> wrote:
>
> Hi Paul,
>>
>> I think you misunderstood. The [BOM] is a separate project and the
>> [PLATFORM] and [DEMO_STORE] are also separate projects, both of which
>> declare as their parent the [BOM].
>>
>> @Robert: I have added the test-case:
>> https://github.com/apache/maven-release/pull/18/commits/
>> Release-aggregator is exactly what's missing. Is there an issue I can
>> subscribe and track?
>>
>>
>> 2017-06-24 14:15 GMT+03:00 Robert Scholte :
>>
>> What we're still missing is a release-aggregator, which can release
>>> multiple release-roots at once. That would probably be the preferred fix,
>>> the suggested patch is just an easy work-around.
>>> It is still on my todo-list.
>>>
>>> Robert
>>>
>>>
>>> On Sat, 24 Jun 2017 12:42:22 +0200, Paul Hammant 
>>> wrote:
>>>
>>> Easy to fix.  Have a profile 'platformOnly' in the root module (I'm not
>>>
 sure if 'BOM' should mean anything to me) that includes only 'platform'
 as
 a child module.

mvn release:prepare -PplatformOnly # etc

 Later when you're ready to do the demo store release, use another (from
 root):

mvn release:prepare -PdemoOnly # etc

 Of course, you man not need to stuff demo in your Artifactory/Nexus/etc
 in
 which case just do your deploy fu after an 'install' w/o the release
 plugin
 involved or that second profile.

 - Paul


 On Sat, Jun 24, 2017 at 2:58 AM, Petar Tahchiev 
 wrote:

 Hey guys,

>
> I'm facing a number of challenges when I release the project at my
> company.
> Here's my setup:
>
> [BOM]
>  /\
>  [PLATFORM]  [DEMO_STORE]
>
> I have a master BOM project which holds all the version as defined
> properties. This BOM is the parent to two other projects - [PLATFORM]
> and
> [DEMO_STORE], The [PLATFORM] is a project with more than 60 modules
> inside,
> and the [DEMO_STORE] is a project that declares those modules as
> dependencies.
>
> Now what I want is to release all three from Jenkins. I can release the
> [BOM] with no problems, then I start release of the [PLATFORM] and all
> of a
> sudden Jenkins blocks because Maven asks me on the command line if I
> want
> to resolve the SNAPSHOT dependencies (remember the parent of the
> [PLATFORM]
> is the [BOM] SNAPSHOT version).
>
> So I created this issue https://issues.apache.org/jira
> /browse/MRELEASE-985
> to be able to specify the [BOM] parent version when I start the release
> of
> [PLATFORM]. I think I also fixed it with