IBM and Red Hat to Vote “No” on Java Modules (Jigsaw)

Re:IBM and Red Hat to Vote “No” on Java Modules (Jigsaw) by mcguire on Tuesday May 02, 2017 @08:22PM (#14252020)

I used the SpringSource server (later known as Eclipse Virgo) as a sort of "platform as a service" for enterprise apps. It could deploy anything from plain war files up to OSGi-aware apps that could access custom services for configuration, db access, authentication/authorization, and so forth. Worked rather well, with decent uptime and no hair pulling on my part.

The down side was that OSGi requires modularization, which exactly no Java developers to my knowledge had any experience with. Plus OSGi modularity is entirely done at runtime and Spring's tooling to try to support it was incredibly flakey. Conversations went like:

"My app works fine on my dev box but blows chunks when I try to deploy it."

Me: "You have to be explicit about whay you are depending on in your app's manifest."

"I see your lips moving, but all i hear is barks, grunts, and squeals."

"Sigh. I'll fix it."

I can't really see jigsaw making the situation any better, especially since it explicitly ignores versioning and containers.

[ Parent | on HN ]

Re:IBM and Red Hat to Vote “No” on Java Modules (Jigsaw) by chopin on Wednesday May 03, 2017 @03:42AM (#14253754)

On the other hand you have the same kind of problems with Maven. You have to state your dependencies explicitly which can be a pain. And Maven does not support multiple versions when running tests. Everything is lumped into one classloader (afaik), where I sometimes wish Maven would make use of something OSGi like. With regards to dependency declaration both are pretty similar.

[ Parent | on HN ]