[jira] (MEAR-150) [patch] support new 'no-version-for-ejbs' file name mapping

["Stéphane Nicoll (JIRA)" <ji...@codehaus.org>]

     [ https://jira.codehaus.org/browse/MEAR-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stéphane Nicoll reassigned MEAR-150:
------------------------------------

    Assignee: Stéphane Nicoll
    
> [patch] support new 'no-version-for-ejbs' file name mapping
> -----------------------------------------------------------
>
>                 Key: MEAR-150
>                 URL: https://jira.codehaus.org/browse/MEAR-150
>             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|https://docs.jboss.org/author/display/AS71/EJB+invocations+from+a+remote+client+using+JNDI?_sscc=t]. 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: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira