Having them under trunk means that they are built and tested as part of the
default trunk build.
Simon
Raymond Feng wrote:
+1 to keep contrib under trunk. It's part of the ongoing work in the trunk!
Raymond Feng
Sent from my iPhone
On Oct 1, 2010, at 6:42 AM, Simon Laws <simonsl...@googlemail.com> wrote:
On Fri, Oct 1, 2010 at 12:29 PM, ant elder <ant.el...@gmail.com> wrote:
On Fri, Oct 1, 2010 at 12:24 PM, Simon Nash <n...@apache.org> wrote:
ant elder wrote:
On Fri, Oct 1, 2010 at 10:56 AM, Luciano Resende <luckbr1...@gmail.com>
wrote:
What should we do with contrib?
From previous long discussion, contrib should in trunk, and can be
excluded from a release.
I think we should revisit trunk/contrib.
The suggested purpose was that it was a place to put things that were
to be built with the trunk build to ensure that they don't get broken.
I don't think that happens, for one most of the contrib stuff isn't
finished so doesn't have any tests so we've no idea if it actually
does work or not, and secondly AFAICT no one, and i mean no one,
actually builds trunk/contrib regularly anyway.
I agree with Florian and think we should get rid of it and just use
the other contrib folder.
...ant
I think trunk/contrib is a good idea and I'd like to put this structure
into 1.x after 1.6.1 is done. It would be used for the thiungs currently
in trunk but not included in releases.
Whats the problem with instead just putting those things in the
existing contrib folders at tuscany/sca-java-1.x/contrib/ and
tuscany/sca-java-2.x/contrib/?
...ant
It's more convenient for me personally to have them under
trunk/contrib which means that I can check trunk out and get the
contrib stuff too. At the higher level I have to check two separate
trees out or pull down all the tags and branches also.
Simon
--
Apache Tuscany committer: tuscany.apache.org
Co-author of a book about Tuscany and SCA: tuscanyinaction.com
