[JBoss JIRA] (ISPN-12342) Add Dependencies Manifest header to Spring artifacts
by Philippe Marschall (Jira)
[ https://issues.redhat.com/browse/ISPN-12342?page=com.atlassian.jira.plugi... ]
Philippe Marschall updated ISPN-12342:
--------------------------------------
Status: Pull Request Sent (was: Open)
> Add Dependencies Manifest header to Spring artifacts
> ----------------------------------------------------
>
> Key: ISPN-12342
> URL: https://issues.redhat.com/browse/ISPN-12342
> Project: Infinispan
> Issue Type: Patch
> Components: Spring Integration
> Reporter: Philippe Marschall
> Priority: Major
>
> We deploy a Spring application inside of WildFly. We use the Infinispan Spring integration to access Infinispan from WildFly through the Spring Cache abstraction.
>
> The Infinispan Spring integration artifacts are part of our deployment but Infinispan is not. The Infinispan Spring integration artifacts instead access the Infinispan modules in WildFly.
>
> This means that we'll either have to add a Dependencies manifest header to our deployment or use jboss-deployment-structure.xml. If instead the Infinispan Spring integration artifacts had a Dependencies manifest header then that step would be redundant.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 6 months
[JBoss JIRA] (ISPN-12342) Add Dependencies Manifest header to Spring artifacts
by Philippe Marschall (Jira)
[ https://issues.redhat.com/browse/ISPN-12342?page=com.atlassian.jira.plugi... ]
Philippe Marschall updated ISPN-12342:
--------------------------------------
Status: Open (was: New)
> Add Dependencies Manifest header to Spring artifacts
> ----------------------------------------------------
>
> Key: ISPN-12342
> URL: https://issues.redhat.com/browse/ISPN-12342
> Project: Infinispan
> Issue Type: Patch
> Components: Spring Integration
> Reporter: Philippe Marschall
> Priority: Major
>
> We deploy a Spring application inside of WildFly. We use the Infinispan Spring integration to access Infinispan from WildFly through the Spring Cache abstraction.
>
> The Infinispan Spring integration artifacts are part of our deployment but Infinispan is not. The Infinispan Spring integration artifacts instead access the Infinispan modules in WildFly.
>
> This means that we'll either have to add a Dependencies manifest header to our deployment or use jboss-deployment-structure.xml. If instead the Infinispan Spring integration artifacts had a Dependencies manifest header then that step would be redundant.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 6 months
[JBoss JIRA] (ISPN-12342) Add Dependencies Manifest header to Spring artifacts
by Philippe Marschall (Jira)
[ https://issues.redhat.com/browse/ISPN-12342?page=com.atlassian.jira.plugi... ]
Philippe Marschall updated ISPN-12342:
--------------------------------------
Git Pull Request: https://github.com/infinispan/infinispan/pull/8704
> Add Dependencies Manifest header to Spring artifacts
> ----------------------------------------------------
>
> Key: ISPN-12342
> URL: https://issues.redhat.com/browse/ISPN-12342
> Project: Infinispan
> Issue Type: Patch
> Components: Spring Integration
> Reporter: Philippe Marschall
> Priority: Major
>
> We deploy a Spring application inside of WildFly. We use the Infinispan Spring integration to access Infinispan from WildFly through the Spring Cache abstraction.
>
> The Infinispan Spring integration artifacts are part of our deployment but Infinispan is not. The Infinispan Spring integration artifacts instead access the Infinispan modules in WildFly.
>
> This means that we'll either have to add a Dependencies manifest header to our deployment or use jboss-deployment-structure.xml. If instead the Infinispan Spring integration artifacts had a Dependencies manifest header then that step would be redundant.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 6 months