cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ralph Goers <>
Subject Re: [RANT] This Maven thing is killing us....
Date Sat, 01 Jul 2006 21:27:44 GMT
We've been using Maven 1 successfully for a couple of years.  We want to 
upgrade to Maven 2 but can't until I (or someone) fixes 
<> However, I suspect that we 
would be having the same problems as the Cocoon builds are currently 
experiencing if we were always trying to go to an external repository. 
I've even seen this with our local repository if the web server is 
having problems.

Rather than packaging a "lib" directory, it would make more sense to me 
if we had a downloadable maven repository that contains only what is 
needed to build Cocoon. This could then be used to set up the internal 
repository.  Unfortunately, this doesn't solve all the problems as every 
time some new component is required the internal repository doesn't 
automatically get updated.

I know in my case our Configuration Management folks have come to love 
Maven and the repository concept as it gives them total control over 
when the third party components are updated.

Carsten Ziegeler wrote:
> Bertrand Delacretaz wrote:
>> -Allow Cocoon users to add their own jars to the build in the old way
>> (lib directory), without forcing them to use Maven for that
> I think this is the most interesting point. We could try to push maven
> to allow this...would be fun to see what they think. Seriously, I think
> if this would be possible with m2, things would be much easier.
> And we could add all ours libs this way and forget about the m2
> dependency stuff for now.
> In addition I think we should force the m2 people to make transitive
> dependency optional. I tried this once but never succeeded.
> Carsten

View raw message