[jbosstools-issues] [JBoss JIRA] (JBIDE-13876) Decide what to do with the Maven Facet
Fred Bricon (JIRA)
jira-events at lists.jboss.org
Wed Mar 27 10:18:42 EDT 2013
[ https://issues.jboss.org/browse/JBIDE-13876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12763481#comment-12763481 ]
Fred Bricon edited comment on JBIDE-13876 at 3/27/13 10:17 AM:
---------------------------------------------------------------
Currently the JBoss Maven Facet is installed explicitely in all our m2e configurators.
I believe it'd be more appropriate to install that facet automatically in a FacetListener, once the Java or EAR Facet is installed and the project has the Maven nature.
was (Author: fbricon):
Currently the JBoss Maven Facet is install explicitely in all our m2e configurators.
I believe it'd be more appropriate to install that facet automatically in a FacetListener, once the Java or EAR Facet is installed and the project has the Maven nature.
> 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: 4.1.x
>
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbosstools-issues
mailing list