Details
-
Improvement
-
Status: Resolved (View Workflow)
-
Major
-
Resolution: Fixed
Description
Split out from a comment in JENKINS-51594: if PluginWrapper.resolvePluginDependencies detects an apparent violation of plugin dependencies due to a version comparison involving a Maven snapshot, it should treat this as a warning rather than a hard error, since this is a developer workflow and the version comparison was not necessarily accurate.
Attachments
Issue Links
- relates to
-
JENKINS-21486 Refuse to load a plugin if dependencies are disabled or outdated
-
- Resolved
-
-
JENKINS-51594 Fix comparison of incremental versions to snapshots
-
- Resolved
-
- links to
Activity
Field | Original Value | New Value |
---|---|---|
Epic Link |
|
Link |
This issue relates to |
Status | Open [ 1 ] | In Progress [ 3 ] |
Labels | lts-candidate | lts-candidate plugin-manager |
Link |
This issue relates to |
Remote Link | This issue links to "PR 3551 (Web Link)" [ 21208 ] |
Status | In Progress [ 3 ] | In Review [ 10005 ] |
Description |
Split out from a comment in |
Split out from a comment in |
Resolution | Fixed [ 1 ] | |
Status | In Review [ 10005 ] | Resolved [ 5 ] |
Labels | lts-candidate plugin-manager | plugin-manager |
Mostly relevant for making JenkinsRule-based tests pass locally; also affects interactive run, though this can be worked around: