resolve deps directly (don't create deps.lst)

[kares]

No description provided.

[headius]

I have not looked at the code closely myself but one concern I had was that deps.lst avoids re-resolving dependencies repeatedly. If that is the case it might be something we'd want to have users include in the gem, but again I have not looked into this possibility at all yet.

[kares]

concern I had was that deps.lst avoids re-resolving dependencies repeatedly. If that is the case it might be something we'd want to have users include in the gem

likely the case, the current approach isn't ideal. deps.lst accomplished "something" in that direction but those deps are still stored with a (hard-coded) M2_HOME.

what jar-dependencies should support would be something like:

1. resolve dependencies and store them in a known location along-side with the gem (ideally gem uninstall also removes downloaded jar dependencies)
2. users should have an opt out of storing jar dependencies and jar-deps would attempt to resolve them again
3. an opt-out of installing/resolving dependencies completely

the first use-case wasn't really supported well. not sure I'll really have the time to do a proper feature development.