Unnamed module and duplicate package

[Alan Bateman]

On 11/03/2016 04:02, Stephen Felts wrote:
> :
>   
>
> The Java EE folks are aware of the problems with both the  transaction and annotation jars.  One of the outstanding issues I have is to get official copies of these module jar files.  Also, the current approach requires two associated jar files on the module path,
>
> javax.enterprise.cdi.api.jar and javax.interceptor.javax.interceptor.api.jar, because of dependencies.  I think the plan is to handle the dependencies so those jar files are not needed.
>
>
Just to add to Stephen's note. The EE version of the java.transaction 
module that Stephen with WebLogic has additional dependences. This 
creates a migration challenge as we are trying to deploy a library as a 
module when it depends on other libraries that have not yet migrated to 
modules. Here is where automatic modules comes in because these 
dependences can be put on the application module path and work as 
automatic modules. They in turn might have to link to types on the class 
path, something that automatic modules can do. It of course makes the 
deployment a bit more complicated but that's another discussion.

-Alan.