[jboss-jira] [JBoss JIRA] Resolved: (JBDEPLOY-232) War's metadata location is used too broadly

[Ales Justin (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBDEPLOY-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ales Justin resolved JBDEPLOY-232.
----------------------------------

    Fix Version/s:     (was:  JBDEPLOY-2.0.9.GA)
       Resolution: Done


> War's metadata location is used too broadly
> -------------------------------------------
>
>                 Key: JBDEPLOY-232
>                 URL: https://jira.jboss.org/jira/browse/JBDEPLOY-232
>             Project: JBoss Deployers
>          Issue Type: Task
>    Affects Versions: JBDEPLOY-2.0.8.SP1
>            Reporter: Ales Justin
>            Assignee: Ales Justin
>             Fix For: JBDEPLOY-2.1.0.Alpha1
>
>
> When adding .war libs metadata locations as deployment's metadata locations,
> we can stumble upon unexpected behavior; see forum for more details.
> We need to limit the usage of alternative metadata locations.
> e.g. diff between default and alternative -- JEE EJB might also pick up from alternative

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