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