[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [tycho-user] Tycho 2.4, Maven Surefire and Jacoco
|
·Switching to 2.4 without any further changes can lead to running (and
failing) maven-surefire on all bundles (both packaging eclipse-plugin
and eclipse-test-plugin), if you use a common parent POM for both.
This only happens when you are running your maven build to have some
specific test patterns this is a bug of sure-fire plugin, if you found
any other cases please report them with a simple reproducer.
The recommended workaround for this is to define the property
surefire.failIfNoSpecifiedTests=false
either on commandline or a suitable place in your pom hierarchy.
I wasn’t aware it would become active
by default for everything.
It isn't active for everything, and we haven't had to change any
integration-test in tycho because of this change. That shows that it
works for a wide range of common usecases, sad enough we don't have the
resources to take care of *every* use case of tycho especially if there
is no itest for it, so if you see room for improvement here, the best is
to provide an itest[1] so we can integrate/investigate and make sure
this specific use-case won't break your builds in the future anymore.
·If you have a bundle with packaging eclipse-plugin (not test!) mixed
into your test bundles and use Jacoco for coverage
I'm not a ware of any itest[1] that covers that combination, also here,
it would be good to have an itest so we can better support this use case.
[1] https://github.com/eclipse/tycho/wiki#providing-an-integration-test
Am 27.07.21 um 15:19 schrieb Keppler Michael (ETAS/ESW-CI) via tycho-user:
Hi folks,
Upgrading to Tycho 2.4 caused some confusion for us, therefore I want to
document that behavior for others:
·Switching to 2.4 without any further changes can lead to running (and
failing) maven-surefire on all bundles (both packaging eclipse-plugin
and eclipse-test-plugin), if you use a common parent POM for both. You
may need to bind maven-surefire with phase none for your none-test
bundles to get rid of that, or split the parent POM. This feature is
documented in release notes, but I wasn’t aware it would become active
by default for everything.
·If you have a bundle with packaging eclipse-plugin (not test!) mixed
into your test bundles and use Jacoco for coverage, you may suddenly see
maven errors about unresolved “tycho.argLine” property. Previously such
bundles were ignored by Tycho when running tests. Now they are included
(due to above changes), and they _/don’t/_ use the “tycho.argLine”
property like the test bundles, but rather the “argLine” property only
(as documented in jacoco-maven-plugin). So if you have only defined
“tycho.argLine” in your common parent and have such a bundle between
your tests, you may need to explicitly disable surefire there, too.
Mit freundlichen Grüßen / Best regards
*Michael Keppler*
Engineering Application Software - Chapter CI/CD and Common
Infrastructure Components
T +49 711 3423-2429
Michael.Keppler@xxxxxxxx <mailto:Michael.Keppler@xxxxxxxx>
ETAS GmbH, ETAS/ESW-CI
Borsigstraße 24, 70469 Stuttgart, Germany
www.etas.com <www.etas.com>*
ETAS – Driving Embedded Excellence*
Managing Directors: Christoph Hartung, Günter Gromeier, Götz Nigge
Chairman of the Supervisory Board: Dr. Walter Schirm
Registered Office: Stuttgart, Registration Court: Amtsgericht Stuttgart,
HRB 19033
_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/tycho-user
