LG-4870: Drop legacy Acuant SDK relative path support#5578
Merged
Conversation
This reverts commit 965177f.
4aec134 to
3ed3505
Compare
Contributor
Author
|
Going to merge this now, since the release branch for RC165 is cut (#5601). |
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
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.
Follow-up to: #5577
Do not merge until after RC165.
This pull request reflects the original changes proposed in #5577, split to a separate pull request to be merged separately after #5577 is merged and deployed. For that reason, it should not be merged until after #5577 is fully live in production.
This will remove references to and support for Acuant paths relative to document capture step, which is now simplified in #5577 to not require symlinks or locale/flow-specific path support.