termsuite/termsuite-core

"fr.univnantes.termsuite.types.*" cannot be resolved to a type.

Closed this issue · 5 comments

mhabsaoui commented

Hi,

The project can be build successfully from console (with 84 warnings though like: termsuite-core/src/main/java/fr/univnantes/termsuite/utils/TermOccurrenceUtils.java:69: warning - @return tag has no arguments. ), BUT under Eclipse, we get many java problems as following:

image

image

Thanks

dcram commented

This is because the UIMA annotation classes must be generated from TermSuite's type system (see file TermSuiteTS.xml)

To do that, run gradle jcasgen before you can compile TermSuite.

$ git clone git@github.com:termsuite/termsuite-core.git
$ cd termsuite-core
$ gradle jcasgen

After that, you might have to refresh the directory tree from your IDE.

mhabsaoui commented

OK 👍

image

What about the "Gradle Eclipse" tasks ?

image

PS: if you're working behind a proxy-firewall (maybe like me), do we have to config the proxy for Maven (.m2/settings.xml) + Groovy (.groovy/grapeConfig.xml) + Gradle (.gradle/gradle.properties) ?

Thanks !

dcram commented

"Gradle Eclipse" tasks won't work properly neither with any class generation tools since the Eclipse's resource tree must be refresh from the inside.

You can use buildship plugin as Gradle integration to Eclipse, but I never managed to reach a perfect gradle/eclipse integration. I prefer to have my Eclipse IDE without gradle and to handle my gradle tasks separately in a console. The inconvenient is that I have to refresh Eclipse whenever gradle tasks impact the resource tree handled by Eclipse. But as far as I know, jcasgen is the only such task.

mhabsaoui commented

I prefer working from the terminal console inside eclipse too, the Gradle Buildship is there just for a trial nothing more... For me, after "gradle jcasgen", it refreshed automatically the project tree :-)

It would nice to update the Reasme with the right commands to follow to make.

dcram commented

I just added it. Thx