On Wed, Oct 6, 2010 at 5:55 AM, Luciano Resende luckbr1...@gmail.com wrote:
On Mon, Oct 4, 2010 at 7:59 AM, Luciano Resende luckbr1...@gmail.com wrote:
Please review and vote on RC1 of the SCA 2.0-M5.1 release.
This is a minor relese based on 2.0-M5 and provides fixes to running
Tuscany
Just a FYI. The following link was pointed out to me. It talks about
using Tuscany with the Eclipse STP project.
http://www.ibm.com/developerworks/web/library/wa-scatools/index.html
Simon
--
Apache Tuscany committer: tuscany.apache.org
Co-author of a book about Tuscany and SCA:
I've now checked in two new modules in the features directory...
tuscany-core-runtime
tuscany-base-runtime
The core-runtime is the set modules required to implement extensions
(exact set still TBD as there's probably too much in there now)
The base-runtime is core-runtime + the modules required
On Wed, Oct 6, 2010 at 10:02 AM, Simon Laws simonsl...@googlemail.com wrote:
I've now checked in two new modules in the features directory...
tuscany-core-runtime
tuscany-base-runtime
The core-runtime is the set modules required to implement extensions
(exact set still TBD as there's
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
distribution sounds good to me...
On Wed, Oct 6, 2010 at 1:22 PM, Simon Laws simonsl...@googlemail.comwrote:
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
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
ant elder wrote:
I've committed the TUSCANY-3698 fix from Padraig Myers to 2.x and will
to 1.x once i can get a build through, whats the status of 1.6.1? Is
it too late for that or can i merge this to the 1.6.1 branch? Its just
a change to the jms module code and a couple of itest updates for
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 04/10/2010 07:56, Luciano Resende wrote:
Yes, that's what I'm doing for M5.1. For next releases, I was
wondering if we should have a better strategy either by working with
OASIS or by removing all of the compliance tests from the final
release. It also makes me wonder if Oasis will give us
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
On Wed, Oct 6, 2010 at 12:03 PM, Simon Nash n...@apache.org wrote:
ant elder wrote:
I've committed the TUSCANY-3698 fix from Padraig Myers to 2.x and will
to 1.x once i can get a build through, whats the status of 1.6.1? Is
it too late for that or can i merge this to the 1.6.1 branch? Its
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
After some tidying our build is now consistently failing in Hudson
when it tries to archive the artifacts that the distro build produces.
The archive step takes ages for all of the artifacts for some reason
but it times out with the large zips that we produce for the distro.
[INFO] Installing
On Wed, Oct 6, 2010 at 3:40 PM, ant elder ant.el...@gmail.com wrote:
On Wed, Oct 6, 2010 at 12:03 PM, Simon Nash n...@apache.org wrote:
ant elder wrote:
I've committed the TUSCANY-3698 fix from Padraig Myers to 2.x and will
to 1.x once i can get a build through, whats the status of 1.6.1? Is
[
https://issues.apache.org/jira/browse/TUSCANY-3698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ant elder closed TUSCANY-3698.
--
Resolution: Fixed
Now also committed to 1.x and the 1.6.1 branch so should be in 1.6.1 release.
On Wed, Oct 6, 2010 at 7:48 AM, ant elder ant.el...@gmail.com wrote:
On Wed, Oct 6, 2010 at 5:55 AM, Luciano Resende luckbr1...@gmail.com wrote:
On Mon, Oct 4, 2010 at 7:59 AM, Luciano Resende luckbr1...@gmail.com wrote:
Please review and vote on RC1 of the SCA 2.0-M5.1 release.
This is a
There is currently some Javadoc from previous Java SCA releases
(0.9 and 1.4) on the Tuscany website under the path
tuscany.apache.org/doc/javadoc/
I'd like to put up something more current, so I tried to make a new
directory on p.a.o under
/www/tuscany.apache.org/doc/javadoc/
This failed
On Wed, Oct 6, 2010 at 12:22 PM, Simon Nash n...@apache.org wrote:
There is currently some Javadoc from previous Java SCA releases
(0.9 and 1.4) on the Tuscany website under the path
tuscany.apache.org/doc/javadoc/
I'd like to put up something more current, so I tried to make a new
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
Luciano Resende wrote:
On Wed, Oct 6, 2010 at 12:22 PM, Simon Nash n...@apache.org wrote:
There is currently some Javadoc from previous Java SCA releases
(0.9 and 1.4) on the Tuscany website under the path
tuscany.apache.org/doc/javadoc/
I'd like to put up something more current, so I tried
On Wed, Oct 6, 2010 at 7:12 AM, Mike Edwards
mike.edwards.inglen...@gmail.com wrote:
On 04/10/2010 07:56, Luciano Resende wrote:
Yes, that's what I'm doing for M5.1. For next releases, I was
wondering if we should have a better strategy either by working with
OASIS or by removing all of the
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
27 matches
Mail list logo
