I could make h2 a `provided` dependency in our poi-ooxml pom. The use of h2 is opt-in in the new code in my PR but I'll need to refactor the code to allow our code not to throw ClassNotFoundException if the h2 classes are not on the runtime classpath. This is do-able but my concern is that this is difficult to automate tests for (checking the code works when the h2 jar is available and when it is not).
https://mvnrepository.com/artifact/com.h2database/h2 is very common dependency, so my preference would be to have the explicit dependency from poi-ooxml on h2 - but I'll go with whatever the consensus is. -- Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org For additional commands, e-mail: dev-h...@poi.apache.org
