cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Lowe <mel...@gmail.com>
Subject Re: Dependencies
Date Sun, 13 Feb 2005 21:02:09 GMT
I can see that having the cocoon build solely with maven would be a
pain, I was just trying to think about how to manage these horendous
dependencies. But then I thought about it, an realised which ever you
use you need to build cocoon from source anyhow.

Mark

On Sun, 13 Feb 2005 09:50:47 -0800, Ralph Goers
<Ralph.Goers@dslextreme.com> wrote:
> I believe what you are suggesting would require that the Cocoon build be
> converted to use Maven.  While I personally would welcome that, this has
> been discussed before and for some reason several committers won't
> support that. Sorry.
> 
> Ralph
> 
> Mark Lowe wrote:
> 
> >Hello
> >
> >Just an idea, not sure if its possible or not, but I'd really like to
> >be able to build cocoon based projects like I would anyother. With the
> >large amount of time-stamped jar files (even for releases) and such
> >like, trying to mavenise a cocoon build is a nightmare. Is there
> >someway that cocoon releases distributions can be stuck on a server
> >and the dependencies resolved via maven (without any additional steps,
> >geeking around, changing this or that xml, and so on)?
> >
> >I've seen the war download and then jelly script to handle that, but I
> >really think that a means of downloading the required jars (other than
> >any with licensing issues, although those wouldn't be in cvs now would
> >they) wouldn't be that much to expect.
> >
> >Thanks
> >
> >Mark
> >
> >
> 
>

Mime
View raw message