[EMAIL PROTECTED] wrote:
This thread highlights the strangeness of developer-driven development.
Cocoon users want easy: easy creation of applications, easy
integration with web servers, and easy addition of new components.
Cocoon devs want Maven to better organize blocks. (Blocks are
standard groups of components provided by the Cocoon project. Users
focus on applications and rarely create blocks.)
I wouldn't characterize it quite that way. What has motivated Cocoon
developers for years was the desire to stop requiring that Cocoon be
downloaded and built from source. Maven and Spring provided the first
workable solution for that.
Lenya users want less bugs, more functions, better control of URLs,
and expansion without compiling.
Lenya devs want Jackrabbit and a ClassLoader to add Java in blocks
like Cocoon but without restarting Lenya.
Both projects are releasing new versions that scare users.
Using Cocoon within Maven should be provided as an optional wrapper.
Maven users can use Maven to create Cocoon projects. Everybody else
can:
1. Download Cocoon,
2.a Fix the the new lines in BAT files. (Microsoft OSes)
2.b Fix the file permissions for SH files. (Real OSes)
3. Create an application with a new XMAP and some supporting files.
4. Build and run without problems.
Can 2.2 be fixed to work with and without Maven so people can choose
whether to use Maven? Can this be handled so both versions are easily
maintained?
As you already know, you have commit rights. If you can come up with a
way to do that that still meets the goals no one is going to stop you.
Ralph
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
