[
https://issues.jboss.org/browse/TOOLSDOC-281?page=com.atlassian.jira.plug...
]
Fred Bricon commented on TOOLSDOC-281:
--------------------------------------
Isaac, the Facet approach will most probably stay, but will rely on the m2e conversion API
internally.
The Maven Facet added value is that it can add maven-based configurations to an existing
project outside the pure conversion mechanism.
Ex : if you have a Maven project and want to add JSF dependencies, then JSF Facet + Maven
Facet => new <dependency> added to the pom
Maven Tools Reference Chapter 4 should use a different way
----------------------------------------------------------
Key: TOOLSDOC-281
URL:
https://issues.jboss.org/browse/TOOLSDOC-281
Project: Documentation for JBoss Tools and Developer Studio
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Affects Versions: 3.3.0.Final
Reporter: Rastislav Wagner
Assignee: Isaac Rooskov
Labels: maven
Fix For: Future
Converting existing project to maven project should be done this way:
1. Right click on existing project -> Preferences
2. Project Facets
3. Activate JBoss Maven Integration
This will set up project rightly (set up webcontent folder in pom.xml, activates other
needed facets..).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira