Page History

...

<dependency>
    <groupId>org.springframework</groupId>
    <artifactId>spring-web</artifactId>
    <version>3.0.3.RELEASE</version>
Since spring-web version 3.0.3 and all of it's dependencies exist in the standard maven repositories, then we're done.
</dependency>

Declaring dependencies on 3rd Party components which have their own repositories

It is possible to add repositories directly to your pom.xml. However, it is preferable to have a MIT Maven Repository Admin mirror the 3rd party repository. This will make the component available to all projects, while also decreasing network loads. (For the SAIS teams, the mirror configured in the MIT Maven Repository should be visible to the "saisGroupRepo" repository. See your network admin for details.)

Declaring dependencies on 3rd Party components which do not have a maven distribution available.

Sometimes the 3rd party components we wish to use will not exist in the standard Maven repositories. This may be because they are closed source, or because the vendor has their own repository. In this case, you will potentially need to perform the following tasks

1. make up a group id (usually com.whateverthevendornameis) and artifactid (e.g my3rdpartycomponent)

2. Wiki Markup
   rename the jar file to \[artifactid]-\[version].jar

3. Wiki Markup
   create a jar file containing the source files, if available, and call it \[artifactid]-\[version]-sources.jar. This step is optional but STRONGLY recommended.

4. create a pom file (pom.xml) with the correct groupId and artifactId. This file should also contain any dependencies to jar files used by the component. If these components are in the standard maven repositories, use those dependencies. Otherwise repeat this process for each dependent component.

5. Wiki Markup
   provide your MIT Maven Repository Admin with the pom.xml, \[artifactid]-\[version].jar and optional \[artifactid]-\[version]-sources.jar and request they add that to the appropriate MIT Maven Repository for your group.

In these cases it is preferred to store the binary file (usually .jar), a corresponding source jar, and a pom.xml file that contains dependencies in the MIT Maven Repository (https://maven-mit-edu.ezproxyberklee.flo.org). See your MIT maven admin for access and repository rules. It is possible to also declare 3rd party repositories in your pom.xml, which is NOT a desirable solution. Finally it is possible to request the

Declaring dependencies on MIT components

...