[ 
http://jira.codehaus.org/browse/MEAR-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=232316#action_232316
 ] 

Fred Bricon commented on MEAR-116:
----------------------------------

Hi,

Benjamin's patch is exactly what we need for m2eclipse-wtp (I was about to 
propose the same kind of stuff). 
Currently, due to m2eclipse project resolution behavior (explained here : 
http://jira.codehaus.org/browse/MWAR-192?focusedCommentId=175406&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_175406),
 artifact.getFile() returns <workspace_project_path>/target/classes. 
That doesn't look good when trying to run  *mvn package* from within eclipse.

As you may know, or not, application.xml in eclipse WTP is currently generated 
using WTP's API. Since it's a source of countless issues, I've tried delegating 
to ear:generate-application-xml instead (more or less), but hit the  
<workspace_project_path>/target/classes bug.

Quick resolution of this issue would help m2eclipse-wtp (at least) to move 
forward. Let me know if I can do anything to help.

regards,

Fred Bricon

> different build results from single module build and from reactor build
> -----------------------------------------------------------------------
>
>                 Key: MEAR-116
>                 URL: http://jira.codehaus.org/browse/MEAR-116
>             Project: Maven 2.x Ear Plugin
>          Issue Type: Bug
>    Affects Versions: 2.4
>         Environment: maven 2.2.0
>            Reporter: Milos Kleint
>            Priority: Critical
>         Attachments: ear116.zip, MEAR-116.patch
>
>
> attached is a sample application as generated by netbeans 6.8 (using 
> archetypes from org.codehaus.mojo.archetypes)
> a simple ear+ejb+war multiproject.
> when building everything together from the root pom, I get this output:
> [ear:ear]
> Copying artifact[ejb:org.kleint:samplejavaee6-ejb:1.0-SNAPSHOT] 
> to[samplejavaee6-ejb.jar]
> Copying artifact[war:org.kleint:samplejavaee6-web:1.0-SNAPSHOT] 
> to[samplejavaee6-web.war]
> and the war and ejb artifacts are included with names not including version.
> However if I later do a mvn clean install on the ear project, I get this 
> output:
> [ear:ear]
> Copying artifact[ejb:org.kleint:samplejavaee6-ejb:1.0-SNAPSHOT] 
> to[samplejavaee6-ejb-1.0-SNAPSHOT.jar]
> Copying artifact[war:org.kleint:samplejavaee6-web:1.0-SNAPSHOT] 
> to[samplejavaee6-web-1.0-SNAPSHOT.war]
> and the war/ejb artifacts get a version in the name.
> This sounds like it has to do with the finalname being resolved differently 
> in single module build and in reactor build.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to