cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Giacomo Pati <>
Subject Re: [RANT] This Maven thing is killing us....
Date Mon, 03 Jul 2006 18:44:42 GMT
Hash: SHA1

On Mon, 3 Jul 2006, Simone Gianni wrote:

> It's not just a question of having a reliable build system, simply in
> many companies they have a lifecycle for their applications that steps
> thru test, integration etc.. and quite often this servers are not
> connected to internet, so building cocoon on those machines would be
> simply impossibile. With the local checkedout repo solution it's like
> having a lib dir, just a matter of checking out cocoon, moving it to the
> target server, and then build with maven as usual.

Ahem.. I think you missunderstud the M10N we've done for 2.2. A Cocoon 
user don't build it's Cocoon apps from Cocoon sources anymore. Instead 
it gets an M2 Cocoon archetype, build its app in there (this includes a 
root sitemap, something you wouldn't really touch in 2.1 because of the 
predefined components in there!) build a war file (which already 
containes all jars the app needs) and ship that to your test, 
intergration and production servers.

What this discussion is looking for is a solution for us Cocoon 
developers (and those who want to check it before final release). In 
the end Cocoon 2.2 users shouldn't have the need to check out the 
sources anymore.

Thus a solution with a M2 repository in our Cocoon SVN repository isn't 
going in the right direction for our users just for us Developers.



- -- 
Giacomo Pati
Otego AG, Switzerland -
Orixo, the XML business alliance -
Version: GnuPG v1.4.4 (GNU/Linux)


View raw message