clirr-devel

[Clirr-devel] Preparing Release 0.5

[<lak...@t-...>]

Hi,

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.

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

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?

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

Regards,
Lars

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

Re: [Clirr-devel] Preparing Release 0.5

[<lak...@t-...>]

Vincent Massol wrote:

> [...]
>
>>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 :-) 
>
>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.
>
>  
>

... and the zip/tgz files you can download from the sf.net download page 
(source and binaries). Not very useful for Maven users, but essential 
for the rest of us. I think sf requires hosted projects to make such 
files available via their download system.

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

I would tag first, then do a fresh checkout and build it? Guess it 
doesn't matter too much...

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

Right.

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

To be clear, with "distributables" I meant the aforementioned zip/tgz 
files, not jars. See 
http://sourceforge.net/project/showfiles.php?group_id=89627

>>ready for upload to sourceforge?
>>    
>>
>
>M1 does allow this. 
>

How? What is required in the"whatever" part? A kingdom for a 
commandline... :-)

>I don't think m2 is there yet but close. At least I
>haven't done it yet with m2.
> 
>  
>
>>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.
>
>  
>

OK, as it's not clear that m2 provides what we need for the build, let's 
defer this move until after 0.5.

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

I think you are talking about creating a Clirr plugin for m2, just as 
you did for m1. Not sure if I have time for that (my little baby 
daughter wants some attention, too), and personally I would be much more 
interested in having an Eclipse plugin.

My question actually was whether it is still possible to script those 
parts of clirr-core's own build that are non-standard (we have three 
calls of javac).

/Lars

RE: [Clirr-devel] Preparing Release 0.5

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

> -----Original Message-----
> From: cli...@li... [mailto:clirr-devel-
> ad...@li...] On Behalf Of Lars K=FChne
> Sent: mercredi 3 ao=FBt 2005 16:39
> To: cli...@li...
> Subject: Re: [Clirr-devel] Preparing Release 0.5

[snip]

> ... and the zip/tgz files you can download from the sf.net download =
page
> (source and binaries). Not very useful for Maven users, but essential
> for the rest of us. I think sf requires hosted projects to make such
> files available via their download system.

Yes, and you can also make them available on ibiblio as the Maven =
repository
also supports distributions (under <groupd id>/distributions/*). But =
then it
probably makes more sense to use the SF download area for this, I agree.

> >M1 does allow this.
> >
>=20
> How? What is required in the"whatever" part? A kingdom for a
> commandline... :-)

I had given you a URL in my original email. It gives command lines.
Basically there are 2: one to modify the changes.xml and project.xml =
files
and to tag (maven scm:prepare-release or something like this) and =
another
one for checking out the tag, doing the build and deploying (maven
scm:deploy-release or something like this).
=20
> I think you are talking about creating a Clirr plugin for m2, just as
> you did for m1. Not sure if I have time for that (my little baby
> daughter wants some attention, too), and personally I would be much =
more
> interested in having an Eclipse plugin.

Sure. What I was saying was that there is a window of opportunity for =
Clirr
by doing a m2 plugin. M2 has lots of visibility and lots of users. =
That's
provided you wish to make it an even more successful project, with more
users, committers, etc. Really, I was just highlighting a way to =
"market"
clirr, nothing more.

> My question actually was whether it is still possible to script those
> parts of clirr-core's own build that are non-standard (we have three
> calls of javac).

With m2? Yes and no. No, because you now need to developer a plugin for
doing anything non-standard. That said, most use cases should be catered
for.

-Vincent

Re: [Clirr-devel] Preparing Release 0.5

[<lak...@t-...>]

Vincent Massol wrote:

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

I've done this, built the whole thing, and uploaded the release zips 
(src and bin) to the sf file release system.

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

... and not even permitted by Sourceforge. Here are the terms of 
acceptable use for the web space:

    File releases may not be made available via your project web space
    (unless you have received permission in writing from SourceForge.net
    staff), with the exception of nightly snapshots. File releases
    should be made available using the *File Release System
    <https://sourceforge.net/project/admin/editpackages.php?group_id=89627>*.


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

Before I do that, could you please make sure that the Maven plugin in 
the binary distribution actually works? I'm not using Maven for anything 
but Clirr, so it's a bit hard for me to test the plugin.

Thanks,
Lars

RE: [Clirr-devel] Preparing Release 0.5

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

> -----Original Message-----
> From: cli...@li... [mailto:clirr-devel-
> ad...@li...] On Behalf Of Lars K=FChne
> Sent: lundi 8 ao=FBt 2005 00:20
> To: cli...@li...
> Subject: Re: [Clirr-devel] Preparing Release 0.5

[snip]

> Before I do that, could you please make sure that the Maven plugin in
> the binary distribution actually works? I'm not using Maven for =
anything
> but Clirr, so it's a bit hard for me to test the plugin.

I've tried to build it but the build doesn't work for me. Try "maven =
dist"
at the top level. Probably something stupid but I don't have the time to
look into it. BTW I've checked the maven.xml and the build is really not
clean...=20

2 things to do:

1/ Rename the "dist" goals to "clirr:dist" and the "dist" goal already
exists (dist plugin).
2/ Use the dist plugin to generate distributions.

Thanks
-Vincent

Re: [Clirr-devel] Preparing Release 0.5

[<lak...@t-...>]

Vincent Massol wrote:

>>Before I do that, could you please make sure that the Maven plugin in
>>the binary distribution actually works?
>>
>I've tried to build it but the build doesn't work for me.
>

Just type 'maven', that should build the distribution zip files. 
Alternatively you can download them from sourceforge:
http://sourceforge.net/project/showfiles.php?group_id=89627


> Try "maven dist"
>at the top level. Probably something stupid but I don't have the time to
>look into it. BTW I've checked the maven.xml and the build is really not
>clean... 
>
>2 things to do:
>
>1/ Rename the "dist" goals to "clirr:dist" and the "dist" goal already
>exists (dist plugin).
>2/ Use the dist plugin to generate distributions.
>  
>

I tried, but I couldn't get the dist plugin to work for multiproject. I 
want a single distribution file, not one for each subproject. The is no 
multiproject:dist goal that would do this, and the dist plugin does not 
take subprojects into account either (don't include the target 
directories of subprojects in the src distribution, etc).

At some point I gave up, figured out the standard maven property names 
from the dist plugin's jelly code and essentially wrote an Ant script 
inside maven.xml to finally get the release out the door.

Vincent, you have commit priviliges, feel free to fix away on the build 
process. I'd be happy to learn how to do things correctly with Maven, 
but I don't have the time to continue learning it the hard way.

Cheers,
Lars

RE: [Clirr-devel] Preparing Release 0.5

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

> -----Original Message-----
> From: cli...@li... [mailto:clirr-devel-
> ad...@li...] On Behalf Of Lars K=C3=BChne
> Sent: lundi 8 ao=C3=BBt 2005 14:32
> To: cli...@li...
> Subject: Re: [Clirr-devel] Preparing Release 0.5
>=20
> Vincent Massol wrote:
>=20
> >>Before I do that, could you please make sure that the Maven plugin =
in
> >>the binary distribution actually works?
> >>
> >I've tried to build it but the build doesn't work for me.
> >
>=20
> Just type 'maven', that should build the distribution zip files.

I have the same error:

[...]
+----------------------------------------
| Generating site for  Clirr Maven plugin
| Memory: 17M/26M
+----------------------------------------
DEPRECATED: the default goal should be specified in the <build> section =
of project.xml instead of maven.xml
DEPRECATED: the default goal should be specified in the <build> section =
of project.xml instead of maven.xml

build:end:

Tentative de t=CE=98l=CE=98chargement de clirr-core-0.5.jar.
ATTENTION: Impossible de t=CE=98l=CE=98charger clirr-core-0.5.jar.

LA CONSTRUCTION A =E2=95=9ACHOU=E2=95=9A
Fichier... C:\Documents and Settings\Vincent =
Massol\.maven\cache\maven-multiproject-plugin-1.4.1\plugin.jelly
=E2=95=9Alement... maven:reactor
Ligne..... 104
Colonne... -1
Le processus ne peut continuer =CE=B1 cause de la d=CE=98pendance =
manquante suivante:

clirr-core-0.5.jar

> Alternatively you can download them from sourceforge:
> http://sourceforge.net/project/showfiles.php?group_id=3D89627

I can't find the maven plugin there. That's what you'd like me to try =
right?

[snip]

> Vincent, you have commit priviliges, feel free to fix away on the =
build
> process. I'd be happy to learn how to do things correctly with Maven,
> but I don't have the time to continue learning it the hard way.

Yep but at this point it'll be better to move to Maven 2.0 as there's =
already an assembly plugin which does this nicely and which I have used =
and I know it works.

When I have some time, I'll help do the m2 migration.

Thanks
-Vincent

Re: [Clirr-devel] Preparing Release 0.5

[<lak...@t-...>]

Vincent Massol wrote:

>>Just type 'maven', that should build the distribution zip files.
>>    
>>
>
>I have the same error:
>
>[...]
>+----------------------------------------
>| Generating site for  Clirr Maven plugin
>| Memory: 17M/26M
>+----------------------------------------
>DEPRECATED: the default goal should be specified in the <build> section of project.xml instead of maven.xml
>DEPRECATED: the default goal should be specified in the <build> section of project.xml instead of maven.xml
>[...]
>  
>

I'm using maven 1.0.2 (latest stable relase). Are you using a newer version?

>  
>
>>Alternatively you can download them from sourceforge:
>>http://sourceforge.net/project/showfiles.php?group_id=89627
>>    
>>
>
>I can't find the maven plugin there.
>

Inside the clirr-0.5 zip is both the core jar and the maven plugin jar, 
bundled with all documentation. Anything else you need?


> That's what you'd like me to try right?
>
>  
>

Yes.


>[snip]
>
>  
>
>>Vincent, you have commit priviliges, feel free to fix away on the build
>>process. I'd be happy to learn how to do things correctly with Maven,
>>but I don't have the time to continue learning it the hard way.
>>    
>>
>
>Yep but at this point it'll be better to move to Maven 2.0 as there's already an assembly plugin which does this nicely and which I have used and I know it works.
>
>When I have some time, I'll help do the m2 migration.
>  
>

Looking forward to that,
Lars

RE: [Clirr-devel] Preparing Release 0.5

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

> -----Original Message-----
> From: cli...@li... [mailto:clirr-devel-
> ad...@li...] On Behalf Of Lars K=FChne
> Sent: lundi 8 ao=FBt 2005 15:14
> To: cli...@li...
> Subject: Re: [Clirr-devel] Preparing Release 0.5

[snip]

> I'm using maven 1.0.2 (latest stable relase). Are you using a newer
> version?

Yes, Maven 1.1-beta2-snapshot

I've just fixed the build.

[snip]

> Inside the clirr-0.5 zip is both the core jar and the maven plugin =
jar,
> bundled with all documentation. Anything else you need?

Ok, I hadn't realized this.

[snip]

Trying the maven clirr plugin on the Cargo project in a few minutes... =
I'll
let you know how it goes.

Thanks
-Vincent

Re: [Clirr-devel] Preparing Release 0.5

[<lak...@t-...>]

Vincent Massol wrote:

>Trying the maven clirr plugin on the Cargo project in a few minutes... I'll
>let you know how it goes.
>
>Thanks
>-Vincent
>  
>

Vincent, did you encounter any problems? Today is the last day of my 
vacation, so it would be cool if we could finish the release today...

Thanks,
Lars

RE: [Clirr-devel] Preparing Release 0.5

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

> -----Original Message-----
> From: cli...@li... [mailto:clirr-devel-
> ad...@li...] On Behalf Of Lars K=FChne
> Sent: mercredi 10 ao=FBt 2005 08:20
> To: cli...@li...
> Subject: Re: [Clirr-devel] Preparing Release 0.5
>=20
> Vincent Massol wrote:
>=20
> >Trying the maven clirr plugin on the Cargo project in a few =
minutes...
> I'll
> >let you know how it goes.
> >
> >Thanks
> >-Vincent
> >
> >
>=20
> Vincent, did you encounter any problems? Today is the last day of my
> vacation, so it would be cool if we could finish the release today...

Yes, I did find a problem. I've entered it in the SF bug tracker and I
thought you would get an email automatically...

Right now, I've not yet been able to have it work for me. I'll try to =
work
more on it today but no promise...

-Vincent

Re: [Clirr-devel] Preparing Release 0.5

[<lak...@t-...>]

Vincent Massol wrote:

>Yes, I did find a problem. I've entered it in the SF bug tracker and I
>thought you would get an email automatically...
>
>  
>

There was a bugtracker setup problem. Thanks for reporting that, 
notifications are now sent to this list.

>Right now, I've not yet been able to have it work for me. I'll try to work
>more on it today but no promise...
>
>  
>

Thanks,
Lars

Re: [Clirr-devel] Preparing Release 0.5

[<lak...@t-...>]

> Vincent Massol wrote:
>
>> Right now, I've not yet been able to have it work for me. I'll try to 
>> work
>> more on it today but no promise...
>

I have now successfully run 'maven clirr' on commons-logging and 
commons-collections, using Maven 1.0.2. Maybe there are some issues only 
with Maven 1.1?

Lars

RE: [Clirr-devel] Preparing Release 0.5

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

> -----Original Message-----
> From: cli...@li... [mailto:clirr-devel-
> ad...@li...] On Behalf Of Lars K=FChne
> Sent: mercredi 10 ao=FBt 2005 23:08
> To: cli...@li...
> Subject: Re: [Clirr-devel] Preparing Release 0.5
>=20
>=20
> > Vincent Massol wrote:
> >
> >> Right now, I've not yet been able to have it work for me. I'll try =
to
> >> work
> >> more on it today but no promise...
> >
>=20
> I have now successfully run 'maven clirr' on commons-logging and
> commons-collections, using Maven 1.0.2. Maybe there are some issues =
only
> with Maven 1.1?

Sorry I haven't had the time to try further today but it's on my todo =
list.
I won't forget it but it may take me some time. Don't wait for me.

Thanks
-Vincent


	

	
		
___________________________________________________________________________ 
Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger 
Téléchargez cette version sur http://fr.messenger.yahoo.com