This repository has been archived by the owner on Dec 13, 2023. It is now read-only.
Migrate conductor JAXB dependency from javax. to jakarta #2497
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.
The conductor has JAXB dependency on javax.* which should be migrated
to jakarta.*.
Signed-off-by: Tao Jiang taoj@vmware.com
Pull Request type
Changes in this PR
The conductor has JAXB dependency on javax.* which should be migrated to jakarta.* due to some legal issues. We, VMware, use and build the conductor as a library into our own service for internal CI/CD requirements. This change will also avoid library clashes.
Describe the new behavior from this PR, and why it's needed
Issue #2495
Alternatives considered
Deploy vanilla Conductor as standalone service. However, we have totally replaced the API layer with our own implementation in order to support using ASL (Amazon State Language) as DSL and security enhancement. It will be much less efficient to keep the conductor's API layer.
Describe alternative implementation you have considered