Max Rydahl Andersen
Max Rydahl Andersen
@quintesse we don't need to handle what is better done in a users module info file. I was thinking more as way to define things like boot module path or...
See https://github.com/jbangdev/jbang/issues/618 And yes each of these are probably separate issues that we can implement separately but wanted to check if overall approach would work.
Reason for *one* {} is that then we can agressive grab that as there is no other } to be found. Also if user want it it per dependency they...
> I'd prefer having each dependency in its own line, rather than grouping them by scope. > > Also agree that `//DEPS !xyz` reads better than `//!DEPS xyz`. After all,...
But exclusions arent dependencies. Can't depend on org.jreleaser:*
Agreed, lets put modifier on GAV syntax: `//DEPS g:a:v{run,build}` that does greatly simplify things internally. If we find cases where it gets too verbose we can consider adding `//DEPS {run,build}...
> FWIW Maven supports both types of exclusions. It actually does not support these - maven exclusions are filters and only applied to an actual GAV transitive deps. They just...
Thinking to not call it scopes but to allow to declare when to use it. Ie. //DEPS A:b:1.2{when=boot} And use when needing to refer to it in i.e. jbang info...
Agent is not taken from //deps today so it's only build,run today.
in #2133 the original idea was to have attribute list on `//DEPS` directive similar to how asciidoc does attributees, i.e. `//DEPS{"run"} g:a:v, g:a2:v` woulde be same as `//DEPS g:a:v{scope="run"}, g:a2:v{scope="run"}`...