You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Mick Knutson <mi...@gmail.com> on 2006/09/18 23:56:04 UTC
[m204] Issue with transistive dependancies and Springframework
I am trying to use this:
<dependency>
<groupId>org.springframework</groupId>
<artifactId>spring</artifactId>
<version>2.0-rc3</version>
<type>jar</type>
<scope>compile</scope>
</dependency>
<dependency>
<groupId>org.springframework</groupId>
<artifactId>spring-mock</artifactId>
<version>2.0-rc3</version>
<type>jar</type>
<scope>compile</scope>
</dependency>
<dependency>
<groupId>aopalliance</groupId>
<artifactId>aopalliance</artifactId>
<version>1.0</version>
<type>jar</type>
</dependency>
<dependency>
<groupId>aspectj</groupId>
<artifactId>aspectjrt</artifactId>
<version>1.5.2a</version>
<type>jar</type>
</dependency>
But my war seems to be getting 1.2.7 and 2.0-rc3 jars
Why?
--
Thanks
DJ MICK
http://www.djmick.com
http://www.myspace.com/mickknutson
Re: [m204] Issue with transistive dependancies and Springframework
Posted by Mick Knutson <mi...@gmail.com>.
Thanks. Works great.
On 10/11/06, Aleksei Valikov <va...@gmx.net> wrote:
>
> Hi.
>
> > Is anyone else using spring 2.0 and acegi 1.0.2????
> >
> >
> > It seems acegi 1.0.2 is requiring spring 1.2.7 and adds 1.2.7 and 2.0into
> > my ear.
> > Is this an issue with the spring libs I imported?
>
> Below are my current dependencies:
>
> <dependency>
> <groupId>org.springframework</groupId>
> <artifactId>spring</artifactId>
> <version>2.0-rc3</version>
> </dependency>
> <dependency>
> <groupId>org.springframework</groupId>
> <artifactId>spring-mock</artifactId>
> <version>2.0-rc3</version>
> </dependency>
> <dependency>
> <groupId>org.acegisecurity</groupId>
> <artifactId>acegi-security</artifactId>
> <version>1.0.1</version>
> <exclusions>
> <exclusion>
> <groupId>org.springframework
> </groupId>
>
> <artifactId>spring-remoting</artifactId>
> </exclusion>
> <exclusion>
> <groupId>org.springframework
> </groupId>
>
> <artifactId>spring-jdbc</artifactId>
> </exclusion>
> <exclusion>
> <groupId>org.springframework
> </groupId>
>
> <artifactId>spring-support</artifactId>
> </exclusion>
> <exclusion>
> <groupId>org.springframework
> </groupId>
>
> <artifactId>spring-mock</artifactId>
> </exclusion>
> <exclusion>
> <groupId>cas</groupId>
> <artifactId>casclient</artifactId>
> </exclusion>
> <exclusion>
> <groupId>aspectj</groupId>
> <artifactId>aspectjrt</artifactId>
> </exclusion>
> <exclusion>
> <groupId>
> org.apache.directory.server</groupId>
>
> <artifactId>apacheds-core</artifactId>
> </exclusion>
> <exclusion>
> <groupId>org.slf4j</groupId>
>
> <artifactId>slf4j-log4j12</artifactId>
> </exclusion>
> </exclusions>
> </dependency>
>
> Bye.
> /lexi
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
Thanks
DJ MICK
http://www.djmick.com
http://www.myspace.com/mickknutson
Re: [m204] Issue with transistive dependancies and Springframework
Posted by Aleksei Valikov <va...@gmx.net>.
Hi.
> Is anyone else using spring 2.0 and acegi 1.0.2????
>
>
> It seems acegi 1.0.2 is requiring spring 1.2.7 and adds 1.2.7 and 2.0 into
> my ear.
> Is this an issue with the spring libs I imported?
Below are my current dependencies:
<dependency>
<groupId>org.springframework</groupId>
<artifactId>spring</artifactId>
<version>2.0-rc3</version>
</dependency>
<dependency>
<groupId>org.springframework</groupId>
<artifactId>spring-mock</artifactId>
<version>2.0-rc3</version>
</dependency>
<dependency>
<groupId>org.acegisecurity</groupId>
<artifactId>acegi-security</artifactId>
<version>1.0.1</version>
<exclusions>
<exclusion>
<groupId>org.springframework</groupId>
<artifactId>spring-remoting</artifactId>
</exclusion>
<exclusion>
<groupId>org.springframework</groupId>
<artifactId>spring-jdbc</artifactId>
</exclusion>
<exclusion>
<groupId>org.springframework</groupId>
<artifactId>spring-support</artifactId>
</exclusion>
<exclusion>
<groupId>org.springframework</groupId>
<artifactId>spring-mock</artifactId>
</exclusion>
<exclusion>
<groupId>cas</groupId>
<artifactId>casclient</artifactId>
</exclusion>
<exclusion>
<groupId>aspectj</groupId>
<artifactId>aspectjrt</artifactId>
</exclusion>
<exclusion>
<groupId>org.apache.directory.server</groupId>
<artifactId>apacheds-core</artifactId>
</exclusion>
<exclusion>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-log4j12</artifactId>
</exclusion>
</exclusions>
</dependency>
Bye.
/lexi
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m204] Issue with transistive dependancies and Springframework
Posted by Wayne Fay <wa...@gmail.com>.
Mick,
I'm not using Spring and Acegi, so this might not work, but perhaps
try adding an <excludes> node on the Acegi dependency to exclude
Spring, and then add the Spring dependency by itself.
If this doesn't work, post your pom back to the list and we'll try to
help debug it some more...
Wayne
On 10/10/06, Mick Knutson <mi...@gmail.com> wrote:
> Is anyone else using spring 2.0 and acegi 1.0.2????
>
>
> It seems acegi 1.0.2 is requiring spring 1.2.7 and adds 1.2.7 and 2.0 into
> my ear.
> Is this an issue with the spring libs I imported?
>
>
>
> On 9/18/06, Wendy Smoak <ws...@gmail.com> wrote:
> >
> > On 9/18/06, Mick Knutson <mi...@gmail.com> wrote:
> >
> > > I am trying to use this:
> > ... {spring dependencies} ...
> > > But my war seems to be getting 1.2.7 and 2.0-rc3 jars
> > > Why?
> >
> > Did you upgrade this app to Spring 2? If so, did you 'mvn clean'
> > after changing the dependency versions? The old ones may have been
> > left in WEB-INF/lib under 'target'.
> >
> > If that's not it, run
> > mvn package -X > output.txt
> >
> > and take a look at the output, which will include an indented tree
> > view of dependencies. You'll be able to see where each dependency is
> > coming from, and exclude the ones you don't want.
> >
> > You can get two versions of the same library if the groupId has
> > changed without being "relocated" in the repository. (Didn't Spring
> > change from 'springframework' to 'org.springframework'?) Maven has no
> > way of knowing they are the 'same'.
> >
> > HTH,
> > --
> > Wendy
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
>
> --
>
> Thanks
>
> DJ MICK
> http://www.djmick.com
> http://www.myspace.com/mickknutson
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m204] Issue with transistive dependancies and Springframework
Posted by Carlos Sanchez <ca...@apache.org>.
You have to exclude spring then.
On 10/11/06, Mick Knutson <mi...@gmail.com> wrote:
> My EAR has
> spring-2.0.jar
> spring-[partial lib]-1.2.7 (i.e spring-aop-1.2.7)
> ....
>
>
> On 10/10/06, Carlos Sanchez <ca...@apache.org> wrote:
> >
> > That's actually wrong. See
> >
> > http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html
> >
> > You don't use excludes to change the version of a dependency, you have
> > to explicitly add that dependency in your pom in the version you want.
> >
> > "Dependency mediation - this determines what version of a dependency
> > will be used when multiple versions of an artifact are encountered.
> > Currently, Maven 2.0 only supports using the "nearest definition" - so
> > you can always guarantee a version by declaring it explicitly in your
> > project's POM."
> >
> > On 10/11/06, Max Cooper <ma...@maxcooper.com> wrote:
> > > Mick,
> > >
> > > I am using Spring 2.0 and Acegi 1.0.2.
> > >
> > > Use dependency excludes to suppress the Spring 1.2.7 stuff.
> > >
> > > -Max
> > >
> > > Mick Knutson wrote:
> > > > Is anyone else using spring 2.0 and acegi 1.0.2????
> > > >
> > > >
> > > > It seems acegi 1.0.2 is requiring spring 1.2.7 and adds 1.2.7 and 2.0into
> > > > my ear.
> > > > Is this an issue with the spring libs I imported?
> > > >
> > > >
> > > >
> > > > On 9/18/06, Wendy Smoak <ws...@gmail.com> wrote:
> > > >>
> > > >> On 9/18/06, Mick Knutson <mi...@gmail.com> wrote:
> > > >>
> > > >> > I am trying to use this:
> > > >> ... {spring dependencies} ...
> > > >> > But my war seems to be getting 1.2.7 and 2.0-rc3 jars
> > > >> > Why?
> > > >>
> > > >> Did you upgrade this app to Spring 2? If so, did you 'mvn clean'
> > > >> after changing the dependency versions? The old ones may have been
> > > >> left in WEB-INF/lib under 'target'.
> > > >>
> > > >> If that's not it, run
> > > >> mvn package -X > output.txt
> > > >>
> > > >> and take a look at the output, which will include an indented tree
> > > >> view of dependencies. You'll be able to see where each dependency is
> > > >> coming from, and exclude the ones you don't want.
> > > >>
> > > >> You can get two versions of the same library if the groupId has
> > > >> changed without being "relocated" in the repository. (Didn't Spring
> > > >> change from 'springframework' to 'org.springframework'?) Maven has
> > no
> > > >> way of knowing they are the 'same'.
> > > >>
> > > >> HTH,
> > > >> --
> > > >> Wendy
> > > >>
> > > >> ---------------------------------------------------------------------
> > > >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > >> For additional commands, e-mail: users-help@maven.apache.org
> > > >>
> > > >>
> > > >
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> > >
> >
> >
> > --
> > I could give you my word as a Spaniard.
> > No good. I've known too many Spaniards.
> > -- The Princess Bride
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
>
> --
>
> Thanks
>
> DJ MICK
> http://www.djmick.com
> http://www.myspace.com/mickknutson
>
>
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m204] Issue with transistive dependancies and Springframework
Posted by Mick Knutson <mi...@gmail.com>.
My EAR has
spring-2.0.jar
spring-[partial lib]-1.2.7 (i.e spring-aop-1.2.7)
....
On 10/10/06, Carlos Sanchez <ca...@apache.org> wrote:
>
> That's actually wrong. See
>
> http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html
>
> You don't use excludes to change the version of a dependency, you have
> to explicitly add that dependency in your pom in the version you want.
>
> "Dependency mediation - this determines what version of a dependency
> will be used when multiple versions of an artifact are encountered.
> Currently, Maven 2.0 only supports using the "nearest definition" - so
> you can always guarantee a version by declaring it explicitly in your
> project's POM."
>
> On 10/11/06, Max Cooper <ma...@maxcooper.com> wrote:
> > Mick,
> >
> > I am using Spring 2.0 and Acegi 1.0.2.
> >
> > Use dependency excludes to suppress the Spring 1.2.7 stuff.
> >
> > -Max
> >
> > Mick Knutson wrote:
> > > Is anyone else using spring 2.0 and acegi 1.0.2????
> > >
> > >
> > > It seems acegi 1.0.2 is requiring spring 1.2.7 and adds 1.2.7 and 2.0into
> > > my ear.
> > > Is this an issue with the spring libs I imported?
> > >
> > >
> > >
> > > On 9/18/06, Wendy Smoak <ws...@gmail.com> wrote:
> > >>
> > >> On 9/18/06, Mick Knutson <mi...@gmail.com> wrote:
> > >>
> > >> > I am trying to use this:
> > >> ... {spring dependencies} ...
> > >> > But my war seems to be getting 1.2.7 and 2.0-rc3 jars
> > >> > Why?
> > >>
> > >> Did you upgrade this app to Spring 2? If so, did you 'mvn clean'
> > >> after changing the dependency versions? The old ones may have been
> > >> left in WEB-INF/lib under 'target'.
> > >>
> > >> If that's not it, run
> > >> mvn package -X > output.txt
> > >>
> > >> and take a look at the output, which will include an indented tree
> > >> view of dependencies. You'll be able to see where each dependency is
> > >> coming from, and exclude the ones you don't want.
> > >>
> > >> You can get two versions of the same library if the groupId has
> > >> changed without being "relocated" in the repository. (Didn't Spring
> > >> change from 'springframework' to 'org.springframework'?) Maven has
> no
> > >> way of knowing they are the 'same'.
> > >>
> > >> HTH,
> > >> --
> > >> Wendy
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > >> For additional commands, e-mail: users-help@maven.apache.org
> > >>
> > >>
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
>
> --
> I could give you my word as a Spaniard.
> No good. I've known too many Spaniards.
> -- The Princess Bride
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
Thanks
DJ MICK
http://www.djmick.com
http://www.myspace.com/mickknutson
Re: [m204] Issue with transistive dependancies and Springframework
Posted by Carlos Sanchez <ca...@apache.org>.
That's actually wrong. See
http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html
You don't use excludes to change the version of a dependency, you have
to explicitly add that dependency in your pom in the version you want.
"Dependency mediation - this determines what version of a dependency
will be used when multiple versions of an artifact are encountered.
Currently, Maven 2.0 only supports using the "nearest definition" - so
you can always guarantee a version by declaring it explicitly in your
project's POM."
On 10/11/06, Max Cooper <ma...@maxcooper.com> wrote:
> Mick,
>
> I am using Spring 2.0 and Acegi 1.0.2.
>
> Use dependency excludes to suppress the Spring 1.2.7 stuff.
>
> -Max
>
> Mick Knutson wrote:
> > Is anyone else using spring 2.0 and acegi 1.0.2????
> >
> >
> > It seems acegi 1.0.2 is requiring spring 1.2.7 and adds 1.2.7 and 2.0 into
> > my ear.
> > Is this an issue with the spring libs I imported?
> >
> >
> >
> > On 9/18/06, Wendy Smoak <ws...@gmail.com> wrote:
> >>
> >> On 9/18/06, Mick Knutson <mi...@gmail.com> wrote:
> >>
> >> > I am trying to use this:
> >> ... {spring dependencies} ...
> >> > But my war seems to be getting 1.2.7 and 2.0-rc3 jars
> >> > Why?
> >>
> >> Did you upgrade this app to Spring 2? If so, did you 'mvn clean'
> >> after changing the dependency versions? The old ones may have been
> >> left in WEB-INF/lib under 'target'.
> >>
> >> If that's not it, run
> >> mvn package -X > output.txt
> >>
> >> and take a look at the output, which will include an indented tree
> >> view of dependencies. You'll be able to see where each dependency is
> >> coming from, and exclude the ones you don't want.
> >>
> >> You can get two versions of the same library if the groupId has
> >> changed without being "relocated" in the repository. (Didn't Spring
> >> change from 'springframework' to 'org.springframework'?) Maven has no
> >> way of knowing they are the 'same'.
> >>
> >> HTH,
> >> --
> >> Wendy
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: users-help@maven.apache.org
> >>
> >>
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m204] Issue with transistive dependancies and Springframework
Posted by Mick Knutson <mi...@gmail.com>.
What does your exclusions look like:
<exclusions>org.springframework.spring-1.2.7</exclusions>
or something else?
On 10/10/06, Max Cooper <ma...@maxcooper.com> wrote:
>
> Mick,
>
> I am using Spring 2.0 and Acegi 1.0.2.
>
> Use dependency excludes to suppress the Spring 1.2.7 stuff.
>
> -Max
>
> Mick Knutson wrote:
> > Is anyone else using spring 2.0 and acegi 1.0.2????
> >
> >
> > It seems acegi 1.0.2 is requiring spring 1.2.7 and adds 1.2.7 and 2.0into
> > my ear.
> > Is this an issue with the spring libs I imported?
> >
> >
> >
> > On 9/18/06, Wendy Smoak <ws...@gmail.com> wrote:
> >>
> >> On 9/18/06, Mick Knutson <mi...@gmail.com> wrote:
> >>
> >> > I am trying to use this:
> >> ... {spring dependencies} ...
> >> > But my war seems to be getting 1.2.7 and 2.0-rc3 jars
> >> > Why?
> >>
> >> Did you upgrade this app to Spring 2? If so, did you 'mvn clean'
> >> after changing the dependency versions? The old ones may have been
> >> left in WEB-INF/lib under 'target'.
> >>
> >> If that's not it, run
> >> mvn package -X > output.txt
> >>
> >> and take a look at the output, which will include an indented tree
> >> view of dependencies. You'll be able to see where each dependency is
> >> coming from, and exclude the ones you don't want.
> >>
> >> You can get two versions of the same library if the groupId has
> >> changed without being "relocated" in the repository. (Didn't Spring
> >> change from 'springframework' to 'org.springframework'?) Maven has no
> >> way of knowing they are the 'same'.
> >>
> >> HTH,
> >> --
> >> Wendy
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: users-help@maven.apache.org
> >>
> >>
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
Thanks
DJ MICK
http://www.djmick.com
http://www.myspace.com/mickknutson
Re: [m204] Issue with transistive dependancies and Springframework
Posted by Max Cooper <ma...@maxcooper.com>.
Mick,
I am using Spring 2.0 and Acegi 1.0.2.
Use dependency excludes to suppress the Spring 1.2.7 stuff.
-Max
Mick Knutson wrote:
> Is anyone else using spring 2.0 and acegi 1.0.2????
>
>
> It seems acegi 1.0.2 is requiring spring 1.2.7 and adds 1.2.7 and 2.0 into
> my ear.
> Is this an issue with the spring libs I imported?
>
>
>
> On 9/18/06, Wendy Smoak <ws...@gmail.com> wrote:
>>
>> On 9/18/06, Mick Knutson <mi...@gmail.com> wrote:
>>
>> > I am trying to use this:
>> ... {spring dependencies} ...
>> > But my war seems to be getting 1.2.7 and 2.0-rc3 jars
>> > Why?
>>
>> Did you upgrade this app to Spring 2? If so, did you 'mvn clean'
>> after changing the dependency versions? The old ones may have been
>> left in WEB-INF/lib under 'target'.
>>
>> If that's not it, run
>> mvn package -X > output.txt
>>
>> and take a look at the output, which will include an indented tree
>> view of dependencies. You'll be able to see where each dependency is
>> coming from, and exclude the ones you don't want.
>>
>> You can get two versions of the same library if the groupId has
>> changed without being "relocated" in the repository. (Didn't Spring
>> change from 'springframework' to 'org.springframework'?) Maven has no
>> way of knowing they are the 'same'.
>>
>> HTH,
>> --
>> Wendy
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m204] Issue with transistive dependancies and Springframework
Posted by Mick Knutson <mi...@gmail.com>.
Is anyone else using spring 2.0 and acegi 1.0.2????
It seems acegi 1.0.2 is requiring spring 1.2.7 and adds 1.2.7 and 2.0 into
my ear.
Is this an issue with the spring libs I imported?
On 9/18/06, Wendy Smoak <ws...@gmail.com> wrote:
>
> On 9/18/06, Mick Knutson <mi...@gmail.com> wrote:
>
> > I am trying to use this:
> ... {spring dependencies} ...
> > But my war seems to be getting 1.2.7 and 2.0-rc3 jars
> > Why?
>
> Did you upgrade this app to Spring 2? If so, did you 'mvn clean'
> after changing the dependency versions? The old ones may have been
> left in WEB-INF/lib under 'target'.
>
> If that's not it, run
> mvn package -X > output.txt
>
> and take a look at the output, which will include an indented tree
> view of dependencies. You'll be able to see where each dependency is
> coming from, and exclude the ones you don't want.
>
> You can get two versions of the same library if the groupId has
> changed without being "relocated" in the repository. (Didn't Spring
> change from 'springframework' to 'org.springframework'?) Maven has no
> way of knowing they are the 'same'.
>
> HTH,
> --
> Wendy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
Thanks
DJ MICK
http://www.djmick.com
http://www.myspace.com/mickknutson
Re: [m204] Issue with transistive dependancies and Springframework
Posted by Wendy Smoak <ws...@gmail.com>.
On 9/18/06, Mick Knutson <mi...@gmail.com> wrote:
> I am trying to use this:
... {spring dependencies} ...
> But my war seems to be getting 1.2.7 and 2.0-rc3 jars
> Why?
Did you upgrade this app to Spring 2? If so, did you 'mvn clean'
after changing the dependency versions? The old ones may have been
left in WEB-INF/lib under 'target'.
If that's not it, run
mvn package -X > output.txt
and take a look at the output, which will include an indented tree
view of dependencies. You'll be able to see where each dependency is
coming from, and exclude the ones you don't want.
You can get two versions of the same library if the groupId has
changed without being "relocated" in the repository. (Didn't Spring
change from 'springframework' to 'org.springframework'?) Maven has no
way of knowing they are the 'same'.
HTH,
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org