[
https://issues.apache.org/jira/browse/OAK-6337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chetan Mehrotra resolved OAK-6337.
----------------------------------
Resolution: Fixed
Removed the deprecated method with 1801134
> Decide major version bump of o.a.j.o.api.jmx
> --------------------------------------------
>
> Key: OAK-6337
> URL: https://issues.apache.org/jira/browse/OAK-6337
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: api
> Reporter: Vikas Saurabh
> Assignee: Chetan Mehrotra
> Fix For: 1.8, 1.7.4
>
>
> With some mixup while resolving OAK-2808,
> [r1797739|https://svn.apache.org/r1797739] made into 1.7.1 release while
> [r1797778|https://svn.apache.org/1797778].
> This led to OAK-6335 once 1.7.1 was released. To fix OAK-6335, I bumped
> o.a.j.o.api.jmx from 4.6.0 to 5.0.0.
> This bump in major version might not be desirable in general (as was being
> discussed on oak-dev recently
> [here|https://lists.apache.org/thread.html/598a58727f3652f28879825ecc501b466586054a0fbd9c27b56b6338@%3Coak-commits.jackrabbit.apache.org%3E]
> \[0].
> Towards that, if we decide to change baseline plugin's config to use last
> stable branch's releases as base then we can avoid this major bump.
> [~chetanm] suggested offline that maybe we should "temporarily" add that
> removed method back with deprecated flag + revert major version bump. That
> should give us some breathing space to decide about how do we want to go
> ahead with this.
> \[0]:
> https://lists.apache.org/thread.html/598a58727f3652f28879825ecc501b466586054a0fbd9c27b56b6338@%3Coak-commits.jackrabbit.apache.org%3E
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
