You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Olivier Lamy <ol...@apache.org> on 2008/11/25 11:01:06 UTC
[ANN] Maven Changes Plugin 2.1 Released
The Maven team is pleased to announce the release of the Maven Changes
Plugin, version 2.1.
http://maven.apache.org/plugins/maven-changes-plugin/
You should specify the version in your project's plugin configuration:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-changes-plugin</artifactId>
<version>2.1</version>
</plugin>
Release Notes - Maven 2.x Changes Plugin - Version 2.1
** Bug
* [MCHANGES-109] - Fix output directory for images of changes-report
* [MCHANGES-110] - No issue links generated if
${project.issueManagement.url} empty but issueLinkTemplate provided
* [MCHANGES-111] - Announcement Mojo doesn't respect Jira
authentication settings
* [MCHANGES-114] - Title in changes.xml is not outputted in
changes-report.html
* [MCHANGES-126] - NullPointerException when executing jira-report
with JIRA 3.13
* [MCHANGES-127] - Generated Announcement is not complete (in
trunk rev 709936)
* [MCHANGES-128] - unable to use "toAddresses" field for announces
** Improvement
* [MCHANGES-61] - Provide DTD/XSD for changes.xml
* [MCHANGES-71] - need add template encoding to announcement-generate
* [MCHANGES-107] - Add html output format for mail annoucement
* [MCHANGES-108] - Allow to configure changes-report mojo from properties
* [MCHANGES-113] - Allow configuration of announcement parameters
from command line
* [MCHANGES-117] - Send only one e-mail to many recipients (all
recipients in one to-header)
* [MCHANGES-118] - AnnouncementMojo can only load velocity
templates from src/main/resources and not a path related to user.dir
* [MCHANGES-120] - announcement:generate mojo should warn, not
fail if the changes file doesn't exist.
** New Feature
* [MCHANGES-47] - Add support for multiple <issue> and <due-to>
tags in changes.xml
* [MCHANGES-69] - Add a date elment or attribute inside the action
element of changes.xml
* [MCHANGES-86] - Create a changes-validate mojo
* [MCHANGES-90] - Add support for Trac-report like Jira-report
* [MCHANGES-112] - Add more than one link template
* [MCHANGES-129] - The version can't be set from the cli in
announcement-mail
* [MCHANGES-130] - Announce mail : Merging content from the
changes file and from jira
* [MCHANGES-132] - Overriding mail introduction with a mojo configuration
* [MCHANGES-133] - adding maven project to the velocity context
when generating announce email
* [MCHANGES-134] - Passing some extra parameters to the announce
velocity context
** Task
* [MCHANGES-119] - Add the changes xsd file
http://maven.apache.org/xsd/ after the 2.1 release
* [MCHANGES-122] - release modello-maven-plugin 1.0-alpha-21
Have fun,
-The Maven team
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [ANN] Maven Changes Plugin 2.1 Released
Posted by Mark Derricutt <ma...@talios.com>.
Congrats.
When using onlyCurrentVersion and the jira report, is it possible to
override the version is looking for? For one reason or another, we
currently have a single Jira project, with module names included in
the version name, i.e. "Statistics Monitoring 1.1", so it'd be a nice
to have that automatically identified rather than just "1.1".
Cheers,
Mark
On Tue, Nov 25, 2008 at 11:01 PM, Olivier Lamy <ol...@apache.org> wrote:
>
> The Maven team is pleased to announce the release of the Maven Changes
> Plugin, version 2.1.
--
"It is easier to optimize correct code than to correct optimized
code." -- Bill Harlan
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [ANN] Maven Changes Plugin 2.1 Released
Posted by Olivier Lamy <ol...@apache.org>.
Hi,
Yes documentation is missing (my bad :-) ).
I do this :
<issueLinkTemplate>http://ip:port/tddetailbug.asp?ID=%ISSUE%</issueLinkTemplate>
<issueLinkTemplatePerSystem>
<jira>http://ip:port/browse/%ISSUE%</jira>
</issueLinkTemplatePerSystem>
In changes.xml
<action type="add" dev="xxx" issue="FOO-8" system="jira">blabla.</action>
<action type="add" dev="xxx" issue="12332">bla bla.</action>
--
Olivier
2008/11/25 Lewis, Eric <Er...@ipi.ch>:
> Great, thanks!
>
> Could you add some documentation on how to use the different issueLinkTemplatePerSystem configurations?
>
> Thanks,
> Eric
>
>> -----Ursprüngliche Nachricht-----
>> Von: oliver.lamy@gmail.com [mailto:oliver.lamy@gmail.com] Im
>> Auftrag von Olivier Lamy
>> Gesendet: Dienstag, 25. November 2008 11:01
>> An: announce@maven.apache.org; Maven Users List
>> Cc: Maven Developers List
>> Betreff: [ANN] Maven Changes Plugin 2.1 Released
>>
>> The Maven team is pleased to announce the release of the Maven Changes
>> Plugin, version 2.1.
>>
>> http://maven.apache.org/plugins/maven-changes-plugin/
>>
>> You should specify the version in your project's plugin configuration:
>>
>> <plugin>
>> <groupId>org.apache.maven.plugins</groupId>
>> <artifactId>maven-changes-plugin</artifactId>
>> <version>2.1</version>
>> </plugin>
>>
>> Release Notes - Maven 2.x Changes Plugin - Version 2.1
>>
>>
>> ** Bug
>> * [MCHANGES-109] - Fix output directory for images of
>> changes-report
>> * [MCHANGES-110] - No issue links generated if
>> ${project.issueManagement.url} empty but issueLinkTemplate provided
>> * [MCHANGES-111] - Announcement Mojo doesn't respect Jira
>> authentication settings
>> * [MCHANGES-114] - Title in changes.xml is not outputted in
>> changes-report.html
>> * [MCHANGES-126] - NullPointerException when executing jira-report
>> with JIRA 3.13
>> * [MCHANGES-127] - Generated Announcement is not complete (in
>> trunk rev 709936)
>> * [MCHANGES-128] - unable to use "toAddresses" field for announces
>>
>> ** Improvement
>> * [MCHANGES-61] - Provide DTD/XSD for changes.xml
>> * [MCHANGES-71] - need add template encoding to
>> announcement-generate
>> * [MCHANGES-107] - Add html output format for mail annoucement
>> * [MCHANGES-108] - Allow to configure changes-report mojo
>> from properties
>> * [MCHANGES-113] - Allow configuration of announcement parameters
>> from command line
>> * [MCHANGES-117] - Send only one e-mail to many recipients (all
>> recipients in one to-header)
>> * [MCHANGES-118] - AnnouncementMojo can only load velocity
>> templates from src/main/resources and not a path related to user.dir
>> * [MCHANGES-120] - announcement:generate mojo should warn, not
>> fail if the changes file doesn't exist.
>>
>> ** New Feature
>> * [MCHANGES-47] - Add support for multiple <issue> and <due-to>
>> tags in changes.xml
>> * [MCHANGES-69] - Add a date elment or attribute inside the action
>> element of changes.xml
>> * [MCHANGES-86] - Create a changes-validate mojo
>> * [MCHANGES-90] - Add support for Trac-report like Jira-report
>> * [MCHANGES-112] - Add more than one link template
>> * [MCHANGES-129] - The version can't be set from the cli in
>> announcement-mail
>> * [MCHANGES-130] - Announce mail : Merging content from the
>> changes file and from jira
>> * [MCHANGES-132] - Overriding mail introduction with a
>> mojo configuration
>> * [MCHANGES-133] - adding maven project to the velocity context
>> when generating announce email
>> * [MCHANGES-134] - Passing some extra parameters to the announce
>> velocity context
>>
>> ** Task
>> * [MCHANGES-119] - Add the changes xsd file
>> http://maven.apache.org/xsd/ after the 2.1 release
>> * [MCHANGES-122] - release modello-maven-plugin 1.0-alpha-21
>>
>> Have fun,
>>
>> -The Maven team
>>
>> ---------------------------------------------------------------------
>> 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
AW: [ANN] Maven Changes Plugin 2.1 Released
Posted by "Lewis, Eric" <Er...@ipi.ch>.
Great, thanks!
Could you add some documentation on how to use the different issueLinkTemplatePerSystem configurations?
Thanks,
Eric
> -----Ursprüngliche Nachricht-----
> Von: oliver.lamy@gmail.com [mailto:oliver.lamy@gmail.com] Im
> Auftrag von Olivier Lamy
> Gesendet: Dienstag, 25. November 2008 11:01
> An: announce@maven.apache.org; Maven Users List
> Cc: Maven Developers List
> Betreff: [ANN] Maven Changes Plugin 2.1 Released
>
> The Maven team is pleased to announce the release of the Maven Changes
> Plugin, version 2.1.
>
> http://maven.apache.org/plugins/maven-changes-plugin/
>
> You should specify the version in your project's plugin configuration:
>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-changes-plugin</artifactId>
> <version>2.1</version>
> </plugin>
>
> Release Notes - Maven 2.x Changes Plugin - Version 2.1
>
>
> ** Bug
> * [MCHANGES-109] - Fix output directory for images of
> changes-report
> * [MCHANGES-110] - No issue links generated if
> ${project.issueManagement.url} empty but issueLinkTemplate provided
> * [MCHANGES-111] - Announcement Mojo doesn't respect Jira
> authentication settings
> * [MCHANGES-114] - Title in changes.xml is not outputted in
> changes-report.html
> * [MCHANGES-126] - NullPointerException when executing jira-report
> with JIRA 3.13
> * [MCHANGES-127] - Generated Announcement is not complete (in
> trunk rev 709936)
> * [MCHANGES-128] - unable to use "toAddresses" field for announces
>
> ** Improvement
> * [MCHANGES-61] - Provide DTD/XSD for changes.xml
> * [MCHANGES-71] - need add template encoding to
> announcement-generate
> * [MCHANGES-107] - Add html output format for mail annoucement
> * [MCHANGES-108] - Allow to configure changes-report mojo
> from properties
> * [MCHANGES-113] - Allow configuration of announcement parameters
> from command line
> * [MCHANGES-117] - Send only one e-mail to many recipients (all
> recipients in one to-header)
> * [MCHANGES-118] - AnnouncementMojo can only load velocity
> templates from src/main/resources and not a path related to user.dir
> * [MCHANGES-120] - announcement:generate mojo should warn, not
> fail if the changes file doesn't exist.
>
> ** New Feature
> * [MCHANGES-47] - Add support for multiple <issue> and <due-to>
> tags in changes.xml
> * [MCHANGES-69] - Add a date elment or attribute inside the action
> element of changes.xml
> * [MCHANGES-86] - Create a changes-validate mojo
> * [MCHANGES-90] - Add support for Trac-report like Jira-report
> * [MCHANGES-112] - Add more than one link template
> * [MCHANGES-129] - The version can't be set from the cli in
> announcement-mail
> * [MCHANGES-130] - Announce mail : Merging content from the
> changes file and from jira
> * [MCHANGES-132] - Overriding mail introduction with a
> mojo configuration
> * [MCHANGES-133] - adding maven project to the velocity context
> when generating announce email
> * [MCHANGES-134] - Passing some extra parameters to the announce
> velocity context
>
> ** Task
> * [MCHANGES-119] - Add the changes xsd file
> http://maven.apache.org/xsd/ after the 2.1 release
> * [MCHANGES-122] - release modello-maven-plugin 1.0-alpha-21
>
> Have fun,
>
> -The Maven team
>
> ---------------------------------------------------------------------
> 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: [ANN] Maven Changes Plugin 2.1 Released
Posted by Mark Derricutt <ma...@talios.com>.
If I hard code a <mailSender> element, things work fine thou...
On Wed, Nov 26, 2008 at 7:50 AM, Mark Derricutt <ma...@talios.com> wrote:
> Strange,
--
"It is easier to optimize correct code than to correct optimized
code." -- Bill Harlan
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [ANN] Maven Changes Plugin 2.1 Released
Posted by Mark Derricutt <ma...@talios.com>.
Strange,
I'm seeing:
Caused by: org.apache.maven.plugin.MojoExecutionException: Invalid
mail sender: name and email is mandatory (null (null)).
at org.apache.maven.plugin.announcement.AnnouncementMailMojo.sendMessage(AnnouncementMailMojo.java:232)
at org.apache.maven.plugin.announcement.AnnouncementMailMojo.execute(AnnouncementMailMojo.java:209)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
even thou I have valid developers, and a valid fromDeveloperId:
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-changes-plugin:2.1:announcement-mail'
-->
[DEBUG] (s) from = [org.apache.maven.model.Developer@8b48081,
org.apache.maven.model.Developer@260999e]
[DEBUG] (s) fromDeveloperId = markd
[DEBUG] (f) mailContentType = text/plain
[DEBUG] (s) mailSender = null (null)
[DEBUG] (s) smtpHost = smtp.xnet.co.nz
[DEBUG] (s) smtpPort = 25
[DEBUG] (s) sslMode = false
[DEBUG] (s) subject = [ANNOUNCEMENT] - smx3.partyresource
1.2.0-SNAPSHOT released
[DEBUG] (s) template = announcement.vm
[DEBUG] (s) templateOutputDirectory =
/Users/amrk/IdeaProjects/securemx/smx3/module/smx3.partyresource/target/announcement
[DEBUG] (s) toAddresses = [mark@talios.com]
mailSender just comes out without the name/email, my effective-pom shows me:
<developers>
<developer>
<id>markd</id>
<name>Mark Derricutt</name>
<email>mark.derricutt@XXXX</email>
</developer>
<developer>
I'll pull out the changes source once I get to the office and see if I
can work out whats going on here.
On Tue, Nov 25, 2008 at 11:01 PM, Olivier Lamy <ol...@apache.org> wrote:
> The Maven team is pleased to announce the release of the Maven Changes
> Plugin, version 2.1.
>
> http://maven.apache.org/plugins/maven-changes-plugin/
>
> You should specify the version in your project's plugin configuration:
>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-changes-plugin</artifactId>
> <version>2.1</version>
> </plugin>
>
> Release Notes - Maven 2.x Changes Plugin - Version 2.1
>
>
> ** Bug
> * [MCHANGES-109] - Fix output directory for images of changes-report
> * [MCHANGES-110] - No issue links generated if
> ${project.issueManagement.url} empty but issueLinkTemplate provided
> * [MCHANGES-111] - Announcement Mojo doesn't respect Jira
> authentication settings
> * [MCHANGES-114] - Title in changes.xml is not outputted in
> changes-report.html
> * [MCHANGES-126] - NullPointerException when executing jira-report
> with JIRA 3.13
> * [MCHANGES-127] - Generated Announcement is not complete (in
> trunk rev 709936)
> * [MCHANGES-128] - unable to use "toAddresses" field for announces
>
> ** Improvement
> * [MCHANGES-61] - Provide DTD/XSD for changes.xml
> * [MCHANGES-71] - need add template encoding to announcement-generate
> * [MCHANGES-107] - Add html output format for mail annoucement
> * [MCHANGES-108] - Allow to configure changes-report mojo from properties
> * [MCHANGES-113] - Allow configuration of announcement parameters
> from command line
> * [MCHANGES-117] - Send only one e-mail to many recipients (all
> recipients in one to-header)
> * [MCHANGES-118] - AnnouncementMojo can only load velocity
> templates from src/main/resources and not a path related to user.dir
> * [MCHANGES-120] - announcement:generate mojo should warn, not
> fail if the changes file doesn't exist.
>
> ** New Feature
> * [MCHANGES-47] - Add support for multiple <issue> and <due-to>
> tags in changes.xml
> * [MCHANGES-69] - Add a date elment or attribute inside the action
> element of changes.xml
> * [MCHANGES-86] - Create a changes-validate mojo
> * [MCHANGES-90] - Add support for Trac-report like Jira-report
> * [MCHANGES-112] - Add more than one link template
> * [MCHANGES-129] - The version can't be set from the cli in
> announcement-mail
> * [MCHANGES-130] - Announce mail : Merging content from the
> changes file and from jira
> * [MCHANGES-132] - Overriding mail introduction with a mojo configuration
> * [MCHANGES-133] - adding maven project to the velocity context
> when generating announce email
> * [MCHANGES-134] - Passing some extra parameters to the announce
> velocity context
>
> ** Task
> * [MCHANGES-119] - Add the changes xsd file
> http://maven.apache.org/xsd/ after the 2.1 release
> * [MCHANGES-122] - release modello-maven-plugin 1.0-alpha-21
>
> Have fun,
>
> -The Maven team
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
"It is easier to optimize correct code than to correct optimized
code." -- Bill Harlan
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: cargo and jboss. ERROR
Posted by Gabriele Columbro <g....@sourcesense.com>.
AFAIK you need to specify the plugin version, unless the plugin resides in
the groupId:
org.apache.maven.plugins
If adding the version (e.g. 1.0-beta-1 as latest in
http://repo2.maven.org/maven2/org/codehaus/cargo/cargo-maven2-plugin/ ) does
not help, then I'm stuck ;)
Hope this helps,
Gab
2008/11/25 <ko...@laudio.info>
> hello
>
> i am one mavien multiproject that has 2 web modules, 2 jar modules.
> into the ear module i have add the next but when i made mvn install apears
> the bellow error.
>
> Can you help me for solving this problem?
> thanks
>
> <plugin>
> <groupId>org.codehaus.cargo</groupId>
> <artifactId>cargo-maven2-plugin</artifactId>
> <configuration>
> <container>
> <containerId>jboss4x</containerId>
> <!--<home>${jboss.home}</home>-->
> <append>false</append>
> </container>
> <configuration>
> <type>existing</type>
> <home>${jboss.home}\server\default</home>
> <properties>
> <cargo.logging>high</cargo.logging>
> <cargo.rmi.port>1099</cargo.rmi.port>
> <cargo.jboss.configuration>default</cargo.jboss.configuration>
> </properties>
> </configuration>
> <deployer>
> <type>installed</type>
> <deployables>
> <deployable>
> <groupId>${pom.groupId}</groupId>
> <artifactId>${pom.artifactId}</artifactId>
> <type>${pom.packaging}</type>
> </deployable>
> </deployables>
> </deployer>
> </configuration>
> <executions>
> <execution>
> <id>start-container</id>
> <phase>pre-integration-test</phase>
> <goals>
> <goal>start</goal>
> </goals>
> </execution>
> <execution>
> <id>stop-container</id>
> <phase>post-integration-test</phase>
> <goals>
> <goal>stop</goal>
> </goals>
> </execution>
> </executions>
> </plugin>
> </plugins>
> </build>
> <properties>
> <jboss.home>C:\Ekirol\jboss-4.2.2.GA</jboss.home>
> <jboss.port>8080</jboss.port>
> </properties>
>
>
> ###########ERROR################
> [INFO] [war:war]
> [INFO] Packaging webapp
> [INFO] Assembling webapp[myAppAdminWeb] in
> [C:\myApp\aplicacion\myApp\myAppAdminWeb\target\myAppAdminWeb]
> [INFO] Processing war project
> [INFO] Webapp assembled in[15 msecs]
> [INFO] Building war:
> C:\myApp\aplicacion\myApp\myAppAdminWeb\target\myAppAdminWeb.war
> [INFO] [install:install]
> [INFO] Installing
> C:\myApp\aplicacion\myApp\myAppAdminWeb\target\myAppAdminWeb.war to
> C:\Documents and Settings\user\.m2\repository\myAppGroup\myApp\
> myAppAdminWeb\1.0\myAppAdminWeb-1.0.war
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Building myAppEar
> [INFO] task-segment: [install]
> [INFO]
> ------------------------------------------------------------------------
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] The plugin 'org.codehaus.cargo:cargo-maven2-plugin' does not exist
> or no
> valid version could be found
> [INFO]
> ------------------------------------------------------------------------
> [INFO] For more information, run Maven with the -e switch
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 4 seconds
> [INFO] Finished at: Tue Nov 25 13:10:07 CET 2008
> [INFO] Final Memory: 13M/24M
> [INFO]
> ------------------------------------------------------------------------
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
Gabriele Columbro
Alfresco ECM Product Strategy Consultant
+31 627 565 103
Sourcesense - Making sense of open Source
cargo and jboss. ERROR
Posted by ko...@laudio.info.
hello
i am one mavien multiproject that has 2 web modules, 2 jar modules.
into the ear module i have add the next but when i made mvn install apears
the bellow error.
Can you help me for solving this problem?
thanks
<plugin>
<groupId>org.codehaus.cargo</groupId>
<artifactId>cargo-maven2-plugin</artifactId>
<configuration>
<container>
<containerId>jboss4x</containerId>
<!--<home>${jboss.home}</home>-->
<append>false</append>
</container>
<configuration>
<type>existing</type>
<home>${jboss.home}\server\default</home>
<properties>
<cargo.logging>high</cargo.logging>
<cargo.rmi.port>1099</cargo.rmi.port>
<cargo.jboss.configuration>default</cargo.jboss.configuration>
</properties>
</configuration>
<deployer>
<type>installed</type>
<deployables>
<deployable>
<groupId>${pom.groupId}</groupId>
<artifactId>${pom.artifactId}</artifactId>
<type>${pom.packaging}</type>
</deployable>
</deployables>
</deployer>
</configuration>
<executions>
<execution>
<id>start-container</id>
<phase>pre-integration-test</phase>
<goals>
<goal>start</goal>
</goals>
</execution>
<execution>
<id>stop-container</id>
<phase>post-integration-test</phase>
<goals>
<goal>stop</goal>
</goals>
</execution>
</executions>
</plugin>
</plugins>
</build>
<properties>
<jboss.home>C:\Ekirol\jboss-4.2.2.GA</jboss.home>
<jboss.port>8080</jboss.port>
</properties>
###########ERROR################
[INFO] [war:war]
[INFO] Packaging webapp
[INFO] Assembling webapp[myAppAdminWeb] in
[C:\myApp\aplicacion\myApp\myAppAdminWeb\target\myAppAdminWeb]
[INFO] Processing war project
[INFO] Webapp assembled in[15 msecs]
[INFO] Building war:
C:\myApp\aplicacion\myApp\myAppAdminWeb\target\myAppAdminWeb.war
[INFO] [install:install]
[INFO] Installing
C:\myApp\aplicacion\myApp\myAppAdminWeb\target\myAppAdminWeb.war to
C:\Documents and Settings\user\.m2\repository\myAppGroup\myApp\
myAppAdminWeb\1.0\myAppAdminWeb-1.0.war
[INFO]
------------------------------------------------------------------------
[INFO] Building myAppEar
[INFO] task-segment: [install]
[INFO]
------------------------------------------------------------------------
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] The plugin 'org.codehaus.cargo:cargo-maven2-plugin' does not exist
or no
valid version could be found
[INFO]
------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 4 seconds
[INFO] Finished at: Tue Nov 25 13:10:07 CET 2008
[INFO] Final Memory: 13M/24M
[INFO]
------------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org