Karl Nelson

It is very light relative to grovy or maven as it is a dependency manager and not a build system. I selected it for my projects internal use mainly because...

@ctrueden so I guess I will tag you as someone interested in seeing this feature added. @marscher This is likely one of those features that it actually makes sense to...

We will only be using a subset of ivy for pulling. But i suspect it would be the majority. We arent going to support pushing or making new packages from...

Well I haven't done much on this beyond the prototype. This behavior is part of scyjava so at least some usage. I personally don't have much use for this type...

Seems like a solution would simply be to add a private class called JPypeDeps somewhere in jpype module. It doesn't contain anything but a reference to the internal class name...

The problem here is the we are still supporting Java 8. We can't build the class file on anything before Java 9 because it requires tools only included in Java...

Generally speaking Java does not work across multiple processes unless the JNI is started after the fork. If you start it before the fork the JNI is often broken resulting...

Java may only be started once. So once started you may not fork. However, you may start a new process by other methods. For example, see the code in pytest...

The file subrun.py in test/jpypetest is an example in which many processes are running jvms. However, this is not a single shared JVM, but rather just a spawn of many...

Unfortunately that was the only method that I found would working with multiprocessing. I am not sure if it is possible to use the same method in a pool.