https://bz.apache.org/bugzilla/show_bug.cgi?id=59799
--- Comment #5 from Andreas Beeker <[email protected]> --- (In reply to Sebb from comment #4) > 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. Nope ... neither the current nor your proposed workflow guarantees that all xmlbeans fragments are included - e.g. we had problems with empty XSLFTables for quite a while and I actually don't know what (test) solved it, but back then the test were successful and the tables empty ... > (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. When developing unit tests, I don't have a problem with that - I just run the unit test in question. Before check-in, I wait the 10 minutes to run the tests - in relation to the time taken to check/develop a feature this is minimal in my view. Can you be a bit more precise why you want to speed up vs. making the build more complicate? -- 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]
