Maven2-Repository
 |
The repository has the openArchitectureWare libraries in Version 4.2.0. Now you can use the new version.
If you use the M2 oAW-Plugin you must update the version to 1.1.0 in your POM. |
The Fornax-Platform is based on the Maven2 Buildsystem
. So we are building an own repository to administrate artifacts produced by the projects hosted on the Fornax-Platform.
Additionally to this we are provide a simple way to access the artifacts provided by the openArchitectureWare project
. This is realized with the Maven-Proxy, a tool to collect and cache artifact from the different repositories. You can access and browse the repository here
.
Structure of the Fornax M2-Repository
The Fornax M2-Repository is based on Maven-Proxy
. This tool collect and cache artifacts from different repositories. The Fornax M2-Repository uses this external repositories to collect the artifacts:
Usage of the Fornax Artifacts
The usage of the Fornax M2-Repository is very simple. You only have to add the informations about the repository into the project's pom.xml or as profile into your settings.xml. If you choose to add a profile you can decide what level you use to enable the profile. For further informations about profiles and their activitation you can refer the Maven2 documentation about profiles
.
Configuring the repository in the project's pom.xml
This is the easiest way if you want to enable only less projects with the Fornax M2-Repository. The only thing you must change is your project's pom.xml:
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http:
xmlns:xsi="http:
xsi:schemaLocation="http:>
[...]
<repositories>
<repository>
<id>fornax.repository</id>
<name>Fornax Repository</name>
<url>http: </repository>
</repositories>
<pluginRepositories>
<pluginRepository>
<id>fornax.plugin.repository</id>
<name>Fornax Plugin Repository</name>
<url>http: </pluginRepository>
</pluginRepositories>
</project>
This is all you must done. At now you can use the Fornax M2-Repository.
Configuring the repository as profile in the settings.xml
To add the configuration as profile is a very useful pattern. With a profile you can use a special configuration for a great number of projects without changing the project's pom.xml. You have 4 locations you can store a profile:
- In the project's pom.xml as profile (another way as described above)
- Per User - Defined in the Maven-settings (%USER_HOME%/.m2/settings.xml)
- Global - Defined in the global maven-settings {{(%M2_HOME%/conf/settings.xml)
- Profile Descriptor - a descriptor located in project basedir (profiles.xml)
For the profile configuration you can use this snippet:
<?xml version="1.0" encoding="iso-8859-1"?>
<settings xmlns="http:
xmlns:xsi="http:
xsi:schemaLocation="http: http:
[...]
<profiles>
[...]
<profile>
<activation>
<activeByDefault>true</activeByDefault>
</activation>
<id>fornax</id>
<pluginRepositories>
<pluginRepository>
<id>fornax.plugin.repository</id>
<name>Fornax Plugin Repository</name>
<url>
http: </url>
</pluginRepository>
</pluginRepositories>
<repositories>
<repository>
<id>fornax.repository</id>
<name>Fornax Repository</name>
<url>
http: </url>
</repository>
</repositories>
</profile>
</profiles>
</settings>
After adding this snippet to your settings you can use the Fornax M2-Repository.