[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-4355?page=c...
]
Hardy Ferentschik resolved HHH-4355.
------------------------------------
Resolution: Fixed
Fix Version/s: 3.5
Since switching to maven and using filtering for the properties files it was able to use
maven profiles to switch the database to run against.
Now after integrating Annotations and EntityManager back into Hibenrate Core we even have
a unified profile handling for all modules
Allow running tests against different databases by using a simple
switch
------------------------------------------------------------------------
Key: HHH-4355
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-4355
Project: Hibernate Core
Issue Type: Task
Reporter: Hardy Ferentschik
Assignee: Hardy Ferentschik
Priority: Minor
Fix For: 3.5
Currently you have to edit hibernate.properties to be able to run the tests against a
different database. The settings of this file should be externalized and filters should be
used to filter appropriate settings according to a property, eg 'ant clean junit
-Dtargetdb=mysql'.
To make this really useful one would also need a way within the test to skip it for a
particular database. Some tests don't make sense against a certain target db. This
might be a separate issue. Maybe one could switch to Junit 4 and add some custom
annotation for enabling/disabling a test depending on the db.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira