Although my issue is about configuring the "jacoco-maven-plugin", I think it's really more of a pure Maven configuration issue, as I don't think this situation is unique to JaCoCo.
I have a somewhat large multi-module project. Each of the child modules has a parent pom that configures the "jacoco-maven-plugin" to do offline instrumentation (at present, all the modules having unit tests using PowerMock, which doesn't work with online instrumentation). I've designed a change that I'll have to make in a few classes in each module that will allow the unit tests to use Mockito, and for JaCoCo to use online instrumentation. I'll eventually fix all of them to work this way, but it will take a little while. In the meantime, I just want to override the configuration in the "fixed" modules with online instrumentation and let the other modules use the default of offline instrumentation. The simple-minded way to do this is just to define the same configuration using online instrumentation in each "fixed" module, so it will override the parent pom. Copying that block to every "fixed" module is not a great idea. I'd like a solution that requires less code duplication. I suppose I could define ANOTHER parent pom, that specifies the existing parent as its parent, and have that second parent use online instrumentation, and have the fixed modules use that second parent instead. I will eventually delete this second parent pom once all of the modules are "fixed". Note that I have a separate aggregator pom that is not a parent pom. Are there other reasonable strategies for this "use original parent for some, override in same way for others" situation? --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
