Difference between revisions of "JSS Development"
From Dogtag
(→Applying a Patch) |
m (→Getting Source Code) |
||
| Line 15: | Line 15: | ||
= Getting Source Code = | = Getting Source Code = | ||
| − | + | To clone JSS source repository for development (requires SSH authentication): | |
| − | |||
| − | |||
$ git clone git@github.com:dogtagpki/jss.git | $ git clone git@github.com:dogtagpki/jss.git | ||
| − | + | To clone read-only JSS source repository: | |
$ git clone https://github.com/dogtagpki/jss.git | $ git clone https://github.com/dogtagpki/jss.git | ||
| − | |||
If the source repository is already available, it can be updated with the following command: | If the source repository is already available, it can be updated with the following command: | ||
Revision as of 17:26, 27 April 2018
Contents
Overview
This page describes JSS development process.
Note that the text in red may need to be adjusted according to the local environment.
See JSS tickets on Mozilla Bugzilla.
Prerequisites
$ dnf install fedpkg
Getting Source Code
To clone JSS source repository for development (requires SSH authentication):
$ git clone git@github.com:dogtagpki/jss.git
To clone read-only JSS source repository:
$ git clone https://github.com/dogtagpki/jss.git
If the source repository is already available, it can be updated with the following command:
$ git pull
The above command will create a new jss folder.
Applying a Patch
$ git am <patch> $ git push
Building Upstream Binaries
To build upstream JSS binaries (without RPM package), first build NSS in sandbox folder, then go to the jss folder and execute the following:
$ export JAVA_HOME=/etc/alternatives/java_sdk_1.8.0_openjdk $ export USE_64=1 $ make clean all
See README.
Building Platform-specific Packages
See JSS Fedora Package.
