Github user kirklund commented on the issue:
https://github.com/apache/geode/pull/403
I think I should pull this in before applying
https://reviews.apache.org/r/56934/. My changes for GEODE-2460 are missing the
webapp NOTICE changes and the change to gradle/dependency-resolution.gradl
Github user jaredjstewart commented on the issue:
https://github.com/apache/geode/pull/403
It seems like it might be simpler to add an explicit dependency for
commons-beanutils to geode-core. That way if we later introduce some new
dependency which requires say commons-beanutils 1.10
Github user metatype commented on the issue:
https://github.com/apache/geode/pull/403
In this case geode-pulse uses commons-beanutils v1.9.3 while geode-core is
pulling in commons-beanutils v1.8.3 via shiro-core. The version is different
between `lib/*` and `geode-pulse-*.war`.
Github user jaredjstewart commented on the issue:
https://github.com/apache/geode/pull/403
Can you explain why the version override strategy is necessary? I think
geode-pulse (or any other submodule with an explicit dependency on
commons-beantuils) should end up with version 1.9.3 al
Github user metatype commented on the issue:
https://github.com/apache/geode/pull/403
@upthewaterspout @scmbuildguy
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and w
