Dion Gillard wrote:
There's a lot more issues that would need to be addressed, including how to name and address and distribute distributions of sub-components...Typically the svn structure would look like this: jakarta/commons/proper/jelly/jelly-tags/interaction/trunk jakarta/commons/proper/jelly/jelly-tags/interaction/tags jakarta/commons/proper/jelly/jelly-tags/interaction/branches But for some reason in Jelly, we have all these branches and tags for the entire project, even though the taglibs are separate source code from the core. Maybe this is something we need to talk about: what is the proper svn structure for a project like Jelly with many modules/subprojects?
Also, my "tag directory" actually needs to be modified in order, e.g., for maven to simply compile it standalone... do we want this ?
Also, the double inheritence of tag-projects is not very nice... ...To be honest, I'd rather strive for a sane jelly complete tree with frequent (sub)-releases.
paul
smime.p7s
Description: S/MIME Cryptographic Signature
