On Mon, Oct 4, 2010 at 9:24 PM, Luciano Resende luckbr1...@gmail.com wrote:
On Mon, Oct 4, 2010 at 12:53 AM, ant elder ant.el...@gmail.com wrote:
Totally agree with that. We should be trying hard to make trunk as small,
quick and easy to build as possible so should put stuff thats deemed not
I've spent this morning on reading our latest discussions in order to
identify what was left out on the way. I'll be starting new threads for each
topic in a moment.
On Thu, Oct 7, 2010 at 1:06 PM, ant elder ant.el...@gmail.com wrote:
Hasn't most of the work been done now, and all thats left is
On Thu, Oct 7, 2010 at 11:06 AM, ant elder ant.el...@gmail.com wrote:
Hasn't most of the work been done now, and all thats left is how to
group the shades, features and distribution folders, is there anything
else?
Don't think so.
For those I think it would be fine to initially just move
This thread has been split into 2 separate topics to keep track of each one
more easy.
On Thu, Oct 7, 2010 at 1:14 PM, Simon Laws simonsl...@googlemail.comwrote:
On Thu, Oct 7, 2010 at 11:06 AM, ant elder ant.el...@gmail.com wrote:
Hasn't most of the work been done now, and all thats left is
ant elder wrote:
On Mon, Oct 4, 2010 at 9:24 PM, Luciano Resende luckbr1...@gmail.com wrote:
On Mon, Oct 4, 2010 at 12:53 AM, ant elder ant.el...@gmail.com wrote:
Totally agree with that. We should be trying hard to make trunk as small,
quick and easy to build as possible so should put stuff
I do say development should happen in trunk, thats a fundamental part
of the Apache Way. I guess the point is that whats in trunk/contrib
(now unreleased) is that its not being actively developed, most of its
not been changed for months, its not included in any build, the
pom.xmls are out of
On Thu, Oct 7, 2010 at 3:06 AM, ant elder ant.el...@gmail.com wrote:
Hasn't most of the work been done now, and all thats left is how to
group the shades, features and distribution folders, is there anything
else? For those I think it would be fine to initially just move
features and shades to
On Thu, Oct 7, 2010 at 6:07 PM, Luciano Resende luckbr1...@gmail.com wrote:
On Thu, Oct 7, 2010 at 3:06 AM, ant elder ant.el...@gmail.com wrote:
Hasn't most of the work been done now, and all thats left is how to
group the shades, features and distribution folders, is there anything
else? For
I've seen you guys started committing things related to the distribution
structure. Could you as well make the agreed adjustments on the trunk
directory structure as they are two tightly related operations?
Are we sticking to the features + distribution + shades folders? I think the
new distro
On Wed, Oct 6, 2010 at 10:54 AM, Florian MOGA moga@gmail.com wrote:
I've seen you guys started committing things related to the distribution
structure. Could you as well make the agreed adjustments on the trunk
directory structure as they are two tightly related operations?
Are we sticking
the agreed adjustments on the trunk
directory structure as they are two tightly related operations?
Are we sticking to the features + distribution + shades folders? I think
the
new distro structure enables us to reduce all that to a single directory.
I think we can have a single folder. What
On Wed, Oct 6, 2010 at 11:30 AM, Florian MOGA moga@gmail.com wrote:
distribution sounds good to me...
distribution sounds ok to me too, its not quite perfect but its not
so far off and at least its a standard sort of directory name you'd
expect to see in a top level folder.
...ant
On Wed, Oct 6, 2010 at 11:30 AM, Florian MOGA moga@gmail.com wrote:
distribution sounds good to me...
In the distribution folder we already have all and tomcat. What
directory should we use to collect together the projects that describe
collections of jars but which are not, in their own
On Fri, Oct 1, 2010 at 10:57 PM, Florian MOGA moga@gmail.com wrote:
IMHO, the real problem is not having the contrib folder inside trunk but the
fact that we've got multiple folders named contrib which have different
purposes. Making a clean separation between them more evident will reduce
Luciano Resende wrote:
On Mon, Oct 4, 2010 at 12:53 AM, ant elder ant.el...@gmail.com wrote:
Totally agree with that. We should be trying hard to make trunk as small,
quick and easy to build as possible so should put stuff thats deemed not
quite ready yet somewhere else. If something isn't
On Fri, Oct 1, 2010 at 12:07 PM, ant elder ant.el...@gmail.com wrote:
On Fri, Oct 1, 2010 at 8:30 AM, Florian MOGA moga@gmail.com wrote:
As per thread [1], I've opened this thread to keep track of this topic.
To sum it up, I'm proposing the following reorganization:
distribution
modules
IIRC the purpose of having this code in trunk and in the default
build was to ensure that it doesn't get broken by changes to trunk.
My understanding is that if code is outside trunk, it's up to the
author(s) to keep it in sync with any trunk changes. For code inside
trunk, the community
Florian MOGA wrote:
IIRC the purpose of having this code in trunk and in the default
build was to ensure that it doesn't get broken by changes to trunk.
My understanding is that if code is outside trunk, it's up to the
author(s) to keep it in sync with any trunk changes. For
On Wed, Oct 6, 2010 at 3:36 AM, Simon Laws simonsl...@googlemail.com wrote:
On Wed, Oct 6, 2010 at 11:30 AM, Florian MOGA moga@gmail.com wrote:
distribution sounds good to me...
In the distribution folder we already have all and tomcat. What
directory should we use to collect together
i agree with the thread spawning :P issue mentioned by Luciano. In my
opinion a wiki page will rapidly get ignored/out-dated so I can try and
start new mail threads on each concerning issue i can extract out of the
latest big disscusions we had (let's say 20 replies). Given the time
difference
Totally agree with that. We should be trying hard to make trunk as small,
quick and easy to build as possible so should put stuff thats deemed not
quite ready yet somewhere else. If something isn't ready to be released or
build by the Hudson nightly build why should everybody else in the world
On Mon, Oct 4, 2010 at 12:53 AM, ant elder ant.el...@gmail.com wrote:
Totally agree with that. We should be trying hard to make trunk as small,
quick and easy to build as possible so should put stuff thats deemed not
quite ready yet somewhere else. If something isn't ready to be released or
As per thread [1], I've opened this thread to keep track of this topic.
To sum it up, I'm proposing the following reorganization:
- distribution
- modules
- samples
- extras
- maven
- archetypes
- maven-tuscany-plugin
- testing
-
On Fri, Oct 1, 2010 at 12:30 AM, Florian MOGA moga@gmail.com wrote:
As per thread [1], I've opened this thread to keep track of this topic.
To sum it up, I'm proposing the following reorganization:
distribution
modules
samples
extras
maven
archetypes
maven-tuscany-plugin
testing
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
@Ant, which other contrib folder? :) We've got plenty of those...
@Luciano, I'm referring to the fact that at the moment we have the features,
shades and distribution folders which define the distro artifacts. With the
new build structure one folder should be enough in my opinion.
Regarding the
On Fri, Oct 1, 2010 at 11:30 AM, Florian MOGA moga@gmail.com wrote:
@Ant, which other contrib folder? :) We've got plenty of those...
Heh, fair point. I was meaning this one:
https://svn.apache.org/repos/asf/tuscany/sca-java-2.x/contrib/
AIUI tuscany/sca-java-2.x/contrib/ is for stuff
On Fri, Oct 1, 2010 at 8:30 AM, Florian MOGA moga@gmail.com wrote:
As per thread [1], I've opened this thread to keep track of this topic.
To sum it up, I'm proposing the following reorganization:
distribution
modules
samples
extras
maven
archetypes
maven-tuscany-plugin
testing
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
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.
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
+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
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
On Fri, Oct 1, 2010 at 6:42 AM, Simon Laws simonsl...@googlemail.com wrote:
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
IMHO, the real problem is not having the contrib folder inside trunk but the
fact that we've got multiple folders named contrib which have different
purposes. Making a clean separation between them more evident will reduce
confusion (through means like for instance suggestive names) and misuse.
Hi,
I'm open to have a name such as experimental.
The contrib should be part of the top-down build and we control which modules
are ready to build in the contrib/pom.xml or its children poms.
Thanks,
Raymond
Raymond Feng
I also expect Hudson to be flexible enough that if the unreleased or
experimental build fails and the trunk build is successful it can proceed
to deploying the artifacts to the snapshots repo.
On Sat, Oct 2, 2010 at 1:05 AM, Raymond Feng enjoyj...@gmail.com wrote:
Hi,
I'm open to have a name
On Fri, Oct 1, 2010 at 2:57 PM, Florian MOGA moga@gmail.com wrote:
IMHO, the real problem is not having the contrib folder inside trunk but the
fact that we've got multiple folders named contrib which have different
purposes. Making a clean separation between them more evident will reduce
On Fri, Oct 1, 2010 at 3:17 PM, Florian MOGA moga@gmail.com wrote:
I also expect Hudson to be flexible enough that if the unreleased or
experimental build fails and the trunk build is successful it can proceed
to deploying the artifacts to the snapshots repo.
You can tell Hudson what
39 matches
Mail list logo
