Supports repeated installation of plugins, using '#' to separate plugin copies, plugin services and configured Key information to carry class loaders #1335
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
【Fix issue】#1332
[Modified content] 1. Modified the way the plug-in manager obtains the plug-in directory when installing plug-ins, and truncated the plug-in name through the copy separator 2. Modified the method of plug-in service manager to identify plug-in services, adding a new class loader to the identification content 3 , Modified the method of plug-in configuration manager to identify plug-in configuration, and added a new class loader to the identification content.
[Use case description] New use case 1. Static installation of multi-copy plug-ins 2. Dynamic installation of multi-copy plug-ins 3. Install copy plug-ins to test plug-in service differentiation 4. Install copy plug-ins to test plug-in configuration differentiation 5. Install copy plug-ins to test bytecode capabilities Take effect
[Self-test situation] 1. The local static check has passed; 2. Baseline use case integration test, new use cases are manually covered
[Scope of impact] 1. Is there any impact on users' use (such as API modifications and startup parameter modifications)? 2. Is it necessary to update some documents (such as user manuals)