If the third party library is incompatible with the new version and the
old version (such as lucene3.5.0-5.5.2), and the dependent version of
Ignite is older, it may cause conflicts in the user's system.
For such scenarios, I think that updating third-party dependencies's
major version is valuable.
在 2017/8/17 上午8:26, Denis Magda 写道:
I would respond why do we need to update? Some bug, new capabilities, security
breach? Alexey K., please shed some light on this.
—
Denis
On Aug 16, 2017, at 5:12 PM, Dmitriy Setrakyan <dsetrak...@apache.org> wrote:
On Wed, Aug 16, 2017 at 5:02 PM, Denis Magda <dma...@apache.org> wrote:
Honestly, I wouldn’t touch a dependency if it works like a charm and
nobody requested us to migrate to a new version.
Why do you need to update Apache Common coded?
Not sure I agree. Why not update it?
—
Denis
On Aug 16, 2017, at 10:36 AM, Alexey Kuznetsov <akuznet...@apache.org>
wrote:
Done
https://issues.apache.org/jira/browse/IGNITE-6090
On Wed, Aug 16, 2017 at 8:01 PM, Dmitriy Setrakyan <
dsetrak...@apache.org>
wrote:
The answer is Yes, we should update. Jira ticket assigned to the next
release should be enough in my view.
D.
On Wed, Aug 16, 2017 at 2:38 AM, Alexey Kuznetsov <
akuznet...@apache.org>
wrote:
Hi, All!
Do we have any policy for updating third-party dependencies?
For example, I found that we are using very old Apache Common codec
v.1.6
(released in 2011)
And latest is Apache Common codec v.1.10
Do we need to update to new versions from time to time?
And how?
Just create JIRA issue, update pom.xml and run all tests on TC - will
be
enough?
--
Alexey Kuznetsov
--
Alexey Kuznetsov
