Investigate whether to include "clean" target as default in ant "build".
At the moment we don't do this due to speed.
Problem occur when a patched file get placed in wih a different name. Both will be included.
Description
Investigate whether to include "clean" target as default in ant "build".
At the moment we don't do this due to speed.
Problem occur when a patched file get placed in wih a different name. Both will be included.
I lost about an hour to this just yesterday – turns out I ended up with both the 1.0.4 and 1.1.1 version of the P4 plugin in the WAR.
Since build.sh is meant to be used by customer and (many of) those customers don't do builds except when integrating new updates, I think it makes sense to have it do a clean.
If anyone objects to the extra time, it's easy enough to provide a workaround. In other words, correctness before performance...
Anders Wallgren added a comment - 06/Dec/05 12:09 AM I lost about an hour to this just yesterday – turns out I ended up with both the 1.0.4 and 1.1.1 version of the P4 plugin in the WAR.
Since build.sh is meant to be used by customer and (many of) those customers don't do builds except when integrating new updates, I think it makes sense to have it do a clean.
If anyone objects to the extra time, it's easy enough to provide a workaround. In other words, correctness before performance...
Task
Resolved
Minor
Investigate whether to include "clean" target as default in ant "build".
Since build.sh is meant to be used by customer and (many of) those customers don't do builds except when integrating new updates, I think it makes sense to have it do a clean.
If anyone objects to the extra time, it's easy enough to provide a workaround. In other words, correctness before performance...