Hacker News Reader

Jigsaw is not maven, nor gradle, the versioning problems should be solved by those tools. I'm getting sick of the multiple version dependency problem being brought up over and over again. That's one of the reason why OSGI is not widely adopted. You should watch some of the talks delivered by the jigsaw team.

View on HN

> Jigsaw is not maven, nor gradle, the versioning problems should be solved by those tools.

Then why do we need Jigsaw at all? If the assumption is that you run Maven or Gradle anyway then what is left for Jigsaw to do? The dependency management and check will happen by those tools.

> the versioning problems should be solved by those tools

I'm not a Java developer; could you explain a bit about how Maven/Gradle solve this problem? My understanding is that what people want is something like what Node gives you—the ability to have both libfoo-1.0 and libfoo-1.1 loaded into the same VM at the same time without clashing. Do the build tools use e.g. name-mangling to achieve this?

For Maven, there is a repackaging facility with name mangling that can do this, the Maven Shade Plugin. https://maven.apache.org/plugins/maven-shade-plugin/

Reply on news.ycombinator.com