Deploying a customized bug tracker plugin
To deploy a customized bug tracker plugin, build a JAR file that contains the plugin classes and any of its dependent classes.
The following example script builds a bug tracker plugin with Gradle:
apply plugin: 'java'sourceCompatibility = '1.8'
targetCompatibility = '1.8'
dependencies {
compile fileTree(dir: 'lib', include: '*.jar')
}
jar.enabled = false // There is no need to generate a default non-osgi jar during build.
clean {
delete "${projectDir}/dist"
}
task pluginJar(type: Jar) {
baseName "com.fortify.BugTrackerPluginAlm"
from sourceSets.main.output
destinationDir = file("${projectDir}/dist")
manifest {
from "${projectDir}/META-INF/MANIFEST.MF"
}
from(projectDir) {
include "plugin.properties"
include "plugin.xml"
}
into("lib") {
from "${projectDir}/lib"
include "*.jar"
exclude "fortify-public*.jar"
}
}
build.dependsOn(pluginJar)
If you customize the sample bug tracker code that comes with Application Security, but you use the same plugin classname, do not change the short display name of the plugin. It is used for the name of the bugfield template group. (For consistency, also avoid changing the long display name.) If you do change the name of the main implementation class, then you must also change the display name(s) for the plugin.
For information about how to build a library that includes all bug tracker plugin dependencies, see the <ssc_distribution_dir>/Samples/<bugtracker_plugin_name>/README file.
See Also