-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[kie-issues#394] Unnecessary warning when DRL file is placed in BOOT-INF/classes directory #5410
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
THanks @baldimir . Could you please replace
/
with the filesystem separator ? We have fixed that in a lot of different places, and wherever possible I think it is better (the hardcoded use of/
led to different unexpected issues on Windows machines)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@gitgabrio I'm not sure this is necessary, this is handling InternalResource so the separator should be already normalized with a '/'.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I thought the same. As far as I remember, KieMemoryFileSystem works internally with "/".
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @mariofusco @baldimir - please bear with me 🙏 😄
It may very well as you say, currently.
My concern is that the method itself is "generic", and nothing prevent that an unexpected code path, now or in the future, will get there with different separator.
IMO currently the method works only by a series of hidden side-effects.
If it is possible to use my suggestion here, I think that method would be more robust.
Side-note: I just noticed
int lastSep = fileName.lastIndexOf( "/" );
at line 372, with the same issue.
The whole point of this discussion is that if all those methods are guaranteed to work ONLY with un underlying
KieMemoryFileSystem
, then this should be enforced as much as possible: does this make sense ?(One sort of "hack" could be to add a
KieMemoryFileSystem
parameter to ththe involeved methods - even if unused - to be sure that this method get's invoked ONLY when there is an underlyingKieMemoryFileSystem
.)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changing the separator here may actually break things. Because if the KIE memory file system uses "/" everywhere internally, and we start working with the OS dependant separator here, the replace method would stop working on e.g. Windows. If we want to do a review of file separators, I would advice to do it in a separate issue, because it would be a much more complex task than changing it only here. Would that be ok please? Currently all tests pass on Windows, except a random failure reported in MBeans test (which is random because it doesn't show up in the backported PRs and the tests and the code around are pretty much the same there as far as I know).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @baldimir.
fine for me