Unfortunately the benefits of this idea are severely diminished because Maven does not really support profile inheritance:
http://www.dashbay.com/2011/03/maven-profile-inheritance/ https://issues.apache.org/jira/browse/MNG-5127 So while we could deduplicate properties, managed dependencies, and Maven plugin configuration that takes place outside a profile (around 200 lines of duplicate code), we would not be able to deduplicate Maven plugin configuration that takes place inside a profile (about 250 lines of duplicate code). And there are other downsides: increased complexity, more involved functional testing, and slower propagation of updates, to say nothing of the effort it would take to implement. Altogether I doubt the benefits are worth the costs. -- 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/CAFwNDjpjL5caUn4VDEHE2GxHz6A-5Y0hy-fA0JXYwiUJDK4N9g%40mail.gmail.com.
