Difference between revisions of "JSS Development"

From Dogtag
Jump to: navigation, search
m (Getting Source Code)
m (Getting Source Code)
Line 23: Line 23:
 
  $  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:
+
The above command will create a new <font color="red">jss</font> folder.
 +
 
 +
The repository cloning should only be done once. If the repository is already available locally, it can be updated with the following command:
  
 
  $ git pull
 
  $ git pull
 
The above command will create a new <font color="red">jss</font> folder.
 
  
 
= Applying a Patch =
 
= Applying a Patch =

Revision as of 17:28, 27 April 2018

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

The above command will create a new jss folder.

The repository cloning should only be done once. If the repository is already available locally, it can be updated with the following command:

$ git pull

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.

References