[jbosstools-dev] JBoss Maven Integration Facet?

[Snjezana Peco]

On 9/23/2011 11:50 AM, Max Rydahl Andersen wrote:
>> I'm prototyping some basic tooling for SwitchYard and have pieced together a crude faceted project preset to allow SwitchYard projects to be deployed to AS using the existing WTP support.  The facets I'm using are:
>> * Java
>> * Utility Module
> Sounds about right yes.
>
> For the case of importing existing maven projects and have these things enabled Fred Bricon should be able to tell you what the m2e/wtp plugin needs to identify them.
>
>> * JBoss Maven Integration
>>
>> My questions: Is the JBoss Maven facet required?  What purpose does it serve?  (Currently, SwtichYard projects are Maven projects, utilizing m2eclipse.)
> JBoss Maven Integration is a feature we have had for a while but not really used much since JBoss AS&  EAP artifacts wasn't readily available in maven repos.
>
> The intent of the jboss maven integration is to allow you to create faceted projects and then use Maven as the Library provider. There are code in jboss tools which
> will look at the given facet and then add a list of dependencies into the pom.  This is actually something that should be in m2eclipse but the m2e team prefer everything
> is done maven first.
>
> Snjezana should be able to point you to this. This is one of the areas where we might need to change things so it accommodate how switchyard needs/wants things.
>

If you want to create a Maven project using a WTP project wizard 
(dynamic web project, ejb project, ear project, utility project ...), 
you have to add the JBoss Maven integration facet that will add the 
Maven builder/nature to the project. It will create pom.xml and the 
corresponding maven plugin (war, ejb, ear) and enable you to add Maven 
dependencies using Maven Library Provider 
(https://issues.jboss.org/browse/JBIDE-4565).

The JBoss Maven Integration facet is also obliged if you want to use 
some of the JBoss Maven configurators (JSF, CDI, Seam 2, Portlet, 
Hibernate ...).

Snjeza