The current Tuscany SVN structure is very complicated with active sub-projects hidden down various places. I'd like to propose that we streamline the curent SVN structure based on the creation of couple sub-projects in Tuscany :

Current SVN Structure

|-- branches
|   |-- various release and other branches
|   |   |das, sdo, sdo cts, sca, native, etc
|   |   |sca 1.x active dev stream
|-- collaboration
|-- contrib
|   `-- java
|-- cpp
|-- interop
|-- java
|   |-- Current SCA 2.x, DAS and SDO and SDO CTS
|   |-- sca-1.x-contrib
|   |-- sca-contrib
|-- maven
|-- maven-plugins
|--sandbox
|-- site
`-- tags

Proposal

  • Create the following SVN sub-projects
    • sca-java-1.x
    • sca-java-2.x
    • das-java
    • sdo-java
    • cpp or (sdo-cpp/sca-cpp)
  • Each sub-project will have the following basic SVN structure
    • Project
      • trunk
      • branches
      • tags
      • contrib (optional)
  • Contents from the current SVN structure (e.g tags, branches, contrib folders, etc) will then be merged into the proposed SVN structure for each sub-project
  • The following folders will not change
    • Maven
    • Site
    • Sanbox
  • The following folders does not seem to be in use currently
    • collaboration (not used... might be removed)
    • interop (suggested to go with sdo-java)
  • TBD
    • Maven plugins (slaws suggested to go with sca-java-2.x)
    • SDO CTS (suggested to go with sdo-java)
  • No labels