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 ther
On Wed, Nov 8, 2017 at 2:31 PM Eric Benzacar 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:
>
>
> test
> org
I don't think I can help much since I don't use sha1 for revision prop.
For my case, I run buildnumber:create-metadata top level only
(true) to track SCM info per build and user
Jenkins env.BUILD_NUMBER for CD version
-Dan
On Wed, Nov 8, 2017 at 2:30 PM, Eric Benzacar wrote:
> Hi Guys,
>
> S
Hi Guys,
Sorry to reopen a 6 month old thread, but I'm trying to add some more
smarts to my stuff, and am failing trying to figure out how to do this.
I want to use the buildnumber-maven-plugin:create-metadata goal to
generate the metadata build.properties file, which is a great addition to
my a
On Sun 5 Nov 2017 at 11:31, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
>
> On Fri 27 Oct 2017 at 23:28, Laird Nelson wrote:
>
>> On Fri, Oct 27, 2017 at 1:58 AM ahardy42
>> wrote:
>>
>> > How can I tell maven to increment the version and commit the edited pom
>> > without the CI
Hi all,
I’m trying to run simple test using maven-plugin-testing-harness (3.3.0). But
it looks like plugin doesn’t support maven 3 (3.2.2) ( it uses old plexus
container and doesn’t support new eclipse sisu).
java.lang.NoSuchMethodError:
org.codehaus.plexus.DefaultPlexusContainer.(Lorg/codehau
