What failure do you see? The same as continuum (it seems to be hit by the
JAX-WS API pom issue)?
--------------------------------------------------
From: "ant elder" <[email protected]>
Sent: Thursday, March 26, 2009 4:15 AM
To: <[email protected]>
Subject: Re: Ship OSGi RFC119 prototype in M2? was: Re: 2.0 M2 release?
I'm also getting a build failure in node-impl-osgi after these changes
...ant
On Thu, Mar 26, 2009 at 7:44 AM, ant elder <[email protected]> wrote:
Could you copy the changes that are required to the m2 branch?
- https://svn.apache.org/repos/asf/tuscany/branches/sca-java-2.0-M2/
...ant
On Thu, Mar 26, 2009 at 12:31 AM, Raymond Feng <[email protected]>
wrote:
I have added the modules to the main build. Everything is building
successfully for the 2.x code base.
Thanks,
Raymond
--------------------------------------------------
From: "ant elder" <[email protected]>
Sent: Wednesday, March 25, 2009 9:17 AM
To: <[email protected]>
Subject: Re: Ship OSGi RFC119 prototype in M2? was: Re: 2.0 M2 release?
Heh, I've literally just finished fixing up all the legal files and
was about to cut the RC tag. But i'd say go for it if it wont take too
long, if its ready now seems a shame not to have include it in M2.
...ant
On Wed, Mar 25, 2009 at 4:09 PM, Raymond Feng <[email protected]>
wrote:
Hi,
Should we consider shipping the RFC 119 prototype in M2? At this
moment,
they are in the "rfc119" maven profile. I can add the related modules
into
the main build if we decide to release them.
The prototype code doesn't include any files from the OSGi RFC 119.
The
distribution of OSGi services are configured as an SCA composite which
contain a component with implementation.osgi. It's transparent to OSGi
users.
Thanks,
Raymond
--------------------------------------------------
From: "ant elder" <[email protected]>
Sent: Monday, March 23, 2009 2:40 AM
To: <[email protected]>
Subject: Re: 2.0 M2 release?
On Sat, Mar 21, 2009 at 9:15 AM, Simon Laws
<[email protected]>
wrote:
Those changes are in now, problems with a few things being broken
have
been fixed so it seems like a good time to start on M2. If no one
says
they need to slip anything else in I'll start on an RC1 first thing
Monday. If you are still making changes please try to be careful
the
build is still working ok till the M2 branch is taken.
...ant
+1
Simon
Ok I've now created a branch for 2.0-M2 in r757361 based on trunk
r757355. The trunk is now free to go wild in, i'll start making the
RC1 release artifacts.
...ant
