Hi Javen,
I think the problem was at the findbugs step, later on the findbugs result
file was empty.
[findbugs] Executing findbugs FindBugsTask from ant task [findbugs] Running
FindBugs... [findbugs] Java Result: 137
Could have been an OOM on the machine or some other os-level thing that
killed
https://bz.apache.org/bugzilla/show_bug.cgi?id=60260
--- Comment #9 from Zero ---
(In reply to Javen O'Neal from comment #8)
> (In reply to Zero from comment #1)
> > The exception also occurred while rename sheet
>
> Do you have a unit test for this as well? Oddly, the two other unit tests
> tha
here:
> [javadoc] *
> [javadoc] ^
> [javadoc] 100 errors
> [javadoc] 100 warnings
> [jar] Building jar: <https://builds.apache.org/
> job/POI-DSL-1.8/ws/build/dist/maven/poi-ooxml/poi-ooxml-3.
> 16-beta2-javadoc.jar>
>
> assemble:
>
https://bz.apache.org/bugzilla/show_bug.cgi?id=60260
--- Comment #8 from Javen O'Neal ---
(In reply to Zero from comment #1)
> The exception also occurred while rename sheet
Do you have a unit test for this as well? Oddly, the two other unit tests that
I wrote in r1778418 that started with a bla
ing jar:
<https://builds.apache.org/job/POI-DSL-1.8/ws/build/dist/maven/poi-ooxml/poi-ooxml-3.16-beta2-javadoc.jar>
assemble:
[zip] Building zip:
<https://builds.apache.org/job/POI-DSL-1.8/ws/build/dist/poi-bin-3.16-beta2-20170112.zip>
[tar] Building tar:
<https://build
Hello Everyone
This email is to tell you about ASF participation at FOSDEM. The event
will be held in Brussels on 4^th & 5^th February 2017 and we are hoping
that many people from our ASF projects will be there.
https://fosdem.org/2017/
Attending FOSDEM is completely free and the ASF will ag
https://bz.apache.org/bugzilla/show_bug.cgi?id=60260
--- Comment #7 from Javen O'Neal ---
http://graphemica.com/%E3%83%BB
This is katakana middle dot (U+30FB)
--
You are receiving this mail because:
You are the assignee for the bug.
--
https://bz.apache.org/bugzilla/show_bug.cgi?id=60260
Javen O'Neal changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://bz.apache.org/bugzilla/show_bug.cgi?id=60260
--- Comment #5 from Zero ---
In my test, maybe multi-byte char is invalid when isUnquotedSheetNameChar check
sheet name chars [1], char '・' not match any case in
> private static boolean isUnquotedSheetNameChar(char ch) {
> if (Character.isL
https://bz.apache.org/bugzilla/show_bug.cgi?id=60260
--- Comment #4 from Javen O'Neal ---
The formula parse tree assumes the formula contains only ASCII. It reads one
**char** from the formula string at a time via GetChar() [1]. For multi-byte
symbols in the formula, a char is returned for each b
https://bz.apache.org/bugzilla/show_bug.cgi?id=60260
--- Comment #3 from Javen O'Neal ---
I stand corrected. Renaming a sheet requires updating named ranges (and
formulas) that refer to that sheet, which requires parsing the formula. We'll
need to dig through the parse tree code either way.
http
https://bz.apache.org/bugzilla/show_bug.cgi?id=60260
--- Comment #2 from Javen O'Neal ---
NamedRange(
name = "test_named_range",
refersTo = "'Sheet・1'!A1:A9"
)
This is the first time I have seen the sheet name be non-ASCII, which probably
breaks some of our assumptions and regular expres
12 matches
Mail list logo