-
Notifications
You must be signed in to change notification settings - Fork 55
Open
Labels
enhancementNew feature or requestNew feature or requestpriority:majorMajor loss of functionMajor loss of function
Description
Réda Housni Alaoui opened MBUILDCACHE-92 and commented
I have the following case:
<plugin>
<groupId>com.github.eirslett</groupId>
<artifactId>frontend-maven-plugin</artifactId>
<executions>
<execution>
<id>yarn-build-dev</id>
<goals>
<goal>yarn</goal>
</goals>
<phase>prepare-package</phase>
<configuration>
<skip>${build-dev.skip}</skip>
<arguments>build:dev</arguments>
</configuration>
</execution>
<execution>
<id>yarn-build-prod</id>
<goals>
<goal>yarn</goal>
</goals>
<phase>prepare-package</phase>
<configuration>
<skip>${build-prod.skip}</skip>
<arguments>build:prod</arguments>
</configuration>
</execution>
</executions>
</plugin>
yarn-build-prod
produces a more complete output than yarn-build-dev
but it also takes more time to execute:
- on a dev environment (build-prod.skip=true and build-dev.skip=false) using a cache produced with build-prod.skip=false and build-dev.skip=true should lead to a cache hit
- on a CI environment (build-prod.skip=false and build-dev.skip=true) using a cache produced with build-prod.skip=true and build-dev.skip=false should lead to a cache miss
The only way I can think of implementing this is to track property skip
only for execution id yarn-build-prod
, but not for execution id yarn-build-dev
.
But I can't, because as of now, this extension allows to track plugin property with reconcile at plugin goal level, not execution level.
Affects: 1.1.0
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or requestpriority:majorMajor loss of functionMajor loss of function