aopalliance com.springsource vs com.springframework

[sarbx]

I have been using 1.1.0-m2 drop so far and everything is working fine. But I switched to 1.1.0-rc1-SNAPSHOT, I started getting the following errors, It looks like the rc1-SNAPSHOT started referring to com.springsource.org.aopalliance instead of org.springframework.osgi.aopalliance.osgi somewhere in the Spring DM tesing framework.

Is this intended?

-------------------------------------------------------------------------------
Test set: net.nextplane.services.test.BeanOsgiIntegrationTes t
-------------------------------------------------------------------------------
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 3.987 sec <<< FAILURE!
testOsgiBundleContext(net.nextplane.services.test. BeanOsgiIntegrationTest) Time elapsed: 3.549 sec <<< ERROR!
java.io.FileNotFoundException: C:\Documents and Settings\sbellan\.m2\repository\org\aopalliance\co m.springsource.org.aopalliance\1.0.0\com.springsou rce.org.aopalliance-1.0.0.jar (The system cannot find the path specified)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(FileInputStream.java:106)
at org.springframework.core.io.FileSystemResource.get InputStream(FileSystemResource.java:108)
at org.springframework.osgi.test.AbstractOsgiTests.in stallBundle(AbstractOsgiTests.java:323)
at org.springframework.osgi.test.AbstractOsgiTests.st artup(AbstractOsgiTests.java:253)
at org.springframework.osgi.test.AbstractOsgiTests.pr epareTestExecution(AbstractOsgiTests.java:374)
at org.springframework.osgi.test.AbstractOsgiTests.ru nBare(AbstractOsgiTests.java:203)
at org.springframework.osgi.test.AbstractOsgiTests$1. protect(AbstractOsgiTests.java:184)
at junit.framework.TestResult.runProtected(TestResult .java:124)
at org.springframework.osgi.test.AbstractOsgiTests.ru n(AbstractOsgiTests.java:181)

[Marten Deinum]

Yes it is intended.

All the new versions will be using the BRITS stuff instead of maintaining our own subset of dependencies.

[Costin Leau]

The BRITS dependencies should be automatically downloaded (the poms and eclipse classpath files have been updated as well). If this is not the case, please raise an issue so we can track down the problem and fix it.

Thanks,