Seems like all urls I'm finding are down.
Grateful for help.
Printable View
Seems like all urls I'm finding are down.
Grateful for help.
The 'snapshot' and 'milestone' repositories should be available as described in this blog post: http://blog.springsource.com/main/20...en-artifacts-2
You can browse the contents also...
milestone:
http://s3browse.com/explore/maven.sp...k/integration/
snapshot: http://s3browse.com/explore/maven.sp...k/integration/
-Mark
Three issues with "m3" or "M3" release.Quote:
Originally Posted by Mark Fisher
1. The convention is different. It used to be "m1" and "m2" and now it is named "M3" with the capital "M".
2. The groupId of the dependencies on "commons-net" and "oro" are wrong.
<dependency>
<groupId>org.apache.commons</groupId>
<artifactId>commons-net</artifactId>
<version>1.4.1</version>
<scope>compile</scope>
</dependency>
<dependency>
<groupId>org.apache.oro</groupId>
<artifactId>oro</artifactId>
<version>2.0.8</version>
<scope>compile</scope>
</dependency>
Please fix at least the "groupId" dependencies on these two jar files.
Thanks!
--Scott Hong
The Spring Integration project uses an ANT and Ivy based build system that resolves dependencies from a private repository. In this repository we've used a consistent set of naming conventions (that meet Maven standards) rather than the inconsistent central repo conventions. We realize that this leads to problems when using the existing Maven POMs and are working towards a longer-term solution. In the short-term, there are two options:
1) install the artifacts into your local maven repository as described here: http://maven.apache.org/guides/mini/...ars-local.html
2) modify the pom
Since only 3 dependencies are affected, and their versions will change very rarely if at all - either option should be fine as a short term solution.
Regards,
Mark
Mark,
Thanks for the response.
The point I want to emphasize is that it might be better off with what available in the public "apache" central repository where most of the "pom"s are depending on. Any project depending on either "commons-net" or "oro" will have to deal with the dependencies manually. I tried to "exclude" the dependency of the spring-integration-adaptor on "commons-net" and "oro" and add dependency on the available repository and it seems not working for me. Adding the dependencies to local repository can solve the problem but when you need to work on multiple machines without a private central repository, then it becomes a problem. After all, this is just a milestone release, why do you want to force these interested in "spring-integration" to deal with these problems!
Thanks!
--Scott Hong