Thank you for the explanation Anders! This is exactly what I wanted to know.
--
Best Regards,
Vilius
-Original Message-
From: Anders Hammar
Sent: Thursday, January 19, 2023 9:16 PM
To: Maven Users List
Subject: Re: how to correctly specify Maven child dependency version for CI
t;
> /Anders
>
> On Thu, Jan 19, 2023 at 10:01 AM Vilius Šumskas
> wrote:
>
> > Can you ellaborate a bit how ${project.version} is resolved? I suppose
> > it is somewhat special parameter?
> >
> > --
> > Vilius
> >
> > -----Original Mes
Sent: Thursday, January 19, 2023 11:36 AM
To: Maven Users List
Subject: Re: how to correctly specify Maven child dependency version for CI
It's properties resolution in Maven. There are plenty of web pages describing
this.
/Anders
On Thu, Jan 19, 2023 at 10:01 AM Vilius Šumskas
wrote:
>
us
>
> -Original Message-
> From: Anders Hammar
> Sent: Wednesday, January 18, 2023 8:45 PM
> To: Maven Users List
> Subject: Re: how to correctly specify Maven child dependency version for CI
>
> I believe this is handled by Flatten Maven plugin (during build) and c
Can you ellaborate a bit how ${project.version} is resolved? I suppose it is
somewhat special parameter?
--
Vilius
-Original Message-
From: Anders Hammar
Sent: Wednesday, January 18, 2023 8:45 PM
To: Maven Users List
Subject: Re: how to correctly specify Maven child dependency
I believe this is handled by Flatten Maven plugin (during build) and could
have been improved in a release after that text was written. If
${revision} is resolved for dependency versions then I guess there is no
problem. It's like you hard-coding it. ${project.version} on the other hand
will IIRC n
