feat: make the cloudnet wrapper a java agent #1839
Open
+401
−583
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.
Motivation
Having the wrapper as java agent instead of a standalone application that boots the regular application resolves issues where e.g. the application depends on SPI to get some implementation, which was not possible with the current wrapper setup.
Modification
Re-designed the wrapper to be a java agent that is attached instead of a standalone application
Result
The wrapper is an agent and we can start taking a look into sponge support again