Message is that even if I'm okay, past fustration barriers and so on, its a bigger problem than just me understanding whats going on. You're a trainer, you must have come across these problems. Yes so far I've needed to dig through the source to see whats going on, despite trying to blackbox cocoon and use it as a framework.
The reference to building a struts-spring-hibernate project was to simply illustrate that there ways of being able to get folk in and coding quickly, able to work on different parts of a system, without understanding all the parts,
Which roles do you have in your projects?
and without requiring to compile the framework itself.
We know this - we are working on getting rid of the compilation step with 2.2 again.
Perhaps a jvm version number with the archieve id would be a way of getting around this. I'd like to understand this incompatability between 1.3 and 1.4 with jvm versions and how other projects manage this. My guess is that the problem would be with one of the dependencies rather than the cocoon source. The thread seems to be a general discussion on how its okay to expect folk wanting to edit html shouldn't mind compiling the framework s/he is hoping to use, with little to no mention of the real problem (where the incompatability is).
--
Reinhard P�tz Independant Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}web(log): http://www.poetz.cc --------------------------------------------------------------------
