Can we flatten the language into the project like the following?
tuscany
sca-java-1.x
sca-java-2.x
das-java
sdo-java
sdo-cpp
sca-cpp
Thanks,
Raymond
--------------------------------------------------
From: "Simon Laws" <[email protected]>
Sent: Wednesday, September 23, 2009 10:23 AM
To: <[email protected]>
Subject: Re: [DISCUSS] Simplifying our current SVN Structure
On Wed, Sep 23, 2009 at 4:40 PM, Luciano Resende <[email protected]>
wrote:
On Wed, Sep 23, 2009 at 4:48 AM, Simon Laws <[email protected]>
wrote:
I like the idea about being a bit more organized (goes for docs too
but that is another thread). I have questions about the proposal
- Create the following SVN sub-projects
--- SCA 1.x
--- SCA 2.x
--- DAS
--- SDO
--- CPP
This seems a bit unbalanced. On one hand you have the projects split
by programming model (SCA, SDO etc.). On the other you have them
grouped by implementation technology (CPP). Is your proposal that SCA
1.x, SCA 2.x, DAS, SDO are Java projects?
I didn't propose splitting the CPP because my understanding is that
they are very tight together at the moment, if this is not the case,
we could look into a different structure.
IIRC CPP SCA depends on CPP SDO (but not the other way round). My
unbalanced comment was that you didn't propose....
svn/
Java
SCA 1.x
SCA 2.x
DAS
SDO
CPP
SCA
SDO
DAS
But put the Java projects at the top level. Was there a particular
reason for that?
- Each sub-project will have the following basic SVN structure
-- Project
---- trunk
---- branches
---- tags
---- contrib
What is the intention of contrib here? We discussed a while back the
idea of having a contrib directory where people could check in and
work on anything that is not yet ready for release so that we don't
have to ask the "what should be in the release" question each time we
do a release. Is this it? If so it should probably be inside trunk.
We currently have verious projects in contrib, and they are not
grouped together (e.g 1.x branch is in branches and the contrib is in
main 2.x trunk).. so the idea was to have a contrib together with each
sub-project as needed, and mostly to accommodate the two sca contrib
contents.
https://svn.apache.org/repos/asf/tuscany/java/sca-1.x-contrib/
https://svn.apache.org/repos/asf/tuscany/java/sca-contrib/
OK, I see. If I remember rightly the sca-contrib stuff all came from
the equinox branch or the trunk before the equinox branch was merged.
This may not be that useful now as both 1.x and 2.x have moved on
since then.
- 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
README says that this is a collaboration area for all ASF committers.
Yes, but since it's creation, nothing has been done here... do we
still need it ?
I don't have any plans but it's not doing any harm.
--- interop
This was for interop testing between CPP and Java SDO.I imagine it's
out of date but could be added to the CPP SDO project if you want to
tidy it out of the way.
+1, works for me...
- TBD
--- Maven plugins (continue as a sub-project ???)
We'll it's Java but the plugins here are only relevant to the 2.x
codebase
That's my thought as well, but I believe Ant had some concerns with
moving this back to 2.x... and I want be flexible and try to
accommodate everybody's need :)
OK, I understand.
Simon
