laeubi commented on pull request #349: URL: https://github.com/apache/maven-surefire/pull/349#issuecomment-828650797
Well its at least confusing (for me) but I'm sure there is a good reason for it :-) I think the NULL checks are there to allow sub classes to either explicit specify a value (true/false) or to specify 'no value, use any sensible default' (null). Your change changes this logic a bit, currently it behaves (if I understand it right) that if i specify -Dtest... (isSpecificTestSpecified() returns true) the default changes to error if no test is found because it is assumed that I wan't to run at least one test ... -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
