Details
-
Story
-
Status: Resolved (View Workflow)
-
Minor
-
Resolution: Fixed
-
None
Description
Need to copy all the POM boilerplate to org.jenkins-ci:jenkins, which would also allow usage from miscellaneous components if we wanted. (Though not externally published libraries based on org.kohsuke:pom, like stapler or groovy-sandbox, or those based on com.cloudbees:cloudbees-oss-parent like groovy-cps.)
IIRC oleg_nenashev had talked about making org.jenkins-ci.plugins:plugin inherit from org.jenkins-ci:jenkins but currently it does not.
Attachments
Issue Links
- links to
Activity
Field | Original Value | New Value |
---|---|---|
Epic Link |
|
Description |
Need to copy all the POM boilerplate to {{org.jenkins-ci:jenkins}}, which would also allow usage from miscellaneous components if we wanted. (Though not externally published libraries based on {{org.kohsuke:pom}}, like {{stapler}} or {{groovy-sandbox}}, or those based on {{com.cloudbees:cloudbees-oss-parent}} like {{groovy-cps}}.) IIRC [~oleg_nenashev] had talked about making {{org.jenkins-ci.plugins:plugin}} inherit from {{org.jenkins-ci:jenkins}} but currently it does not. |
Status | Open [ 1 ] | In Progress [ 3 ] |
Remote Link | This issue links to "core PR 3394 (Web Link)" [ 20445 ] |
Status | In Progress [ 3 ] | In Review [ 10005 ] |
Link | This issue is blocked by INFRA-1583 [ INFRA-1583 ] |
Resolution | Fixed [ 1 ] | |
Status | In Review [ 10005 ] | Resolved [ 5 ] |
Yes, I was about doing JEP for that when the time comes (read as "when I have time after JEP-3"). I have a proposal draft which I can publish if you want. I did some changes in Parent POM to make them closer (Upper Bounds, FindBugs, Animal Sniffer, etc., etc.), but merging still requires some changes.
I would copy-paste your changes for now and then just remove from Plugin POM once it starts inheriting the main parent POM