Using Maven to resolve Cocoon and other dependencies

[Michael Wechner <mi...@wyona.com>]

Hi

Since some of us are changing stuff within Cocoon (and maybe other projects)
I think it would make sense to use Maven to resolve dependencies, especially
if we want to do continous development with the trunk.

For instance Lenya could have it's own Maven remote repo, e.g.

http://lenya.apache.org/maven/

WDYT?

Michi

-- 
Michael Wechner
Wyona      -   Open Source Content Management   -    Apache Lenya
http://www.wyona.com                      http://lenya.apache.org
michael.wechner@wyona.com                        michi@apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org

Re: Using Maven to resolve Cocoon and other dependencies

["Gregor J. Rothfuss" <gr...@apache.org>]

Michael Wechner wrote:
> Hi
> 
> Since some of us are changing stuff within Cocoon (and maybe other 
> projects)
> I think it would make sense to use Maven to resolve dependencies, 
> especially
> if we want to do continous development with the trunk.
> 
> For instance Lenya could have it's own Maven remote repo, e.g.
> 
> http://lenya.apache.org/maven/

i think this makes sense when / if cocoon moves to maven (which has been 
discussed a couple times). before that, i think the work / benefit ratio 
doesn't look good.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org