slachiewicz opened a new pull request, #1784: URL: https://github.com/apache/maven-site/pull/1784
The plugin testing guide told readers to extend `PlexusTestCase`, a JUnit 3 base class. It now shows plexus-testing 2.2.0's `@PlexusTest`, which starts a Plexus container per test, injects the test class's `@Inject` fields and lets you look components up from the injected `PlexusContainer`, with the POM it needs and an example. The old `#Using_PlexusTestCase` anchor still resolves. The POM imports `junit-bom` and runs sisu-maven-plugin's `main-index` goal; the text says why: plexus-testing brings a newer `junit-jupiter-api`, which without the BOM clashes with older engine jars, and the container finds `@Named` components only through the Sisu index. A plugin that inherits from the Maven parent POM gets both from its parent and only needs to add sisu-maven-plugin to `<build><plugins>`. This was meant to be part of #1781 but was pushed after it had been merged. Verified: the example built from the page's snippets passes on Maven 3.10.0 and 4.0.0-rc-7, and fails without the `junit-bom` import (`NoSuchMethodError`) or without the index (no component found); `mvn site` with Fluido 2.1.0 → no URL or content anchor lost. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
