AmirHossein Sojoodi

AmirHossein Sojoodi

PhD student in Computer Engineering at Queen's University

Setup Nexus Repository Manager

Published:
6 minute read

Install Nexus Repository Manager

Get all the files and edit the config.sh files. I’m sure you are smart enough to use the script! Edit the variables and follow the instructions. You can execute script commands seperately on your own.

Upgrading

  • Become familiar with the basic directory structure of a Nexus Repository Manager installation. You are encouraged to stick with the standard installation layout to make future upgrades as simple as possible.

You will have to determine your existing installation data directory location. Record this value for later use.

Download the Latest Installer Archive

Download the latest installer archive for your platform from the official downloads. Extract the newest downloaded distribution archive using the standard approach.

Preparing the new Install

Suppose 3.14.0-04 is the new version.

  • Move the downloaded zip to your desired directory. (Basic place is /usr/local)
sudo cp nexus-3.14.0-04-unix.tar.gz /usr/local
sudo tar xzvf nexus-3.14.0-01-unix.tar.gz

  • Compare the nexus-3.14.0-04/bin/nexus.vmoptions file with your existing version.

  • If you have changed the default location of the Data Directory, then edit ./bin/nexus.vmoptions and change the line -Dkaraf.data=../sonatype-work/nexus3 to point to your existing data directory. Example: -Dkaraf.data=/app/nexus3/data

  • If you changed the default location of the temporary directory, then edit ./bin/nexus.vmoptions and replace the line -Djava.io.tmpdir=../sonatype-work/nexus3/tmp to point to your preferred temporary directory.

  • If you adjusted the default Java virtual machine max heap memory, then edit ./bin/nexus.vmoptions and edit the line -Xmx1200M accordingly.

  • If you have enabled jetty HTTPS access, make sure your etc/jetty/jetty-https.xml SSL keystore location is still available to the new install.

  • If you manually adjusted any other install files under ./etc you will need to manually perform a diff between the old files and the new files and apply your changes if applicable to the new version.

  • Perform the Upgrade.

  • Ensure you have taken recent backups of the existing Data Directory and any custom blobstore locations according to our recommended practices. Because of involved Upgrade steps, downgrading a NXRM version is not supported and will almost always result in failures.If you have issues, restore from this backup instead.

  • Stop your existing install using the scripts under ./bin or your operating system service. Make sure it stops completely.

sudo service nexus stop
./nexus/bin/nexus stop
  • Change owner of the new directory to the your desired user:
sudo chown user:user nexus-3.14.0-04/ -R
  • Remove previous soft links and create new one and update permissions of it:
sudo rm nexus
sudo ln -s /usr/local/nexus-3.14.0-04 /usr/local/nexus
sudo chown user:user nexus -R
  • If you have configure Nexus Service, update the service as well:
sudo update-rc.d nexus defaults
  • Update user in the file /usr/local/nexus/bin/nexus.rc
run\_as\_user="user"
  • Start the new installation using the scripts under ./bin or adjust your operating system service to use these scripts.
./nexus start
sudo service nexus start
  • Review the log files for any possible issues and sign-in to the server to confirm things are working as expected.

Resources

  1. changeRepo script:
#!/bin/bash

if [ -f ~/.m2/settings.xml ]
then
  if [ -f ~/.m2/settings.xml.orig ]
  then
    mv ~/.m2/settings.xml ~/.m2/settings.xml.tmp
    mv ~/.m2/settings.xml.orig ~/.m2/settings.xml
    mv ~/.m2/settings.xml.tmp ~/.m2/settings.xml.orig
    # echo "settings.xml and settings.xml.orig replaced successfully!"
    if grep --quiet "nexus" ~/.m2/settings.xml ; then
      echo "Maven is behind nexus!"
    else
      echo "Maven isn't behind nexus!"
    fi
  else
    echo "settings.xml.orig doesn't exist!"
  fi
else
  echo "settings.xml doesn't exist!"
fi

exit 0
  1. config.sh script:
#!/bin/bash

# install 

# change the user to your preferred user
myUser="user"
# This file should be next to this script
nexusTarGz="nexus-3.1.0-04-unix.tar.gz"
nexusVer="nexus-3.1.0-04"
changeRepo="changeRepo"

confirm () {
    # call with a prompt string or use a default
    read -r -p "${1:-Are you sure? [y/N]} " response
    case $response in
        [yY][eE][sS]|[yY]) 
            true
            ;;
        *)
            false
            ;;
    esac
}

sudo cp $changeRepo /usr/bin/
sudo cp settings.xml.orig /home/$myUser/.m2

sudo cp $nexusTarGz /usr/local
cd /usr/local
sudo tar xzf $nexusTarGz
sudo rm $nexusTarGz
sudo ln -s /usr/local/$nexusVer /usr/local/nexus
sudo chown $myUser:$myUser nexus -R
sudo chown $myUser:$myUser $nexusVer -R
sudo chown $myUser:$myUser sonatype-work/ -R

echo "export NEXUS_HOME=\"/usr/local/nexus\"" | tee -a /home/$myUser/.bashrc
source /home/$myUser/.bashrc

NEXUS_HOME="/usr/local/nexus"

echo "Set this variable in $NEXUS_HOME/bin/nexus"
echo "INSTALL4J_JAVA_HOME_OVERRIDE=/usr/lib/jvm/java-8-oracle"

confirm "Do you want to viw nexus file now?(y/n recommended yes)" && sudo vim /usr/local/nexus/bin/nexus

cd $NEXUS_HOME/bin
./nexus run | echo "Type ctrl+c to continue the installation!"

echo "run_as_user=\"$myUser\"" | sudo tee $NEXUS_HOME/bin/nexus.rc

sudo service nexus stop

sudo ln -s $NEXUS_HOME/bin/nexus /etc/init.d/nexus

cd /etc/init.d
sudo update-rc.d nexus defaults

sudo service nexus restart

changeRepo

echo "Installation finished! you can visit configuration UI at (defaults)localhost:8081."
echo "Also your settings.xml file updated in your home directory. to enable maven to nexus or not to use it, run changeRepo"
echo "Make sure to edit settings.xml and settings.xml.orig in the ~/.m2/ directory and put the correct values for <localrepository> and <url> vice versa."
  1. ConfigBower.sh script:
#!/bin/bash

sudo npm install -g bower-nexus3-resolver

# Edit file /home/user/.bowerrc and put these lines in it:
# {
#   "registry" : {
#     "search" : [ "http://172.16.144.29:8081/repository/bower" ]
#    },
#  "resolvers" : [ "bower-nexus3-resolver" ]
# }
  1. ConfigNPM script:
#!/bin/bash

# nexus= IP of nexus 
nexus="192.168.1.83"

npm config set registry http://$nexus:8081/repository/npm/

# to revert back, edit /home/user/.npmrc and delete registry line
  1. settings.xml
<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
  http://maven.apache.org/xsd/settings-1.0.0.xsd">
  <localRepository>/path/to/.m2/repository</localRepository>
  <interactiveMode>true</interactiveMode>
  <usePluginRegistry>false</usePluginRegistry>
  <offline>false</offline>
  
</settings>
  1. settings.xml.orig
<settings>
  <mirrors>
    <mirror>
      <!--This sends everything else to /public -->
      <id>nexus</id>
      <mirrorOf>external:*</mirrorOf>
      <url>http://serverIP:8081/repository/maven-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>

You May Also Enjoy

Utilize PTX Just-In-Time (JIT) Compilation in CUDA

4 minute read

Published:

In this post I’ve written about how to utilize PTX Just-In-Time (JIT) compilation in CUDA. PTX is a low-level assembly-like language that is used to represent the GPU code. The PTX code is then compiled to the machine code by the NVIDIA driver at runtime. This process is called Just-In-Time (JIT) compilation. But before I write about how to use PTX JIT compilation, I’ll provide some background on why you might want to use it.

Collection of my dotfiles (public version)

1 minute read

Published:

This is a collection of my dotfiles that I use on my Linux system. I have written about them in various posts, but I thought I can put them all in one place. You can checkout the github repository here, too.

Tmux Tips and Tricks

10 minute read

Published:

(If you are already familiar with tmux, and you are looking for a simple .tmux.conf, go to the end of this post.)

Setup LAMMPS

4 minute read

Published:

Large-scale Atomic/Molecular Massively Parallel Simulator (LAMMPS) is a classical molecular dynamics code that can be used to model atoms or, more generally, as a parallel particle simulator at various scales. The complete documentation of LAMMPS can be found here. In this post, I will provide a guide on how to setup LAMMPS on a Linux machine. My setup is on a cluster with NVIDIA GPUs, UCX, and OpenMPI. Also, we have a built-in module system to load the necessary modules.