[jbosstools-issues] [JBoss JIRA] (JBIDE-10762) make jboss tools maven facet generate a "good" pom.xml
[
https://issues.jboss.org/browse/JBIDE-10762?page=com.atlassian.jira.plugi...
]
Fred Bricon resolved JBIDE-10762.
---------------------------------
Fix Version/s: (was: 3.3.0.CR1)
Resolution: Done
I tried to clean up the pom.xml as best I could :
- don't add plugin configuration when existing values correspond to maven defaults
- lock down plugin versions
- remove java nature from EAR, POM projects
- added children projects to parent's dependency management section
- made the plugin configs IProjectFacetVersion-aware
- removed custom output directory settings, everything goes to target/classes now
- jboss seam is now referenced as an ejb type dependency everywhere.
- fixed Facet -> maven packaging synchro in M2E Facet UI (Ear -> ear, EJB -> ejb
...)
- added support for web fragments
Also added a JSF2 maven provided library template, usable for JSF 2 Facet, using standard
BOM POM in dependencyManagement
make jboss tools maven facet generate a "good" pom.xml
-------------------------------------------------------
Key: JBIDE-10762
URL: https://issues.jboss.org/browse/JBIDE-10762
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: maven
Reporter: Max Rydahl Andersen
Assignee: Fred Bricon
Priority: Critical
Fix For: 3.3.0.Beta1
currently we generate a very custom and not at all clean pom.xml with context of
dependenciees and setup when using jboss maven facet.
This pom.xml should:
A) be clean
B) not add dependencies against Project Wolf recommendations (should it have an "use
enterprise" flag?)
C) make maven library provider work or remove/disable it so dependencies are clean.
--
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