You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running ./Build.sh clean in Fiji (i.e. using MiniMaven), only artifacts with current version suffixes are removed. However, it is common to occasionally see older versions of the same artifacts in the jars and plugins folders. One would expect MiniMaven to clean those out as well when run with the clean target.
Though clean does not remove them, MiniMaven will remove them at build time when rebuilding those artifacts at newer versions. However, it can be argued that that behavior is less intuitive, and that furthermore, it is desirable to truly have a clean working copy without any old artifacts after clean has been run.
It is counterintuitive when installing removes other versions from the
ImageJ.app/ directory, but cleaning does not even remove the artifact
which would be installed.
So let's fix that bug.
Reported by Curtis Rueden in:
#6
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
When running
./Build.sh clean
in Fiji (i.e. using MiniMaven), only artifacts with current version suffixes are removed. However, it is common to occasionally see older versions of the same artifacts in thejars
andplugins
folders. One would expect MiniMaven to clean those out as well when run with theclean
target.Though
clean
does not remove them, MiniMaven will remove them at build time when rebuilding those artifacts at newer versions. However, it can be argued that that behavior is less intuitive, and that furthermore, it is desirable to truly have a clean working copy without any old artifacts afterclean
has been run.This issue was originally reported as fiji/fiji#36 by @ctrueden.
The text was updated successfully, but these errors were encountered: