Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Developers List" <dev@maven.apache.org>
Received-SPF: pass (nike.apache.org: local policy)
From: John Dix <John.Dix@amdocs.com>
To: Maven Developers List <dev@maven.apache.org>
Subject: RE: Failure to find artifact in Nexus
Thread-Topic: Failure to find artifact in Nexus
Thread-Index: 
 Ac6qkTAMHVqs+VFZTfC73aQ2YM3cOgALS6uAAAn+X+D//82ogP//ROpg//6H0yD//Q6/YAD2u+uA//00zhD/+mVkoP/0dKiA/+k3QSD/0hZ5AP+kf/8Q/0jfTjA=
Date: Mon, 9 Sep 2013 19:53:23 +0000
Message-ID: 
 <1B8FF9BB83FDCE44AB581D7E394AB90D2A2D7725@USSTLDAGBE1.corp.amdocs.com>
References: 
 <1B8FF9BB83FDCE44AB581D7E394AB90D2A2D66F2@USSTLDAGBE1.corp.amdocs.com>
 <52291BB9.7050205@yahoo.com>
 <1B8FF9BB83FDCE44AB581D7E394AB90D2A2D6765@USSTLDAGBE1.corp.amdocs.com>
 <5229348F.1090902@artifact-software.com>
 <1B8FF9BB83FDCE44AB581D7E394AB90D2A2D6C4F@USSTLDAGBE1.corp.amdocs.com>
 <1B8FF9BB83FDCE44AB581D7E394AB90D2A2D6C6D@USSTLDAGBE1.corp.amdocs.com>
 <1B8FF9BB83FDCE44AB581D7E394AB90D2A2D6C88@USSTLDAGBE1.corp.amdocs.com>
 <op.w21v9bmjkdkhrr@columbia>
 <1B8FF9BB83FDCE44AB581D7E394AB90D2A2D751F@USSTLDAGBE1.corp.amdocs.com>
 <1B8FF9BB83FDCE44AB581D7E394AB90D2A2D7609@USSTLDAGBE1.corp.amdocs.com>
 <op.w25lqjodkdkhrr@columbia>
 <1B8FF9BB83FDCE44AB581D7E394AB90D2A2D763B@USSTLDAGBE1.corp.amdocs.com>
 <op.w25neqbqkdkhrr@columbia>
 <1B8FF9BB83FDCE44AB581D7E394AB90D2A2D766F@USSTLDAGBE1.corp.amdocs.com>
In-Reply-To: 
 <1B8FF9BB83FDCE44AB581D7E394AB90D2A2D766F@USSTLDAGBE1.corp.amdocs.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

https://jira.codehaus.org/browse/MNG-5181 ... The use of the MAVEN_OPTS fla=
g has resolved this issue for us. However now it is telling us that maven-c=
lean-plugin 2.5 cannot be found in our release repository. This might be an=
 ancillary issue as we have not encountered this before until I used the wo=
rkaround given in the Jira bug.

Also, that bug feels like a hack to a problem that is a bug in the code. ht=
tps://jira.codehaus.org/browse/MNG-5185 seems to point towards working offl=
ine or over a VPN is a cause however that is not the case for us. I feel th=
at this is a bug in the code. Once it finds the artifact, it should not kee=
p looking for it, and then fail later. Is it possible that this is still un=
der investigation elsewhere and that I can follow it? I think that this nee=
ds follow-up and further investigation rather than just tell my 3.1 system =
to act like it's 2.x. if that's the solution, why should I upgrade ay all?

-----Original Message-----
From: John Dix=20
Sent: Monday, September 09, 2013 10:44 AM
To: Maven Developers List
Subject: RE: Failure to find artifact in Nexus

I am deleting the .m2/repository (rm -rf ~/.m2/repository/*) before every b=
uild.

I have used the -U before as well.

-----Original Message-----
From: Robert Scholte [mailto:rfscholte@apache.org]
Sent: Monday, September 09, 2013 10:41 AM
To: Maven Developers List
Subject: Re: Failure to find artifact in Nexus

Well, it is actually not a bug, but a more strict behavior of Maven 3 compa=
red to Maven 2.
The issue is a solution to get the Maven 2 behavior with Maven 3.

In short: Maven 3 tries to predict if the project can still be built with a=
n empty repository, even if the dependencies are available in your local re=
pository.

It could be that for some reason your local repository got corrupt.
Have you tried to remove the commons-httpclient folder and build the projec=
t again ( with -U to force an update?). You should be fine, since these fil=
es should exist at the Nexus repository.

Robert

Op Mon, 09 Sep 2013 19:29:09 +0200 schreef John Dix <John.Dix@amdocs.com>:

> Still repro's in Maven 3.1. The bug says it is fixed there if I am=20
> reading it correctly. However, the artifact is stored in Nexus in=20
> exactly where we want it: 3rdparty. Maven pulls it down, and rather=20
> than acknowledge it's existence in the local .m2 repository, it=20
> continues to try and find it and then dies when it cannot locate. Is=20
> this the same thing? The bug doesn't read like it is. Bear in mind I=20
> am mostly new to Maven and still getting used to the lingo.
>
> -----Original Message-----
> From: Robert Scholte [mailto:rfscholte@apache.org]
> Sent: Monday, September 09, 2013 10:05 AM
> To: Maven Developers List
> Subject: Re: Failure to find artifact in Nexus
>
> In that case you're probably hitting
> https://jira.codehaus.org/browse/MNG-5181
>
> Robert
>
> Op Mon, 09 Sep 2013 18:57:25 +0200 schreef John Dix
> <John.Dix@amdocs.com>:
>
>> What I mean by being "downloaded" is that it is easily found in the=20
>> local .m2 repository of the machine maven is being executed on.
>>
>> -----Original Message-----
>> From: John Dix
>> Sent: Monday, September 09, 2013 9:44 AM
>> To: Maven Developers List
>> Subject: RE: Failure to find artifact in Nexus
>>
>> Thanks!
>>
>> The problem is not that I am not getting the artifact because I am.
>> The problem is that Maven acts like it doesn't have the file(after=20
>> downloading it) and then exits. If I rerun the build it passes just=20
>> fine. It does this on very specific artifacts every time. It is very=20
>> reproducible. What I am trying to find out is why it is doing this so=20
>> that I can correct the behaviour.
>>
>> -----Original Message-----
>> From: Robert Scholte [mailto:rfscholte@apache.org]
>> Sent: Saturday, September 07, 2013 10:02 AM
>> To: Maven Developers List
>> Subject: Re: Failure to find artifact in Nexus
>>
>> hi,
>>
>> /nexus/content/repositories/releases should be used for releases of=20
>> your company or project /nexus/content/repositories/thirdparty should=20
>> be used for ... third party artifacts.
>>
>> Developers should connect to a repository-*group* instead of a=20
>> repository-*host*, so the Nexus administrator can control which=20
>> hosted and proxied repositories should be available for them (on URL=20
>> to rule them all).
>> Normally this would be the .../public repository
>>
>> What I don't understand is what you mean with the file being downloaded.
>> Maven always comes with 2 lines:
>> Downloading .... which mean it will *try* to download this file=20
>> Downloaded .... means that Maven succeeded.
>> If you don't see the second line, then it is not downloaded.
>> I guess that confused you a bit.
>>
>> Robert
>>
>> Op Fri, 06 Sep 2013 20:09:30 +0200 schreef John Dix
>> <John.Dix@amdocs.com>:
>>
>>> + maven dev team..
>>>
>>> -----Original Message-----
>>> From: John Dix
>>> Sent: Friday, September 06, 2013 11:08 AM
>>> To: Maven Users List; rwheeler@artifact-software.com
>>> Subject: RE: Failure to find artifact in Nexus
>>>
>>> Let me rephrase this. It is finding it in the repository we have it=20
>>> in (3rdparty), but when it gets to=20
>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releas
>>> e s , which is where the artifact ISN'T, maven says "Oops. I can't=20
>>> find it I give up" and craps out DESPITE the fact that it has=20
>>> already found it and downloaded the file.
>>>
>>> -----Original Message-----
>>> From: John Dix
>>> Sent: Friday, September 06, 2013 10:59 AM
>>> To: Maven Users List; rwheeler@artifact-software.com
>>> Subject: RE: Failure to find artifact in Nexus
>>>
>>> Yes it is. It downloads the file. I have verified it is in the .m2=20
>>> repository on the drive where the build is located. When I execute a=20
>>> second time it bypasses the error.
>>>
>>> -----Original Message-----
>>> From: Ron Wheeler [mailto:rwheeler@artifact-software.com]
>>> Sent: Thursday, September 05, 2013 6:49 PM
>>> To: users@maven.apache.org
>>> Subject: Re: Failure to find artifact in Nexus
>>>
>>>
>>> Is the artifact
>>>
>>> commons-httpclient:commons-httpclient:jar:3.1
>>>
>>> in the
>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releas
>>> e
>>> s
>>> repo?
>>>
>>> That will split your problem in half.
>>>
>>> Ron
>>>
>>> On 05/09/2013 8:17 PM, John Dix wrote:
>>>> Mark: We are going to our own Nexus repository:
>>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/relea
>>>> s
>>>> e
>>>> s
>>>>
>>>> -----Original Message-----
>>>> From: Mark Eggers [mailto:its_toasted@yahoo.com]
>>>> Sent: Thursday, September 05, 2013 5:03 PM
>>>> To: Maven Users List
>>>> Subject: Re: Failure to find artifact in Nexus
>>>>
>>>> On 9/5/2013 4:47 PM, John Dix wrote:
>>>>> Hello everyone,
>>>>>
>>>>> I have hit a wall in trying to figure out why we're getting this
>>>>> failure:
>>>>>
>>>>> org.sonatype.aether.transfer.ArtifactNotFoundException: Failure to=20
>>>>> find commons-httpclient:commons-httpclient:jar:3.1 in=20
>>>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/rele
>>>>> a s e s was cached in the local repository, resolution will not be=20
>>>>> reattempted until the update interval of=20
>>>>> qpass-nexus-hosted-releases has elapsed or updates are forced
>>>>>
>>>>> during our builds. On a clean .m2/repository directory(ran rm -rf
>>>>> ~/.m2/repository/*) and executing the following command:
>>>>>
>>>>> mvn -e -DskipTests clean install -f <path to our pom>. This=20
>>>>> happens the first time and then after that it picks up the file.
>>>>> It happens on the SAME file everytime after a wiping of the=20
>>>>> .ms/repository directory. I have looked and visually verified that=20
>>>>> the jar file it is looking for is in the .m2 repo and is the=20
>>>>> correct version it is looking for. I have tried using the -U=20
>>>>> switch with the maven command to no avail. We are getting this on=20
>>>>> one more jar file after this one gets resolved but it behaves the
>>>>> same: rerun and it finds it. We do not encounter this on other produc=
ts, just this one.
>>>>>
>>>>> Does anyone have any idea on how to move forward on this? I am at=20
>>>>> a loss.
>>>>>
>>>>> Regards!
>>>>> -Caolan.
>>>>>
>>>>> Maven essentials:
>>>>> Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da;
>>>>> 2013-02-19 13:51:28+0000) Maven home: /usr/local/maven-3.0.5 Java
>>>>> version: 1.7.0_02, vendor: Oracle Corporation Java home:
>>>>> /usr/local/jdk1.7.0_02/jre Default locale: en_US, platform encoding:
>>>>> UTF-8 OS name: "linux", version: "2.6.30.10-105.2.23.fc11.x86_64",
>>>>> arch: "amd64", family: "unix"
>>>>>
>>>>>
>>>>> Full Stack:
>>>>> [ERROR] Failed to execute goal on project
>>>>> applicationContextComponents: Could not resolve dependencies for=20
>>>>> project=20
>>>>> com.amdocs.dc.applicationcontext:applicationContextComponents:jar:1.
>>>>> 0
>>>>> -
>>>>> rc-4-SNAPSHOT: Failure to find
>>>>> commons-httpclient:commons-httpclient:jar:3.1 in=20
>>>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/rele
>>>>> a s e s was cached in the local repository, resolution will not be=20
>>>>> reattempted until the update interval of=20
>>>>> qpass-nexus-hosted-releases has elapsed or updates are forced ->=20
>>>>> [Help 1]
>>>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to=20
>>>>> execute goal on project applicationContextComponents: Could not=20
>>>>> resolve dependencies for project
>>>>> com.amdocs.dc.applicationcontext:applicationContextComponents:jar:1.0=
-rc-4-SNAPSHOT:
>>>>> Failure to find commons-httpclient:commons-httpclient:jar:3.1 in=20
>>>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/rele
>>>>> a s es was cached in the local repository, resolution will not be=20
>>>>> reattempted until the update interval of=20
>>>>> qpass-nexus-hosted-releases has elapsed or updates are forced
>>>>>                   at
>>>>> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDe=
pendencies(LifecycleDependencyResolver.java:210)
>>>>>                   at
>>>>> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resol=
veProjectDependencies(LifecycleDependencyResolver.java:117)
>>>>>                   at
>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAr=
eResolved(MojoExecutor.java:258)
>>>>>                   at
>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor=
.java:201)
>>>>>                   at
>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor=
.java:153)
>>>>>                   at
>>>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor=
.java:145)
>>>>>                   at
>>>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProje=
ct(LifecycleModuleBuilder.java:84)
>>>>>                   at
>>>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProje=
ct(LifecycleModuleBuilder.java:59)
>>>>>                   at
>>>>> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBu=
ild(LifecycleStarter.java:183)
>>>>>                   at
>>>>> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(Lifecycl=
eStarter.java:161)
>>>>>                   at
>>>>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
>>>>>                   at
>>>>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>>>>>                   at
>>>>> org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
>>>>>                   at
>>>>> org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
>>>>>                   at
>>>>> org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
>>>>>                   at
>>>>> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>>                   at
>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.=
java:57)
>>>>>                   at
>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces=
sorImpl.java:43)
>>>>>                   at java.lang.reflect.Method.invoke(Method.java:601)
>>>>>                   at
>>>>> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Laun=
cher.java:290)
>>>>>                   at
>>>>> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.jav=
a:230)
>>>>>                   at
>>>>> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(La=
uncher.java:409)
>>>>>                   at
>>>>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:
>>>>> 3
>>>>> 52) Caused by: =20
>>>>> org.apache.maven.project.DependencyResolutionException:
>>>>> Could not resolve dependencies for project
>>>>> com.amdocs.dc.applicationcontext:applicationContextComponents:jar:1.0=
-rc-4-SNAPSHOT:
>>>>> Failure to find commons-httpclient:commons-httpclient:jar:3.1 in=20
>>>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/rele
>>>>> a s es was cached in the local repository, resolution will not be=20
>>>>> reattempted until the update interval of=20
>>>>> qpass-nexus-hosted-releases has elapsed or updates are forced
>>>>>                   at
>>>>> org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(D=
efaultProjectDependenciesResolver.java:189)
>>>>>                   at
>>>>> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDe=
pendencies(LifecycleDependencyResolver.java:185)
>>>>>                   ... 22 more
>>>>> Caused by:
>>>>> org.sonatype.aether.resolution.DependencyResolutionException:
>>>>> Failure to find commons-httpclient:commons-httpclient:jar:3.1 in=20
>>>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/rele
>>>>> a s es was cached in the local repository, resolution will not be=20
>>>>> reattempted until the update interval of=20
>>>>> qpass-nexus-hosted-releases has elapsed or updates are forced
>>>>>                   at
>>>>> org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDepe=
ndencies(DefaultRepositorySystem.java:375)
>>>>>                   at
>>>>> org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(D=
efaultProjectDependenciesResolver.java:183)
>>>>>                   ... 23 more
>>>>> Caused by: =20
>>>>> org.sonatype.aether.resolution.ArtifactResolutionException:
>>>>> Failure to find commons-httpclient:commons-httpclient:jar:3.1 in=20
>>>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/rele
>>>>> a s es was cached in the local repository, resolution will not be=20
>>>>> reattempted until the update interval of=20
>>>>> qpass-nexus-hosted-releases has elapsed or updates are forced
>>>>>                   at
>>>>> org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(Def=
aultArtifactResolver.java:538)
>>>>>                   at
>>>>> org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArti=
facts(DefaultArtifactResolver.java:216)
>>>>>                   at
>>>>> org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDepe=
ndencies(DefaultRepositorySystem.java:358)
>>>>>                   ... 24 more
>>>>> Caused by: org.sonatype.aether.transfer.ArtifactNotFoundException:
>>>>> Failure to find commons-httpclient:commons-httpclient:jar:3.1 in=20
>>>>> http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/rele
>>>>> a s es was cached in the local repository, resolution will not be=20
>>>>> reattempted until the update interval of=20
>>>>> qpass-nexus-hosted-releases has elapsed or updates are forced
>>>>>                   at
>>>>> org.sonatype.aether.impl.internal.DefaultUpdateCheckManager.newExcept=
ion(DefaultUpdateCheckManager.java:230)
>>>>>                   at
>>>>> org.sonatype.aether.impl.internal.DefaultUpdateCheckManager.checkArti=
fact(DefaultUpdateCheckManager.java:176)
>>>>>                   at
>>>>> org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(
>>>>> D
>>>>> e
>>>>> f
>>>>> a
>>>>> ultArtifactResolver.java:427)
>>>>>
>>>>> John "Caolan" Dix
>>>>> Programming Sr. SME, Digital Commerce Amdocs Digital Services=20
>>>>> Division
>>>>> o: 206-288-0334 m: 425.351.7340
>>>> Why is Maven looking in the "releases" repository on Nexus?
>>>>
>>>> I would expect it to be looking at either public (if you use the=20
>>>> group), or the mirror of central.
>>>>
>>>> . . . just my naive two cents.
>>>> /mde/
>>>>
>>>>
>>>> -------------------------------------------------------------------
>>>> -
>>>> - To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>
>>>>
>>>> This message and the information contained herein is proprietary=20
>>>> and confidential and subject to the Amdocs policy statement, you=20
>>>> may review at http://www.amdocs.com/email_disclaimer.asp
>>>>
>>>> -------------------------------------------------------------------
>>>> -
>>>> - To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>
>>>>
>>>
>>>
>>> --
>>> Ron Wheeler
>>> President
>>> Artifact Software Inc
>>> email: rwheeler@artifact-software.com
>>> skype: ronaldmwheeler
>>> phone: 866-970-2435, ext 102
>>>
>>>
>>> --------------------------------------------------------------------
>>> - To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>> This message and the information contained herein is proprietary and=20
>>> confidential and subject to the Amdocs policy statement, you may=20
>>> review at http://www.amdocs.com/email_disclaimer.asp
>>>
>>> --------------------------------------------------------------------
>>> - 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
>>>
>>>
>>> --------------------------------------------------------------------
>>> - To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For=20
>>> additional commands, e-mail: dev-help@maven.apache.org
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For=20
>> additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>> This message and the information contained herein is proprietary and=20
>> confidential and subject to the Amdocs policy statement, you may=20
>> review at http://www.amdocs.com/email_disclaimer.asp
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For=20
>> additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For=20
>> additional commands, e-mail: dev-help@maven.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For=20
> additional commands, e-mail: dev-help@maven.apache.org
>
>
> This message and the information contained herein is proprietary and=20
> confidential and subject to the Amdocs policy statement, you may=20
> review at http://www.amdocs.com/email_disclaimer.asp
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For=20
> additional commands, e-mail: dev-help@maven.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For additional com=
mands, e-mail: dev-help@maven.apache.org


This message and the information contained herein is proprietary and confid=
ential and subject to the Amdocs policy statement, you may review at http:/=
/www.amdocs.com/email_disclaimer.asp

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For additional com=
mands, e-mail: dev-help@maven.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org