On 12/12/19 2:23 PM, James Nord wrote:
For those of you that are not aware the jenkins bom is trying to solve
to problem of not consuming newer versions of libraries that are
shipped in Jenkins core as this can cause unexpected failure at
runtime, and to make keeping the versions used in step with the
Jenkins version targeted in the POM.
I really like the goals you are pursuing here, to produce a parent pom
that is more consistent and reduces problems at build and run time. It's
a hard task to get everything lined up right and it does require
"breaking some eggs".
(skipTests is a surefire flag but we abuse it to also skip spotbugs
which when you know how maven works becomes surprising)
I would really like to break that egg. That overloading is just
confusing and it causes problems when people aren't aware of its
non-standard behavior. If people need they can create local aliases or
whatever to achieve the same result. It shouldn't be in a parent pom
like this.
we have findbugs properties as well (to cope with people that are have
used a findbugs flag in their build and we now use spotbugs.
I'm in favor of breaking this egg, also. Findbugs is dead and has been
for a while. We're past the point of needing to support a migration period.
Jeff
--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/082a905a-9370-aec9-3065-9a0cad80f3bf%40cloudbees.com.
