ado about nothing (Re: WSCOMMONS-131 and options for
Tuscany SCA Java M2 release)
Hi,
I did some further investigations with Ant and here are some observations:
1) maven2 build will pull in axis2 artifacts from maven1 or maven2 repo
randomly. I even see a mixture that the pom is downloaded
?
Thanks,
Raymond
- Original Message -
From: Raymond Feng [EMAIL PROTECTED]
To: tuscany-dev@ws.apache.org
Sent: Monday, December 04, 2006 12:10 PM
Subject: Re: Much ado about nothing (Re: WSCOMMONS-131 and options for
Tuscany SCA Java M2 release)
Hi,
I did some further investigations
I'm starting to wonder if the subject line is even more apt than we realize
and we're just assuming this is a significant problem without investigating.
AFAICT the only thing thats happening is what I originally reported - you
see log messages about the AXIOM API SNAPSHOT when using the WS
This is a good set of observations and if we can figure out why this
snapshot is not being used (or even returned despite the dependency
onit) I think we'd be good to go. If we're going to do that though I
think it's important to understand the cause of this behaviour and
not just the
, 2006 5:48 AM
Subject: Re: Much ado about nothing (Re: WSCOMMONS-131 and options for
Tuscany SCA Java M2 release)
Folks,
Can't you just use maven's exclusion mechanism:
http://maven.apache.org/ref/2.0.4/maven-model/maven.html#class_exclusion
to exclude the specific version of axiom and add
Folks,
Can't you just use maven's exclusion mechanism:
http://maven.apache.org/ref/2.0.4/maven-model/maven.html#class_exclusion
to exclude the specific version of axiom and add a specific dependency
on the new one?
thanks,
dims
On 11/29/06, Davanum Srinivas [EMAIL PROTECTED] wrote:
Aha! so
Hi,
This is an appealing proposal. I will give a try.
Thanks,
Raymond
- Original Message -
From: Davanum Srinivas [EMAIL PROTECTED]
To: tuscany-dev@ws.apache.org
Sent: Thursday, November 30, 2006 5:48 AM
Subject: Re: Much ado about nothing (Re: WSCOMMONS-131 and options for
Tuscany
Thanks, Dims.
We will need a new release of Axis2 as well, since the POMs in
Axis2 1.1 point to Axiom 1.2. Will this be available at the
same time as the new release of Axiom?
Simon
Davanum Srinivas wrote:
Thanks Jim/Jeremy :)
Please look at the pom's in the svn. the SNAPSHOT jars are
Aha! so there's a catch. We still haven't started the process for a
Axis2 1.1.1. Hoping to do that with a thorough JIRA scrub this week or
early next week. To see what needs to be fixed for a quick 1.1.1
release. Will let you all know when we have some idea.
thanks,
dims
On 11/29/06, Simon Nash
On yesterday's IRC chat we discussed WSCOMMONS-131, which causes the
current Tuscany M2 RC to have a SNAPSHOT dependency on axiom-api.
This creates a time bomb which would cause the Axis2 binding
in Tuscany SCA Java M2 to stop working at some future time when
incompatible changes are made to the
Hi,
My opinion is that 'we release what we have presently because IMO we should
not be pushing M2 any further. It would also be good if we can publish the
potential problem in our website and ask users to check back at the website
for patches. This way we just get done with M2 and move
This the kind of thing usually added in release notes as well..
-- dims
On 11/28/06, Venkata Krishnan [EMAIL PROTECTED] wrote:
Hi,
My opinion is that 'we release what we have presently because IMO we should
not be pushing M2 any further. It would also be good if we can publish the
potential
I think that it is irresponsible to put out a release that we know
has a lurking problem in it with no workaround.
I was chatting with Raymond yesterday and he was planning on working
with Axis2/Axiom to get -131 fixed fairly quickly so waiting a few
days should be no big deal.
In the
the
axis2 or axiom release.
Thanks,
Raymond
- Original Message -
From: Jeremy Boynes [EMAIL PROTECTED]
To: tuscany-dev@ws.apache.org
Sent: Tuesday, November 28, 2006 8:43 AM
Subject: Re: WSCOMMONS-131 and options for Tuscany SCA Java M2 release
I think that it is irresponsible
- From: Jeremy Boynes [EMAIL PROTECTED]
To: tuscany-dev@ws.apache.org
Sent: Tuesday, November 28, 2006 8:43 AM
Subject: Re: WSCOMMONS-131 and options for Tuscany SCA Java M2 release
I think that it is irresponsible to put out a release that we know
has a lurking problem in it with no workaround
On the chat we identified 3 options that we could consider for
how to deal with this problem.
1. release what we have
2. release without axis
3. wait until axis is fixed
Other options were discussed but did not get much support. For the
three that I have listed above (as summarized by Meeraj
Folks,
Fact #1: WSCOMMONS-131 is fixed in SVN.
Fact #2: We've started a VOTE for releasing Axiom 1.2.1 [1]. Plan is
to do the release this week.
What's the ruckus all about? (Please don't make me all the emails :)
thanks,
dims
[1]
(Please don't make me *READ* all the emails :)
On 11/28/06, Davanum Srinivas [EMAIL PROTECTED] wrote:
Folks,
Fact #1: WSCOMMONS-131 is fixed in SVN.
Fact #2: We've started a VOTE for releasing Axiom 1.2.1 [1]. Plan is
to do the release this week.
What's the ruckus all about? (Please don't
On Nov 28, 2006, at 1:24 PM, Davanum Srinivas wrote:
Folks,
Fact #1: WSCOMMONS-131 is fixed in SVN.
Fact #2: We've started a VOTE for releasing Axiom 1.2.1 [1]. Plan is
to do the release this week.
What's the ruckus all about? (Please don't make me all the emails :)
Thanks Dims, that's
On Nov 28, 2006, at 1:24 PM, Davanum Srinivas wrote:
Folks,
Fact #1: WSCOMMONS-131 is fixed in SVN.
Fact #2: We've started a VOTE for releasing Axiom 1.2.1 [1]. Plan is
to do the release this week.
What's the ruckus all about? (Please don't make me all the emails :)
Well, now, nothing :-)
Thanks Jim/Jeremy :)
Please look at the pom's in the svn. the SNAPSHOT jars are here:
http://ws.zones.apache.org/repository/org.apache.ws.commons.axiom/jars/
thanks,
dims
On 11/28/06, Jeremy Boynes [EMAIL PROTECTED] wrote:
On Nov 28, 2006, at 1:24 PM, Davanum Srinivas wrote:
Folks,
Fact
21 matches
Mail list logo
