I would like to distribute JFilament as part of Fiji

I think I have met the requirements outlined on http://imagej.net/Fiji/Contribution_requirements for including a project in Fiji. The project is currently at http://www.github.com/odinsbane/jfilament.

We published the work in 2009 & 2010.

1 Like

Hi @odinsbane

This is looking very good.

I made a jenkins job for your project and added instructions for linking your project with Jenkins.

Once that is done and the Jenkins automation is working, you can release the next version of your library that incorporates your recent changes. The Jenkins job should automatically deploy the latest release to the ImageJ maven repo.

Then I will add management and a dependency to JFilament to pom-fiji and fiji, repsectively, so that it can be uploaded to the Fiji update site.

A couple suggestions (not required for integration):

  • Remove the dependency versions from your pom, as this will override the version managed by your parent pom (pom-fiji) and is more likely to create dependency skew.
  • Remove the scope declarations. compile is the default scope.
  • Create a wiki page :smile:

Thank you for the detailed response, and sorry for the delay. I got a jenkins job to start , but it has not finished successfully yet. Here is the error I get:

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on project JFilament_: Fatal error compiling: invalid target release: 1.8 -> [Help 1]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
Build step ‘Execute shell’ marked build as failure
Archiving artifacts

Thanks again.

Ah my mistake. The Jenkins job was still set to use Java 6. I updated it to Java 8 and now it passes! :smile:


A post was split to a new topic: Automating NMQC builds