4 ms·
I'd say that is a big honking "yes" to jganetsk's question. The acceptance of the build system limitations is so uncritical that you don't even try to build mor
by Daniel_Newby 17y ago
I'd say that is a big honking "yes" to jganetsk's question. The acceptance of the build system limitations is so uncritical that you don't even try to build more than a few times a year.
Which means that you don't do regression localization by doing an automated binary search of the total revision history of the complete product. ("Oh, but touching the complete product is rate limited by paperwork." [sob]) Having the build system hand you the exact delta that introduced a subtle bug once in your product's lifetime would pay for rather a lot of build optimization.
- pohl 17y agoA jar is a packaging mechanism. It is not required step in most builds that I've encountered. Nor is it required to run (test) the code. Java classes can also be linked into a CLASSPATH from an unpackaged directory. Infrequent packaging does not imply infrequent building and/or testing.