![]() |
OpenMake Meister |
The Meister Ant War Build Method includes the logic to integrate with Archiva. The following PERL Modules must be installed, Frontier::Client, Frontier::RPC2 and LWP::Simple for the Ant War Build Method to run correctly. This integration allows Archiva to be used without changing any Targets or Build Services. Targets that use Build Services: Java War, Java Weblogic War, Java War as Jar, Java War from Filter, Java Weblogic War, Java Weblogic WLI War, or Java Websphere War, will automatically place the transitive runtime dependencies into the WEB-LIB/lib folder in the war archive when Archiva interface is enabled. Any .jar or .zip listed as a dependency to the Target will be interrogated against Archiva for transitive dependencies. For example, a jar listed as a Set Classpath dependency in the Target will be queried against Archiva for transitive dependencies. Also, a jar listed as a dependency in the WEB-INF/lib option group will queried against Archiva.
To enable the Archiva integration the following environment variables must be used. These environment variables can be defined at the machine system level, Workflow level or passed in as parameters to om.
Table ARCHIVA-1 Required Meister Archiva Environment Variables
Variable |
Value |
Example |
ARCHIVA_URL |
Points to the Archiva Repository Server |
|
ARCHIVA_USERID |
Userid for Archiva |
user1 |
ARCHIVA_PASSWORD |
Password for Archiva |
Mysecret |
ARCHIVA_REPO |
Repository in Archiva to use to find an archive’s dependency tree from |
internal |
<archive-time dependency versions> |
Dependencies in the Archiva Repository may have version numbers defined as variables. This means that they must be supplied in order for the dependency tree to be resolved. For example: commons-logging.version |
commons-logging.version=1.1.2 |
NOTES
• The ARCHIVA_USERID can be Guest which will use anonymous access to Archiva.
• The ARCHIVA_REPO can be a virtual Archiva repository.
• Archive-time version numbers must be specified or an ERROR 210 will occur.