maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stéphane Nicoll (JIRA) <>
Subject [jira] (MEAR-150) Support new 'no-version-for-ejb' file name mapping
Date Thu, 02 Aug 2012 19:31:21 GMT


Stéphane Nicoll closed MEAR-150.

    Resolution: Fixed

Applied, thanks. I used 'no-version-for-ejb' for the name to be consistent.

Also deployed a 2.8-SNAPSHOT with the change.
> Support new 'no-version-for-ejb' file name mapping
> --------------------------------------------------
>                 Key: MEAR-150
>                 URL:
>             Project: Maven 2.x Ear Plugin
>          Issue Type: New Feature
>    Affects Versions: 2.7
>            Reporter: Philippe Marschall
>            Assignee: Stéphane Nicoll
>            Priority: Minor
>             Fix For: 2.8
>         Attachments: maven-ear-plugin.patch
> JBoss 7 has a new [remote lookup naming stragety|].
The name of the ejb-jar is not part of remote name. If that includes the version this is obviously
going to cause problems. Using 'no-version' would fix this but I would like to keep version
of the library jars as a quick way of verifying the ears contents. What this name mapping
does is essentially 'no-version' for ejb-jars, 'standard' for library jars.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message