getting oracle builds?

Ian Springer ian.springer at redhat.com
Tue Apr 24 21:18:29 UTC 2012


Make sure you're setting the rhq.dev.ds.* props in your oracle profile - 
those are the ones that are used by the dev-container. Here's what my 
oracle profile looks like:

<profile>
<id>oracle</id>
<properties>
<rhq.test.ds.connection-url>jdbc:oracle:thin:@127.0.0.1:1521:orcl</rhq.test.ds.connection-url>
<rhq.test.ds.user-name>rhq</rhq.test.ds.user-name>
<rhq.test.ds.password>rhq</rhq.test.ds.password>
<rhq.test.ds.type-mapping>Oracle10g</rhq.test.ds.type-mapping>
<rhq.test.ds.driver-class>oracle.jdbc.driver.OracleDriver</rhq.test.ds.driver-class>
<rhq.test.ds.xa-datasource-class>oracle.jdbc.xa.client.OracleXADataSource</rhq.test.ds.xa-datasource-class>
<rhq.test.ds.server-name></rhq.test.ds.server-name> <!-- can be left 
blank, oracle does not use this -->
<rhq.test.ds.port></rhq.test.ds.port> <!-- can be left blank, oracle 
does not use this -->
<rhq.test.ds.db-name></rhq.test.ds.db-name> <!-- can be left blank, 
oracle does not use this -->
<rhq.test.ds.hibernate-dialect>org.hibernate.dialect.Oracle10gDialect</rhq.test.ds.hibernate-dialect>
<!-- quartz properties -->
<rhq.test.quartz.driverDelegateClass>org.quartz.impl.jdbcjobstore.oracle.OracleDelegate</rhq.test.quartz.driverDelegateClass>
<rhq.test.quartz.selectWithLockSQL>SELECT * FROM {0}LOCKS ROWLOCK WHERE 
LOCK_NAME = ? FOR UPDATE</rhq.test.quartz.selectWithLockSQL>
<rhq.test.quartz.lockHandlerClass>org.quartz.impl.jdbcjobstore.StdRowLockSemaphore</rhq.test.quartz.lockHandlerClass>

<rhq.dev.ds.connection-url>jdbc:oracle:thin:@127.0.0.1:1521:orcl</rhq.dev.ds.connection-url>
<rhq.dev.ds.user-name>rhq</rhq.dev.ds.user-name>
<rhq.dev.ds.password>rhq</rhq.dev.ds.password>
<rhq.dev.ds.type-mapping>Oracle10g</rhq.dev.ds.type-mapping>
<rhq.dev.ds.driver-class>oracle.jdbc.driver.OracleDriver</rhq.dev.ds.driver-class>
<rhq.dev.ds.xa-datasource-class>oracle.jdbc.xa.client.OracleXADataSource</rhq.dev.ds.xa-datasource-class>
<rhq.dev.ds.server-name></rhq.dev.ds.server-name> <!-- can be left 
blank, oracle does not use this -->
<rhq.dev.ds.port></rhq.dev.ds.port> <!-- can be left blank, oracle does 
not use this -->
<rhq.dev.ds.db-name></rhq.dev.ds.db-name> <!-- can be left blank, oracle 
does not use this -->
<rhq.dev.ds.hibernate-dialect>org.hibernate.dialect.Oracle10gDialect</rhq.dev.ds.hibernate-dialect>
<!-- quartz properties -->
<rhq.dev.quartz.driverDelegateClass>org.quartz.impl.jdbcjobstore.oracle.OracleDelegate</rhq.dev.quartz.driverDelegateClass>
<rhq.dev.quartz.selectWithLockSQL>SELECT * FROM {0}LOCKS ROWLOCK WHERE 
LOCK_NAME = ? FOR UPDATE</rhq.dev.quartz.selectWithLockSQL>
<rhq.dev.quartz.lockHandlerClass>org.quartz.impl.jdbcjobstore.StdRowLockSemaphore</rhq.dev.quartz.lockHandlerClass>

<rhq.db.admin.username>rhq</rhq.db.admin.username>
<rhq.db.admin.password>rhq</rhq.db.admin.password>
</properties>
</profile>


Also, if you're switching your dev-container from postgres to oracle, I 
think you'll need to do a clean build of the container:

cd modules/enterprise/server/container
mvn clean install

On 04/24/2012 04:34 PM, John Mazzitelli wrote:
> I thought this used to work (its the whole reason we added those two sets of database settings in our settings.xml), but I can't get oracle builds to work. I have a profile "oracle" and I turn it on in my mvn build via -Poracle. I know this works because if I build core/dbutils with -Poracle -Ddbsetup, my oracle DB is properly setup.
>
> But when I build the container (enterprise/server/container) it still builds with postgres (e.g. rhq-server.properties has all my postgres settings, plus the datasources are postgres).
>
> Did something break or am I not building properly?
> _______________________________________________
> rhq-devel mailing list
> rhq-devel at lists.fedorahosted.org
> https://fedorahosted.org/mailman/listinfo/rhq-devel


-- 
Ian Springer
Principal Software Developer
JBoss Operations Network
Red Hat
ian.springer at redhat.com



More information about the rhq-devel mailing list