Build problem in Eclipse environment about jsat HOT 10 CLOSED

Can you try this with Netbeans/ just the command line. I want to know if this is a Java 1.8 issue, or if this is an issue with the Eclipse compiler.

from jsat.

It's not a Java 1.8 issue. I've tried both with Java 1.6 and Java 1.7 with
the same results.

On Thu, Nov 26, 2015 at 4:05 PM, EdwardRaff [email protected]
wrote:

Can you try this with Netbeans/ just the command line. I want to know if
this is a Java 1.8 issue, or if this is an issue with the Eclipse compiler.

—
Reply to this email directly or view it on GitHub
#26 (comment).

from jsat.

Sorry, I'm not sure if I'm communicating well. My question is if Java 1.8 causes the issue or not. Eclipse has its own separate compiler, ecj, that it likes to use instead of javac. If Java 1.8 changed slightly and the old code is no longer valid, I will change it. If Only ecj causes the issue, then we should file a bug report with them.

from jsat.

I'm pretty sure that Java 1.8 is not the problem. My default Eclipse
compliance settings was 1.7 and Java build path was set to 1.7 library
initially and build failed. I changed this to 1.8 hoping that may help,
without success. On the other hand, maven builds project fine with Java
1.8 in my console environment.

On Thu, Nov 26, 2015 at 6:26 PM, EdwardRaff [email protected]
wrote:

Sorry, I'm not sure if I'm communicating well. My question is if Java 1.8
causes the issue or not. Eclipse has its own separate compiler, ecj, that
it likes to use instead of javac. If Java 1.8 changed slightly and the old
code is no longer valid, I will change it. If Only ecj causes the issue,
then we should file a bug report with them.

—
Reply to this email directly or view it on GitHub
#26 (comment).

from jsat.

If that's the case, I'm not sure what I can do. I've built JSAT in Eclipse with 1.7 before. I can try it again later, but unless that reveals something I don't think I can help.

from jsat.

Using latest version of Eclipse, it is giving me errors too. But only in Eclipse. Very weird.

from jsat.

Does my workaround with double casting work for you?
Does it break anything?

On Thu, Nov 26, 2015 at 8:06 PM, EdwardRaff [email protected]
wrote:

Using latest version of Eclipse, it is giving me errors too. But only in
Eclipse. Very weird.

—
Reply to this email directly or view it on GitHub
#26 (comment).

from jsat.

I changed the load methods type to just use the wild card directly, it makes more sense and avoids the Eclipse issue. If you could pull and confirm I'll close the issue

from jsat.

Yes Edward, it works now, thanks.

On Sat, Dec 5, 2015 at 9:57 PM, EdwardRaff [email protected] wrote:

I changed the load methods type to just use the wild card directly, it
makes more sense and avoids the Eclipse issue. If you could pull and
confirm I'll close the issue

—
Reply to this email directly or view it on GitHub
#26 (comment).

from jsat.

Awesome, thanks!

from jsat.