This is an example Maven project implementing an ImageJ2 command.
For an example Maven project implementing an original ImageJ plugin, see: https://github.com/imagej/example-legacy-plugin
It is intended as an ideal starting point to develop new ImageJ2 commands in an IDE of your choice. You can even collaborate with developers using a different IDE than you.
-
In Eclipse, for example, it is as simple as File › Import... › Existing Maven Project.
-
In NetBeans, it is even simpler: File › Open Project.
-
The same works in IntelliJ.
-
If jEdit is your preferred IDE, you will need the Maven Plugin.
Die-hard command-line developers can use Maven directly by calling mvn
in the project root.
However you build the project, in the end you will have the .jar
file
(called artifact in Maven speak) in the target/
subdirectory.
To copy the artifact into the correct place, you can call
mvn -Dscijava.app.directory="/path/to/ImageJ2.app/"
.
This will not only copy your artifact, but also all the dependencies.
Developing code in an IDE is convenient, especially for debugging.
To that end, this project contains a main
method which launches ImageJ2,
loads an image and runs the command.
Since this project is intended as a starting point for your own developments, it is in the public domain.
-
Visit this link to create a new repository in your space using this one as a template.
-
Edit the
pom.xml
file, fixing all the lines labeledFIXME
. -
Remove the
GaussFiltering.java
file and add your own.java
files tosrc/main/java/<package>/
(if you need supporting files such as icons in the resulting.jar
file, put them intosrc/main/resources/
) -
Replace the contents of
README.md
with information about your project. -
Make your initial commit and push the results!
- Go to Run Configurations...
- Choose Maven Build
- Add the following parameter:
- name:
scijava.app.directory
- value:
/path/to/ImageJ2.app/
- name:
This ensures that the final .jar
file will also be copied
into your ImageJ2 folder everytime you run the Maven build.