RE: [Clirr-devel] Preparing Release 0.5

[Vincent M. <vm...@pi...>]

Hi Lars,

> -----Original Message-----
> From: cli...@li... [mailto:clirr-devel-
> ad...@li...] On Behalf Of Lars K=FChne
> Sent: mercredi 3 ao=FBt 2005 12:55
> To: cli...@li...
> Subject: [Clirr-devel] Preparing Release 0.5
>=20
> Hi,
>=20
> I'm currently on vacation so I have some time to work on clirr (yay!).
> Given that we have two significant enhancements, I'd like to release
> version 0.5 in the next few days.

Very cool

> Problem is, even with Vincent's multiproject instructions from
> 11/10/2004 I still don't know how to do a release properly. Probably =
my
> fault (seems I'm a bit dense when it comes to Maven).

Hehe :-)=20

There are different ways of doing it, more or less automated. Here's the
less automated one (which works quite well):

1/ Rename the version so that it's a final one (0.5-SNAPSHOT in 0.5 for
example). Make sure your changes.xml files are updated and the release =
date
mentioned.

2/ Build the projects to produce the artifacts. I guess you'll produce 2
artifacts: one main jar containing the core classes and the Ant ones and
another jar which is the Maven plugin for Clirr.

3/ Tag the SCM using your favorite tool (tortoisecvs, eclipse, etc).

4/ (optional) Publish the 2 jars to the clirr's sourceforge maven
repository. Honestly I think this should be dropped as it's not useful.

5/ Publish the 2 jars to the ibiblio repository following the =
instructions
here: http://maven.apache.org/reference/repository-upload.html

That's all.

Now you could also automate this using the Maven 1.x scm plugin, as
described on that page:
http://maven.apache.org/developers/making-releases.html. That said, it =
won't
bring much in term of time spent as steps 1-5 are simply and quick.

> I see that maven2 has improved support for multiprojects (one of the =
new
> features is "/Built-in multiple project handling/"), but I haven't =
tried
> it. Will m2 finally allow me to tag 0.5, do a fresh checkout and then
> just do a "m2 whatever" in the toplevel project and have the site
> deployed and distributables ready for upload to sourceforge?

M1 does allow this. I don't think m2 is there yet but close. At least I
haven't done it yet with m2.
=20
> Should we try to move to m2 or does that create more problems than it
> solves? Currently we need maven.xml to generate the test input jars -
> would it still be possible to script this or do we have to create a
> "create-clirr-testinputs" plugin for that (a third subproject)?

I think you should try to move to m2. I'm doing this for cargo so you =
could
use that as an example and I can help you with my m2 knowledge. It's =
really
neater and faster.

Also, I think there's a very nice opportunity for Clirr in providing a =
m2
plugin. This is something missing and I'm 100% sure it would be greatly
appreciated and would make lot of people using Clirr. I would promote it =
as
well as this is a plugin I would use on Cargo and other projects.

You'll find m2 plugin creation quite easy once you understand the =
basics.
Again I can help a bit, by at least providing directions (I don't have =
the
time to do it myself just yet though).

Thanks
-Vincent