+1 if you change: "with the subproject's directory being named after the subproject's root package"
to "with the subproject's directory being named after the subproject's *bundle symbolic name*" which I think was previously discussed. There is also no clear definition of what a "root" package is anyway :-) BJ Hargrave Senior Technical Staff Member, IBM OSGi Fellow and CTO of the OSGi Alliance [EMAIL PROTECTED] Office: +1 407 849 9117 Mobile: +1 386 848 3788 "Richard S. Hall" <[EMAIL PROTECTED]> 2005-12-21 11:55 AM Please respond to [email protected] To [email protected] cc Subject [VOTE] Repository structure I think it is about time we made a final decision on our SVN repository structure. According to my understanding of the situation, it seems like we have gravitated toward a Maven-like subproject structure. Thus, I propose we finalize the overall repository structure as follows (example subproject shown): felix/ trunk/ org.apache.felix.framework/ org.apache.felix.shell/ org.apache.felix.shell.tui/ org.apache.felix.prefs.jndi/ ... releases/ org.apache.felix.framework-0.8.0/ org.apache.felix.shell-1.0.0/ org.apache.felix.shell-1.0.1/ ... sandbox/ tbennett/ erodriquez/ akarasulu/ ... The trunk/ directory contains a subdirectory for each subproject with the subproject's directory being named after the subproject's root package. The releases/ directory contains release snapshots of the subprojects. The sandbox/ directory contains directories for developer experimentation. Each individual subproject will have the following Maven 2 structure: org.apache.felix.<subproject>/ src/ main/ java/ org/apache/felix/... resources/ test/ java/ org/apache/felix/... resources/ [ ] +1 Accept SVN repository structure. [ ] 0 Does not matter to me. [ ] -1 Reject SVN repository structure. -> richard
