Skip to content
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

Pax URL should not use GenericVersion directly [PAXURL-343] #371

Open
ops4j-issues opened this issue Jan 29, 2017 · 1 comment
Open

Pax URL should not use GenericVersion directly [PAXURL-343] #371

ops4j-issues opened this issue Jan 29, 2017 · 1 comment
Assignees
Labels

Comments

@ops4j-issues
Copy link

ŁukaszD created PAXURL-343

Currently AetherBasedResolver in some places uses custom logic to compare versions. Changing requested version passed to VersionRangeResolver delivered by aether may lead to unpredictable results if implementation is different than expected.

While I acknowledge this code is result of aether API shortcomings and lack of way to retrieve VersionScheme used for comparing artifact versions, it would be great to solve this while porting code to new maven resolver poject (successor of aether moved back to ASF).


Affects: 2.5.2
Votes: 0, Watches: 2

@ops4j-issues
Copy link
Author

Grzegorz Grzybek commented

ŁukaszD any example of such custom logic? I could take care of it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants