>>because Maven might just treat it as though it weren't set at all, and ignore >>it. One of our user pointed to the issue with empty property and I said it is bug in Maven. Somebody should fix it in Maven.
> The most useful of the three would be UNCATEGORIZED, so it can be combined > with other categories and I'd expect that would require JUnit support > underneath. No it does not need JUnit support since it is our Filters we implement and JUnit uses our filter in some kind of preprocessing of Runners. This is doable and you can open pull in GitHub, but the test result might be quite unusual: Running UncategorizedTest Tests: 0, Errors: 0, ... Skipped:5 -- Cheers Tibor --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
