[infinispan-issues] [JBoss JIRA] (ISPN-5900) Cleanup uberjar packaging (ideal solution)

[Sebastian Łaskawiec (JIRA)]

     [ https://issues.jboss.org/browse/ISPN-5900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sebastian Łaskawiec updated ISPN-5900:
--------------------------------------
    Description: 
ISPN-5838 provides a backwards compatible solution whereas an ideal solution involves also changing packages (which will fix Weld/OSGi errors) into:
* org.infinispan.cdi.common
 * org.infinispan.cdi.remote
 * org.infinispan.cdi.embedded

Client side changes:
* When client uses standard {{infinispan-cdi-remote}} or {{infinispan-cdi-embedded}} jars in his deployment, no further changes are needed (everything is being wired on CDI services level)
* However when someone uses CDI integration and JBoss Modules dependencies (e.g. in {{MANIFEST.MF}} or {{deployment-structure.xml}} and embedded mode, he will need to change the dependency to {{org.infinispan.cdi.embedded}}

  was:
ISPN-5838 provides a backwards compatible solution whereas an ideal solution involves also changing packages (which will fix Weld/OSGi errors) into:
* org.infinispan.cdi.common
 * org.infinispan.cdi.remote
 * org.infinispan.cdi.embedded



> Cleanup uberjar packaging (ideal solution)
> ------------------------------------------
>
>                 Key: ISPN-5900
>                 URL: https://issues.jboss.org/browse/ISPN-5900
>             Project: Infinispan
>          Issue Type: Feature Request
>          Components: Build process
>            Reporter: Sebastian Łaskawiec
>            Assignee: Sebastian Łaskawiec
>            Priority: Critical
>              Labels: jdg7
>
> ISPN-5838 provides a backwards compatible solution whereas an ideal solution involves also changing packages (which will fix Weld/OSGi errors) into:
> * org.infinispan.cdi.common
>  * org.infinispan.cdi.remote
>  * org.infinispan.cdi.embedded
> Client side changes:
> * When client uses standard {{infinispan-cdi-remote}} or {{infinispan-cdi-embedded}} jars in his deployment, no further changes are needed (everything is being wired on CDI services level)
> * However when someone uses CDI integration and JBoss Modules dependencies (e.g. in {{MANIFEST.MF}} or {{deployment-structure.xml}} and embedded mode, he will need to change the dependency to {{org.infinispan.cdi.embedded}}



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