[jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1716) Move EjbParsingDeployer parsing deployer from jboss-ejb3-embedded to jboss-ejb3-deployers

[Carlo de Wolf (JIRA)]

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

Carlo de Wolf updated EJBTHREE-1716:
------------------------------------

          Component/s:     (was: deployers)
        Fix Version/s: embedded-1.0.0-alpha-2
                           (was: 1.1.1)
    Affects Version/s: embedded-1.0.0-Alpha1
                           (was: 1.0.0-GA)


> Move EjbParsingDeployer parsing deployer from jboss-ejb3-embedded to jboss-ejb3-deployers
> -----------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1716
>                 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1716
>             Project: EJB 3.0
>          Issue Type: Sub-task
>          Components: embedded
>    Affects Versions: embedded-1.0.0-Alpha1
>            Reporter: jaikiran pai
>            Assignee: jaikiran pai
>             Fix For: embedded-1.0.0-alpha-2
>
>
> This involves:
> 1) Moving org.jboss.ejb3.embedded.deployers.EjbParsingDeployer from jboss-ejb3-embedded to org.jboss.ejb3.deployers.EjbParsingDeployer under jboss-ejb3-deployers project 
> 2) Updating the jboss-ejb3-deployers pom.xml to add a dependency on jboss-deployers-vfs (EjbParsingDeployer requires this)
> 3) Bumping the following artifact versions of pom.xml of jboss-ejb3-embedded to use the correct dependencies:
> 	- Parent - jboss-ejb3-build to 1.0.0
> 	- jboss-ejb3-core to 1.0.0
> 	- jboss-ejb3-deployers to 1.0.1-SNAPSHOT (which contains the newly moved EjbParsingDeployer)
> 4)  Update the jpa-deployers-beans.xml in jboss-ejb3-embedded to add a SpecCompliantSearchStrategy MC bean (Refer to forum thread for a related discussion).
> 5) Update the ejb-deployers-beans.xml in jboss-ejb3-embedded to use the new deployer (and remove reference to the earlier one)

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