[ 
https://issues.apache.org/jira/browse/FINERACT-2745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dhroov Sankla updated FINERACT-2745:
------------------------------------
    Description: 
*Background*
During recent refactoring of JAX-RS response handling in the Mix Report module 
(FINERACT-2651 / PR #6017 and FINERACT-2670 / PR #6090), legacy technical debt 
was identified—specifically deprecated Java dependencies (such as ScriptEngine) 
and reliance on an obsolete external reporting standard (MIX XBRL).

Following a discussion thread on the official Apache DEV mailing list, 
community consensus was reached to deprecate and completely remove the MIX XBRL 
capability from upcoming releases to reduce technical debt and streamline build 
dependencies.

 *Proposed Changes*
 - Remove legacy Java controllers, services, repositories, and DTOs related to 
MIX XBRL reporting.
 - Unhook REST API endpoints and Spring configurations mapping to the MIX 
module.
 - Clean up obsolete build dependencies in `build.gradle` that were exclusively 
used by this module.
 - Remove associated unit and integration tests for the deprecated endpoints 
while ensuring the overall test suite passes cleanly.

 # 
 ## 
 ### Context / Reference

 - Dev Mailing List Thread: 
https://lists.apache.org/thread/mtp88gmrl5d3py5b7g3llo1d7lr023wv
 - Related PRs: #6017, #6090

  was:
*Background*
During recent refactoring of JAX-RS response handling in the Mix Report module 
(FINERACT-2651 / PR #6017 and FINERACT-2670 / PR #6090), legacy technical debt 
was identified—specifically deprecated Java dependencies (such as ScriptEngine) 
and reliance on an obsolete external reporting standard (MIX XBRL).

Following a discussion thread on the official Apache DEV mailing list, 
community consensus was reached to deprecate and completely remove the MIX XBRL 
capability from upcoming releases to reduce technical debt and streamline build 
dependencies.

 *Proposed Changes*
- Remove legacy Java controllers, services, repositories, and DTOs related to 
MIX XBRL reporting.
- Unhook REST API endpoints and Spring configurations mapping to the MIX module.
- Clean up obsolete build dependencies in `build.gradle` that were exclusively 
used by this module.
- Remove associated unit and integration tests for the deprecated endpoints 
while ensuring the overall test suite passes cleanly.

### Context / Reference
- Dev Mailing List Thread: [Insert link to mailing list thread if available]
- Related PRs: #6017, #6090


> Deprecate and remove obsolete MIX XBRL reporting module
> -------------------------------------------------------
>
>                 Key: FINERACT-2745
>                 URL: https://issues.apache.org/jira/browse/FINERACT-2745
>             Project: Apache Fineract
>          Issue Type: Task
>            Reporter: Dhroov Sankla
>            Priority: Major
>
> *Background*
> During recent refactoring of JAX-RS response handling in the Mix Report 
> module (FINERACT-2651 / PR #6017 and FINERACT-2670 / PR #6090), legacy 
> technical debt was identified—specifically deprecated Java dependencies (such 
> as ScriptEngine) and reliance on an obsolete external reporting standard (MIX 
> XBRL).
> Following a discussion thread on the official Apache DEV mailing list, 
> community consensus was reached to deprecate and completely remove the MIX 
> XBRL capability from upcoming releases to reduce technical debt and 
> streamline build dependencies.
>  *Proposed Changes*
>  - Remove legacy Java controllers, services, repositories, and DTOs related 
> to MIX XBRL reporting.
>  - Unhook REST API endpoints and Spring configurations mapping to the MIX 
> module.
>  - Clean up obsolete build dependencies in `build.gradle` that were 
> exclusively used by this module.
>  - Remove associated unit and integration tests for the deprecated endpoints 
> while ensuring the overall test suite passes cleanly.
>  # 
>  ## 
>  ### Context / Reference
>  - Dev Mailing List Thread: 
> https://lists.apache.org/thread/mtp88gmrl5d3py5b7g3llo1d7lr023wv
>  - Related PRs: #6017, #6090



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to