tesla / tesla-aether Goto Github PK

When we set the remoteRepositories to empty we expect that tesla-aether will only use local repo and never contact any remote repo for downloading artifacts, however, this does not seem to be valid while resolving transitive dependencies, there should be a way to ignore looking at artifact descriptors during transitive dependency collection.

RepositorySystemSessionProvider always attaches

    session.setTransferListener(new ConsoleTransferListener());
    session.setRepositoryListener(new ConsoleRepositoryListener());

To the session. This fills the logs with a bunch of lines about resolutions, which is definitely nice to have in a development/debugging environment, but I'd rather not having it pollute my normal logs.

It would be awesome if it were easier for me to turn these off/plugin my own listeners/something that gives me control. It appears as if overriding the guice binding might be the easiest way to do this, but it's not clear how to override the repositories without having users adjust their settings.xml.

One option might be to make the Guice modules use a Guice Multibinder to inject a Set, then your default module could setup central like it's currently defaulting to and other users could use the Multibinder to add RemoteRepositories to the Set<>.

Can you please provide guidance on what license you are making this code available under? I'd really like to use it, but as it stands, I'm not sure if I actually have the right to use it.

Currently there is no way to pass in username and password for authentication with remote repositories to DefaultTeslaAether.

It looks like the rest of the code already handles the authentication part, so there are a couple ways this could be addressed:

• Either by allowing to pass user information through the URI
• Or having one of the DefaultTeslaAether constructors take a list of Repository objects
• Or making the required methods / variables protected so someone could add the functionality by subclassing