I came from Clojure and I wanted a programming language that is fast. Scala is hard to learn ... even the book is 800 pages. and Fantom is great.

However I miss lein. Do you have such a tool for Fantom ?

owever I miss lein. Do you have such a tool for Fantom ?

I am not familiar with that tool. I guess you are talking about this. Could you describe what you like about it?

We have a repository tool called fanr, but it is a work in progress and there is no standard online repository yet.

Also need an integration from fanr to Java lang.

Lein is based on maven but simpler

I like it because the syntax is not xml It is easy to understand

It builds the project but also it downloads the packages from the repositories to the folder of the project (so I can find them easily from my IDE)

I believe that fantom solved most of the problems but I want from build.fan to download java libraries if they dont exist in the lib folder

for example

depends = ["sys 1.0" , "concurrent 1.0" , "fwt 1.0" , "gfx 1.0"]

mavenDepends = [ "mysql-connector-java 5.1.9" , "org.springframework/spring 2.5.6"]

It would be great if there was a tool that uses maven and make the integration with java libraries without creating new make() {...} all the time .

Do you believe that you need such a tool ?

#1517 is recent thread about repo design; #1370, #1674, and #1812 are recent discussions around improving constructor syntax... that subject is always alive, in various forms.

Maven integration and simplifying Java interop, is (from what I infer, anyway) about due for some attention. There has been a tendency to try to stay "pure" Fantom, so that the Fantom-JavaScript path isn't blocked. But there is certainly some opportunity to take advantage of Java ecosystem. Hopefully in a way that doesn't set your hair on fire.

Also I dont understand why build.fan sends the fresh created pod to ../lib/fan ... how can I change that ?

I believe (as I've not tried it myself) you can use the util::PathEnv as described in Env

C:\dev\fan>set FAN_ENV=util::PathEnv
C:\dev\fan>set FAN_ENV_PATH=/dev/work/

It's also mentioned in this topic : PathEnv feedback