Java dependency diff

🔄 camunda-root: 7.22.0-SNAPSHOT => 7.22.0-SNAPSHOT  
 └─ 🔄 camunda-parent: 7.22.0-SNAPSHOT => 7.22.0-SNAPSHOT  
     └─ 🔄 camunda-database-settings: 7.22.0-SNAPSHOT => 7.22.0-SNAPSHOT  
         └─ 🔄 camunda-tomcat: 7.22.0-SNAPSHOT => 7.22.0-SNAPSHOT  
             ├─ 🔄 camunda-tomcat-assembly: 7.22.0-SNAPSHOT => 7.22.0-SNAPSHOT  
             │   └─ ⬆ tomcat: 9.0.85 ❓ => 9.0.89 ❓  
             └─ 🔄 camunda-bpm-tomcat: 7.22.0-SNAPSHOT => 7.22.0-SNAPSHOT  
                 └─ 🔄 camunda-tomcat-assembly: 7.22.0-SNAPSHOT => 7.22.0-SNAPSHOT  
                     └─ ⬆ tomcat: 9.0.85 ❓ => 9.0.89 ❓

Module details

tomcat:9.0.85

Declared licenses: None Links: None

tomcat:9.0.89

Declared licenses: None Links: None

Checklist

Unique changes

[x] tomcat: 9.0.85 ❓ => 9.0.89 ❓

Unique additions

Developer comments

Glossary

Limitations

The reported transitive dependencies may not always be accurate in a multi-module project. The SBOM file format represents a unique dependency (coordinates + type) only once. In a multi-module project a dependency can be declared in multiple locations with different exclusions of transitive dependencies or different version overrides for transitive dependencies.

Emojies

✔: All licenses are on the Go list
⚠: (At least one) license is on the Caution list
❌: (At least one) license is on the Stop list
❓: (At least one) license cannot be determined or is unknown
‼: Dependency has multiple licenses declared
⬆: New dependency version is higher than previous
⬇: New dependency version is lower than previous
🔄: Dependency version is equal and the dependencies of this component changed (e.g. when comparing snapshots)
🤷: The change of the dependency version can not be determined further (e.g. because the version does not follow semantic versioning)

psavidis commented 2 weeks ago

License Check

✔ Tomcat 9.0.89 uses Apache License 2.0 which falls under the Go List

License check Passed Successfully