[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-9125) Add support for jboss-packaging-maven-plugin

[Fred Bricon (JIRA)]

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

Fred Bricon updated JBIDE-9125:
-------------------------------

    Fix Version/s: 3.3.x
                       (was: 3.3.0.M3)


Postponing resolution to 3.3.x for the complete set of packages :
* jboss-packaging:aop Builds a deployable JBoss AOP Archive.
* jboss-packaging:esb Builds a deployable JBoss ESB Archive.
* jboss-packaging:har Builds a deployable JBoss Hibernate Archive.
* jboss-packaging:par Builds a deployable JBoss Process Archive.
* jboss-packaging:spring Builds a deployable JBoss Spring Archive.

Need to figure out what packages are relevant.

> Add support for jboss-packaging-maven-plugin
> --------------------------------------------
>
>                 Key: JBIDE-9125
>                 URL: https://issues.jboss.org/browse/JBIDE-9125
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: maven
>    Affects Versions: 3.2.0.Final
>            Reporter: Fred Bricon
>            Assignee: Fred Bricon
>             Fix For: 3.3.x
>
>
> The original feature request was created in m2e-wtp ([Add support for SAR projects|https://issues.sonatype.org/browse/MECLIPSEWTP-46])
> The idea is to create a set of configurators, to handle jboss packages packages (http://mojo.codehaus.org/jboss-packaging-maven-plugin/).
> The configurators would work pretty much the same as the Connector configurator :
> - read the jboss-packaging-maven-plugin
> - all dependencies would have to be declared in .component
> - the project woul have to have the utility facet, in order to be deployed in an EAR
> First configurator would support SAR projects

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira