Robert Burrell Donkin (JIRA) wrote:
[ https://issues.apache.org/jira/browse/JAMES-834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677677#action_12677677 ]
Robert Burrell Donkin commented on JAMES-834:
---------------------------------------------
AIUI these are phoenix container dependencies
(I'm still a little hazy about the way that the Spring stuff works)
Why are they needed for spring?
There are two separate issues here:
1. Broken manifests in some libs
This has nothing to do with spring. It's a problem of deploying libs
with broken manifests in a web container.
There are multiple solutions to it:
a. Fix the Manifests
b. Upgrade to a later release of the libs
c. Don't deploy the libs at all
I favor a., because the impact of b. and c. is not so easy to test,
isn't it?
2. Inclusion of any lib from phoenix-depl in spring-depl
When creating spring-depl I tried to follow a very canonical approach of
deriving spring-depl from phoenix-depl because we saw spring-depl only
as a supplemental deployment. That meant taking all of phoenix, inluding
libs and configs, not asking any questions and adopt that to spring.
I never checked libs if they are redundant in spring or anything could
be streamlined.
So, I don't know the answer to the question.
Anyone fancy any particular solution or having any other idea?
Bernd
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
