Crucible 2.2 : Developing Crucible Plugins
This page last changed on Nov 19, 2009 by edawson.
IntroductionCrucible uses the standard Atlassian Plugins framework, so many of the tasks involved in developing a plugin for Crucible are the same as for other Atlassian products. The differences are:
Building a Crucible PluginThe simplest way to build a Crucible plugin is via Maven. Atlassian provides an Archetype for Fisheye/Crucible plugins. You can create a maven 2 project containing a sample Servlet Plugin Module with the following command: mvn org.apache.maven.plugins:maven-archetype-plugin:1.0-alpha-7:create \ -DarchetypeGroupId=com.atlassian.maven.archetypes \ -DarchetypeArtifactId=crucible-plugin-archetype \ -DarchetypeVersion=1-SNAPSHOT \ -DremoteRepositories=https://maven.atlassian.com/repository/public/ \ -DgroupId=com.foo -DartifactId=foo-crucible-plugin Crucible Plugin Module TypesServlet ModulesCreate a servlet which is deployed to the same web application context as Fisheye/Crucible. See Servlet Plugin Modules for more details. Crucible SCM PluginsAn SCM plugin module lets Crucible create reviews based on files stored in another source code management system. See Crucible SCM Plugins for details. Event Listener PluginsAn event listener plugin module will be called when certain events occur inside Crucible. See Crucible Event Listener Plugins for details. The Crucible APIYour plugin will need to use The Crucible API to retrieve data from Crucible and to perform operations on it, such as changing the state of reviews. Debugging your pluginYou can start Crucible in debug mode with the environment variable setting: export FISHEYE_OPTS="-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005" This allows you to connect your IDE to the debugger listening on port 5005. |
![]() |
Document generated by Confluence on Feb 23, 2010 02:04 |