-
Notifications
You must be signed in to change notification settings - Fork 10
technologyMaven
http://metalcon2.physik.uni-mainz.de:8080/mvn/
There are parental POM Metalcon projects inherit from:
- root POM: https://github.com/Metalcon/pom
- for Tomcat projects: https://github.com/Metalcon/tomcatPom
- (de.metalcon.utils) utils-meta-database [1.0.2]
- (de.metalcon.utils) utils-form-item-list [1.0.2]
At first you have to set a master password for Maven if not set yet.
mvn --encrypt-master-password <**master-password**>
This returns a String such as {123...}
.
Add this to your Maven security settings file .m2/settings-security.xml
<settingsSecurity>
<master>**{123...}**</master>
</settingsSecurity>
Now you need to encrypt the password for the SSH account of the Metalcon server with your master password by running
mvn --encrypt-password <**password**>
This returns again a String such as {456...}
.
Finally you need to add the Metalcon deployment server to your Maven settings file .m2/settings.xml
:
...
<servers>
...
<server>
<id>metalcon-deploy</id>
<username>metalcon</username>
<password>**{456...}**</password>
</server>
...
</servers>
...
You can now deploy to the server using
mvn clean install source:jar javadoc:jar deploy
Projects depending at artifacts hosted in the Metalcon repository will be automatically resolved if you use the parental Metalcon POM.
As the deploying to the Maven Central Repository via Nexus Sonatype does not work as supposed to, we will use an own Maven repository hosted by our server.
There will be no synchronization delay and no user ticket issues which are quite an improvement to Sonatype.
There is no additional software required to host a Maven repository except an SSH server supporting SCP.
All users deploying to the server will need to set server IP and the password of the default SSH account in their Maven settings file.
These directories have to be set in each pom file of the projects depending on the hosted artifacts.