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

Issue #574: When upgrading from previous version #602

Merged
merged 1 commit into from
Feb 18, 2025
Merged

Issue #574: When upgrading from previous version #602

merged 1 commit into from
Feb 18, 2025

Conversation

CherfaElyes
Copy link
Contributor

@CherfaElyes CherfaElyes commented Feb 18, 2025 •
edited
Loading

  • Removed versions on metricshub extensions to avoid problems when unzipping a new metricshub version on the same metricshub directory where an old version is.
  • Tested on MetricsHub windows and linux.

Tests

Windows

image

Linux

image

@CherfaElyes
Issue #574: When upgrading from previous version
8a13982 
* Removed versions on metricshub extensions to avoid problems when unzipping a new metricshub version on the same metricshub directory where an old version is unzipped.
* Tested on MetricsHub windows and linux.
@CherfaElyes CherfaElyes added this to the 1.0.02 milestone Feb 18, 2025
@CherfaElyes CherfaElyes self-assigned this Feb 18, 2025
@CherfaElyes CherfaElyes linked an issue Feb 18, 2025 that may be closed by this pull request
When upgrading from previous version, it must be ensured that older extensions are removed #574
Closed
@bertysentry
Copy link
Member

Now, the same problem may arise with the ./connectors directory. I had a mix of older and new connectors, causing all sorts of warnings and errors when using MetricsHub 1.0.01. I'm wondering whether we should build a community-connectors.jar artifact, just like we do for Enterprise Edition. TBD!

@NassimBtk NassimBtk merged commit d281973 into main Feb 18, 2025
2 checks passed
@NassimBtk NassimBtk deleted the feature/issue-574-when-upgrading-from-previous-version-it-must-be-ensured-that-older-extensions-are-removed branch February 18, 2025 19:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@bertysentry bertysentry bertysentry approved these changes

@NassimBtk NassimBtk Awaiting requested review from NassimBtk

Assignees

@CherfaElyes CherfaElyes

Labels
developer_tested
Projects
None yet
Milestone
1.0.02
Development

Successfully merging this pull request may close these issues.

When upgrading from previous version, it must be ensured that older extensions are removed
3 participants
@CherfaElyes @bertysentry @NassimBtk