[
https://issues.apache.org/jira/browse/ACCUMULO-3942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14639632#comment-14639632
]
Christopher Tubbs commented on ACCUMULO-3942:
---------------------------------------------
I implemented the {{combine.self}} solution, because it was the smallest
change, and easiest to explain why it works (if anybody asks).
However, I'm still not 100% certain *why* it was failing to begin with. The
PluginIT should have behaved like any IT in the test module without a Category,
but it wasn't. It was executing no tests, and showing the following, even when
I configured invoker to pass "-Dit.test=PluginIT", explicitly:
{code}
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
{code}
My best guess (after much debugging and trying various things) is that, for
some reason, the invoker plugin was constructing an environment such that an
older version of JUnit (4.7?), which didn't support categories as well, was on
the classpath instead of 4.11, which we specify in the parent pom.
> PluginIT fails
> --------------
>
> Key: ACCUMULO-3942
> URL: https://issues.apache.org/jira/browse/ACCUMULO-3942
> Project: Accumulo
> Issue Type: Bug
> Reporter: Christopher Tubbs
> Assignee: Christopher Tubbs
> Fix For: 1.8.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> PluginIT fails to run its junit tests under normal circumstances.
> Can easily reproduce with:
> {code}
> mvn clean verify -Dtest=42 -Dit.test=42 -DfailIfNoTests=false \
> -Drat.skip -Dcheckstyle.skip -Dfindbugs.skip
> {code}
> The problem appears that surefire is not triggering inside the invoked
> project and the tests never create the files which the groovy script checks
> for to determine whether the plugin was successful.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
