Looks like I should update my local JDK anyway, it's out of date, I'll see
what that says Monday.
As for asking the conditional rules what cells they cover, and then only
checking those cells, that may be faster. I tried to have it fail fast if
the cell in question is not in a range covered by a
For completeness purposes, I should say that the language level in IntelliJ
is 8. The JDK in use is 1.8.0_131 which I believe is the official Oracle
release.
And this is line being objected to:
return op != null && op.isValid(val, comp, (Comparable)null);
On Fri, Jan 5, 2018 at 8:05 PM, Blake
On Fri, Jan 5, 2018 at 4:19 PM, Greg Woolsey wrote:
> for getRules() you can just create your own subclass and override it with a
> public version that returns super.getRules()
>
That is precisely what I did, yes. And then I hit the matches thing.
for matches, I
https://bz.apache.org/bugzilla/show_bug.cgi?id=61959
--- Comment #4 from Alain Fagot Bearez ---
The alternative would be to copy each slide to a new presentation, by creating
a new slide in the new presentation and importing the content of the original
slide into the newly
https://bz.apache.org/bugzilla/show_bug.cgi?id=61960
Alain Fagot Bearez changed:
What|Removed |Added
Status|NEW |NEEDINFO
Github user asfgit closed the pull request at:
https://github.com/apache/poi/pull/72
---
-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org
for getRules() you can just create your own subclass and override it with a
public version that returns super.getRules()
for matches, I don't see a quick easy way to override. What rule
definition seems to be slow, and what range does it cover? There are
definitely some formulas that take
Which Java version is your compiler compatibility set to? POI 4.0 requires
Java 8.
On Fri, Jan 5, 2018 at 3:14 PM Blake Watson wrote:
> I am trying to =just= recompile two classes:
> ConditionalFormattingEvaluator, EvaluationConditionalFormatRule. I'm trying
> to expose
I am trying to =just= recompile two classes:
ConditionalFormattingEvaluator, EvaluationConditionalFormatRule. I'm trying
to expose ConditionalFormattingEvaluator.getRules and
EvaluationConditionalFormatRule.matches. I think the latter is the source
of the slowness I'm experiencing.
On Fri, Jan 5,
I use IntelliJ and it handles the poi repo well, in my experience.
I allow IntelliJ to use the gradle build and use a Zulu 8 JDK as the SDK.
--
Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
-
To
When I try to compile EvaluationConditionalFormatRule.java I get an error:
**
Error:(348, 40) java: method isValid in enum
org.apache.poi.ss.formula.EvaluationConditionalFormatRule.OperatorEnum
cannot be applied to given types;
required: C,C,C
found:
GitHub user pjfanning opened a pull request:
https://github.com/apache/poi/pull/87
Xmlbeans 2.6.3
I'm suggesting that we use xmlbeans fork in POI 4.0.0 while we consider the
options around replacing xmlbeans or coming up with a better way of maintaining
xmlbeans.
You can merge
https://bz.apache.org/bugzilla/show_bug.cgi?id=61967
PJ Fanning changed:
What|Removed |Added
Status|NEW |RESOLVED
https://bz.apache.org/bugzilla/show_bug.cgi?id=61967
Bug ID: 61967
Summary: Semantic Versioning semver
Product: POI
Version: unspecified
Hardware: All
OS: All
Status: NEW
Severity: normal
14 matches
Mail list logo