https://bz.apache.org/bugzilla/show_bug.cgi?id=59799
--- Comment #4 from Sebb <[email protected]> --- (In reply to David North from comment #3) > What's the concrete problem here - the time taken to run compile-ooxml-lite, > or something else? The time taken to run the target, and the fact that it is rerun even if there has been no change to the sources. > We could consider having a static list in source control and a separate > Jenkins job to warn us when that list goes out of date, but obviously it's > more overhead than the current system. AFAICT there's no need for a separate Jenkins job to check if the list is out of date; just ensure that the check is done as part of the normal unit tests. If the unit tests are run against the lite jar rather than the merged input, this should show up any problems. This would check that the jar really did contain everything required. Alternatively, run the unit tests as normal, but add a new test at the end to compare the generated list with the static list. Or a combination: run against the statically created lite jar, but also record the used classes. At the end, check if any classes are no longer needed. -- 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]
