Skip to content

Fix Apache Tomcat Importer by not using Semver#1791

Open
kunalsz wants to merge 2 commits intoaboutcode-org:mainfrom
kunalsz:fix-tomcat
Open

Fix Apache Tomcat Importer by not using Semver#1791
kunalsz wants to merge 2 commits intoaboutcode-org:mainfrom
kunalsz:fix-tomcat

Conversation

@kunalsz
Copy link

@kunalsz kunalsz commented Mar 1, 2025

In reference to the issue #1555

Changes made:

  • Usage of Semver versioning is removed which was creating problems
  • Only Maven versioning is being used

Apache Tomcat Versioning Overview

Apache Tomcat versions follow a Maven-like versioning scheme, which can include:

  • Milestone versions (e.g., 9.0.0.M1)
  • Release candidates (e.g., 8.0.0.RC1)
  • Regular numeric versions (e.g., 8.5.32)

This is not Semver-compliant, but Maven versioning handles all of these cases

@TG1999 looking forward to your insights !

kunalsz added 2 commits March 1, 2025 14:17
Signed-off-by: kunalsz <kunalavengers@gmail.com>
Signed-off-by: kunalsz <kunalavengers@gmail.com>
@kunalsz kunalsz changed the title Fixed Apache Tomcat Importer by not using Semver Fix Apache Tomcat Importer by not using Semver Mar 26, 2025
Copy link
Member

@keshav-space keshav-space left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@kunalsz IMO this is not the right approach instead we should fix the version_class in upstream univers ApacheVersionRange.

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.

2 participants

Comments