On Fri, Oct 3, 2014 at 11:29 AM, Scott Wolk <[email protected]> wrote: > I like > the incremental builds feature of the maven-plugin and think this would be a > useful enhancement to the maven task. We're basically talking about checking > changlog to see which modules are impacted and including them in maven -pl > and -amd flags.
Yes, this would be very useful. > should I start a new plugin that extends on Maven core task, could I just > extend the core task, or is there other options? The most conservative option for the incremental builds feature would be a new plugin that adds a separate build step which inspects your changelog, computes the right -pl/-amd flags (possibly empty, for example for an initial build), and defines this as a build variable. Then you could just pass this variable to the “goals and options” of the existing Maven build step. What I would really like to see [1] is for the existing Maven task to be moved to a plugin with its own lifecycle. This would make it easier and safer to add significant new features to it directly, especially if you need to do things like link against Maven core libraries to parse POMs. (You might not need to do that; for -pl you can pass directory names, so you would just need to pay attention to what subdirs contain a pom.xml.) I believe this is a pretty easy refactoring and could work on it if there is interest (CC @domi). [1] https://trello.com/c/ImfSSGkj/4-classic-maven-builder-into-maven-builder-plugin -- 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]. For more options, visit https://groups.google.com/d/optout.
