Reverting XML namespaces from V2 back to V1#244
Merged
Zakaria-Kofiro merged 1 commit intomasterfrom Jun 9, 2023
Merged
Conversation
kevin-mcgoldrick
approved these changes
Jun 9, 2023
shawn-h-park
approved these changes
Jun 9, 2023
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
title: - Reverting XML namespaces from V2 back to V1
Tank tools currently running the V1 API are expecting NAMESPACE_V1 from Tank XML files, while the namespace for several models has been updated to V2. To remediate this issue, it will need to be reverted back to V1 to work with the current V1 tools. It will be kept at V1 since a namespace version update is not needed for continued functionality.
Please make sure these check boxes are checked before submitting
mvn clean test -P default** PR review process **