The problem seems to be within surefire. A new release 2.3.1 is being cut soon to address this issue. This is discussed in a few JIRAs: http://jira.codehaus.org/browse/MNG-3118 http://jira.codehaus.org/browse/SUREFIRE-61 http://jira.codehaus.org/browse/MNG-2365
Wayne On 12/7/07, Paul Benedict <[EMAIL PROTECTED]> wrote: > The problem might be within the SureFire plugin? Maybe it requires an update > to select the correct classpath for testing. > > Paul > > On Dec 7, 2007 2:36 PM, NicholasHall <[EMAIL PROTECTED]> wrote: > > > > > I too have had this problem since upgrading to 2.0.8. I actually > > regressed > > to 2.0.7 until I can come up with a solution. In my case, I'm using a > > different hibernate.cfg.xml file in test than in main. In main, I'm > > expecting a JNDI datasource from the container, but my test version is > > configured for HSQLDB. I noticed after upgrading to 2.0.8 that my test > > cases fail because it's trying to get the JNDI datasource. > > > > I'm hoping there's a solution in the works out there. There doesn't > > appear > > to be much noise about this. MNG-3118 appears to fix this situation, so I > > find it ironic that it wasn't a problem until now. > > -- > > View this message in context: > > http://www.nabble.com/Maven-2.0.8-test-resource-loading-tf4961073s177.html#a14220128 > > Sent from the Maven - Users mailing list archive at Nabble.com. > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
