You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Milos Kleint (JIRA)" <ji...@codehaus.org> on 2009/11/27 11:26:55 UTC

[jira] Created: (MEAR-116) different build results from single module build and from reactor build

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


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

        

[jira] Updated: (MEAR-116) different build results from single module build and from reactor build

Posted by "Milos Kleint (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MEAR-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Milos Kleint updated MEAR-116:
------------------------------

    Attachment: ear116.zip

here are the projects. 

> 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
>
>
> 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

        

[jira] Updated: (MEAR-116) different build results from single module build and from reactor build

Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MEAR-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stephane Nicoll updated MEAR-116:
---------------------------------

    Fix Version/s: 2.4.3

> 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
>             Fix For: 2.4.3
>
>         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

        

[jira] Commented: (MEAR-116) different build results from single module build and from reactor build

Posted by "Milos Kleint (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MEAR-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=206162#action_206162 ] 

Milos Kleint commented on MEAR-116:
-----------------------------------

I'm not entirely sure this is a ear plugin problem only, could be a general feat that just backfires here. The question is how to protect from it.


> 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
>
>
> 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

        

[jira] Updated: (MEAR-116) different build results from single module build and from reactor build

Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MEAR-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Bentmann updated MEAR-116:
-----------------------------------

    Attachment: MEAR-116.patch

Quote from javadoc of {{StandardFileNameMapping}}:
bq. It returns the name of the file in the local repository.
This does not always hold when calling {{Artifact.getFile().getName()}}.

During a reactor build, the artifact is resolved from the project's output directory and the filename here is controlled by the {{finalName}} of the build section or the config of the packaging plugin. In contrast, the filename in the local/remote repo is entirely controlled by the repo layout (which doesn't consider {{finalName}}). Milos' example is using non-default finalName's, thereby making the conceptual difference visible.

The attached patch demos a potential solution by calculating the filename in the plugin itself, based on the artifact coordinates. The code basically mimics the calculation from {{DefaultRepositoryLayout}} with the difference of using {{getBaseVersion()}} instead of {{getVersion()}}.

The patch is incomplete. Apart from tests, it doesn't update the other affected {{FullFileNameMapping}}.

> 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

        

[jira] Commented: (MEAR-116) different build results from single module build and from reactor build

Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MEAR-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=206080#action_206080 ] 

Stephane Nicoll commented on MEAR-116:
--------------------------------------

Nothing is attached Milos...

> 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
>
> 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

        

[jira] Commented: (MEAR-116) different build results from single module build and from reactor build

Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MEAR-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=206192#action_206192 ] 

Stephane Nicoll commented on MEAR-116:
--------------------------------------

That's also what I think. It might be a misuse of core API in the EarMojo itself.

Thanks for the project.

> 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
>
>
> 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

        

[jira] Commented: (MEAR-116) different build results from single module build and from reactor build

Posted by "Fred Bricon (JIRA)" <ji...@codehaus.org>.
    [ 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

        

[jira] Closed: (MEAR-116) different build results from single module build and from reactor build

Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MEAR-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stephane Nicoll closed MEAR-116.
--------------------------------

    Resolution: Fixed

Fixed. I just deployed a snapshot of 2.4.3 for you to try. Your sample project works fine now.

> 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
>            Assignee: Stephane Nicoll
>            Priority: Critical
>             Fix For: 2.4.3
>
>         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

        

[jira] Commented: (MEAR-116) different build results from single module build and from reactor build

Posted by "Milos Kleint (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MEAR-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=206195#action_206195 ] 

Milos Kleint commented on MEAR-116:
-----------------------------------

the project is basically what we generate in netbeans when someone wants an ear maven project. It's backed by archetypes at mojo.codehaus.org.

> 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
>
>
> 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

        

[jira] Work started: (MEAR-116) different build results from single module build and from reactor build

Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MEAR-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on MEAR-116 started by Stephane Nicoll.

> 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
>            Assignee: Stephane Nicoll
>            Priority: Critical
>             Fix For: 2.4.3
>
>         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