Build failed in Jenkins: POI-DSL-1.8 #440

See -- [...truncated 7.82 KB...] check-jars: fetch-jars: check-ooxml-jars: fetch-ooxml-jars: init: [mkdir] Created dir: [mkdir]

Build failed in Jenkins: POI-DSL-Maven #558

See Changes: [kiwiwings] #59268 - remove duplicated typeloader in POI and use fixed XmlBeans implementation instead -- [...truncated 1.19 MB...] [ERROR] symbol: method newI

Build failed in Jenkins: POI-DSL-1.8 #439

See Changes: [kiwiwings] #59268 - remove duplicated typeloader in POI and use fixed XmlBeans implementation instead -- [...truncated 8.05 KB...] check-jars: fetch-jars: chec

Re: XmlBeans 3.0.0 review

Another feature in POIXMLTypeLoader is its usage of the requested type classloader (POIXMLTypeLoader:102). If I comment out the POIXMLTypeLoader replacement in the build.xml, the OSGi test case [1] doesn't work anymore. I'm not sure, if this feature should be implemented in XmlBeans directly, as

Re: XmlBeans 3.0.0 review

I'm happy to discuss alternatives. The XMLBeans SAXHelper was lifted directly from POI. https://github.com/apache/poi/blob/trunk/src/ooxml/java/org/apache/poi/ooxml/util/SAXHelper.java But with setEntityExpansionLimit being used too, it's probably safe to not have the ignoring entity resolver.

XmlBeans 3.0.0 review

Hi, I don't want to hijack the vote thread even more, so here I start a new thread about things I've noticed. I think it's confusing that in [1] the entity resolver is overwritten, which was initialized as No-Op-Resolver in [2]. The DefaultEntityResolver is also a No-Op-Resolver. Andi [1]  o

Jenkins build is back to normal : POI-DSL-Maven #557

See - To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org For additional commands, e-mail: dev-h...@poi.apache.org

[GitHub] poi pull request #113: WIP: xmlbeans 3.0.0

Github user pjfanning closed the pull request at: https://github.com/apache/poi/pull/113 --- - To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org For additional commands, e-mail: dev-h...@poi.apache.org