...
| Code Block | ||||
|---|---|---|---|---|
| ||||
<dependency>
<groupId>org.springframework</groupId>
<artifactId>spring-web</artifactId>
<version>3.0.3.RELEASE</version>
</dependency>
|
Since
...
spring-web
...
version
...
3.0.3
...
and
...
all
...
of
...
it's
...
dependencies
...
exist
...
in
...
the
...
standard
...
maven
...
repositories,
...
then
...
we're
...
done.
...
Declaring dependencies on 3rd Party components which have their own repositories
...
Once this is done, add your dependency to pom.xml as normaldescribed in "Declaring dependencies on 3rd Party components - the easy way".
Declaring dependencies on MIT components
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
<dependency> |
...
<groupId>edu.mit.ist.es.common</groupId> |
...
<artifactId>sais-common-workflow</artifactId> |
...
<version>[0.0.0,999.999.999)</version> |
...
</dependency> |
Below is an example of aexcerpt from the sais-common pom.xml file which shos how to configure sais-common, such that applications which depend on sais-common will use snapshot builds when resolving a dependency range.
| Code Block | ||||
|---|---|---|---|---|
| ||||
...
<build>
<plugins>
<plugin>
<!-- because this component is a plugin, and because dev and ci
builds always point to the LATEST SNAPSHOT, we will configure
the maven-install-plugin to consider snapshot builds to the
local repo to be a release.
-->
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-install-plugin</artifactId>
<version>2.3.1</version>
<configuration>
<updateReleaseInfo>true</updateReleaseInfo>
</configuration>
</plugin>
...
</plugins>
...
</build>
...
|