You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
https://github.com/jenkinsci/plugin-pom/blob/a316c25e449b4ba43267a97fedc17cec74c9253a/pom.xml#L779 is useful enough that Jenkins core also defines it. I think it would make more sense for this to be defined in the parent POM so that it applies to all Jenkins core components (consistent with it being applied to all Jenkins plugins), at which point the customization could be removed from core.
The text was updated successfully, but these errors were encountered:
Should this issue be assigned to you? As far as I can tell jenkinsci/plugin-pom#92 was incomplete in that it applied to only one of our two parent POMs. In general any change that is made to one parent POM should also be applied to the other, unless there is a compelling reason to increase the already large technical debt of having two largely duplicate parent POMs. Yes this is painful but that should also serve as an incentive to unify the two POMs.
https://github.com/jenkinsci/plugin-pom/blob/a316c25e449b4ba43267a97fedc17cec74c9253a/pom.xml#L779 is useful enough that Jenkins core also defines it. I think it would make more sense for this to be defined in the parent POM so that it applies to all Jenkins core components (consistent with it being applied to all Jenkins plugins), at which point the customization could be removed from core.
The text was updated successfully, but these errors were encountered: