[JBoss JIRA] Commented: (JBIDE-719) Hibernate Tools should be able to use a named Eclipse provided connection
by Vitali Yemialyanchyk (JIRA)
[ http://jira.jboss.com/jira/browse/JBIDE-719?page=comments#action_12397500 ]
Vitali Yemialyanchyk commented on JBIDE-719:
--------------------------------------------
I have 2 propositions how to posible to release this issue:
we have some db definition in Data Source Explorer
1) when we create hibernate.cfg.xml - on db config page add other option to give possibility select named WTP provided database connection;
2) add context menu to tree item Data Source Explorer -> Databases -> some db -> Create hibernate.cfg.xml where user can select project/place for hibernate.cfg.xml and select if necessary "Create a console configuration"
Max, what is your vision?
> Hibernate Tools should be able to use a named Eclipse provided connection
> -------------------------------------------------------------------------
>
> Key: JBIDE-719
> URL: http://jira.jboss.com/jira/browse/JBIDE-719
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: Hibernate
> Reporter: Max Andersen
> Assigned To: Vitali Yemialyanchyk
> Priority: Optional
> Fix For: 2.1
>
> Original Estimate: 4 days
> Remaining Estimate: 4 days
>
> currently we use the settings specified in hibernate.properties/cfg.xml/persistence.xml
> Users should be able to say to use a named WTP provided database connection.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 2 months
[JBoss JIRA] Created: (JBIDE-1647) New Seam wizard creates org.eclipse.jdt.core.prefs file with Java 6 enabled
by Max Andersen (JIRA)
New Seam wizard creates org.eclipse.jdt.core.prefs file with Java 6 enabled
---------------------------------------------------------------------------
Key: JBIDE-1647
URL: http://jira.jboss.com/jira/browse/JBIDE-1647
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam
Affects Versions: 2.0.0.GA
Reporter: Max Andersen
Priority: Critical
Fix For: 2.0.1
I got a Bad version in class file error today when deploying a freshly created seam and noticed that the War project (not the test project) had Java 6 enabled for the compiler (see screenshot)
1) Why are we actually generating this file ?
2) Why is it Java 6 that is chosen ? (on second run it was actually Java 5 so it is non-deterministic)
3) If it is needed, why only on the war project and not the test projet ? (note: i ahven't tested Ear)
I've seen a couple of questions on Bad Version in Class in the forum so I guess this is not new behavior.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 2 months