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

The older versions showing up as the latest in maven central/IntelliJ #110

Closed
QAInsights opened this issue Apr 27, 2022 · 5 comments
Closed

Comments

@QAInsights
Copy link

The older version of JMeter DSL is showing as the latest. Could you please check the issue? Please see the below screenshots.

image

image

@rabelenda
Copy link
Contributor

Hello @QAInsights , nice to see you around :).

Thank you for brining this!

This is a known issue due to a mistake when we tried to do a release (we missed a dot). Sadly, we can't remove the version from maven repository, here is our request and as much we got was the removal of the jar, so, if anyone tries to use that version, it will fail.

The only way I see to overcome this issue right now is to change jmeter dsl coordinates (change maven group id or artifact id). We have plans to do at near/medium term a major release (1.0) and when we do that we will probably change artifacts coordinates (to fix this issue at the same time), but, meanwhile, I don't think is worth changing it before such release due to the level of impact of changing coordinates vs leaving current issue.

Does anyone have other ideas?

Regards

@QAInsights
Copy link
Author

Thanks, @rabelenda :) I understand. I can wait for 1.0. Is it possible to highlight this somewhere in the docs? It would be helpful for newbies like me.

@kirillyu
Copy link
Contributor

maybe we can to release 1.0 and probably it should fix it?

@rabelenda
Copy link
Contributor

Before doing release 1.0 we want to review API compatibility with some changes we plan to do in the near future, and would like to avoid releasing 1.0 to soon after having to release 2.0. We will keep this issue open until we fix this, and hope to have a fix/release soon.

@rabelenda
Copy link
Contributor

Today we released 1.0, so this should no longer be an issue.

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

No branches or pull requests

3 participants