In #56, we implemented custom parsers and representations for semantic version numbers and Maven version ranges. Currently, they are only available as "standalone" functionalities for users to include in their analyses, but not used in our internal POM file resolution process - for the latter, we currently depend on external libraries.
I'd would be nice to include our own version range handling in the core pom resolution process - it would allow us to reduce our large amount of dependencies, and give us more control about the resolution process. Of course, equality of resolution must be ensured (compared to the current implementation / Maven default).
In #56, we implemented custom parsers and representations for semantic version numbers and Maven version ranges. Currently, they are only available as "standalone" functionalities for users to include in their analyses, but not used in our internal POM file resolution process - for the latter, we currently depend on external libraries.
I'd would be nice to include our own version range handling in the core pom resolution process - it would allow us to reduce our large amount of dependencies, and give us more control about the resolution process. Of course, equality of resolution must be ensured (compared to the current implementation / Maven default).