Hi,
By this patch, you fixed also bug
https://bz.apache.org/bugzilla/show_bug.cgi?id=62259 which you can accordingly
close.
Best regards,
Alain
On 2018/07/11 23:39:45, "pj.fanning" wrote:
> I checked in some artificial tests that load some of the ooxml-schemas>
> classes that are missing.>
Great!
Would be nice if we can add this as separate step in the builds on Jenkins
as we run into such issues quite often. We could try to do it similar to
how we verify that scratchpad-jar is only required by ooxml-jar for a few
selected things, see "noScratchpad" in create_jobs.groovy and
"scratc
I checked in some artificial tests that load some of the ooxml-schemas
classes that are missing.
I was able to get the ooxml build and tests to work locally after
regenerating poi-ooxml-schemas with the extra classes.
--
Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
-
I modified my local poi build.xml to use a poi-ooxml-schemas 4.0.0-SNAPSHOT
from a recent nightly build and found lots of compile issues building
poi-ooxml.
My build crashes with a Stackoverflow issue after this output so I suspect
that this is the tip of the iceberg.
compile-ooxml:
[javac] C
Hi,
Not with the current approach as far as I see. It injects a custom
classloader before running all unit-tests. This classloader records all
loaded classes from the -schemas jar and so it only can see classes which
are actually used during execution time, not compile time.
If type-erasure remov
