[
https://issues.jboss.org/browse/JBIDE-10750?page=com.atlassian.jira.plugi...
]
Fred Bricon resolved JBIDE-10750.
---------------------------------
Labels: new_and_noteworthy (was: )
Resolution: Done
Fixed in trunk.
* New JPA configurator depends on Dali JPT.
* If persistence.xml is detected, JPA facet version will be inferred from the version
attribute in the file
* "discover classes automatically" is enabled
* JPA implementation type set to "disable Library configuration"
* Platform set to hibernate (or eclipselink) if the provider or one of the properties of
persistence.xml contains hibernate (or eclipselink)
* no orm.xml is created
* a warning is displayed : "No connection specified for project. No
database-specific validation will be performed."
Archetype created projects should also be "JPA Projects"
--------------------------------------------------------
Key: JBIDE-10750
URL:
https://issues.jboss.org/browse/JBIDE-10750
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: maven
Affects Versions: 3.3.0.M5
Reporter: Burr Sutter
Assignee: Fred Bricon
Labels: new_and_noteworthy
Fix For: 3.3.0.Beta1
Attachments: Screen Shot 2012-01-30 at 10.27.02 AM.png, Screen Shot 2012-01-30 at
10.27.29 AM.png, Screen Shot 2012-01-30 at 10.27.43 AM.png
When the end-user selects an archetype from JBoss Central, it creates a project, in many
cases with JPA entities in that project but does not "turn on" the JPA Project
Facet. Therefore, the end-user is stuck trying to figure out how to turn on that facet
(currently undocumented). See screenshots for the current workflow.
--
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