Ok, I know that the OSGi tests were running on commit
2ec1117fec41919a68d04ba3a51724562e3b46f8 ("Updating Jetty to
9.4.34.v20201102", made by Colm on Nov 6th) and stopped being run with
commit 04212704be56cdcb750ca571081a5e55fa03bfb8 ("Started the migration
to Junit 5", made by me on Dec, 23th).
On 12/05/2021 09:18, Emmanuel Lécharny wrote:
Will analyse further tonite.
FTR I have added a test class, which get executed, which means the tests
are somehow visible. May be an issue with the RunWith(PaxExam.class) ?
On 12/05/2021 06:47, Stefan Seelmann wrote:
On 5/11/21 11:45 PM, Emmanuel Lécharny wrote:
And after going back to the existing project (44) parent, I can't have
the osgi-integ test run at all :
[INFO] --- maven-surefire-plugin:3.0.0-M3:test (default-test) @
apacheds-osgi-integ ---
[INFO]
[INFO] -------------------------------------------------------
[INFO] T E S T S
[INFO] -------------------------------------------------------
[INFO]
[INFO] Results:
[INFO]
[INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO]
...
This is more than bizarre...
Same happens currently in master e.g. on Jenkins. I assume we need to
add the junit-vintage dependency.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
--
*Emmanuel Lécharny - CTO* 205 Promenade des Anglais – 06200 NICE
T. +33 (0)4 89 97 36 50
P. +33 (0)6 08 33 32 61
[email protected] https://www.busit.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
