[
https://issues.apache.org/jira/browse/AMQ-9161?focusedWorklogId=825808&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-825808
]
ASF GitHub Bot logged work on AMQ-9161:
---------------------------------------
Author: ASF GitHub Bot
Created on: 14/Nov/22 15:55
Start Date: 14/Nov/22 15:55
Worklog Time Spent: 10m
Work Description: mattrpav commented on PR #931:
URL: https://github.com/apache/activemq/pull/931#issuecomment-1313975488
> If that's the intention then I'd spell it out more clearly in the JIRA so
folks can see.
JIRA updated with those notes, and I went ahead and added a task to
@Deprecate the JDBC Journal now, so it'll be in 5.18.0 as deprecated.
Issue Time Tracking
-------------------
Worklog Id: (was: 825808)
Time Spent: 1h (was: 50m)
> Relocate activeio classes to activemq-jdbc-store and deprecate JDBC Journal
> ---------------------------------------------------------------------------
>
> Key: AMQ-9161
> URL: https://issues.apache.org/jira/browse/AMQ-9161
> Project: ActiveMQ
> Issue Type: Task
> Reporter: Matt Pavlovich
> Assignee: Matt Pavlovich
> Priority: Major
> Fix For: 5.18.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> The activeio dependency is very dated. Currently, the only module using any
> classes is the activemq-jdbc-store.
> This JIRA will relocate the activeio classes to the jdbc module and remove
> the activeio dependency.
> The intent of this changes is to take a step forward towards eventual removal
> of the JDBC Journal. This approach is lieu of an activeio upgrade + release
> so we can make the breaking change (remove activeio and deprecate JDBC
> Journal) in 5.18.0 and then complete the removal in 5.18.x point release or
> 5.19.x.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
