I tried that already and it doesn't seem to help.
But there might be another hope:
In the M2 parent/pom.xml, we have the following repo defined:
<repositories>
<!-- needed for Apache webServices artifacts -->
<repository>
<id>apache.m1</id>
<name>Apache Maven 1 Repository</name>
<url>http://people.apache.org/repository</url>
<layout>legacy</layout>
</repository>
</repositories>
Since it's a maven1 repo, the "org.apache.axis2:axis-1.1.jar" is pulled in
from this repo as a maven1 artifact whose dependencies cannot be resolved
transitively. We might be able to take advantage of this side effect and add
axiom 1.2.1 explictly as follows (or simple bump the axiom version to 1.2.1
in the dependencyManagement section in sca/pom.xml):
<dependency>
<groupId>org.apache.ws.commons.axiom</groupId>
<artifactId>axiom-api</artifactId>
<version>1.2.1</version>
<scope>compile</scope>
</dependency>
<dependency>
<groupId>org.apache.ws.commons.axiom</groupId>
<artifactId>axiom-impl</artifactId>
<version>1.2.1</version>
<scope>runtime</scope>
</dependency>
Please note that axis2 1.1 artifacts are available in maven2 repos as well
and these versions will bring in the axiom 1.2 stuff. I'm not sure if
there's a way in maven to control the order of remote repositories.
Thanks,
Raymond
----- Original Message -----
From: "Jeremy Boynes" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Friday, December 01, 2006 2:03 PM
Subject: Re: Much ado about nothing (Re: WSCOMMONS-131 and options for
Tuscany SCA Java M2 release)
There's mention in that bug's comments of ordering being important - have
you tried rearranging the ordering in our pom to see if it makes a
difference?
--
Jeremy
On Dec 1, 2006, at 12:29 PM, Raymond Feng wrote:
Hi,
Axiom 1.2.1 is out but I had no luck to get the exclusion working as I
hit a serious maven bug:
http://jira.codehaus.org/browse/MNG-1797
Thanks,
Raymond
----- Original Message ----- From: "Davanum Srinivas"
<[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Thursday, November 30, 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 a specific dependency
on the new one?
thanks,
dims
On 11/29/06, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
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 <[EMAIL PROTECTED]> wrote:
> 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 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 #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 :-)
> >>
> >> Are there any artifacts for 1.2.1 that we can take a look at?
> >> --
> >> Jeremy
> >>
> >
> >
>
>
>
--------------------------------------------------------------------
-
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service
Developers)
--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service
Developers)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
