I just (finally) staged Grizzly 3.0.0-M1. Besides the issues with the CI (which hadn't been migrated yet, and had issues with expired certificates etc), a major issue was in the way how Grizzly uses a bom.
In essence the logical structure is:
- pom.pom extends bom/pom.xml
- bom/pom.xml extends EE4J 1.0.6 pom
No amount of specifying nexusUrls or other properties can convince Maven in this setup to use jakarta.oss.sonatype.org
. The phrase stubborn as a mule comes to mind here.
Investigating a number of other projects that use boms, it seems the "solution" is to put an extra subdirectory in between:
- pom.pom extends boms/bom/pom.xml
- boms/bom/pom.xml extends EE4J 1.0.6 pom