Should jenkinsci/plugin-pom be made to inherit from jenkinsci/pom? jenkinsci/plugin-pom duplicates a large amount of material from jenkinsci/pom, and inheriting it instead would greatly ease maintenance by allowing the duplicate material to be deleted. There are only a few things in jenkinsci/pom that we do _not_ want to be inherited by plugins:
- Top-level URL: This can simply be deleted from jenkinsci/pom after verifying that all core components have it. - Mailing lists, issue management, and CI management: These can simply be moved to jenkinsci/jenkins or deleted. - A managed dependency on a specific version of SpotBugs annotations: this is inappropriate for plugins because they get their copy of SpotBugs annotations via their Jenkins core dependency. This can simply be deleted from jenkinsci/pom and inlined into core and core components (if needed). - FindSecBugs. Similarly, this can simply be deleted from jenkinsci/pom and inlined into core and core components (if needed). Altogether I think such a change, while not trivial, is likely feasible. Does anyone have any opinions about whether or not we should do this? -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAFwNDjokzBBrX5r40EWG9WX%2BrPRmXhsxsY0bUwqQfZAnFnv8Uw%40mail.gmail.com.
