[ http://issues.apache.org/jira/browse/JCR-227?page=comments#action_12331611 ]
Jukka Zitting commented on JCR-227: ----------------------------------- Edgar Poce wrote: > Well, I'm not sure whether each subproject should have its own release cycle. Agreed. My point was that if we end up in such a situation, the subproject should either be integrated in the main release cycle or graduated into a separate project. The Jackrabbit project should only make Jackrabbit releases. :-) > move core module to a subdirectory > ---------------------------------- > > Key: JCR-227 > URL: http://issues.apache.org/jira/browse/JCR-227 > Project: Jackrabbit > Type: Wish > Components: maven > Reporter: fabrizio giustina > Assignee: Jukka Zitting > Priority: Minor > Fix For: 1.0 > > Actually the jackrabbit svn holds the code for the main module in the top > level dir > http://svn.apache.org/repos/asf/incubator/jackrabbit/trunk/ > and all the subprojects in subdirectories > http://svn.apache.org/repos/asf/incubator/jackrabbit/trunk/contrib/ > given this layout is not possible to checkout from svn only the main module > (if you get trunk, you get all), and you can't work to different modules > using any IDE which doesn't support nested projects (namely Eclipse). > I would like to request moving the main module (that means moving all the > files and directories in trunk except "contrib") from > http://svn.apache.org/repos/asf/incubator/jackrabbit/trunk/ > to > http://svn.apache.org/repos/asf/incubator/jackrabbit/trunk/jackrabbit > following the usual organization of maven-based projects and solving these > problems... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
