Re: [Clirr-user] using clirr through maven

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

Torsten Curdt wrote:

>> Aside from clirr itself, I don't use maven, so sorry, I can't help  
>> you much.
>
>
> Huh!? ...just realized that at least clirr web pages are generated by  
> maven :)
>

What I meant is I only use Maven for Clirr and for no other project.

As for your "you better should" comment in the other email: Well, I'm in 
a love-hate relationship with Maven. I love that it (1) allows you to 
build simple one-source-tree-one-jar projects declaratively, and that it 
(2) downloads dependencies automatically. I hate all other aspects of 
Maven :-)

As an example, try to have a look at the maven.xml in the clirr toplevel 
module [1]. I'm sure this is not the "maven way", but I couldn't find 
any other way to build the release binaries that contain everything in 
one download, and I spent way too much time wrestling with this stuff - 
much longer than it would have taken me to write a build.xml for Ant.

Other points: Unit test execution takes forever and doesn't report the 
failing test on the console, "maven clean" starts downloading all 
dependencies, extensions have to be written in a XML scripting language 
that doesn't behave very intuitive, etc, etc.

Maybe it's just me and at 35 I'm getting old, but so far I'm not 
convinced that maven helps me more than it hurts. From what I hear 
maven2 is a bit better - contributions for converting the clirr build to 
m2 would be welcome.

Cheers, and sorry for the extra "h" in my original email,
Lars

[1] 
http://cvs.sourceforge.net/viewcvs.py/clirr/clirr/maven.xml?rev=1.6&view=auto