You are viewing a plain text version of this content. The canonical link for it is here.
Posted to announce@maven.apache.org by Hervé Boutemy <hb...@apache.org> on 2019/12/16 08:02:46 UTC

[ANN] Apache Maven Release Plugin 3.0.0-M1 Released

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:
 
<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-release-plugin</artifactId>
  <version>3.0.0-M1</version>
</plugin>
 
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



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

Posted by Robert Scholte <rf...@apache.org>.
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 <ma...@talios.com> wrote:
On 16 Dec 2019, at 21:02, Hervé Boutemy wrote:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<version>3.0.0-M1</version>
</plugin>
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:
<properties> <projectVersionPolicyId>default</projectVersionPolicyId> </properties> ... <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-release-plugin</artifactId> <version>2.5.3</version> <configuration> <preparationGoals> clean reproducible:apply sortpom:sort tidy:pom rangeresolver:lock-deps install </preparationGoals> <goals>deploy</goals> <completionGoals> reproducible:clear sortpom:sort tidy:pom </completionGoals> <projectVersionPolicyId>${projectVersionPolicyId}</projectVersionPolicyId> <autoVersionSubmodules>true</autoVersionSubmodules> <pushChanges>false</pushChanges> <localCheckout>true</localCheckout> </configuration> <dependencies> <dependency> <groupId>com.smxemail</groupId> <artifactId>qualified-version-policy</artifactId> <version>1.0.2</version> </dependency> </dependencies> </plugin>
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

Posted by Mark Derricutt <ma...@talios.com>.
On 16 Dec 2019, at 21:02, Hervé Boutemy wrote:

> <plugin>
>   <groupId>org.apache.maven.plugins</groupId>
>   <artifactId>maven-release-plugin</artifactId>
>   <version>3.0.0-M1</version>
> </plugin>

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:

      <properties>
        <projectVersionPolicyId>default</projectVersionPolicyId>
      </properties>
      ...
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-release-plugin</artifactId>
        <version>2.5.3</version>
        <configuration>
          <preparationGoals>
            clean
            reproducible:apply
            sortpom:sort
            tidy:pom
            rangeresolver:lock-deps
            install
          </preparationGoals>
          <goals>deploy</goals>
          <completionGoals>
            reproducible:clear
            sortpom:sort
            tidy:pom
          </completionGoals>
          <projectVersionPolicyId>${projectVersionPolicyId}</projectVersionPolicyId>
          <autoVersionSubmodules>true</autoVersionSubmodules>
          <pushChanges>false</pushChanges>
          <localCheckout>true</localCheckout>
        </configuration>
        <dependencies>
          <dependency>
            <groupId>com.smxemail</groupId>
            <artifactId>qualified-version-policy</artifactId>
            <version>1.0.2</version>
          </dependency>
        </dependencies>
      </plugin>

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." &mdash; 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

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

Posted by Rémy Sanlaville <re...@gmail.com>.
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 <rf...@apache.org> 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

Posted by Robert Scholte <rf...@apache.org>.
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 <re...@gmail.com> 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-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>

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

Posted by Rémy Sanlaville <re...@gmail.com>.
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 <hb...@apache.org> 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:
>
> <plugin>
>   <groupId>org.apache.maven.plugins</groupId>
>   <artifactId>maven-release-plugin</artifactId>
>   <version>3.0.0-M1</version>
> </plugin>
>
> 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-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>