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.

@eric. - the Maven POMs you see in the source tree exist primarily as dependency descriptors only. We publish these poms when uploading Spring Jars to our internal Maven repositories and to Maven Central, but we do not use them to build. For that, we use ant (which I thought you were doing too).

Simply run the following from the root of the source tree. It should work.

Code:

>$ ant -f build-spring-framework/build.xml jar

This will build all the jars

To install those jars in your local Maven ~/.m2/repository cache:

Code:

>$ ant -f build-spring-framework/build.xml install-maven

To run all tests:

Code:

>$ ant -f build-spring-framework/build.xml test

The point is, that if you're having trouble with the tests, you don't necessarily have to run them just to build spring locally.

. Hi Adam, Thankyou for your response. I am saying that unlike spring2.5.6 direct jar, spring 3.0.5 jar is not available.we have to build it from release.Can we have a direct jar instead of entire release to build like for spring 2.5.6

Comment

, Thankyou for your response. I am saying that unlike spring2.5.6 direct jar, spring 3.0.5 jar is not available.we have to build it from release.Can we have a direct jar instead of entire release to build like for spring 2.5.6

Hi ksalic,

I'm not quite sure that I understand your request. What do you mean by "direct jar"? You do not have to build Spring from source for any released version. The complete compiled jar file is available from the community download center, specifically the Spring 3.0.5 release is there.

If you are referring to the old Spring-with-dependencies versions that we previously made available then that is a different matter. We have stopped releasing those because of the prevalence of common build systems like Maven that help you add only the libraries you need to your project. If you are not familiar with Maven then I recommend reading the Green Beans post: Getting Started with Maven and Spring.

If you continue to have problems or are not able to see the files I have identified in the links above, please post your OS and browser version details here so that we can see if there is a problem with your environment.

Comment

@eric. - the Maven POMs you see in the source tree exist primarily as dependency descriptors only. We publish these poms when uploading Spring Jars to our internal Maven repositories and to Maven Central, but we do not use them to build. For that, we use ant (which I thought you were doing too).

Simply run the following from the root of the source tree. It should work.

Code:

>$ ant -f build-spring-framework/build.xml jar

This will build all the jars

To install those jars in your local Maven ~/.m2/repository cache:

Code:

>$ ant -f build-spring-framework/build.xml install-maven

To run all tests:

Code:

>$ ant -f build-spring-framework/build.xml test

The point is, that if you're having trouble with the tests, you don't necessarily have to run them just to build spring locally.

@Chris Beams,

Thank you for your reply.

These commands do work. But I still have questions might be bothering ( sorry for that ): How can I trust them if their tests fail? How can I develop over them if I can't make the tests run?

Anyway, would you mind to give a trustful version which all tests run successfully (older version is ok) ? Thanks in advance.

Comment

The Maven POMs are not supported for building the framework. These exist only for the purpose of maintaining Maven metadata for *consuming* Spring framework artifacts, as opposed to building them. The best approach is simply to use the ant build which all the core developers use on a daily basis. This has been documented here: https://github.com/cbeams/spring-framework/wiki

Comment

Understood. Please file a bug for this. The team builds against OS X, Ubuntu and Windows every day, and this test isn't failing for any of us, so this suggests it's something local on your machine. Nevertheless, it'll be good to figure out.