This repository has been archived by the owner on Jun 22, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 18
Home
Michael edited this page Sep 13, 2019
·
6 revisions
Welcome to the sw360chores wiki!
- Docker https://www.docker.com/products/docker-desktop
- Homebrew https://brew.sh
- Well, sw360chores ...
At first you may need to install a tool which computes hashes for the downloads to check their integrity:
$ brew install md5sha1sum
Then execute the main command for sw360chores:
$ ./sw360chores.pl --build -- up
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-master/_deploy/liferay
-Dbackend.deploy.dir=/${path-to-chores}/sw360chores-master/_deploy/tomcat
-Drest.deploy.dir=/${path-to-chores}/sw360chores-master/_deploy/tomcat
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)
- The portal needs to go into the Liferay deploy folder (named
- 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
-DskipTests
if you would like to avoid it.