You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Olivier Lamy <ol...@apache.org> on 2008/10/30 23:42:18 UTC
[ANN] Maven Release Plugin 2.0-beta-8 Released
The Maven team is pleased to announce the release of the Maven Release
Plugin, version 2.0-beta-8.
http://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>2.0-beta-8</version>
</plugin>
Release Notes - Maven 2.x Release Plugin - Version 2.0-beta-8
** Bug
* [MRELEASE-87] - Poms are written with wrong encodings
* [MRELEASE-188] - release:perform is not updating some modules to
the next version identifier correctly.
* [MRELEASE-201] - Deployed POM is not valid XML
* [MRELEASE-221] - XML header missing in modified POM after release:prepare
* [MRELEASE-223] - Generated pom.xml has invalid chars (does not
correctly handle xml entities)
* [MRELEASE-254] - tests failed on windows
* [MRELEASE-255] - during a release several elements are removed
from the pom.xml (which should be left there)
* [MRELEASE-267] - Whitespaces in artifactId or groupId prevent
version update
* [MRELEASE-268] - Release is broken with Subversion 1.3.x and earlier
* [MRELEASE-302] - Test don't pass on windows due to encoding issues
* [MRELEASE-305] - release:prepare forgets a slash when changing
the <scm> urls
* [MRELEASE-337] - generated command line must remove newLine characters
* [MRELEASE-351] - xml declaration removed on release
* [MRELEASE-355] - Deploying from Leopard, with Svn 1.4.4 has
error on automated Svn commit
* [MRELEASE-360] - NullPointerException in release
* [MRELEASE-364] - InvokerMavenExecutor fails with NPE if
additional arguments are not set
* [MRELEASE-365] - ForkedMavenExecutor fails with NoSuchMethodError
* [MRELEASE-366] - Using InvokerMavenExecutor fails in combination
with space in paths
** Improvement
* [MRELEASE-173] - Allow command line specification of versions
* [MRELEASE-321] - Add support for -DdevelopmentVersion and
-DreleaseVersion to facilitate command line configuration
* [MRELEASE-341] - support release process that use a staging repository
* [MRELEASE-345] - Keep comments in rewritten elements
* [MRELEASE-359] - Release plugin depends on mvn being in the path
of the shell that started the current build
* [MRELEASE-382] - Specifying workingDirectory as system property
on CL is not picked up by release:perform
** New Feature
* [MRELEASE-369] - upgrade scm version to last 1.1 (and add by
default new providers accurev and git)
** Task
* [MRELEASE-316] - remove copy of plexus-utils' XML encoding support sources
** Wish
* [MRELEASE-313] - add an option to set the profile(s) used to
perform the release
Have fun !
-The Maven team
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Keep version when doing a release
Posted by Gu...@tieto.com.
Hi,
I have a multi module project that I want to make a release for.
Some of the modules changes frequently and they are marked as SNAPSHOTS.
Some modules are very stable and have a fixed version.
I run maven 2 release plug-in 2.0-beta-7 with the --batch-mode
parameter.
The problem is that the stable modules will also have there version
changed.
Is there any way to tell the plug-in to only change version for SNAPSHOT
modules?
/Gunnar
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Keep version when doing a release
Posted by Anders Kristian Andersen <an...@gmail.com>.
Hi
You need a trunk to each module you want to release individually
/Anders
On 09/12/2008, at 11.02, <Gu...@tieto.com> <Gunnar.Bostrom@tieto.com
> wrote:
> Hi,
> I have a multi module project that I want to make a release for.
> Some of the modules changes frequently and they are marked as
> SNAPSHOTS.
> Some modules are very stable and have a fixed version.
> I run maven 2 release plug-in 2.0-beta-7 with the --batch-mode
> parameter.
> The problem is that the stable modules will also have there version
> upgraded.
> Is there any way to tell the plug-in to only change version for
> SNAPSHOT
> modules?
> /Gunnar
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Keep version when doing a release
Posted by Graham Leggett <mi...@sharp.fm>.
Gunnar.Bostrom@tieto.com wrote:
> I have a multi module project that I want to make a release for.
> Some of the modules changes frequently and they are marked as SNAPSHOTS.
> Some modules are very stable and have a fixed version.
> I run maven 2 release plug-in 2.0-beta-7 with the --batch-mode
> parameter.
> The problem is that the stable modules will also have there version
> upgraded.
> Is there any way to tell the plug-in to only change version for SNAPSHOT
> modules?
Break up your multi module project into a smaller set of multi module
projects.
I had a project like this a while back, and I defined some variables in
the super pom of multi module project B to point at the version number
of multi module project A.
This eliminated confusion over what relied on what, and ensured that the
dependency was defined in just one place only.
The more code you release at one time, the more difficult it is to tell
where a bug might lie. Spin off the stable stuff into their own release
cycles, and your troubleshooting problems will become significantly
less, as a problem will most likely be caused by a smaller subset of
newly released code.
Regards,
Graham
--
Re: Keep version when doing a release
Posted by Stephen Connolly <st...@gmail.com>.
You will run into problems having non-SNAPSHOT versions...
You do know that Maven will refuse to re-deploy non-SNAPSHOT versions... and
it refuses silently... so any changes to a non-SNAPSHOT module will not
actually be picked up by any build on another machine...
or to put it another way:
"Danger! Will Robinson! Danger!"
2008/12/9 <Gu...@tieto.com>
> Hi,
> I have a multi module project that I want to make a release for.
> Some of the modules changes frequently and they are marked as SNAPSHOTS.
> Some modules are very stable and have a fixed version.
> I run maven 2 release plug-in 2.0-beta-7 with the --batch-mode
> parameter.
> The problem is that the stable modules will also have there version
> upgraded.
> Is there any way to tell the plug-in to only change version for SNAPSHOT
> modules?
> /Gunnar
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Keep version when doing a release
Posted by Gu...@tieto.com.
Hi,
I have a multi module project that I want to make a release for.
Some of the modules changes frequently and they are marked as SNAPSHOTS.
Some modules are very stable and have a fixed version.
I run maven 2 release plug-in 2.0-beta-7 with the --batch-mode
parameter.
The problem is that the stable modules will also have there version
upgraded.
Is there any way to tell the plug-in to only change version for SNAPSHOT
modules?
/Gunnar
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org