https://bz.apache.org/bugzilla/show_bug.cgi?id=59799
--- Comment #2 from Sebb <[email protected]> --- The problem with this approach is the overhead when changing a single source file. AFAICT the test phase will generate the same list of classes each time, only changing very rarely when tests are updated. There has to be a better way to do this. For example, create a fixed list of the classes from a recent run, and use that to build the jar. As part of the unit tests, recreate the class list, and check if it is the same. Or one could run the unit tests against the lite jar. There seems no point redoing the same work for every build regardless. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
