You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by NGUYEN Cong Kinh <co...@it-sudparis.eu> on 2009/12/11 13:38:39 UTC

modules are built but not copied to local repository?

Hello everybody,

I'm using Maven 2.2.1, JDK 6. I have a problem concerning compilation by 
Maven. In fact, for example I have the following structure:

- trunk
 + pom.xml
 +-- A
    + pom.xml
    +-- A1
        + pom.xml
        +-- A11
         ...
        +-- A12
        ...
    +-- A2
    +-- A3
 +-- B
    +-- B1

In the trunk, I execute the "mvn clean install" (before executing this 
command, I used rm -rf ~/.m2/repository). Only modules in the trunk/A 
are copied to ~/.m2/repository. The other modules in trunk/B, they 
compiled to target/..., but they aren't copied to ~/.m2/repository.


Is there any way to specify that they must be copied to local repository ?

Thanks in advance,
Kinh

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


Re: modules are built but not copied to local repository?

Posted by Anders Hammar <an...@hammar.net>.
Executing mvn install gives me this:

[INFO] Building examples in J2ME with juliac
[INFO]
------------------------------------------------------------------------
[INFO] [site:attach-descriptor {execution: default-attach-descriptor}]
[INFO]
------------------------------------------------------------------------
[INFO] Building COSMOS Helloworld example for J2ME/CLDC
[INFO]
------------------------------------------------------------------------
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] A required plugin was not found: Plugin could not be found - check
that the goal name is correct: Unable to download the artifact from any
repository

Try downloading the file manually from the project website.

Then, install it using the command:
    mvn install:install-file -DgroupId=cosmos-me
-DartifactId=cosmos-me-plugin -Dversion=0.1.8-SNAPSHOT
-Dpackaging=maven-plugin -Dfile=/path/to/file

Alternatively, if you host your own repository you can deploy the file
there:
    mvn deploy:deploy-file -DgroupId=cosmos-me -DartifactId=cosmos-me-plugin
-Dversion=0.1.8-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/path/to/file
-Durl=[url] -DrepositoryId=[id]


  cosmos-me:cosmos-me-plugin:maven-plugin:0.1.8-SNAPSHOT

from the specified remote repositories:
  central (http://repo1.maven.org/maven2)


  cosmos-me:cosmos-me-plugin:maven-plugin:0.1.8-SNAPSHOT

from the specified remote repositories:
  central (http://repo1.maven.org/maven2)


This is my nevironment:
Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)
Java version: 1.5.0_15
Java home: C:\Program Files\Java\jdk1.5.0_15\jre
Default locale: sv_SE, platform encoding: Cp1252
OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"

Sorry, I give up.

/Anders

PS. The earlier NPE I mentioned was when building with Maven 3.0-alpha-5.
Try it for yourself; either there's a bug in Maven 3.0 or something weird in
your project(s).

On Mon, Dec 14, 2009 at 08:39, Anders Hammar <an...@hammar.net> wrote:

> Kinh,
>
> When doing mvn clean, I get a message about a missing plugin:
> [INFO] A required plugin was not found: Plugin could not be found - check
> that the goal name is correct: Unable to download the artifact from any
> repository
>
> Try downloading the file manually from the project website.
>
> Then, install it using the command:
>     mvn install:install-file -DgroupId=cosmos.distribution.deployment
> -DartifactId=fdf-plugin -Dversion=0.1.8-SNAPSHOT -Dpackaging=maven-plugin
> -Dfile=/path/to/file
>
> Alternatively, if you host your own repository you can deploy the file
> there:
>     mvn deploy:deploy-file -DgroupId=cosmos.distribution.deployment
> -DartifactId=fdf-plugin -Dversion=0.1.8-SNAPSHOT -Dpackaging=maven-plugin
> -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>
>
>   cosmos.distribution.deployment:fdf-plugin:maven-plugin:0.1.8-SNAPSHOT
>
> Where is that plugin? Some repo I need to configure in my settings.xml?
>
> /Anders
>
>
> On Fri, Dec 11, 2009 at 17:48, NGUYEN Cong Kinh <
> cong_kinh.nguyen@it-sudparis.eu> wrote:
>
>> Please send this error to me.  Because I haven't seen it. Thank you.
>>
>>
>> Kinh
>>
>> Anders Hammar a écrit :
>>
>>> After checking out and building for ages I get a NPE in helloworld ex
>>> 1...
>>>
>>> /Anders
>>>
>>> On Fri, Dec 11, 2009 at 13:55, NGUYEN Cong Kinh <
>>> cong_kinh.nguyen@it-sudparis.eu> wrote:
>>>
>>>
>>>
>>>> In fact, in the trunk/B, there are some modules, for example B1 & B2,
>>>> but
>>>> B2 uses B1 as the dependency. When executing the command "mvn clean
>>>> install"
>>>> for B2, Maven finds the dependency B1, but it is not located in local
>>>> repository. Therefore, there's an error "missing artifact...". You can
>>>> check
>>>> at
>>>> svn co svn+ssh://guest@picoforge.int-evry.fr/cosmos/trunk
>>>> with "guest" as password (twice for entering password)
>>>>
>>>> Kinh
>>>>
>>>> Anders Hammar a écrit :
>>>>
>>>>  What does the build output say - any errors?
>>>>
>>>>
>>>>> /Anders
>>>>>
>>>>> On Fri, Dec 11, 2009 at 13:38, NGUYEN Cong Kinh <
>>>>> cong_kinh.nguyen@it-sudparis.eu> wrote:
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>> Hello everybody,
>>>>>>
>>>>>> I'm using Maven 2.2.1, JDK 6. I have a problem concerning compilation
>>>>>> by
>>>>>> Maven. In fact, for example I have the following structure:
>>>>>>
>>>>>> - trunk
>>>>>> + pom.xml
>>>>>> +-- A
>>>>>>  + pom.xml
>>>>>>  +-- A1
>>>>>>     + pom.xml
>>>>>>     +-- A11
>>>>>>      ...
>>>>>>     +-- A12
>>>>>>     ...
>>>>>>  +-- A2
>>>>>>  +-- A3
>>>>>> +-- B
>>>>>>  +-- B1
>>>>>>
>>>>>> In the trunk, I execute the "mvn clean install" (before executing this
>>>>>> command, I used rm -rf ~/.m2/repository). Only modules in the trunk/A
>>>>>> are
>>>>>> copied to ~/.m2/repository. The other modules in trunk/B, they
>>>>>> compiled
>>>>>> to
>>>>>> target/..., but they aren't copied to ~/.m2/repository.
>>>>>>
>>>>>>
>>>>>> Is there any way to specify that they must be copied to local
>>>>>> repository
>>>>>> ?
>>>>>>
>>>>>> Thanks in advance,
>>>>>> Kinh
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> 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: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>

Re: modules are built but not copied to local repository?

Posted by Anders Hammar <an...@hammar.net>.
Kinh,

When doing mvn clean, I get a message about a missing plugin:
[INFO] A required plugin was not found: Plugin could not be found - check
that the goal name is correct: Unable to download the artifact from any
repository

Try downloading the file manually from the project website.

Then, install it using the command:
    mvn install:install-file -DgroupId=cosmos.distribution.deployment
-DartifactId=fdf-plugin -Dversion=0.1.8-SNAPSHOT -Dpackaging=maven-plugin
-Dfile=/path/to/file

Alternatively, if you host your own repository you can deploy the file
there:
    mvn deploy:deploy-file -DgroupId=cosmos.distribution.deployment
-DartifactId=fdf-plugin -Dversion=0.1.8-SNAPSHOT -Dpackaging=maven-plugin
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]


  cosmos.distribution.deployment:fdf-plugin:maven-plugin:0.1.8-SNAPSHOT

Where is that plugin? Some repo I need to configure in my settings.xml?

/Anders

On Fri, Dec 11, 2009 at 17:48, NGUYEN Cong Kinh <
cong_kinh.nguyen@it-sudparis.eu> wrote:

> Please send this error to me.  Because I haven't seen it. Thank you.
>
>
> Kinh
>
> Anders Hammar a écrit :
>
>> After checking out and building for ages I get a NPE in helloworld ex 1...
>>
>> /Anders
>>
>> On Fri, Dec 11, 2009 at 13:55, NGUYEN Cong Kinh <
>> cong_kinh.nguyen@it-sudparis.eu> wrote:
>>
>>
>>
>>> In fact, in the trunk/B, there are some modules, for example B1 & B2, but
>>> B2 uses B1 as the dependency. When executing the command "mvn clean
>>> install"
>>> for B2, Maven finds the dependency B1, but it is not located in local
>>> repository. Therefore, there's an error "missing artifact...". You can
>>> check
>>> at
>>> svn co svn+ssh://guest@picoforge.int-evry.fr/cosmos/trunk
>>> with "guest" as password (twice for entering password)
>>>
>>> Kinh
>>>
>>> Anders Hammar a écrit :
>>>
>>>  What does the build output say - any errors?
>>>
>>>
>>>> /Anders
>>>>
>>>> On Fri, Dec 11, 2009 at 13:38, NGUYEN Cong Kinh <
>>>> cong_kinh.nguyen@it-sudparis.eu> wrote:
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> Hello everybody,
>>>>>
>>>>> I'm using Maven 2.2.1, JDK 6. I have a problem concerning compilation
>>>>> by
>>>>> Maven. In fact, for example I have the following structure:
>>>>>
>>>>> - trunk
>>>>> + pom.xml
>>>>> +-- A
>>>>>  + pom.xml
>>>>>  +-- A1
>>>>>     + pom.xml
>>>>>     +-- A11
>>>>>      ...
>>>>>     +-- A12
>>>>>     ...
>>>>>  +-- A2
>>>>>  +-- A3
>>>>> +-- B
>>>>>  +-- B1
>>>>>
>>>>> In the trunk, I execute the "mvn clean install" (before executing this
>>>>> command, I used rm -rf ~/.m2/repository). Only modules in the trunk/A
>>>>> are
>>>>> copied to ~/.m2/repository. The other modules in trunk/B, they compiled
>>>>> to
>>>>> target/..., but they aren't copied to ~/.m2/repository.
>>>>>
>>>>>
>>>>> Is there any way to specify that they must be copied to local
>>>>> repository
>>>>> ?
>>>>>
>>>>> Thanks in advance,
>>>>> Kinh
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> 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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

Re: modules are built but not copied to local repository?

Posted by Anders Hammar <an...@hammar.net>.
I will on Monday; don't have my laptop with me over the weekend. Possibly
the fault is on my side; I rushed things as the build took a loooong time (I
skipped the unit tests). Why are you always generating the javadocs (and not
only in the release profile)?

/Anders

On Fri, Dec 11, 2009 at 17:48, NGUYEN Cong Kinh <
cong_kinh.nguyen@it-sudparis.eu> wrote:

> Please send this error to me.  Because I haven't seen it. Thank you.
>
>
> Kinh
>
> Anders Hammar a écrit :
>
>> After checking out and building for ages I get a NPE in helloworld ex 1...
>>
>> /Anders
>>
>> On Fri, Dec 11, 2009 at 13:55, NGUYEN Cong Kinh <
>> cong_kinh.nguyen@it-sudparis.eu> wrote:
>>
>>
>>
>>> In fact, in the trunk/B, there are some modules, for example B1 & B2, but
>>> B2 uses B1 as the dependency. When executing the command "mvn clean
>>> install"
>>> for B2, Maven finds the dependency B1, but it is not located in local
>>> repository. Therefore, there's an error "missing artifact...". You can
>>> check
>>> at
>>> svn co svn+ssh://guest@picoforge.int-evry.fr/cosmos/trunk
>>> with "guest" as password (twice for entering password)
>>>
>>> Kinh
>>>
>>> Anders Hammar a écrit :
>>>
>>>  What does the build output say - any errors?
>>>
>>>
>>>> /Anders
>>>>
>>>> On Fri, Dec 11, 2009 at 13:38, NGUYEN Cong Kinh <
>>>> cong_kinh.nguyen@it-sudparis.eu> wrote:
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> Hello everybody,
>>>>>
>>>>> I'm using Maven 2.2.1, JDK 6. I have a problem concerning compilation
>>>>> by
>>>>> Maven. In fact, for example I have the following structure:
>>>>>
>>>>> - trunk
>>>>> + pom.xml
>>>>> +-- A
>>>>>  + pom.xml
>>>>>  +-- A1
>>>>>     + pom.xml
>>>>>     +-- A11
>>>>>      ...
>>>>>     +-- A12
>>>>>     ...
>>>>>  +-- A2
>>>>>  +-- A3
>>>>> +-- B
>>>>>  +-- B1
>>>>>
>>>>> In the trunk, I execute the "mvn clean install" (before executing this
>>>>> command, I used rm -rf ~/.m2/repository). Only modules in the trunk/A
>>>>> are
>>>>> copied to ~/.m2/repository. The other modules in trunk/B, they compiled
>>>>> to
>>>>> target/..., but they aren't copied to ~/.m2/repository.
>>>>>
>>>>>
>>>>> Is there any way to specify that they must be copied to local
>>>>> repository
>>>>> ?
>>>>>
>>>>> Thanks in advance,
>>>>> Kinh
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> 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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

Re: modules are built but not copied to local repository?

Posted by NGUYEN Cong Kinh <co...@it-sudparis.eu>.
Please send this error to me.  Because I haven't seen it. Thank you.

Kinh

Anders Hammar a écrit :
> After checking out and building for ages I get a NPE in helloworld ex 1...
>
> /Anders
>
> On Fri, Dec 11, 2009 at 13:55, NGUYEN Cong Kinh <
> cong_kinh.nguyen@it-sudparis.eu> wrote:
>
>   
>> In fact, in the trunk/B, there are some modules, for example B1 & B2, but
>> B2 uses B1 as the dependency. When executing the command "mvn clean install"
>> for B2, Maven finds the dependency B1, but it is not located in local
>> repository. Therefore, there's an error "missing artifact...". You can check
>> at
>> svn co svn+ssh://guest@picoforge.int-evry.fr/cosmos/trunk
>> with "guest" as password (twice for entering password)
>>
>> Kinh
>>
>> Anders Hammar a écrit :
>>
>>  What does the build output say - any errors?
>>     
>>> /Anders
>>>
>>> On Fri, Dec 11, 2009 at 13:38, NGUYEN Cong Kinh <
>>> cong_kinh.nguyen@it-sudparis.eu> wrote:
>>>
>>>
>>>
>>>       
>>>> Hello everybody,
>>>>
>>>> I'm using Maven 2.2.1, JDK 6. I have a problem concerning compilation by
>>>> Maven. In fact, for example I have the following structure:
>>>>
>>>> - trunk
>>>> + pom.xml
>>>> +-- A
>>>>  + pom.xml
>>>>  +-- A1
>>>>      + pom.xml
>>>>      +-- A11
>>>>       ...
>>>>      +-- A12
>>>>      ...
>>>>  +-- A2
>>>>  +-- A3
>>>> +-- B
>>>>  +-- B1
>>>>
>>>> In the trunk, I execute the "mvn clean install" (before executing this
>>>> command, I used rm -rf ~/.m2/repository). Only modules in the trunk/A are
>>>> copied to ~/.m2/repository. The other modules in trunk/B, they compiled
>>>> to
>>>> target/..., but they aren't copied to ~/.m2/repository.
>>>>
>>>>
>>>> Is there any way to specify that they must be copied to local repository
>>>> ?
>>>>
>>>> Thanks in advance,
>>>> Kinh
>>>>
>>>> ---------------------------------------------------------------------
>>>> 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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: modules are built but not copied to local repository?

Posted by Anders Hammar <an...@hammar.net>.
After checking out and building for ages I get a NPE in helloworld ex 1...

/Anders

On Fri, Dec 11, 2009 at 13:55, NGUYEN Cong Kinh <
cong_kinh.nguyen@it-sudparis.eu> wrote:

> In fact, in the trunk/B, there are some modules, for example B1 & B2, but
> B2 uses B1 as the dependency. When executing the command "mvn clean install"
> for B2, Maven finds the dependency B1, but it is not located in local
> repository. Therefore, there's an error "missing artifact...". You can check
> at
> svn co svn+ssh://guest@picoforge.int-evry.fr/cosmos/trunk
> with "guest" as password (twice for entering password)
>
> Kinh
>
> Anders Hammar a écrit :
>
>  What does the build output say - any errors?
>>
>> /Anders
>>
>> On Fri, Dec 11, 2009 at 13:38, NGUYEN Cong Kinh <
>> cong_kinh.nguyen@it-sudparis.eu> wrote:
>>
>>
>>
>>> Hello everybody,
>>>
>>> I'm using Maven 2.2.1, JDK 6. I have a problem concerning compilation by
>>> Maven. In fact, for example I have the following structure:
>>>
>>> - trunk
>>> + pom.xml
>>> +-- A
>>>  + pom.xml
>>>  +-- A1
>>>      + pom.xml
>>>      +-- A11
>>>       ...
>>>      +-- A12
>>>      ...
>>>  +-- A2
>>>  +-- A3
>>> +-- B
>>>  +-- B1
>>>
>>> In the trunk, I execute the "mvn clean install" (before executing this
>>> command, I used rm -rf ~/.m2/repository). Only modules in the trunk/A are
>>> copied to ~/.m2/repository. The other modules in trunk/B, they compiled
>>> to
>>> target/..., but they aren't copied to ~/.m2/repository.
>>>
>>>
>>> Is there any way to specify that they must be copied to local repository
>>> ?
>>>
>>> Thanks in advance,
>>> Kinh
>>>
>>> ---------------------------------------------------------------------
>>> 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: modules are built but not copied to local repository?

Posted by NGUYEN Cong Kinh <co...@it-sudparis.eu>.
In fact, in the trunk/B, there are some modules, for example B1 & B2, 
but B2 uses B1 as the dependency. When executing the command "mvn clean 
install" for B2, Maven finds the dependency B1, but it is not located in 
local repository. Therefore, there's an error "missing artifact...". You 
can check at
svn co svn+ssh://guest@picoforge.int-evry.fr/cosmos/trunk
with "guest" as password (twice for entering password)

Kinh

Anders Hammar a écrit :
> What does the build output say - any errors?
>
> /Anders
>
> On Fri, Dec 11, 2009 at 13:38, NGUYEN Cong Kinh <
> cong_kinh.nguyen@it-sudparis.eu> wrote:
>
>   
>> Hello everybody,
>>
>> I'm using Maven 2.2.1, JDK 6. I have a problem concerning compilation by
>> Maven. In fact, for example I have the following structure:
>>
>> - trunk
>> + pom.xml
>> +-- A
>>   + pom.xml
>>   +-- A1
>>       + pom.xml
>>       +-- A11
>>        ...
>>       +-- A12
>>       ...
>>   +-- A2
>>   +-- A3
>> +-- B
>>   +-- B1
>>
>> In the trunk, I execute the "mvn clean install" (before executing this
>> command, I used rm -rf ~/.m2/repository). Only modules in the trunk/A are
>> copied to ~/.m2/repository. The other modules in trunk/B, they compiled to
>> target/..., but they aren't copied to ~/.m2/repository.
>>
>>
>> Is there any way to specify that they must be copied to local repository ?
>>
>> Thanks in advance,
>> Kinh
>>
>> ---------------------------------------------------------------------
>> 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: modules are built but not copied to local repository?

Posted by Anders Hammar <an...@hammar.net>.
What does the build output say - any errors?

/Anders

On Fri, Dec 11, 2009 at 13:38, NGUYEN Cong Kinh <
cong_kinh.nguyen@it-sudparis.eu> wrote:

> Hello everybody,
>
> I'm using Maven 2.2.1, JDK 6. I have a problem concerning compilation by
> Maven. In fact, for example I have the following structure:
>
> - trunk
> + pom.xml
> +-- A
>   + pom.xml
>   +-- A1
>       + pom.xml
>       +-- A11
>        ...
>       +-- A12
>       ...
>   +-- A2
>   +-- A3
> +-- B
>   +-- B1
>
> In the trunk, I execute the "mvn clean install" (before executing this
> command, I used rm -rf ~/.m2/repository). Only modules in the trunk/A are
> copied to ~/.m2/repository. The other modules in trunk/B, they compiled to
> target/..., but they aren't copied to ~/.m2/repository.
>
>
> Is there any way to specify that they must be copied to local repository ?
>
> Thanks in advance,
> Kinh
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>