-
Notifications
You must be signed in to change notification settings - Fork 196
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[sbom] BOM is calculated multiple times for the same unit #3911
Comments
Unless I'm missing something, you're talking about CycloneDX generating both an XML and a JSON file? Edit: |
yes :-) |
To briefly describe what's happening: Each IU is listed twice in the SBOM. Once as a dependency of the current artifact (repository) and once as a separate component (example.feature) with its own dependencies. The IU should effectively be unmodifiable within the same reactor build, so I'll see if one can simply cache the BOM representation. Example:
|
The BOM representation is currently calculated twice for each artifact. Within a reactor build, such IUs should always produce the same BOM representation and should therefore be cached. Resolves eclipse-tycho#3911
The BOM representation is currently calculated twice for each artifact. Within a reactor build, such IUs should always produce the same BOM representation and should therefore be cached. Resolves eclipse-tycho#3911
The BOM representation is currently calculated twice for each artifact. Within a reactor build, such IUs should always produce the same BOM representation and should therefore be cached. Resolves eclipse-tycho#3911
The BOM representation is currently calculated twice for each artifact. Within a reactor build, such IUs should always produce the same BOM representation and should therefore be cached. Resolves eclipse-tycho#3911
The BOM representation is currently calculated twice for each artifact. Within a reactor build, such IUs should always produce the same BOM representation and should therefore be cached. Resolves eclipse-tycho#3911
The BOM representation is currently calculated twice for each artifact. Within a reactor build, such IUs should always produce the same BOM representation and should therefore be cached. Resolves eclipse-tycho#3911
The BOM representation is currently calculated twice for each artifact. Within a reactor build, such IUs should always produce the same BOM representation and should therefore be cached. Resolves #3911
While debugging some problems with changes in Tycho I noticed the following message:
As one can see error/warning printed twice, so it seems the bom is also computed twice for
org.eclipse.update.feature
!@ptziegler do you like to take a look? It might not be a problem for small examples, but with larger products/sites it can easily become a performance bottleneck.
The text was updated successfully, but these errors were encountered: