I've noticed that in repeated builds some directory where left on
working folder,
even after executing 'clobber' target.
The solution, tested on current trunk, seems to add a line to 'clobber'
target
and adding a note to BUILDING.html.
The work log
Bryan Pendleton wrote:
2) I'm surprised by the concept of removing the class files but not
removing the jar files; I have trouble thinking of situations in
which I'd want to rebuild the class files but not rebuild the jars.
I think some developers feel that it is more convenient to include
John Embretsen wrote:
2) I'm surprised by the concept of removing the class files but not
removing the jar files; I have trouble thinking of situations in
which I'd want to rebuild the class files but not rebuild the jars.
I think some developers feel that it is more convenient to include the
Bryan Pendleton wrote:
What I don't understand is a target that *cleans* only the classes, and
not the jars. I think it makes it too easy for the distracted developer
to accidentally run with the wrong code, by using the old jars.
I think some of it is history with the product. The
I can second this, when debugging a file I tend to just use the classes
and rebuild over/over the same .java file. There use to be better
support with previous build systems to optimize this case - but you
had to know what you were doing since if you didn't run the build from
the top you might
Andrew McIntyre wrote:
I think it would be good for the clobber target to clean up the jars and
other release target files or provide an alternate target for cleanup.
If there are no complaints, I'll add the jars and javadoc output
directories to the clobber target.
Somewhat of a tangent
properties, the parser files
generated by javacc and the class size catalog. It seems to me that
the jars, being generated files and living outside the build output
directory, would be a logical candidate for addition to the clobber
target.
Personally, I almost always clobber and almost never clean
clean removes the contents of the build output directory only.
...
clobber also removes generated files outside of the build
output directory
Thanks for the good explanation. Two follow-ups:
1) It seems like there are build products (the jars and the
javadoc, at least, perhaps others?) which
