-builds.html<https://maven.apache.org/guides/mini/guide-reproducible-builds.html>
which also links to a wiki about the topic. There is a lot you can do to
insure reproducible builds with Maven.
From: Creager, Greg
mailto:greg.crea...@hp.com.INVALID>>
Date: Friday, April 15, 2022 at 8:10
ut also have benefits and certainly made hot
fixes much easier to handle when we had different deployments staggered
into production between customer sites.
--
"Great artists are extremely selfish and arrogant things" — Steven Wilson,
Porcupine Tree
On 14/04/2022 at 6:25
Another question, if the published pom has a range:
Published pom:
com.hp.cp.dfe.shared
common-types
[1.0,1.1)
Does that mean when another maven build that depends on this will select the
latest available common-types in that range, not the one that was
much easier to handle when we had different deployments staggered
into production between customer sites.
--
"Great artists are extremely selfish and arrogant things" — Steven Wilson,
Porcupine Tree
On 14/04/2022 at 6:25:47 AM, "Creager, Greg"
mailto:greg.crea...@hp.com
I am trying to reproduce a build that was done a week ago. Our maven pom files
use range in many places ([1.0,1.1), when I go look at the pom of the published
project, it just shows the range, not the actual version chosen:
Published pom:
com.hp.cp.dfe.shared
common-types
blocks in child poms
either. You can reference them in the same pom that declares
management blocks just fine, and the references will cascade into any
pom that declare your pom as parent.
I hope this clears it up a bit.
On Thu, May 6, 2021 at 2:20 PM Creager, Greg
mailto:greg.crea...@hp.com.invalid
I am new to Maven and doing a lot of learning about Parent pom inheritance.
When I first set things up, I put the common plugins in the parent pom under
the plugingManagement tags and things are working fine (with no plugins in the
child poms)
But in my research of all things maven I came
