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

Allow component upgrades to relocate own plugins #280

Merged

Conversation

1000TurquoisePogs
Copy link
Member

@1000TurquoisePogs 1000TurquoisePogs commented Sep 19, 2023

Type of change

Please delete options that are not relevant.

  • New feature (non-breaking change which adds functionality)

PR Checklist

Please delete options that are not relevant.

  • If the changes in this PR are meant for the next release / mainline, this PR targets the "staging" branch.
  • My code follows the style guidelines of this project (see: Contributing guideline)
  • New and existing unit tests pass locally with my changes
  • video or image is included if visual changes are made
  • Relevant update to CHANGELOG.md
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works, or describe a test method below

VERSION: v2.12.0
CHANGELOG: enhancement: new versions of components can change the location of their plugins, as the app-server will now re-inspect the plugin locations on each startup.

Testing

To test this you can reorganize a component you have to change the location of a plugin within.
In the example below, i previously had the plugin at '.', and moved it to 'newlocation'.
I inspected that the code worked by reading the json at the bottom after a zowe restart, and it correctly had 'newlocation'.
location-change

Signed-off-by: 1000TurquoisePogs <[email protected]>
1000TurquoisePogs and others added 2 commits September 26, 2023 09:33
Signed-off-by: 1000TurquoisePogs <[email protected]>
@1000TurquoisePogs 1000TurquoisePogs merged commit fa71348 into v2.x/staging Oct 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants