jira-importer opened a new issue, #310: URL: https://github.com/apache/maven-build-cache-extension/issues/310
**[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 <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" /> ``` 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 <input><plugins>...</plugins></input> ``` seems like it might be a reasonable place. --- 1 votes, 2 watchers -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
