[
https://issues.apache.org/jira/browse/OPENNLP-1708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17945168#comment-17945168
]
Nishant Shrivastava commented on OPENNLP-1708:
----------------------------------------------
Hi, I have tried to capture my understanding of the current state and the draft
modularized target state of the modules' dependencies. Would like to understand
more around the responsibility of opennlp-tools module in the target state,
does it become a maven reactor?
!image-2025-04-16-21-08-35-757.png|width=398,height=249!
!image-2025-04-16-21-23-56-036.png|width=359,height=224!
> Modularize OpenNLP
> ------------------
>
> Key: OPENNLP-1708
> URL: https://issues.apache.org/jira/browse/OPENNLP-1708
> Project: OpenNLP
> Issue Type: Epic
> Components: Command Line Interface
> Affects Versions: 2.0.0, 2.1.0, 2.2.0, 2.3.0, 2.4.0, 2.5.0
> Reporter: Martin Wiesner
> Priority: Major
> Fix For: 3.0.0
>
> Attachments: image-2025-04-16-21-08-35-757.png,
> image-2025-04-16-21-09-23-654.png, image-2025-04-16-21-23-56-036.png
>
>
> The main goal is to split the CLI parts and define a solid API module, along
> with well-structured dependent modules something like „api“, „cli“, „core“,
> „addons“, ...
> A secondary aim is to maintain backward compatibility for the CLI, ensuring
> that users can still grab the distribution binary or „opennlp-tools“ via
> Maven as before.
> By implementing these changes, we believe OpenNLP will become more modular,
> flexible, and easier to maintain. This should make it easier to integrate
> OpenNLP into core libraries while improving maintainability for future use
> cases.
> Detailed tasks related to this epic should be linked here to allow for a
> better overview on the current status.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
