support Modules

[maxandersen]

when //MODULE is present vscode java should put dependencies on module classpath not the classpath so the compiler does not complain about missing modules :)

[fbricon]

Can you please provide some sample script?

Also please note that we don't parse the Jbang directives to set the class path, we depend on what jbang info tools provides. So it would be best if it returned the list of modules

[maxandersen]

We return the module name and the dependency locations. You don't need module names do you?

[fbricon]

do all dependencies need to be added to the modulepath instead of the classpath? or can you mix-n match? (I don't remember, I never use that abomination)

[maxandersen]

Yes. Just add to module path instead of classpath.

You can in theory add on classpath but it isn't a thing.

If we ever did that we would have an explicit classpath in the tools info output.

One additional caveat is that jbang generates a module info if user don't provide one. Not sure if we can deal with that in the IDE. Ill try make an example an share to see. It relies on stuff only in main atm.

[fbricon]

As soon as we enable module support in Eclipse, we'll need to point to that module-info.java. Is there a way to run jbang (preferebly via jbang info tools) so it calls https://github.com/jbangdev/jbang/blob/1e13a0b0dec31361c5d99eaddb96f92820788972/src/main/java/dev/jbang/util/ModuleUtil.java#LL70C2-L112C3? We need to either return the module-info.java location or be able to tell JBang where to generate it

[maxandersen]

pretty sure we can for sure include it in tools output - but its not necessarily a stable location.

can eclipse pickup an arbitrary .java anywhere?

@quintesse ^^

[fbricon]

@maxandersen eclipse could link to any location, but it'd be better if it pointed to the same file on each jbang invocation.