Home

Welcome to the sw360chores wiki!

Installation Notes for Mac OS X Computers

Prerequisites

• Docker https://www.docker.com/products/docker-desktop
• Homebrew https://brew.sh
• Well, sw360chores ...

Steps 1: Setup Docker Environment

A. At first you may need to install a tool which computes hashes for the downloads to check their integrity:

$ brew install md5sha1sum

B. Then, you need to add some shared folders so that the docker containers can access your file system. For this go to the docker menu (the docker icon in the menu bar) -> select the item Preferences-> go to tab File Sharing and add the following two folders:

/${path-to-chores}/sw360choress/_deploy/
/${path-to-chores}/sw360choress/configuration

C. Then execute the main command for sw360chores:

$ ./sw360chores.pl --build -- up

Steps 2: Get the SW360 Software

A. You need to deploy the SW360 packages to the Liferay container. You can generate the packages from the SW360 project:

mvn package -P deploy
  -Dbase.deploy.dir=.
  -Dliferay.deploy.dir=/${path-to-chores}/sw360chores/_deploy/liferay
  -Dbackend.deploy.dir=/${path-to-chores}/sw360chores/_deploy/tomcat
  -Drest.deploy.dir=/${path-to-chores}/sw360choress/_deploy/tomcat

B. Note two things here:

• The SW360 solution ha three major parts:
  • The portal needs to go into the Liferay deploy folder (named liferay here)
  • The backend needs to go into the tomcat webapps folder (named tomcat here)
  • The rest API components need to go into the tomcat webapps folder as well (named tomcat here)
• If you want to build the packages and it fails (at the lib-datahandler) at some tests: in 99% of the cases there is no couchdb database server running which is required for tests. Try -DskipTestsif you would like to avoid it.