[ https://issues.apache.org/jira/browse/MBUILDCACHE-73?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17794603#comment-17794603 ]
Olivier Lamy commented on MBUILDCACHE-73: ----------------------------------------- [~pdudits] but this will run only once :) TBH this is the simple (and natural) solution for this. Maven is always based on gav so why not here as well :) > Add project version as additional property for reconcilation > ------------------------------------------------------------ > > Key: MBUILDCACHE-73 > URL: https://issues.apache.org/jira/browse/MBUILDCACHE-73 > Project: Maven Build Cache Extension > Issue Type: New Feature > Affects Versions: 1.0.1 > Reporter: Patrik Dudits > Priority: Major > > Certain plugins or goals might require to run when project version changes > regardless of other inputs. A typical example would be {{deploy:deploy}} or > in my specific case {{docker:build}} - It is OK to reuse the build artifact, > but if version changed, I do want to upload it. > Currently only way to achieve that isĀ to put the goal into {{runAlways}} > section. But that results in needles snapshots to be deployed or docker > images being built even if there's no relevant change. > The reconcile section allows to specify properties for futher fine tuning the > input. These are limited to goal parameters, and neither of my examples > contain project version as a parameter, both use project model to fetch it. > Proposal would be to extend tag {{reconcile}} either with: > * special magic name {{project.version}} to include version tracking, so > this could be achieved by {{<reconcile propertyName="project.version"/>}} > * attribute {{{}expression{}}}, to achieve the result with {{<reconcile > propertyName="version" expression="${project.version}"/>}} > * interpolating {{defaultValue}} attribute > The second form would be preferrable as it has much larger scale of > application, I can imagine putting base docker image digests in environment > variable to invalidate builds when base tag gets updated. It is also more > discoverable than third option. -- This message was sent by Atlassian Jira (v8.20.10#820010)