[MBUILDCACHE-109] Configuration to exclude plugins from cache key calculation

**[Tiemen Schut](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=JIRAUSER307287)** opened **[MBUILDCACHE-109](https://issues.apache.org/jira/browse/MBUILDCACHE-109?redirect=false)** and commented

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:

```java

```

It is currently not possible to exclude complete plugins from cache key calculation. I'm not sure where in the configuration this should land,

```java
...
```

seems like it might be a reasonable place.

---

1 votes, 2 watchers

No source file, test, or entry point is named. Start by tracing how the effective POM's input/plugins configuration contributes to cache-key calculation, then determine where an exclusion setting belongs and verify that excluded plugins no longer produce cache-key mismatches while other plugins remain included.

Written by the indexing model from the issue text.