We've finally worked this down to some repeatable steps, so now I bring my confusion to the list. :-) Our problem is around getting the Oracle ojdbc driver to load.
Scenario 1: include ojdbc bundle in list.xml or in pom.xml in "additionalBundles" of launchpad plugin. We have a launchpad project[1] that works great. When this project has had the ojdbc bundle added to it, be it in the pom or list.xml, everything loads correctly and is able to talk to Oracle just fine. I can also load the ojdbc bundle without error if I don't include it in the build but add it manually through the admin console. Scenario 2: include ojdbc bundle "additionalBundles" of child launchpad project. Our second launchpad project[2], uses #1 as the parent pom and to get its defaultBundleList. Whenever the ojdbc bundle is included in this pom, the following exception is displayed in the logs: Caused by: java.lang.ClassNotFoundException: *** Class 'oracle.jdbc.driver.OracleDriver' was not found, but this is likely normal since package 'oracle.jdbc.driver' is dynamically imported by bundle org.apache.sling.jcr.jackrabbit.server [26]. However, bundle org.sakaiproject.nakamura.ojdbc [117] does export this package with attributes that do not match. *** #2 uses the exact same ojdbc bundle as #1. I've also checked that the file list of the resulting launchpad artifact match (same bundle name, start level, same jars in the same folders in the build artifact). Any suggestions of where to go with this? 1 http://github.com/thecarlhall/open-experiments/tree/ojdbc_pom_fix/app 2 http://github.com/thecarlhall/open-experiments/blob/ojdbc_pom_fix/contrib/nyu/pom.xml
