NOTICE! This is a static HTML version of a legacy Fiji BugZilla bug.

The Fiji project now uses GitHub Issues for issue tracking.

Please file all new issues there.

Bug 40 - Fiji build does not re-build after fake.jar is updated
Fiji build does not re-build after fake.jar is updated
Status: RESOLVED FIXED
Product: Fiji
Classification: Unclassified
Component: Other
unspecified
All All
: P2 minor
Assigned To: ImageJ Bugs Mailing List
Depends on:
Blocks:
 
Reported: 2009-04-06 09:34 CDT by Stephan Saalfeld
Modified: 2009-04-16 01:48 CDT
1 user (show)

See Also:

Description Stephan Saalfeld 2009-04-06 09:34:50 CDT
Building fiji after fake.jar was re-built does not re-build the whole source tree.  I think it should do so because changes in the builder will change the way things are built.  BTW---Is there a clean-target?
Comment 1 Johannes Schindelin 2009-04-06 14:56:19 CDT
That would take a rather long time, no?

But I could be convinced to add that; should be relatively easy, too.

And yes, there is a "clean" target; it just removes all the .jar files specified in any rule.  (It leaves the .class files needed for .jar files alone, as they are ignored for the up-to-date check anyway.)
Comment 2 Stephan Saalfeld 2009-04-06 15:12:36 CDT
(In reply to comment #1)
> That would take a rather long time, no?

Indeed.  But having all "binaries" built with an outdated builder, it makes total sense for me.  What about changing the target for fake.jar such that it initially cleans and afterwards builds all?

> But I could be convinced to add that; should be relatively easy, too.

Then---let's poll.  I am PRO.

> And yes, there is a "clean" target; it just removes all the .jar files
> specified in any rule.  (It leaves the .class files needed for .jar files
> alone, as they are ignored for the up-to-date check anyway.)
> 

Thanks.


Comment 3 Johannes Schindelin 2009-04-16 01:48:31 CDT
Fixed in 0a2324fd402b3875f1d072d572f2fa07d2a04ded in 'master'.