Maven Compatibility Test Failure
The automated Maven compatibility test has detected a failure with one or more Maven versions.
Details:
Possible Causes:
- A new Maven version has been released with breaking changes
- New required fields have been added to DefaultMavenPluginManager
- Method signatures have changed in Maven core classes
- New dependencies or requirements were introduced
- Our Plexus components.xml is missing field declarations
Action Required:
- Check the "Check for new Maven versions" job output to see if new versions were detected
- Check the workflow logs for specific error messages
- Download the failure logs artifact from the workflow run
- Look for error patterns:
NullPointerException → Missing field in components.xml
NoSuchMethodError → Method signature changed
NoClassDefFoundError → Missing dependency
- If NullPointerException on a field:
- Identify the missing field name from the error
- Download Maven source for that version
- Use
CHECK-MAVEN-FIELDS.sh <maven-version> to compare fields
- Update
build-info-extractor-maven3/src/main/resources/META-INF/plexus/components.xml
- Add missing field requirements to the ArtifactoryEclipsePluginManager component
- If a new Maven version was detected, update the workflow matrix to include it
Helpful Commands:
# Check for missing fields in a specific Maven version
./CHECK-MAVEN-FIELDS.sh <maven-version>
# Compare Maven's DefaultMavenPluginManager with our components.xml
# Look for new fields that need to be added
Resources:
- Maven release notes: https://maven.apache.org/docs/history.html
- Our components.xml:
build-info-extractor-maven3/src/main/resources/META-INF/plexus/components.xml
- DefaultMavenPluginManager source: Search in Maven's GitHub repository
Maven Compatibility Test Failure
The automated Maven compatibility test has detected a failure with one or more Maven versions.
Details:
Possible Causes:
Action Required:
NullPointerException→ Missing field in components.xmlNoSuchMethodError→ Method signature changedNoClassDefFoundError→ Missing dependencyCHECK-MAVEN-FIELDS.sh <maven-version>to compare fieldsbuild-info-extractor-maven3/src/main/resources/META-INF/plexus/components.xmlHelpful Commands:
Resources:
build-info-extractor-maven3/src/main/resources/META-INF/plexus/components.xml