Jenkins build is back to normal : POI-DSL-1.8 #364

2018-02-16 Thread Apache Jenkins Server
See - To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org For additional commands, e-mail: dev-h...@poi.apache.org

Jenkins build is back to normal : POI-DSL-OpenJDK #368

2018-02-16 Thread Apache Jenkins Server
See - To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org For additional commands, e-mail: dev-h...@poi.apache.org

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

2018-02-16 Thread Apache Jenkins Server
See Changes: [fanningpj] apply changes from com.github.pjfanning:xmlbeans [fanningpj] add xmlbeans code (latest from xmlbeans svn) -- [...truncated 1.84 MB...] .

Jenkins build is back to normal : POI-DSL-Windows-1.8 #135

2018-02-16 Thread Apache Jenkins Server
See - To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org For additional commands, e-mail: dev-h...@poi.apache.org

Jenkins build is back to normal : POI-DSL-API-Check #277

2018-02-16 Thread Apache Jenkins Server
See - To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org For additional commands, e-mail: dev-h...@poi.apache.org

[Bug 62108] ArrayIndexOfBounds exception when getColumnWidth()

2018-02-16 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62108 --- Comment #4 from PJ Fanning --- Java 8's unsigned int support is not at all nice. We have limitations about supporting long - eg a lot of the XSSF clases used Lists and this has the method `E get(int index);` I would argue that the pragmatic

[Bug 62108] ArrayIndexOfBounds exception when getColumnWidth()

2018-02-16 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62108 --- Comment #3 from Mark Murphy --- Since the font index value is an xsd:unsignedInt, maybe a long is the appropriate data type. I know Java 8 kinda halfheartedly supports unsigned ints by adding some methods that treat an int as unsigned to th

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

2018-02-16 Thread Apache Jenkins Server
he JVM Languages page -- [...truncated 967.81 KB...] [zip] Building zip: <https://builds.apache.org/job/POI-DSL-1.8/ws/build/dist/poi-src-4.0.0-SNAPSHOT-20180216.zip> [tar] Building tar: <https://builds.apache.org/job/POI-DSL-1.8/363/arti

Build failed in Jenkins: POI-DSL-OpenJDK #367

2018-02-16 Thread Apache Jenkins Server
See <https://builds.apache.org/job/POI-DSL-OpenJDK/367/display/redirect> -- [...truncated 405.83 KB...] [zip] Building zip: <https://builds.apache.org/job/POI-DSL-OpenJDK/ws/build/dist/poi-bin-4.0.0-SNAPSHOT-20180216.zip> [tar]

Build failed in Jenkins: POI-DSL-Windows-1.8 #134

2018-02-16 Thread Apache Jenkins Server
om the JVM Languages page -- [...truncated 593.54 KB...] [zip] Building zip: <https://builds.apache.org/job/POI-DSL-Windows-1.8/ws/build\dist\poi-bin-4.0.0-SNAPSHOT-20180216.zip> [tar] Building tar: <https://builds.apache.org/job/POI-DSL

[Bug 62108] ArrayIndexOfBounds exception when getColumnWidth()

2018-02-16 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62108 --- Comment #2 from PJ Fanning --- I independently put together a change to use ints instead of shorts for indexing fonts. https://github.com/apache/poi/pull/102 Still would be good to have a reproducible test case though. -- You are receivin

[GitHub] poi pull request #102: [bug-62018] use ints to index fonts

2018-02-16 Thread pjfanning
GitHub user pjfanning opened a pull request: https://github.com/apache/poi/pull/102 [bug-62018] use ints to index fonts With 4.0.0 being the next release, it seems like we can make relatively large changes like using ints for indexing fonts (instead of shorts). Ideally, it would

[Bug 62108] ArrayIndexOfBounds exception when getColumnWidth()

2018-02-16 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62108 Nick Burch changed: What|Removed |Added OS||All Status|NEW

[Bug 62108] New: ArrayIndexOfBounds exception when getColumnWidth()

2018-02-16 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62108 Bug ID: 62108 Summary: ArrayIndexOfBounds exception when getColumnWidth() Product: POI Version: 3.17-FINAL Hardware: PC Status: NEW Severity: major Priority: