Andrus Adamchik

Related: #294

Also maybe related... Artifact resolution starts with "central", not "local" per screenshots above. This makes things pretty slow, as it pings central every single time (which is a separate problem,...

Another pieces of `%maven` randomness... I have two notebooks with the same imports: ``` %maven com.nhl.dflib:dflib:0.6-SNAPSHOT %maven com.nhl.dflib:dflib-jdbc:0.6-SNAPSHOT ``` So: 1. I start by doing `rm -rf ~/.ivy2/` (this often...

> School has taken priority as of lately and as a result I haven't had much free time to work on IJava and friends other than try and keep up...

More classpath fun. I reworked DFLibJupyter to use Logack for logging (this allows dynamic log level changes among other things). When I start with a clean Ivy repo (`rm -rf...

Thanks for the quick reply and for confirming my solution. Regarding the plugin design. Yeah, `%loadExtension com.nhl.dflib:dflib-jupyter-ijava:0.6-SNAPSHOT`, with a lifecycle method called on startup would be ideal. As for how...

> I would like to have this in the api package of the jupyter base libs since a plugin like the one you are describing can be reused to work...

I am concerned about l2fprod dependency. I don't see this artifact in a public Maven repo : http://search.maven.org/#search|ga|1|l2fprod (though there are similarly named jars) . If you think the new...

This effort may depend on #118.

Reopening due to the iJava classpath issue described here: https://github.com/SpencerPark/IJava/issues/63#issuecomment-501479020 ... Once the issue is addressed, we can patch it back per attached diff: [61-diff.txt](https://github.com/nhl/dflib/files/3286169/61-diff.txt)