Hi all,

I'm currently experimenting with using maven-build-cache-extension in some
of our projects. I've mostly got everything setup, and am now in the
process of trying to make sure CI builds and local builds will result in
the same cache keys.

The issue I'm running into is that in the parent pom I'm using there is a
profile which is activated based on whether we're running on the CI
environment or not. Depending on this, the profile will conditionally add
configuration for a plugin. This then causes differences in the effective
pom. Running with -Dmaven.build.cache.baselineUrl confirms this:

<mismatch item="my-maven-plugin" reason="Cached build doesn't contain
plugin my-maven-plugin" resolution="Different set of plugins produces
different build results. Filter out non-critical plugins or make sure
remote cache always run full build with all plugins" />

This is an internal plugin and we know that it's fine to use this cache
entry. Is there any way to configure the maven-build-cache-extension to
completely ignore a plugin? I've managed to ignore specific plugin
configuration using <input><plugins><plugin><effectivePom>, but I can't
find any way to fully exclude a plugin.

Tiemen

Reply via email to