Skip to content

FINERACT-2543: Fix SBOM generation errors and issues#5676

Open
KRYSTALM7 wants to merge 1 commit intoapache:developfrom
KRYSTALM7:FINERACT-2543-fix-sbom-eclipse-swt-exclusion
Open

FINERACT-2543: Fix SBOM generation errors and issues#5676
KRYSTALM7 wants to merge 1 commit intoapache:developfrom
KRYSTALM7:FINERACT-2543-fix-sbom-eclipse-swt-exclusion

Conversation

@KRYSTALM7
Copy link

JIRA

https://issues.apache.org/jira/browse/FINERACT-2543

Problem

SBOM generation fails with the following error:

'dependencies.dependency.artifactId' for
org.eclipse.platform:org.eclipse.swt.${osgi.platform}:jar
does not match a valid id pattern.

This occurs because org.eclipse.swt uses a platform-specific
artifact ID containing ${osgi.platform} — a Maven property
that the CycloneDX plugin cannot resolve when building the
effective POM.

Fix

Added skipConfigs to exclude eclipse and swt related
configurations from SBOM metadata resolution in the
CyclonedxDirectTask configuration in build.gradle.

Changes

  • build.gradle: Added skipConfigs.set(['.*eclipse.*', '.*swt.*']) to the CyclonedxDirectTask configuration
    to skip unresolvable eclipse/swt dependencies during
    SBOM generation.

Testing

Run the following to verify the fix:
gradlew.bat cyclonedxBom

The task should now complete without the
IllegalStateException for org.eclipse.swt.

@KRYSTALM7
Copy link
Author

Testing Notes

The original org.eclipse.swt POM resolution error is resolved
by this fix. A separate pre-existing Jackson version conflict
(CLEAR_CURRENT_TOKEN_ON_CLOSE) was encountered during testing
which is unrelated to this fix and should be tracked separately.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant