Tiemen Schut created MBUILDCACHE-109:
----------------------------------------
Summary: Configuration to exclude plugins from cache key
calculation
Key: MBUILDCACHE-109
URL: https://issues.apache.org/jira/browse/MBUILDCACHE-109
Project: Maven Build Cache Extension
Issue Type: Improvement
Reporter: Tiemen Schut
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:
{code:java}
<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" />{code}
It is currently not possible to exclude complete plugins from cache key
calculation. I'm not sure where in the configuration this should land,
{code:java}
<input><plugins>...</plugins></input>{code}
seems like it might be a reasonable place.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
