Re: Will a version range for a parent pom reference work?

--000000000000b9f3e5065570c6b3
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

If 'works' means 'compile without expressly failing', I guess it 'works'.

If 'works' means 'have a consistent, reproducible build process', then
probably not. Version ranges and metaversions like LATEST are the opposite
of that, a great way to introduce subtle bugs and waste time hunting them.
Most would try to avoid adding that into their builds.

On Mon, Jun 29, 2026 at 1:37=E2=80=AFPM KARR, DAVID via users <
[email protected]> wrote:

> We are wondering whether we can use a version range for the
> "parent"->"version" property in our pom.xml. The docs don't explicitly sa=
y
> so, but comparing the info for the "version" property in "parent" vs.
> "dependency", we see that only in "dependency" does it mention the
> possibility of using the range syntax.  In our tests, it didn't reject th=
e
> range syntax in the parent, but we'd have to set up a more complex test t=
o
> verify whether it's actually respecting it.  We're currently on version
> 3.9.8.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

--000000000000b9f3e5065570c6b3--