Which spring version to use? 2.5.6 or 2.5.6.A?

[craigching]

I've seen a few different projects answer this question as 2.5.6.A, but I note that the code for the spring-osgi project uses 2.5.6. Can anyone provide guidance on what I should be using if I'm going to be using the next release of Spring DM 1.2.0? And what is the difference between 2.5.6 and 2.5.6.A? A quick look at the manifests makes me think they're pretty much identical.

[craigching]

Well, a search showed this:

http://forum.springsource.org/showth...hlight=2.5.6.A

But I guess I still don't know what the answer is. It appears from everything I'm reading that the groupId and artifactId are moving to the form:

    <dependency>
      <groupId>org.springframework</groupId>
      <artifactId>org.springframework.core</artifactId>
      <version>2.5.6.A</version>
    </dependency>

But that the spring-osgi trunk still uses:

        <dependency>
          <groupId>org.springframework</groupId>
          <artifactId>spring-core</artifactId>
          <version>${spring.maven.artifact.version}</version>
        </dependency>

Where ${spring.maven.artifact.version} is 2.5.6. So which should I use? Or is it going to be different depending on which repository you use (Apache vs. Spring)? I'd prefer that they be the same personally

[Costin Leau]

We're aware that the difference in naming causes a lot of unneeded problems and we're trying to sort this out. In the upcoming Spring DM 1.2 release we're using the Spring 3.0 naming conventions which are currently used in SpringSource Enterprise Bundle Repository (EBR).
In fact, it would be great if you could use the upcoming Spring DM nightly build.

[craigching]

Sure, I'm currently using:

    <dependency>
      <groupId>org.springframework</groupId>
      <artifactId>org.springframework.core</artifactId>
      <version>2.5.6.A</version>
    </dependency>

And I think that's the new format. I'll give the nightly a try then.

[Costin Leau]

I've started the nightly build which should be ready in about 20 minutes : http://build.springframework.org/browse/OSGI-NIGHTLY

[craigching]

I'm probably being dense, but I have never used bamboo before and I'm not seeing where to download the nightly artifacts. Or maybe they're in a maven repo somewhere? In any case, I'm going to build from source, hopefully that will allow me to test what you want me to.

[Costin Leau]

You can download the artifacts from our S3 snapshot repo: http://www.springsource.org/osgi#repos
I gave the link to Bamboo as I wasn't sure if (and when) the build will complete. I'll see whether there is an integration between Bamboo and S3 so the artifacts can be downloaded directly from the build server.

Cheers,

[craigching]

Ok, I'll give that a try. Just a heads up, I pulled trunk and tried to do a build (mvn -P equinox,samples clean install) and am getting some integration test failures:

Failed tests:
  testHtmlPage(org.springframework.osgi.samples.simplewebapp.OsgiHttpIntegrationTest)
  testHelloServlet(org.springframework.osgi.samples.simplewebapp.OsgiHttpIntegrationTest)
  testResourceServlet(org.springframework.osgi.samples.simplewebapp.OsgiHttpIntegrationTest)
  testJSP(org.springframework.osgi.samples.simplewebapp.OsgiHttpIntegrationTest)

[craigching]

Ugh, never mind, that was me. Note to self, don't build Spring DM when you have your own test running on port 8080

[Costin Leau]

That tends to happen to me from time to time as well (even on the build server). I wanted to move the port but then we ran into some issues with various firewalls - 8080 is more or less standard and doesn't require any extra configuration so we just let it be.
Anyway Craig, feedback is always welcome so if something goes wrong or doesn't work as expected (i.e. the paths in Eclipse are wrong or there is a missing dependency), fire away.