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.

Sign up for GitHub

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

Jump to bottom

org.apache.commons.jxpath went from 1.3.0.v200911051830 to just 1.3.0 #47

Closed
andrew-tram opened this issue Feb 21, 2025 · 1 comment
Closed

org.apache.commons.jxpath went from 1.3.0.v200911051830 to just 1.3.0 #47

andrew-tram opened this issue Feb 21, 2025 · 1 comment

Comments

@andrew-tram
Copy link

Somewhere between 2022-03 and 4.29-ish, org.apache.commons.jxpath went from 1.3.0.v200911051830 to just 1.3.0 which causes Eclipse to do an update on the plugin, I believe.

So if an 4.31 RCP app packages 1.3.0 and an update-site has 1.3.0.qualifier, it'll trigger an update as I guess Eclipse thinks the one with the qualifier is "newer."
@merks
Copy link
Contributor

merks commented Feb 21, 2025

Yes the older one’s version is higher and given a choice p2 will tend to install it. That’s just how it is.

@merks merks closed this as not planned Won't fix, can't repro, duplicate, stale Mar 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@merks @andrew-tram