Multiple versions of a non-exported dependency

[cowwoc]

Remi,

I don't understand what you mean by "resolve incompatible versions". All 
I am asking the JDK to do is note the version number associated with a 
dependency and expose it using reflection for tools to use. Which part 
of this causes you problems?

Gili

On 2016-08-31 5:35 PM, Remi Forax [via jigsaw-dev] wrote:
> I think Alex is too gentle,
> I don't want the JDK dictate to me how to resolve incompatible versions,
> JBoss has it's own way to resolve versions, OSGI has another way, etc,
> I don't want a n+1 way to resolve incompatible versions.
>
> https://xkcd.com/927/
>
> Rémi
>
> ----- Mail original -----
> > De: "Alex Buckley" <[hidden email] 
> </user/SendEmail.jtp?type=node&node=5713380&i=0>>
> > À: [hidden email] </user/SendEmail.jtp?type=node&node=5713380&i=1>
> > Envoyé: Mercredi 31 Août 2016 22:07:59
> > Objet: Re: Multiple versions of a non-exported dependency
>
> > On 8/31/2016 12:51 PM, cowwoc wrote:
> >> I agree that the situation is better, but not by much. Developers
> >> routinely run across transitive dependencies that are incompatible 
> with
> >> each other. You seem to be under the impression that this a rare
> >> occurrence or only occurs in the context of web containers, but 
> this is
> >> simply not the case.
> >
> > We're not under this impression at all. The problem is that the cost of
> > solving incompatible indirect dependencies is high -- it would mean
> > introducing first-class versions and changing the class loading
> > characteristics of regular ('java'-launched) applications. Project
> > Jigsaw chose a long time ago to let tools handle the version selection
> > problem while it pursues other areas, namely strong encapsulation and
> > "modules all the way down" (the modular JDK). I see no reason why a
> > future project that wanted to introduce first-class versions 
> couldn't do
> > it on top of JDK 9.
> >
> > Alex
>
>
> ------------------------------------------------------------------------
> If you reply to this email, your message will be added to the 
> discussion below:
> http://jigsaw-dev.1059479.n5.nabble.com/Multiple-versions-of-a-non-exported-dependency-tp5713364p5713380.html 
>
> To unsubscribe from Multiple versions of a non-exported dependency, 
> click here 
> <http://jigsaw-dev.1059479.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5713364&code=Y293d29jQGJicy5kYXJrdGVjaC5vcmd8NTcxMzM2NHwxNTc0MzIxMjQ3>.
> NAML 
> <http://jigsaw-dev.1059479.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> 
>






--
View this message in context: http://jigsaw-dev.1059479.n5.nabble.com/Multiple-versions-of-a-non-exported-dependency-tp5713364p5713381.html
Sent from the jigsaw-dev mailing list archive at Nabble.com.