I'm trying to set up a private remote repository for our team. Now the repository serves the following with so far I have tried -
When a 'mvn compile' is issued, then it searches dependencies in "~/.m2". If it is not found there then it goes to the remote private repository and when the dependencies still absent here then it goes to the central repository.
Before compilation, I have to put all dependencies in our private (and remote) repository along with checksum and metadata.
When we need an artifact(eg - spring-mvc), we need to put it in the remote private repository along with all dependencies of that artifact (spring-mvc). In this case "spring-mvc" is downloaded from our remote private repository. But the dependencies of "spring-mvc" are not downloaded from our remote private repository. They are downloaded from the central repository.
Now what I am trying to do are -
Configuring a private remote repository 'R' in such a way that I do not have to put all the dependencies to it by hand. When a "mvn compile" issued then first of all; dependencies are searched in "~/.m2" if not found then it goes to the private remote repository 'R'. If the dependencies are found in 'R' then "~/.m2" will get it from 'R'. If the dependencies are not found in 'R' then these dependencies are downloaded from the central repositories and keep the dependencies in 'R' for further uses. After that '~/.m2' will get them from 'R'. Here I do not need to put the dependencies in our remote private repository 'R' by hand.
'~/.m2' will get all dependencies of "spring-mvc" (which is the main dependency mentioned in my project's pom.xml) from the remote private repository 'R' and 'R' will get them from the respective central repository.
Can anyone suggest some way/or tutorial for reference to meet these two above targets? Thanks in advance.
EDIT : I have tried with Nathaniel Waisbrot's answer and nexus-2.7.0-06-bundle. After hours of endeavors, I am able to set it up while I am using jre-7. With jre-6, nexus cannot be started. But our project is deployed with JDK-6. We do not want to the change the current jre
version. With jre-6 apache-archiva
is OK. But I am not sure whether I can achieve all the goals in previous section. Is there any archiva
user/expert who can tell me whether I can meet these goals in the previous section?
To install your packages, you will need to configure Maven to access your Gemfury repository by adding a new repository entry in the repositories section of the pom. xml of your project with your Repository URL. Then, you can specify the specific package your application depends on, in the <dependencies> section.
Maven central repository is located at http://repo.maven.apache.org/maven2/. Whenever you run build job, maven first try to find dependency from local repository. If it is not there, then, by default, maven will trigger the download from this central repository location.
Putting non-standard repositories in the pom. xml file (which gets checked into source control) means every developer can build. But YES, your authentication for a repository server should be in your private settings. xml file.
I have setup nexus
for mirroring my maven local repository (at ~/.m2/repository.
) Since this post is still visited by a lot of people, I think it would be helpful for others if I share how I configured nexus
as a repository manager. This procedure works perfectly for me in Ubuntu 12.04
. Here it is -
1. Download nexus-2.11.1-01-bundle.tar.gz or latest version of nexus oss.
2. Extract the tar file in you home directory-
$ tar -xvf nexus-2.11.1-01-bundle.tar.gz
Now you will get two directories - nexus-2.11.1-01
and sonatype-work
in your home directory.
3. Copy these two directories to /usr/local/
directory (they can be copied to other place) -
$ cp -r nexus-2.11.1-01 /usr/local/ $ cp -r sonatype-work /usr/local/
The executable/configuration files related to nexus are stored in nexus-2.11.1-01
directory and the jar file mentioned in pom.xml
are stored in sonatype-work
directory.
These jar files are mirror of your ~/.m2/repository
. First time you issue a mvn package
command then all the jar
s are stored here. After then when you issue mvn package
again then all jars are downloaded from the nexus repository instead of downloading from the central repository.
4. Go to the /usr/local/
directory -
$ cd /usr/local/
5. Create a link to nexus-2.11.1-01
-
$ sudo ln -s nexus-2.7.0-06 nexus
6. Now to run nexus type the following in terminal -
$ bash nexus/bin/nexus console
Here nexus is attached with your console. If you close your console then the nexus server will be terminated. When you are trying to run nexus for a Ubuntu server machine then you may use screen.
Note: While trying to run nexus by using the command above there may occur 2 problems. If you do not found any problem then skip next 2 steps (step - 7 and 8)
7. First problem may occur due to insufficient permission. Read the error message and take necessary steps. But as a quick solution you may do this -
$ sudo chmod -R 777 nexus-2.11.1-01/ $ sudo chmod -R 777 sonatype-work/
8. If you are using any jdk
version lower than java 7 than the following error message may be shown -
wrapper | Launching a JVM... wrapper | JVM exited while loading the application. jvm 1 | Exception in thread "main" java.lang.UnsupportedClassVersionError: org/sonatype/nexus/bootstrap/jsw/JswLauncher : Unsupported major.minor version 51.0
In this case use jdk7 to run the command mentioned in step 6. In ubuntu its pretty easy. Assuming you have two jdk - jdk6 and jdk7. Your project runs on jdk6. Then only for running nexus you may do this from your terminal (assuming your jdk7 in /usr/lib/jvm/jdk1.7.0_45
directory) -
$ export JAVA_HOME=/usr/lib/jvm/jdk1.7.0_45 $ export PATH=$JAVA_HOME/bin:$PATH
9. Now in browser type the address - http://localhost:8081/nexus/. If step 1 to 6 (if errors occurred then step 1 to 8) are done perfectly you may successfully find the login screen. The default login user name is - admin and password is - admin123
10. Stop nexus. Just close the terminal or press Ctrl+C at step 6's terminal. In you ~/.m2
directory create an empty file named - settings.xml
. Copy the following content into this settings.xml
file -
<settings> <mirrors> <mirror> <!--This sends everything else to /public --> <id>nexus</id> <mirrorOf>*</mirrorOf> <url>http://localhost:8081/nexus/content/groups/public</url> </mirror> </mirrors> <profiles> <profile> <id>nexus</id> <!--Enable snapshots for the built in central repo to direct --> <!--all requests to nexus via the mirror --> <repositories> <repository> <id>central</id> <url>http://central</url> <releases><enabled>true</enabled></releases> <snapshots><enabled>true</enabled></snapshots> </repository> </repositories> <pluginRepositories> <pluginRepository> <id>central</id> <url>http://central</url> <releases><enabled>true</enabled></releases> <snapshots><enabled>true</enabled></snapshots> </pluginRepository> </pluginRepositories> </profile> </profiles> <activeProfiles> <!--make the profile active all the time --> <activeProfile>nexus</activeProfile> </activeProfiles> </settings>
11. And add these following lines in your project's pom.xml
file -
<distributionManagement> <snapshotRepository> <id>my-snapshots</id> <name>My internal repository</name> <url>http://localhost:8081/nexus/content/repositories/snapshots</url> </snapshotRepository> <repository> <id>my-releases</id> <name>My internal repository</name> <url>http://localhost:8081/nexus/content/repositories/releases</url> </repository> </distributionManagement>
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With