[M2] Preparing a Release

[Bernd Mau <Ma...@hhla.de>]

Hi,

1. Can anybody give me an example how to prepare a release in
combination with cvs?
2. How to prepare a release for a multi project? Will dependencies
automatically change, if I want to release version 1.0 and
ModuleA-1.0-SNAPSHOT depends on ModuleB-1.0-SNAPSHOT?

Thanks for your help.
Bernd


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: [M2] Preparing a Release

[John Casey <jd...@commonjava.org>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

There will actually be one glaring problem with rewriting the SCM URL
during the release process. This plugin is currently only geared for SVN
use, so it expects /trunk/ and so forth...but this is *not* the way it
*should* be...it's more a function of immediate need. If/when you try
running against a CVS repository, please do let us know how it goes, so
we can start moving toward better support for different SCM URL types.

Thanks,

john

Brett Porter wrote:
| The release plugin (especially the previous release) is still a little
| rough, but essentially it should be:
|
| m2 release:prepare
|
| and follow the prompts. You can also run in batch mode to avoid
| prompts, and pass the config via system properties.
|
| Let us know your experiences and feedback - we are forming
| documentation right now and can incorporate that.
|
| - Brett
|
| On 9/29/05, Bernd Mau <Ma...@hhla.de> wrote:
|
|>Hi,
|>
|>1. Can anybody give me an example how to prepare a release in
|>combination with cvs?
|>2. How to prepare a release for a multi project? Will dependencies
|>automatically change, if I want to release version 1.0 and
|>ModuleA-1.0-SNAPSHOT depends on ModuleB-1.0-SNAPSHOT?
|>
|>Thanks for your help.
|>Bernd
|>
|>
|>---------------------------------------------------------------------
|>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
|
|
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFDO/HMK3h2CZwO/4URAhRRAJ4yjuivVmBvXS/ugXYLIK8zvrU/dgCfWfZX
41iqLHPtsiKfl+XBW1Z8noc=
=+AM1
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: [M2] Preparing a Release

[Brett Porter <br...@gmail.com>]

The release plugin (especially the previous release) is still a little
rough, but essentially it should be:

m2 release:prepare

and follow the prompts. You can also run in batch mode to avoid
prompts, and pass the config via system properties.

Let us know your experiences and feedback - we are forming
documentation right now and can incorporate that.

- Brett

On 9/29/05, Bernd Mau <Ma...@hhla.de> wrote:
> Hi,
>
> 1. Can anybody give me an example how to prepare a release in
> combination with cvs?
> 2. How to prepare a release for a multi project? Will dependencies
> automatically change, if I want to release version 1.0 and
> ModuleA-1.0-SNAPSHOT depends on ModuleB-1.0-SNAPSHOT?
>
> Thanks for your help.
> Bernd
>
>
> ---------------------------------------------------------------------
> 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