Hi Joern,
I found out, as part of OPENNLP-580 you refactored loadResources() but
forgot to change UIMA to add a new parameter. Java 7 doesn't catch this
when building... not sure why, but a bit concerning none the less.
Anyway I fixed that for UIMA as well by adding null for the second
parameter to keep the original functionality.
James Kosin
PS: Sorry for the misspelling below. :) I'm terrible at spelling but
can code wonders.
On 3/25/2014 12:08 AM, James Kosin wrote:
Hi Jeorn,
I've got most of the documentation issues addressed in tools.
There is a problem with UIMA in that in:
java.uima.namefind.NameFinderTrainer
there is a call to:
TokenNameFinderTrainerTool.loadResources() with one parameter;
however, Java 8 can't find the function.
Is this a call to a Java resource of the libraries or did someone
forget to refactor UIMA after changing the loadResources() functions?
Thanks,
James
On 3/20/2014 4:40 AM, Jörn Kottmann wrote:
Hello James,
we have to fix this for the upcoming release.
Would you mind to open a jira issue?
We also have to make sure that it doesn't happen again.
I suggest as long as we are on 1.7 we should have a job
on our build server which additionally builds and tests with 1.8.
Thanks,
Jörn
On 03/20/2014 04:56 AM, James Kosin wrote:
All,
I just wanted to let everyone know, the OpenNLP project is not
compatible with the new Java 1.8.
I get two (2) issues:
1) Fails test:
Failed tests:
testPerceptronOnPrepAttachDataWithStepSizeDecrease(opennlp.tools
.ml.perceptron.PerceptronPrepAttachTest):
expected:<0.7756870512503095> but was:
<0.7766773953948998>
2) Java document generation fails miserably.
[ERROR] * <li>.bin --> the file is binary
[ERROR] ^
[ERROR]
C:\Users\jkosin\Documents\Projects\OpenNLP\opennlp\opennlp-tools\src\mai
n\java\opennlp\tools\ml\perceptron\SuffixSensitivePerceptronModelWriter.java:41:
error: bad use of '>'
[ERROR] * <li>.bin --> the file is binary
[ERROR] ^
[ERROR]
C:\Users\jkosin\Documents\Projects\OpenNLP\opennlp\opennlp-tools\src\mai
n\java\opennlp\tools\postag\POSModel.java:64: error: reference
not found
The second for javadoc errors are probably due to more stringent
checking in javadoc.
The first... is a bit disconcerting and troubling. I'm going to
check into this; because this error shouldn't be happening.
Just letting everyone know before we get too many complaints.
James Kosin
