Re: Build Environment

Peter Donald wrote:
> On Fri, 3 Jan 2003 01:10, Berin Loritsch wrote:
> 
>>Maven
>>-----
>>* Integrates with Forrest, but not by default.
>>* Not easy to extend with user defined modules, it requires user
>>  intervention to install project specific modules.
> 
> 
> not in CVS version! 
> 
> Writing plugins is very easy (usually just a jelly script and some resources). 
> Recently their download as just another dependency made it easy to add them 
> into your builds.

Great!  All they need to do is make a release!  I only evaluated the
released versions.


>>* Difficult to extend with project-specific modules.  The machinery
>>  is there, but it has a lot of rough edges.  
> 
> 
> So not the case. Can you point out something that you found difficult to do 
> with it? The one thing that has held me up was a bug in the POM loading.


The main thing I was looking at is the process of adding project
specific extensions like our Metagenerate stuff for Phoenix.
I would prefer an option that would allow Maven to use what we provide
in the project.

WIth Centipede, that is as simple as adding an import statement:

<import cent="...."/>

If Maven can do that too, then great!  I am still on the fence.

>>                       -o0 Unclear Things 0o-
>>
>>Both projects have the typical Open Source failings.  Documentation
>>is sparse, and typically only covers what the developers were
>>concentrating on.  For example, both focus more attention to
>>_converting_ an existing project than to _creating_ a new project
>>from scratch.  Between the two, Maven does have marginally better
>>documentation.
> 
> 
> I feel comfortable with Maven (after the first few days bashing head against 
> wall). So feel free to ask anything about it - once you get a grip of jelly 
> everything becomes relatively easy and jelly rocks.

Sounds good.