I tried removing the empty sha1 declaration as well but that didn't work
either.
I'm guessing it's due to sequencing - that the interpolation of these
special parameters must happen prior to the execution of any plugins, but
would love confirmation of that. Additionally would love to know if there
is a workaround for this situation.
Thanks
Eric
On Nov 8, 2017 6:35 PM, "Laird Nelson" <ljnel...@gmail.com> wrote:
> On Wed, Nov 8, 2017 at 2:31 PM Eric Benzacar <e...@benzacar.ca> wrote:
>
> > But when I actually run the build all the interpolated version numbers
> > ignore the ${sha1} property as generated by the buildnumber-m-p, even
> > though I bound the create to the validate phase.
> >
>
> [snip]
>
> A snippet of my pom:
> >
> > <project>
> > <artifactId>test</artifactId>
> > <groupId>org.project</groupId>
> > <version>${revision}${sha1}${changelist}</version>
> > <properties>
> > <sha1></sha1>
> >
>
> Blind guess: since the buildnumber-maven-plugin is going to set properties
> using internal machinery, and you've told it the one to set should be named
> sha1, is it possible that this empty property of the same name is shadowing
> the one set by the plugin, or that perhaps the plugin won't set it since
> it's already (effectively) specified?
>
> Best,
> Laird
> --
> https://about.me/lairdnelson
>
