NOTICE! This is a static HTML version of a legacy ImageJ Trac ticket.

The ImageJ project now uses GitHub Issues for issue tracking.

Please file all new issues there.

Ticket #1962 (closed enhancement: fixed)

Opened 2013-07-19T14:06:41-05:00

Last modified 2013-07-23T10:21:43-05:00

Investigate whether maven-failsafe-plugin is more appropriate than maven-invoker-plugin for our integration tests

Reported by: dscho Owned by: dscho
Priority: major Milestone: imagej2-b8-analysis
Component: Build System Version:
Severity: minor Keywords:
Cc: Blocked By:
Blocking: #1919


We have a couple of integration tests in ij-legacy and ij-updater-core (needed because they start the JVM in a specific state). This developer found tutorials to use the invoker plugin to perform those tests, but recently, the question arose whether the failsafe plugin would be more appropriate to use.

While at it, investigate whether the updater tests could not be plain regression tests instead, creating fresh class loaders for the purpose of excluding certain classes from being found at first.

Change History

comment:1 Changed 2013-07-23T10:21:43-05:00 by dscho

  • Status changed from new to closed
  • Resolution set to fixed

This was not only addressed and answered in, but the follow-up wish (turning all the invoker plugin based integration tests into failsafe based ones), too.