In the IDE I'm building, I currently have a project roughly correspond to a a pod (or set of) right now, would it make more sense to just have the project be a full fledge repo ?

I suppose this would be more like a "j2ee/ruby" project setup at that point ?

Also I see in the repo page(which i knew nothing about) that it has a "lib/java" folder, and it says i could put "jars" in there, would they be loaded by the fan class loader(ie: runtime jar) or are those just build dependencies.

Can I "run" a repo like running a pod (what's the entry point ?)

Can a repo be "built" into a standalone deployable unit(called what ?) ?

What's implemented so far ? should i just forget about this until later ?

Thanks.

I would say that IDEs would typically be using a working repo.

Also I see in the repo page(which i knew nothing about) that it has a "lib/java" folder, and it says i could put "jars" in there

I have not changed the launcher code to load non-Fan stuff (jars, dlls, etc) from anything other than the boot repo - do we want to try to do that? It requires increasingly complicated launcher boot (which in unix as bash scripts kind of sucks).

Can I "run" a repo like running a pod (what's the entry point ?)

No

Can a repo be "built" into a standalone deployable unit(called what ?) ?

no - and I think long term the focus should continue to be on pods, repos are a local issue for organization

ok, thanks.

Yeah, i just ran into this today. I can't build using a jar unless I put the jar in lib/java/ext in the fan dist folder. Which is a bit of a bummer. I'll play with with the loader code and see about dynamically adding the repo paths to the classpath.