Updating deps of 2.0.0.M1 to Spring 3.0.0.RELEASE?

[jetztgradnet]

Hi Costin,

I would like to use Spring DM 2.0.0.M1 from the SpringSource Milestone Maven repository (on Amazon S3). Unfortunately, the dependencies for Spring are set to 3.0.0.RC1 (which does not seem to be available there). Would it be possible, to update the POM(s) to 3.0.0.RELEASE and republish it?

Is a final Spring DM 2.0 release still planed or will it be released in the Eclipse Gemini project?

Regards,

Wolfgang

[jetztgradnet]

OK, just found http://jira.springframework.org/browse/OSGI-793 ("check compatibility with Spring 3.0"), but this is targeted at 2.0.0.M2. Is there a planned release date for M2? Would it meanwhile be possible to republish M1 with Spring 3.0 GA as dependency?

[Costin Leau]

The Spring 3.0.0.RC1 dependencies are present (they were used to compile the project). To retrieve them take a look at the EBR repository on S3 (under milestones):
http://shrub.appspot.com/repository....framework.aop/

Since these are present and M1 is just a milestone, it will not be republished. We'd like to release M2 as soon as possible but we're also tracking the updates to the blueprint spec so it's unclear at this point when the actual release will happen. Hopefully things will stabilize in the next few weeks.

2.0 GA is scheduled to be released as part of the Eclipse Gemini project.

[jetztgradnet]

Hi Costin,

The Spring 3.0.0.RC1 dependencies are present (they were used to compile the project). To retrieve them take a look at the EBR repository on S3 (under milestones):
http://shrub.appspot.com/repository....framework.aop/

ok, I only have releases from EBR enabled. But as I'm using Spring 3.0 GA in the same project, I would prefer to ignore/update Spring DM's dependency.

Since these are present and M1 is just a milestone, it will not be republished.

OK, fair enough. So I'll have to create a repo with a local copy of the Spring DM jars and patched pom.xml.

We'd like to release M2 as soon as possible but we're also tracking the updates to the blueprint spec so it's unclear at this point when the actual release will happen. Hopefully things will stabilize in the next few weeks.

2.0 GA is scheduled to be released as part of the Eclipse Gemini project.

Thanks for the update!

Regards,

Wolfgang

[jetztgradnet]

So I simply ignored all transistive dependencies. Spring DM 2.0.0.M1 works perfectly well with Spring 3.0.0.RELEASE.

[Costin Leau]

Glad to hear that - it worked fine during our tests as well.

[rherrick]

I have been unable to get this to work properly and would really appreciate some help getting it going. I've been beating my head against the wall and just can't come up with the solution...

I have the following repositories in my pom.xml:

http://repository.springsource.com/maven/bundles/release
http://repository.springsource.com/maven/bundles/external
http://repository.springsource.com/maven/bundles/milestone
http://repository.springsource.com/maven/libraries/release
http://repository.springsource.com/maven/libraries/external
http://repository.springsource.com/maven/libraries/milestone

<dependency>
	<groupId>org.springframework.osgi</groupId>
	<artifactId>org.springframework.osgi.core</artifactId>
	<version>${spring.osgi.version}</version>
</dependency>
<dependency>
	<groupId>org.springframework.osgi</groupId>
	<artifactId>org.springframework.osgi.extensions.annotation</artifactId>
	<version>${spring.osgi.version}</version>
</dependency>
<dependency>
	<groupId>org.springframework.osgi</groupId>
	<artifactId>org.springframework.osgi.test</artifactId>
	<version>${spring.osgi.version}</version>
	<scope>test</scope>
</dependency>

Lastly, I've tried setting spring.osgi.version to a couple different values:

• 2.0.0.M1 doesn't work at all, as it just can't find these three dependencies. I would have thought these would be available in the milestone EBR. What am I missing there?
• 1.2.1 resolves all of the dependencies in the pom.xml, but then I have a very simple unit test (shown below) that fails. Basically, I get a number of dependencies on 2.5.6.SEC01 libraries: org.springframework.aop-2.5.6.SEC01.jar gets downloaded and the unit test fails because org.springframework.test-2.5.6.SEC01.jar is unavailable.

public class TestOsgi extends AbstractConfigurableBundleCreatorTests
{
    @Test
    public void testSimpleLoad()
    {
        System.out.println(bundleContext);
    }
}

I guess what I'd like to do is what jetztgradnet accomplished: use Spring 3.0.0.RELEASE with Spring DM 2.0.0.M1. I'd settle for using Spring 3.0.0.RELEASE with Spring DM 1.2.1. But as you can see I can't get either to work!

I've attached the pom.xml to this post as pom.txt for reference.

I'm not at all sensitive: if I'm doing something stupid, I'm happy to be informed of that But it would be a great help if I can get this resolved.

[Costin Leau]

Rick,
Have you looked at http://www.springsource.org/osgi#repos ?
The Spring DM 2.0.0.M1 can be downloaded from maven.springframework.org/milestones:
for example: https://s3browse.springsource.com/br...ing-osgi-core/

Spring DM 1.2.1 can be found at repository.springsource.com/maven/bundles/release/ (with EBR notation):
https://s3browse.springsource.com/br...gi.core/1.2.1/

or with normal notation at Maven Central:
http://mvnrepository.com/artifact/or...sgi-core/1.2.1