RAT-559: fix DocumentName issues in archives/on Windows#674
Conversation
|
@Claudenw test failure seem to address the problem you tried to self: |
# Conflicts: # apache-rat-core/src/main/java/org/apache/rat/configuration/XMLConfigurationReader.java
Add testing Expanded testing to include multiple file system types Fix recursion issue in DocumentName equals and compareTo Additional migration to assertj Changed File options to return DocumentName instances. Cleaned up Sonar review issues
62d2521 to
00f3079
Compare
|
@ottlinger when you get a chance would you review this please. |
ottlinger
left a comment
There was a problem hiding this comment.
Feel free to review my changes - the onliest thing to clarify would be if we need this assertDoNotThrow() at all. The rest is covered by tests and proven/secured against regressions.
Thanks for the PR!
| String[] excluded = {"some.foo", "B.bar", "justbaz"}; | ||
| try { | ||
|
|
||
| assertDoesNotThrow(() -> { |
There was a problem hiding this comment.
@Claudenw I honestly did not really get why there were these try/catch before .... if the test fails an exception should be logged properly. Not sure if all this assertDoesNotThrow() makes sense at all, but it makes logging an exception more explicit. Any particular reason for these constructs?
There was a problem hiding this comment.
They are used in the OptionTest implementations, so they have to either fail() or fail an assert.
Also, I think this was originally coded before assertDoesNotThrow was available.
# Conflicts: # src/changes/changes.xml
|



Fix for RAT-559
fixed DocumentName and DocumentName.Builder and added extensive testing to validate correctness.