Alternatives to MiniMaven

[Squareys]

@ctrueden wrote in #3:

[..] personally, I would like to move away from any MiniMaven dependencies across the board. It is one more wrinkly component that we do not really have time to maintain. Rather, we should lean on the JRE's built-in infrastructure as much as possible, even if it means end users have to install a JDK. Maybe we could consolidate Java compilation logic into the scripting-java component itself, which can be reused in other places as needed? Unfortunately, I don't really have time to investigate and think through the issues thoroughly.

The first two problems that come to my mind are managing dependencies and compilation of pom files being supported up to now, so removing this feature may break other applications using scripting-java.

With "end users have to install a JDK", we might aswell go "end users have to install maven", to solve those issues.

This issue will remain open for discussion until somebody (possibly myself) finds time to look after this in the future.

[ctrueden]

Maybe this issue would have been better filed in the minimaven project itself. That is: it's not MiniMaven I want to avoid, so much as recapitulating any functionality that the JDK gives you for free these days. And like I said, I really haven't investigated the issues thoroughly so my take may be off-base. See also imagej/ImageJ#105.

[dscho]

My 2c: Does this really constitute a bug?