[jboss-jira] [JBoss JIRA] Updated: (JBAS-7025) Do not rely on single "server/target/etc/deployers/metadata-deployer-jboss-beans.xml" list

[Jason T. Greene (JIRA)]

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

Jason T. Greene updated JBAS-7025:
----------------------------------

    Fix Version/s: Unscheduled
                       (was: 6.0.0.M3)


Unscheduling due to inactivity. Reassign to a release that you feel comfortable resolving this issue in, or leave as is.

> Do not rely on single "server/target/etc/deployers/metadata-deployer-jboss-beans.xml" list
> ------------------------------------------------------------------------------------------
>
>                 Key: JBAS-7025
>                 URL: https://jira.jboss.org/jira/browse/JBAS-7025
>             Project: JBoss Application Server
>          Issue Type: Patch
>      Security Level: Public(Everyone can see) 
>          Components: Deployers
>    Affects Versions: JBossAS-5.1.0.GA
>            Reporter: Scott Marlow
>            Assignee: Scott Marlow
>            Priority: Minor
>             Fix For: Unscheduled
>
>
> We should not rely on the single "server/target/etc/deployers/metadata-deployer-jboss-beans.xml" list.  Deployments should be self contained with proper jboss-scanning.xml (or whatever is necessary).  
> This comes from development forum email.  Thread starts at http://lists.jboss.org/pipermail/jboss-development/2009-June/014537.html.  Also see http://lists.jboss.org/pipermail/jboss-development/2009-June/014599.html + http://lists.jboss.org/pipermail/jboss-development/2009-June/014603.html

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