Carsten Ziegeler pisze:
Grzegorz Kossakowski wrote:
Hmm, no I don't think so :)
Personally, I really love maven 2 and it works very well for a lot of
our projects. It makes sense to use it for developing cocoon itself, but
we should not force everyone who wants to do a cocoon project to use
maven 2. This ain't gonna work.
You're right that we should not maintain all possible different ways,
but we spend a lot of energy into 2.2 to make it independent from m2.
For example that's the reason why we extract blocks at runtime through
cocoon itself and not at build time. So if someone wants to use
something different than m2, all he has to do is to create a block. A
block is just a jar with a special format. We have to document this
format anyway and that's all we have to do for other build systems.
Nothing more but also nothing less.
But as a proof that the docs are correct and our ideas work, we should
just come up with one additional solution like an ant script. My idea is
to put this script into the documentation and not into our svn. The
script would act as a starting point.
Carsten, thanks for your clarification. Now I'm fine with the proposal and our
current view on this issue.
--
Grzegorz Kossakowski
http://reflectingonthevicissitudes.wordpress.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
