Spring Integration 1.0.0.M4 released

[magnusheino]

Nico,

As of M4, Spring Integration is using the SpringSource Enterprise Bundle Repository. See the FAQ for the necessary ivy and maven configuration for the repository: http://www.springsource.com/repository/app/faq#q7

How is this supposed to work in practice??

Are you saying that spring integration will never appear at repo1?

Also, the pom is useless if you use more repos than the spring repo. I do not want com.springsource artifacts.

Please reconsider this. I don't want to depend on any jars other than the official jars for a project.

/Magnus

[mikaelhg]

This works for me with Maven. Remove the spaces after the protocol parts of the repository URLs.

  <repositories>
    <repository>
      <id>com.springsource.repository.bundles.milestone</id>
      <url>http ://repository.springsource.com/maven/bundles/milestone</url>
    </repository>
    <repository>
      <id>com.springsource.repository.bundles.release</id>
      <url>http ://repository.springsource.com/maven/bundles/release</url>
    </repository>
    <repository>
      <id>com.springsource.repository.bundles.external</id>
      <url>http ://repository.springsource.com/maven/bundles/external</url>
    </repository> 
  </repositories>

  <dependencies>
    <dependency>
      <groupId>org.springframework.integration</groupId>
      <artifactId>org.springframework.integration</artifactId>
      <version>1.0.0.M4</version>
    </dependency>
  </dependencies>

[magnusheino]

This works for me with Maven. Remove the spaces after the protocol parts of the repository URLs.

Sure, but you get lots of com.springsource artifacts. It's impossible to mix the springsource repo with repo1. Which is great if you are using the springsource platform, but not so great otherwise.

It's easy to create a new pom and upload it to repo1. But I don't see this happening for any other spring portfolio project and think this is a huge mistake.

/Magnus

[ryandaum]

Hi Mark,

When integration goes final, does SpringSource plan on publishing artifacts to the central Maven repo that use the traditional Maven groupIds and artifactIds for the dependencies? As it is now, these bundle repositories are unusable for our project because they mandate the use of new artifacts which are not harmonious with the rest of our (much larger) build.