FINERACT-2543: Fix SBOM generation errors and issues#5676
Conversation
Testing NotesThe original org.eclipse.swt POM resolution error is resolved |
|
@KRYSTALM7 Please fix the failing checks and make sure you are signing your commits with GPG |
614c3a3 to
9944fed
Compare
|
Hi @adamsaghy, thank you for the feedback! I have configured GPG signing for my commits. Happy to address any other feedback! |
|
Here's one of the failed case-
|
9944fed to
e0b5d59
Compare
|
Hi @adamsaghy,@airajena, I have re-run the required checks after updating the fix:
Both commands completed successfully with a green build.
The fix adds Please let me know if any further changes are needed! |


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
skipConfigs.set(['.*eclipse.*', '.*swt.*'])to theCyclonedxDirectTaskconfigurationto 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.