public
Description: Add Twitter-like functionality to Confluence.
Homepage:
Clone URL: git://github.com/keithb/twikkir.git
keithb (author)
Thu May 08 18:31:08 -0700 2008
commit  5979c709d28a8a99aaf47624c819e635cf895e18
tree    9afbf5d556ab1b476ffcad62d558c582d633c60d
parent  739f6c19ba610ebf6036db759223ccab856fbd39
name age message
file .DS_Store Loading commit data...
file .classpath
file .project
file LICENSE.TXT
file README.txt
directory bin/
file pom.xml
directory src/
README.txt
You have successfully created a plugin using the Confluence plugin archetype. What to do now:

1. CUSTOMISE THE PLUGIN

- Run 'mvn eclipse:eclipse' to generate an Eclipse project file.
- Edit pom.xml. Add information about your project, its developers and your organisation. Check the version of
  Confluence in the dependencies section is correct.
- Edit the plugin descriptor, src/main/resources/atlassian-plugin.xml. Add or modify plugin modules in your project.
- Edit the plugin code in src/main/java/ or the unit tests in src/test/java/.

More documentation on Confluence plugins is available here:

http://confluence.atlassian.com/display/DOC/Confluence+Plugin+Guide


2. BUILD THE PLUGIN

Building with your plugin with Maven is really easy:

- Run 'mvn compile' to compile the plugin.
- Run 'mvn test' to run the unit tests.
- Run 'mvn package' to produce the JAR.

Please remove this file before releasing your plugin.


** NOTE ON RESOURCE FILTERING **

The default pom has 'resource filtering' enabled, which means files in the src/main/resources directory will have
variables in the form ${var} replaced during the build process. For example, the default atlassian-plugin.xml includes
${project.artifactId}, which is replaced with the artifactId taken from the POM when building the plugin.

More information on resource filtering is available in the Maven documentation:

http://maven.apache.org/plugins/maven-resources-plugin/examples/filter.html