Hi! I am trying to get Derby to work just like Ian Stewart - with a new Derby database for each module.
Your Spring example looks promising, sadly I have no experience with Spring (yet). Do I place to code below in the top level pom.xml? What else needed - an example with more information would be great. I don't want to use the Derby database under target in our shipped product - it's is strictly for testing. Also, we plan on setting up our Continous Integration environment so that it will run the tests on all support databases. What is the best approach for this? Does there exist a useful plugin? Do we use profiles? ...? Regards, Jimisola -- View this message in context: http://www.nabble.com/derby-maven-plugin-t1461715.html#a4855389 Sent from the Maven - Users forum at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
