<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Sorry not to CC you on my previous reply, but it's below anyway.<div class=""><br class=""></div><div class="">Just to add to this:</div><div class=""><br class=""></div><div class="">I --- personally, this is not a project position --- would like us to be able to support the Java module path in the long run. That's not an easy thing to do, though, because of the way they have defined things. A lot of products which were invented long before the JPMS was will have some trouble fitting into the constraints that have been introduced, particularly around the way things need to be strictly partitioned between what were JAR artifacts. It remains to be seen, really, whether everyone will adopt the module system or whether instead it will just wither because too many things can't use it.</div><div class=""><br class=""></div><div class="">One aspect of this is that I'd be very surprised if OpenSAML was the only thing you'd hit problems with if you attempt to deploy things on the module path today. It may interest you to know that I surveyed all of the dependencies we ship with the IdP product, and other than our own components the only JAR which even has a reserved module names is Guava. Everything else is completely unaware of the module system and it's a toss-up whether they will work in that environment.</div><div class=""><br class=""></div><div class="">We know of a number of cases where the split package issue comes up in our code, which is one reason we don't support the module path at this point. You shouldn't expect that we will be able to address that soon. It _would_ nevertheless be useful for the longer term if you could open a JIRA case for the issue you've found so that we can make sure that we consider it for a future release.</div><div class=""><br class=""></div><div class=""><a href="https://issues.shibboleth.net/jira/projects/OSJ/" class="">https://issues.shibboleth.net/jira/projects/OSJ/</a></div><div class=""><br class=""></div><div class="">Cheers,</div><div class=""><br class=""></div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>-- Ian<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 12 Oct 2018, at 16:49, Ian Young <<a href="mailto:ian@iay.org.uk" class="">ian@iay.org.uk</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html; charset=us-ascii" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div class=""><br class=""><blockquote type="cite" class=""><div class="">On 12 Oct 2018, at 15:43, Cristi Chircu <<a href="mailto:cristian.chircu@gmail.com" class="">cristian.chircu@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 13px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Hello everyone,<span class="Apple-converted-space"> </span><br class=""><br class="">I've been using<span class="Apple-converted-space"> </span><a href="https://mvnrepository.com/artifact/org.opensaml/opensaml-core/3.3.0" target="_top" style="color: purple; text-decoration: underline;" class="">OpenSAML 3.3.0<span class="Apple-converted-space"> </span></a>for a java 8 service provider and it made my life a lot easier (thanks for sharing, by the way :) ).<span class="Apple-converted-space"> </span><br class="">Now I'm trying to upgrade to java 10 and it looks like I'm out of luck. When I try to deploy I get an exception: "java.lang.module.ResolutionException: Modules opensaml.saml.impl and opensaml.saml.api export package org.opensaml.saml.config to module jersey.client".</div></div></div></blockquote><div class=""><br class=""></div><div class="">I'm guessing that you are trying to put OpenSAML on the Java module path rather than on the classpath. We don't support that at present.</div><div class=""><br class=""></div><blockquote type="cite" class=""><div class=""><div class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 13px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">I've searched around for a bit and I can't seem to find clear information on your plans for newer java versions support.</div></div></div></blockquote><div class=""><br class=""></div><div class="">We have a page describing our approach here:</div><div class=""><br class=""></div><div class=""><a href="https://wiki.shibboleth.net/confluence/display/DEV/Java+Modularity" class="">https://wiki.shibboleth.net/confluence/display/DEV/Java+Modularity</a></div><div class=""><br class=""></div><div class="">You will be aware that we recently released a new version of the Shibboleth IdP, and in conjunction with that a new version of OpenSAML. These versions include reserved module names for the various components, and it's _possible_ that may help with the issue you're seeing. As before, though, no guarantees at this stage because we don't support use of the module path yet (we're aware of some split packages, although I don't think the one you've come across was one I was aware of).</div><div class=""><br class=""></div><div class=""><br class=""></div><blockquote type="cite" class=""><div class=""><div class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 13px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">I would like to know when you are planning to release a version that works with java 11 (since it's the newest LTS version)</div></div></div></blockquote><div class=""><br class=""></div><div class="">The IdP (which uses OpenSAML) works just fine under Java 11. Use the classpath, not the module path.</div><div class=""><br class=""></div><div class=""><br class=""></div><blockquote type="cite" class=""><div class=""><div class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 13px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">and what will your approach be regarding Oracles change to their release strategy (will you support all versions? will you support all LTS versions?).<span class="Apple-converted-space"> </span><br class=""></div></div></div></blockquote><div class=""><br class=""></div><div class=""><div class="">For more information:</div><div class=""><br class=""></div><div class=""><a href="https://wiki.shibboleth.net/confluence/display/DEV/Product+Platforms" class="">https://wiki.shibboleth.net/confluence/display/DEV/Product+Platforms</a></div><div class=""><br class=""></div><div class=""><br class=""></div></div></div><div class=""><span class="Apple-style-span" style="border-collapse: separate; font-variant-ligatures: normal; font-variant-east-asian: normal; font-variant-position: normal; line-height: normal; border-spacing: 0px; -webkit-text-decorations-in-effect: none;"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-variant-east-asian: normal; font-variant-position: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; border-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-stroke-width: 0px;"><div class=""> -- Ian<br class=""></div><div class=""><span class="Apple-style-span" style="font-size: 13px;"><br class=""></span></div></span></div></span></div></div></div></blockquote></div><br class=""></div></body></html>