bart remmerie pisze:
I've been a 'jojo' cocoon user for some years now and a convinced addict.
The learning curve is rather steep, but with nices 'plateaus': repeated
steps of steep learning followed by rather easy mass-production.
<snip/>
Upgrading to a next version has never been a smooth process so far. I'm
currently using 2.1.10 and the YourCocoonBasedProject ant scripts from
the wiki. One day, I'll shift to 2.2, but so far, trying to set it up
out of curiosity has brought me nothing but frustration.
Could you share your experiences? I would like to know what caused the
frustration.
As a cocoon user, learning yet another framework (Maven) is not what I'm
looking for. If is can make development easier, I'm interested to
learn, but please explain the benefits & basics to get people going
before pushing them into a direction (they didn't ask for in the first
place).
Or replace the 'easy to use' by 'easy to use, ... if you are an
experienced user of spring, maven and other related frameworks like
hibernate, ...)
Even I'm Cocoon developer I don't think about myself like a Maven or Spring guru. After switching to Maven 2.0.6 I'm really happy with it
because most of annoying bugs has been resolved and working with Maven is really straightforward. Thanks to archetypes and quite good
Cocoon's documentation on this topic (kudos to Reinhard) you really don't need to know Maven inside out.
If cocoon has the ambition to be used, please pay attention to what the
(potential) user wants (and documentation might be just one of the
priorities).
Our aim is to pay the attention but it's good if users provide some feedback.
Thanks for your thoughts.
--
Grzegorz Kossakowski
http://reflectingonthevicissitudes.wordpress.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
