How to build WAR file from custom nexus repository?

[Mike London]

We are switching our version of Spring to the latest release. Because our current nexus repository is for the current Spring version, I created a custom nexus repository for the new Spring framework jars.

My question is how do I get Maven to build from that custom repository using the "mvn -e -" command?

In a directory in nexus called: "newspringversion", I have the Spring 4.0.1 jars.

Really not sure what the "mvn -e -" command should look like so Maven will pull the Spring Framework jars from the custom repository instead of the regular one.

Any help would be appreciated.

Thanks.

-mike

[Saif Asif]

Hello Mike,

We are switching our version of Spring to the latest release. Because our current nexus repository is for the current Spring version, I created a custom nexus repository for the new Spring framework jars.

What is the purpose of making a completely new nexus repository? If you just want to make use of some other jars version, simply refer to them from your existing nexus repo, why make a new one ? Keep the new ones along with the old ones and refer to any version that is required

[Tim Holloway]

It is a fundamental premise in Maven that for a given group, artifact and version ID, the component you obtain should be 100% identical with any other component having those attributes no matter where on the planet you obtain it from.

A separate repository isn't really necessary from Maven's point of view. Just a separate artifact ID.

However, if your problem is because your projects have been referencing third-party (Spring) jars by sloppy ID's ("just give me the latest version"), then you are beginning to see why Maven makes such a big deal of including actual version numbers in dependencies. If you do that, then bringing new Spring jars online won't break old projects.