[jbosstools-issues] [JBoss JIRA] (JBIDE-13876) Decide what to do with the Maven Facet

[Fred Bricon (JIRA)]

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

Fred Bricon updated JBIDE-13876:
--------------------------------
    Fix Version/s: LATER
                       (was: 4.1.x)


> Decide what to do with the Maven Facet
> --------------------------------------
>
>                 Key: JBIDE-13876
>                 URL: https://issues.jboss.org/browse/JBIDE-13876
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: maven
>    Affects Versions: 4.1.0.Alpha1
>            Reporter: Fred Bricon
>            Assignee: Fred Bricon
>             Fix For: LATER
>
>
> The JBoss Maven Facet has been used to :
> - convert projects to Maven
> - add new dependencies to an existing Maven project (by acting as a Library provider)
> The conversion part has been superceded (mostly) by m2e's conversion API.
> The way the Maven facet acts (not on its own but in support of other Facets, Seam most notably) is pretty ugly (storing Facets models in a MavenPostInstallListener), potentially leading to memory leaks.
> The project conversion bit needs to be revisited, see how m2e's conversion API could be leveraged.
> All in all, I'm convinced the whole Maven Facet programming model need a facelift. This issue is opened to discuss what we need to do and how to implement that.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)