Use PlexusIoResourceAttributes.UNKNOWN_OCTAL_MODE for unknown file mode #26
Conversation
This file contains 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
Plexus IO 2.7.1 introduces new constant to indicate the absence of information about a resource octal mode (permissions). Use it instead of hard-coded -1.
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.
Plexus IO 2.7.1 introduces new constant to indicate the absence
of information about a resource octal mode (permissions).
Use it instead of hard-coded
-1.Actually
AbstractArchiveruses quite a lot hard-coded-1to indicate absence of explicit file mode, but my understanding is that the others areAbstractArchiverrelated/specific and not the same asPlexusIoResourceAttributes.UNKNOWN_OCTAL_MODE. For exampleforcedFileModeset to-1means that the entry file mode will not be overridden.