Setting `-Dtest` on CLI cause build failure on eclipse-plugin about tycho HOT 8 CLOSED

@mickaelistria Where do I find documentation about -Dtest=... (e.g. values to use as ...?)

from tycho.

I think I found it: https://www.eclipse.org/tycho/sitedocs/tycho-surefire-plugin/test-mojo.html#test is that what you mean? Do you have an example I can use for testing?

from tycho.

For example, with rt.equinox.p2 repo, you can try mvn clean install -Pbuild-individual-bundles -Dtest=BaseChange. The expected behavior is that all modules before the test build fine, and then test will only run BaseChange.

from tycho.

I'll take a look at it.

from tycho.

This is intentional but (from my point of view) badly documented. Surefire docu says for test that

This parameter overrides the parameter includes, excludes, and the TestNG parameter suiteXmlFiles.

but in fact it enables also a check that tests are run (most probably this is expected to be used not on the root level). Sad enough the error message

No tests were executed! (Set -DfailIfNoTests=false to ignore this error.)

is misleading as failIfNoTests is false by default.

Instead one should specify failIfNoSpecifiedTests, I have raised a bug for this.

So running mvn clean install -Pbuild-individual-bundles -Dtest=BaseChange -Dsurefire.failIfNoSpecifiedTests=false should do the trick, if you think that is useful we could try to set this property (if not specified) to false by default in the project setup.

from tycho.

OK, I see this is consistent with maven-surefire-plugin.
It's a bit annoying as it basically breaks 1 useful workflow, but there are solutions (eg set test parameter in the pom.xml, combine install then verify...), so I think it's fine to just keep things as they are now in master. and don't try to support this former workflow.

from tycho.

Alright then I think this could be closed

from tycho.

I also added a warning note to the RELEASE_NOTES

from tycho.