+1 to having a shared trunk. In Apache OODT, we tried to separate them (and prior to bringing the software to Apache did so at JPL), however we found that folks want a fully compatible Apache release, including compatible versions of the sub components. See OODT-15 [1] for our discussion and decision to keep it as 1 trunk.
Cheers, Chris [1] https://issues.apache.org/jira/browse/OODT-15 On Jul 16, 2012, at 3:29 PM, Chen, Pei wrote: > https://issues.apache.org/jira/browse/CTAKES-10?focusedCommentId=13415605#comment-13415605 > how should the new SVN structure look like for Apache cTAKES? > > Currently in SF, it looks like: > {cTAKES-root} > /branches > /tags > /trunk > -/cTAKES > -/core > /src > /desc > -/chunker > -/coref-resolver > Etc.. > Which means that all of those projects are all children of trunk and will > share the same release cycle. > > One alternative option looks something like (each component could have it's > own trunk/jar file?): > {cTAKES-root} > -/ctakes-core > /trunk > /src > /java > /main > /resources > /branches > /tags > -/ctakes-chunker > /trunk > /src > /java > /main > /resources > /branches > /tags > -/ctakes-coreference > /trunk > /src > /java > /main > /resources > /branches > /tags > > There are pro's and con's to both, but let's get the discussion started as > this will be required for the code migration. > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: [email protected] WWW: http://sunset.usc.edu/~mattmann/ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
