If we did consider al three as separate projects http://...sevak/api/ , http://...sevak/jo/ , http://...sevak/jetty/ etc would it be OK?
What I'm in Merlin is to package the suite under a root directory (e.g. "servak").
Cough, 'sevak' cough :-)
Each sub-directory contains the respective projects. You can then easly maintain the subprojects as semi-independent builds. As Maven gets stronger on the composite build side then it will be clear when to move to considation of the documentation. Anyway - aside from the problems - for Merlin I find the seperate sub-projects good and the considated document sufficient even with the problems I mentioned.
Agree. Lets look for mindshare and move towards a vote.
I would be supportive of the update.
So be it. Vote looming.
There are not that many users of Sevak yet so few would be in pain. Perhaps we could simplify further by not generating the xinfo.
To be frank xinfo generation is only interesting when you don't have any xinfo. I personally prefer having direct XML xinfo in CVS because it takes away the magic - people can see the logic.
Agree. People think @ttributes are some sort of magic. For a company choosing Phoenix, or Merlin, I'd suggest that xinfo generation is best. For some 'known beast' in the OSS world, xinfo in CVS defuses the confusion a little.
- Paul
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
