Aias00 opened a new issue, #7295:
URL: https://github.com/apache/shenyu/issues/7295

   ## Background
   
   Motan runtime code and its Spring Boot starter were copied to 
`apache/shenyu-plugin-store` in PRs 
[#1](https://github.com/apache/shenyu-plugin-store/pull/1) and 
[#3](https://github.com/apache/shenyu-plugin-store/pull/3). The main repository 
later removed Motan support in commit 
[338ea9adaf](https://github.com/apache/shenyu/commit/338ea9adaf), but the store 
copy still depends on Motan-specific classes removed from ShenYu core, 
including `PluginEnum.MOTAN`, `RpcTypeEnum.MOTAN`, Motan DTOs/constants, and 
result codes.
   
   The migration is therefore present as source code but is not yet a 
buildable, releasable, or E2E-verified external plugin.
   
   Depends on #7294.
   
   ## Scope
   
   ### plugin-store
   
   - Rebase the Motan plugin and starter onto the supported ShenYu 
external-plugin API.
   - Move Motan-owned identifiers, configuration DTOs, result mapping, and 
protocol constants out of ShenYu core dependencies or replace them with the 
agreed generic extension contract.
   - Retain Spring Boot 2/3 auto-configuration metadata only where it matches 
the supported compatibility matrix.
   - Restore and expand unit tests for plugin execution, metadata/config 
refresh, proxy/cache lifecycle, and starter loading.
   - Add a real E2E scenario with a Motan provider, gateway, admin/config 
setup, successful invocation, invalid metadata/body handling, and config 
refresh.
   - Document Motan and JDK/framework compatibility and mark the plugin 
maintenance status clearly.
   
   ### apache/shenyu and companion repositories
   
   - Remove stale Motan dependency-governance and distribution LICENSE entries 
that were reintroduced after the source removal; retain historical release 
notes and upgrade SQL.
   - Decide whether client registration remains supported. If yes, maintain it 
in the authoritative client repository and cover registration-to-invocation 
E2E; if no, document manual metadata registration.
   - Ensure no current distribution or default bootstrap contains Motan 
artifacts.
   
   ## Acceptance Criteria
   
   - [ ] Motan plugin and starter build against the declared ShenYu release 
without restored Motan-specific core enums/DTOs.
   - [ ] Unit tests run in CI and cover success, failure, metadata refresh, and 
resource cleanup.
   - [ ] E2E starts a real Motan provider and proves gateway invocation and 
dynamic config update.
   - [ ] The produced artifacts can be consumed by a minimal ShenYu bootstrap.
   - [ ] Main-repository stale docs/licenses are cleaned without rewriting 
historical migrations.
   - [ ] Support/deprecation status and rollback instructions are documented.
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to