This forum is now a read-only archive. All commenting, posting, registration services have been turned off. Those needing community support and/or wanting to ask questions should refer to the Tag/Forum map, and to http://spring.io/questions for a curated list of stackoverflow tags that Pivotal engineers, and the community, monitor.

I tried downloading the latest 2.2.6, but I'm getting these errors:
An error occurred while collecting items to be installed
No repository found containing: com.springsource.org.aspectj.runtime/osgi.bundle/1.6.3.RELEASE
No repository found containing: com.springsource.org.aspectj.weaver/osgi.bundle/1.6.3.RELEASE
No repository found containing: org.springframework.context.support/osgi.bundle/3.0.0.SNAPSHOT
No repository found containing: org.springframework.ide.eclipse/osgi.bundle/2.2.6.200908051215-RELEASE
No repository found containing: org.springframework.ide.eclipse.beans.core/osgi.bundle/2.2.6.200908051215-RELEASE
No repository found containing: org.springframework.ide.eclipse.beans.ui/osgi.bundle/2.2.6.200908051215-RELEASE
No repository found containing: org.springframework.ide.eclipse.beans.ui.editor/osgi.bundle/2.2.6.200908051215-RELEASE
No repository found containing: org.springframework.ide.eclipse.beans.ui.graph/osgi.bundle/2.2.6.200908051215-RELEASE
No repository found containing: org.springframework.ide.eclipse.beans.ui.refactori ng/osgi.bundle/2.2.6.200908051215-RELEASE
No repository found containing: org.springframework.ide.eclipse.beans.ui.search/osgi.bundle/2.2.6.200908051215-RELEASE
No repository found containing: org.springframework.ide.eclipse.core/osgi.bundle/2.2.6.200908051215-RELEASE
No repository found containing: org.springframework.ide.eclipse.doc/osgi.bundle/2.2.5.200908051215-RELEASE
No repository found containing: org.springframework.ide.eclipse.feature/org.eclipse.update.feature/2.2.6.200908051215-RELEASE
No repository found containing: org.springframework.ide.eclipse.ui/osgi.bundle/2.2.6.200908051215-RELEASE
No repository found containing: org.springframework.jms/osgi.bundle/3.0.0.SNAPSHOT
No repository found containing: com.springsource.javax.xml.stream/osgi.bundle/1.0.1
No repository found containing: com.springsource.org.antlr/osgi.bundle/3.0.1
No repository found containing: org.springframework.osgi.core/osgi.bundle/2.0.0.M1
No repository found containing: org.springframework.osgi.io/osgi.bundle/2.0.0.M1

Spring IDE ships the Spring 3.0 XSDs and maps the version-less schemalocation to the 3.0 XSDs which is causing the validation of your XML files to fail. I recommend you specify the concrete version as otherwise your XML files will not work when upgrading to Spring 3.0.

Spring IDE ships the Spring 3.0 XSDs and maps the version-less schemalocation to the 3.0 XSDs which is causing the validation of your XML files to fail. I recommend you specify the concrete version as otherwise your XML files will not work when upgrading to Spring 3.0.

HTH

Christian

I'm sorry to hear that. It seems to run contrary to the "backward compatibility" we've come to expect from new Spring releases. Did I miss a warning in 2.5 that this would be removed?

I'm sorry to hear that. It seems to run contrary to the "backward compatibility" we've come to expect from new Spring releases. Did I miss a warning in 2.5 that this would be removed?

No, you didn't miss a warning. Deprecation of xsd features is not as convenient as it is for Java code. The removal of the "default-dependency-check" in the 3.0 xsd IS the "deprecation". You can still use the 2.5 xsd by specifying the version and it will all work since the attribute is still supported in the 3.0 code, just not present in 3.0 xsd anymore.

You're better off always specifying the version for the xsd you are using.

Comment

What should be used instead of default-dependency-check and dependency-check ?
The current documentation: http://static.springsource.org/sprin...y-dependencies
uses the following (quote):
"In XML-based configuration metadata, you specify dependency checking via the dependency-check attribute in a bean definition, which can have the following values."

Comment

BTW, major (first-digit change) releases typically does not guarantee 100% backward compatibility, here is more or less standard convention for release numbering (established by Apache Portable Runtime and followed by many projects around the world)

Versions are denoted using a standard triplet of integers: MAJOR.MINOR.PATCH. The basic intent is that MAJOR versions are incompatible, large-scale upgrades of the API. MINOR versions retain source and binary compatibility with older minor versions, and changes in the PATCH level are perfectly compatible, forwards and backwards.

Comment

What should be used instead of default-dependency-check and dependency-check ?
The current documentation: http://static.springsource.org/sprin...y-dependencies
uses the following (quote):
"In XML-based configuration metadata, you specify dependency checking via the dependency-check attribute in a bean definition, which can have the following values."

Comment

I was wondering if the @Required annotation can be used together with constructor injection? Also what about the documentation:http://static.springsource.org/sprin...y-dependencies
Is this an error in the documentation (quote): In XML-based configuration metadata, you specify dependency checking via the dependency-check attribute in a bean definition, which can have the following values...