Got feedback or spotted a mistake?

Leave a comment at the end of this page or email contact@krishagni.com

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Introduction

This document describes the steps to create a plugin for OpenSpecimen. This guide is intended for developers or technical IT staff. To write a plugin one should be aware of the OpenSpecimen domain structure.

As a developer you are expected to have working knowledge of:

  1. Using REST APIs.
  2. Java Spring
  3. Angular JS

Following are high level steps:

  1. Install prerequisite software which can be downloaded from http://demo.openspecimen.org/releases/Prerequisites/
  2. Download the plugin skeleton os-plugin.zip  
  3. Unzip the downloaded file into a directory.

Prerequisites

Following table lists prerequisites and their supported versions.

Pre-requisite

Version

JDK

1.8

Gradle

2.0

Environment Variables

Following table lists and describes environment variables

Environment Variable

Description

JAVA_HOME

Absolute path of directory where JDK is installed. For example: 'C:\JDK1.8'

Please refer to following variables used throughout the document.

Keyword

Comment

PLUGIN_HOME

Directory where plugin source code is kept. For example, F:\os-plugin.

JAVA_HOME

Directory where JDK is installed. For example, C:\JDK1.8

Steps to add custom Java classes:

  1. Please add all your Java classes under PLUGIN_HOME/src/main/java/com/krishagni/openspecimen
  2. All the Spring configuration should be done in PLUGIN_HOME/src/main/resources/pluginContext.xml

Steps to create plugin archive

The build system uses Gradle to manage code compilation, building plugin jar archive. 

  1. Open command prompt. Change your current directory PLUGIN_HOME.
  2. Use the following commands to build the plugin archive:
    gradle clean
    gradle build
  3. The above target will create the archive in the build directory under respective plugin module. e.g. For current plugin the jar will get created at ${PLUGIN_HOME}/build/libs/os-plugin*.jar
  • No labels