1:57 p.m.
Burr Sutter created JBIDE-10750:
-----------------------------------
Summary: 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
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
2 p.m.
[
https://issues.jboss.org/browse/JBIDE-10750?page=com.atlassian.jira.plugi...
]
Burr Sutter updated JBIDE-10750:
--------------------------------
Attachment: 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
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
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
2:07 p.m.
[
https://issues.jboss.org/browse/JBIDE-10750?page=com.atlassian.jira.plugi...
]
Burr Sutter commented on JBIDE-10750:
-------------------------------------
The Hibernate runtime should also have been pre-configured but that is more during the
addition of AS.
https://issues.jboss.org/browse/JBIDE-10751
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
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
6:48 a.m.
[
https://issues.jboss.org/browse/JBIDE-10750?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen updated JBIDE-10750:
----------------------------------------
Fix Version/s: 3.3.0.Beta1
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
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
8:30 a.m.
[
https://issues.jboss.org/browse/JBIDE-10750?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-10750:
---------------------------------------------
There are three parts here:
A) detect if JPA relevant (look for persistence.xml) and enable JPA - this will allow for
form editor of persistence.xml
B) detect which JPA runtime is available - lookup key classes to make that choice or just
look for org.hibernate | eclipselink. in persistence.xml - this will allow for hibernate
tools to be enabled when doing generation.
C) When A+B make sure Dali doesn't create/overwrite/forgets persistence.xml
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
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
8:32 a.m.
[
https://issues.jboss.org/browse/JBIDE-10750?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen edited comment on JBIDE-10750 at 1/31/12 9:30 AM:
----------------------------------------------------------------------
There are three parts here:
A) detect if JPA relevant (look for persistence.xml) and enable JPA - this will allow for
form editor of persistence.xml
B) detect which JPA runtime is available - lookup key classes to make that choice or just
look for org.hibernate | eclipselink. in persistence.xml - this will allow for hibernate
tools to be enabled when doing generation.
C) When A+B make sure Dali doesn't create/overwrite/forgets persistence.xml
D) Connection info - there is no info in pom.xml nor persistence.xml (just a datasource
name) etc. about connection info so this cannot be done automatically.
was (Author: maxandersen):
There are three parts here:
A) detect if JPA relevant (look for persistence.xml) and enable JPA - this will allow for
form editor of persistence.xml
B) detect which JPA runtime is available - lookup key classes to make that choice or just
look for org.hibernate | eclipselink. in persistence.xml - this will allow for hibernate
tools to be enabled when doing generation.
C) When A+B make sure Dali doesn't create/overwrite/forgets persistence.xml
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
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
8:32 a.m.
[
https://issues.jboss.org/browse/JBIDE-10750?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen edited comment on JBIDE-10750 at 1/31/12 9:31 AM:
----------------------------------------------------------------------
There are multiple parts here:
A) detect if JPA relevant (look for persistence.xml) and enable JPA - this will allow for
form editor of persistence.xml
B) detect which JPA runtime is available - lookup key classes to make that choice or just
look for org.hibernate | eclipselink. in persistence.xml - this will allow for hibernate
tools to be enabled when doing generation.
C) When A+B make sure Dali doesn't create/overwrite/forgets persistence.xml
D) Connection info - there is no info in pom.xml nor persistence.xml (just a datasource
name) etc. about connection info so this cannot be done automatically.
was (Author: maxandersen):
There are three parts here:
A) detect if JPA relevant (look for persistence.xml) and enable JPA - this will allow for
form editor of persistence.xml
B) detect which JPA runtime is available - lookup key classes to make that choice or just
look for org.hibernate | eclipselink. in persistence.xml - this will allow for hibernate
tools to be enabled when doing generation.
C) When A+B make sure Dali doesn't create/overwrite/forgets persistence.xml
D) Connection info - there is no info in pom.xml nor persistence.xml (just a datasource
name) etc. about connection info so this cannot be done automatically.
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
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
5:48 a.m.
[
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
9:05 a.m.
[
https://issues.jboss.org/browse/JBIDE-10750?page=com.atlassian.jira.plugi...
]
Burr Sutter commented on JBIDE-10750:
-------------------------------------
where should connection info be placed, pom or persistence xml files? And does Dali offer
a place to map datasource names to actual connection bindings?
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
4:54 a.m.
[
https://issues.jboss.org/browse/JBIDE-10750?page=com.atlassian.jira.plugi...
]
Rastislav Wagner closed JBIDE-10750.
------------------------------------
verified in jbdevstudio-product-universal-5.0.0.v201203081830M-H105-Beta1
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
4584
days inactive
4634
days old
jbosstools-issues@lists.jboss.org
9 comments
4 participants
participants (4)
-
Burr Sutter (JIRA) -
Fred Bricon (JIRA)
-
Max Rydahl Andersen (JIRA)
-
Rastislav Wagner (JIRA)