Max Rydahl Andersen

btw. remember jbang run has defaults it searches for when no arguments(i.e. main.java, jbang.build..) jbang dep/search could have the same.

`jbang deps update` could incorporate #2148 deps@jbangdev

These are reasons to extract those core logic as library. that said it also feels like something like deps mgmt is a core feature so let's see how it looks...

as it would know what tests to run and which are from sources and which are binaries could even make ability for continous running the tests; have "re-run" of failed...

@quintesse @cstamas - curious about feedback on this one - its a bit complicated but its important to get somewhat right thus curious about questions/clarifications and if you think there...

> Does this mean that configuring an annotation processor would have to use the following? > > ``` > //DEPS{compile} org.kordamp.jipsy:jipsy-processor:1.2.0 > ``` that was my thinking yes.

> That’s how it’s been done so far. Question is, should JBang do the same or break with tradition? > > * Is it weird to have a composite scope...

> Just FYI: > > https://github.com/apache/maven/blob/master/api/maven-api-core/src/main/java/org/apache/maven/api/DependencyScope.java#L62 so maven and Gradle calls what I want to call "compile" for "compile-only" because maven 2.5 decades ago decided to use "compile" to mean...

if we did use "compile-only" and "runtime-only" should it then also be "agent-only" and "boot-only" ...? or are agent and boot not good for scopes? I'm leaning towards that its...

> > so maven and Gradle calls what I want to call "compile" for "compile-only" because maven 2.5 decades ago decided to use "compile" to mean everything ? is that...