...
To use the jasig-parent project add the following to the top of your pom.xml:
| Code Block |
|---|
|
<parent>
<groupId>org.jasig.parent</groupId>
<artifactId>jasig-parent</artifactId>
<version>30<<version>34</version>
</parent>
|
Configure your POM's SCM element:
| Code Block |
|---|
|
<scm>
<connection>scm:svn:https://source.jasig.org/MyProject/trunk</connection>
<developerConnection>scm:svn:https://source.jasig.org/MyProject/trunk</developerConnection>
<url>https://developer.jasig.org/source/browse/jasigsvn/MyProject/trunk</url>
</scm>
|
If your project generates a Maven site use the following distributionManagement configuration and add the profile below.
| Code Block |
|---|
|
<distributionManagement>
<site>
<id>developer.jasig</id>
<url>${jasig-site-dist-base}${project-site-path}</url>
</site>
</distributionManagement>
|
| Code Block |
|---|
|
<profile>
<id>ci-local-site</id>
<distributionManagement>
<site>
<id>ci-local-site</id>
<url>${jasig-site-ci-dist-base}${project-site-path}</url>
</site>
</distributionManagement>
</profile>
|
...
To ease running the deploy goals the ~/.m2/settings.xml file should be edited and configured for authentication with the Sonatype repository. If you need an account to publish Maven artifacts for your Jasig project please ask the steering committee appropriate for your project.
| Code Block |
|---|
|
<settings>
<servers>
<server>
<id>sonatype-nexus-snapshots</id>
<username>username</username>
<password>password</password>
</server>
<server>
<id>sonatype-nexus-staging</id>
<username>username</username>
<password>password</password>
</server>
</servers>
</settings>
|
...