Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[jersey-dev] Grizzly 3.0.0-M1 staged


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

This seems logical, but with this structure, Maven is absolutely hell-bent on using instead of for everything except bom/pom.xml itself.

No amount of specifying nexusUrls or other properties can convince Maven in this setup to use 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

I suspect this might have to do with bugs in Maven regarding the concept of an "aggregator root", e.g like in this bug fix:

Kind regards,
Arjan Tijms

Back to the top