Hi all, Currently the maven-hpi-plugin has a way to override the scopes for plugins to include when doing a `hpi:run`.
However the only way to configure this is to edit the pom as the config is not bound to a property. To that end I opened up https://github.com/jenkinsci/maven-hpi-plugin/pull/877 however as stated in this PR I am not convinced this is a good thing for the following reasons: 1) its too coarse grained, what about when someone does or doesn't want `optional` dependencies included (and optioanl transitive deps of plugins..)? (this would be a future enhancement I am not proposing at this time) 2) we have to maintain code that is exactly what maven would be using 3) I found very few users of this config in the jenkins github repo. (may are obsolete plugins, several just set the default anyway, and others set it but had no need to as they had no test scoped dependencies. So, the alternative is to just remove this code. This also would affect the `custom-war` mojo, but I would say if you want a different dependency set there then use a `profile` rather than scope for management. Would anyone see any reason not to remove being able to specify the scope at all? /James -- CONFIDENTIALITY NOTICE:_ This email and any attachments contain confidential and proprietary information of CloudBees intended only for the named recipient(s). Unauthorized use or distribution is prohibited. If you received this in error, please notify the sender and delete this email._ -- 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 visit https://groups.google.com/d/msgid/jenkinsci-dev/060122e4-396f-4c8b-a771-c963e391ca53n%40googlegroups.com.
