[jboss-jira] [JBoss JIRA] (WFLY-6375) Identify colliding JBoss modules WRT JEP 200, section 6

[Richard Opalka (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-6375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13181134#comment-13181134 ] 

Richard Opalka edited comment on WFLY-6375 at 3/23/16 7:20 AM:
---------------------------------------------------------------

>From Jigsaw ML:
---
The six modules that you have listed here are the EE modules that are in Java SE. If you compare the output of the following commands:

  java -limitmods java.se -listmods

vs.

   java -limitmods java.se.ee -listmods

then you'll see the same six.

In all cases then the way to override/upgrade these to the EE version is to deploy the EE version of the module on the upgrade module path. In recent years then the need for app servers to upgrade JAXB and JAX-WS has diminished significantly so you might not need to upgrade both of those.

-Alan 
---


was (Author: ropalka):
>From Jigsaw ML:
---
This link didn't work for me yesterday but it does now.

The six modules that you have listed here are the EE modules that are in Java SE. If you compare the output of the following commands:

  java -limitmods java.se -listmods

vs.

   java -limitmods java.se.ee -listmods

then you'll see the same six.

In all cases then the way to override/upgrade these to the EE version is to deploy the EE version of the module on the upgrade module path. In recent years then the need for app servers to upgrade JAXB and JAX-WS has diminished significantly so you might not need to upgrade both of those.

-Alan 
---

> Identify colliding JBoss modules WRT JEP 200, section 6
> -------------------------------------------------------
>
>                 Key: WFLY-6375
>                 URL: https://issues.jboss.org/browse/WFLY-6375
>             Project: WildFly
>          Issue Type: Sub-task
>    Affects Versions: 10.0.0.Final
>            Reporter: Richard Opalka
>            Assignee: Richard Opalka
>
> JKD9 with jigsaw throws ClassNotFound exception if we're trying to 'override/enrich' JDK9 exported packages. This is collision with JEP 200, section 6: *A non-standard module must not export any standard API packages. A non-standard module may grant implied readability to a standard module.*



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)