#1708 the java native compile phase

parasitid Wed 23 Nov 2011

Hello again

still trying to get the talesfwk work on my localhost.

firstable : is it a good design to link a fantom project ( like tales ) to many java native libs ? in a way, i find the fantom portable promise very attractive. ( .net, java, js, llvm? ) but as soon as your projectis linked to java natives, in fact you still get stuck to the jvm.

then : the tales fwk is structured like this :

fan/ java/ etc...

fan sources are linked to java classes but it seems that the build script doesn't compile and install the java native jar of classes issued from the javaDirs

am i doing something wrong ? do i have to build the jar by myself and install it in my lib/java/ext fan local repo ?

brian Wed 23 Nov 2011

@yanndegat

firstable : is it a good design to link a fantom project ( like tales ) to many java native libs?

I think in general it is nice to always work at the Fantom level and have clean, simple Fantom APIs. But I think reusing existing Java libraries seems a pretty pragmatic approach to get stuff done (especially if your code is server side only).

However, as you are experiencing pulling in lots of Java libraries gets you back into classpath hell and you loose lots of the elegance of Fantom's module system. As we continue to flush out fanr (our online module system) we will need to figure out best way to incorporate existing Java jars.

Login or Signup to reply.