-
-
Notifications
You must be signed in to change notification settings - Fork 289
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
Ensure that plugin dependencies are aligned with JFR requirements + Remove the obsolete databound
demo and test
#430
Ensure that plugin dependencies are aligned with JFR requirements + Remove the obsolete databound
demo and test
#430
Conversation
jfr.version
+ Ensure that plugin dependencies are aligned with JFR requirements
So this is also "solves" #392 for Custom WAR Packager based flows |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me.
I will merge it to get the boilerplate development going. As documented in jenkinsci/custom-war-packager#193 , it leads to a Custom WAR Packager flow incompatibility, at least for the development versions. |
jfr.version
+ Ensure that plugin dependencies are aligned with JFR requirementsjfr.version
+ Ensure that plugin dependencies are aligned with JFR requirements + remove the obsolete databound
demo and test
jfr.version
+ Ensure that plugin dependencies are aligned with JFR requirements + remove the obsolete databound
demo and testdatabound
demo and test
Contributes to #344 . After this patch, it will be possible to use custom versions in children packaging POMs.
[ ] Allow using custom version numbers in child packaging POMsReverted in Revert the jfr.version support and minimun Jenkins core version #434[ ] Allow setting a Jenkinsfile Runner version viaReverted in Revert the jfr.version support and minimun Jenkins core version #434jfr.version