[#APF-584] Provide DB specific build profiles in the archetypes - AppFuse JIRA

AppFuse

Provide DB specific build profiles in the archetypes

Created: 20/Jan/07 11:49 AM Updated: 16/Feb/07 02:18 AM Resolved: 16/Feb/07 02:18 AM

Component/s:

Installation

Affects Version/s:

2.0-M2

Fix Version/s:

2.0-M4

Description

« Hide

If a user wants to use a database other than MySql, quite a few properties in the pom.xml need to be changed. In certain cases, e.g. MS SQL, changes also need to be made to other areas of the pom - the dbunit process also needs to change. By including a set of database specific profiles, we could cut down on the number of changes that users need to make to the poms to switch databases.

One disadvantage, of course, is that the pom could become rather lengthy.

Sort Order:

[ Permalink | « Hide ]

Matt Raible added a comment - 22/Jan/07 03:48 PM

There are profiles in the root pom.xml for embedded databases - but none of them work. Feel free to add ones for SQL Server and Oracle. The only problem currently is that iBATIS has MySQL statements hard-coded in its mapping files, so tests fail for other databases.

[ Permalink | « Hide ]

Matt Raible added a comment - 13/Feb/07 05:20 PM

Mike - if you can post the changes needed for MS SQL, I can try to make this change. Having Oracle and DB2 profiles would probably be good too. We already have one for PostgreSQL.

[ Permalink | « Hide ]

Matt Raible added a comment - 14/Feb/07 04:03 AM

Couldn't get Oracle Express nor Derby Embedded to work:

http://www.nabble.com/AppFuse-2.0-with-Oracle-Express-tf3225784s2369.htm
http://www.nabble.com/Issues-trying-to-use-Embedded-Derby-with-hibernate3-and-dbunit-tf3226221.html

[ Permalink | « Hide ]

Matt Raible added a comment - 16/Feb/07 02:18 AM

Fixed Oracle Express and Derby (only works in Networked mode). Not worrying about DB2 until there's one JAR for the JDBC Driver.