Bruno Melloni wrote:
> First, you are right... I misread. When I look at the maven plugins in
> pluginManagement I see v2 and v3: clean=3.1.0, compiler=3.8.1,
> surefire=2.22.1, jar=3.0.2, install=2.5.2, deploy=2.8.2, site=3.7.1,
> project-info-reports=3.0.0. Still, it is > 2.0 so LATEST
Hi,
Does yesterday dependency build on an other pc? Then it should be "deploy"
to your company central repository (Artifactory, Nexus, ...) to be fetched
from your pc.
Using version range and snapshot is not good idea. It's better to use
snapshot only.
If you want incremental version from you
> Finally I opened app2-0.0.1-SNAPSHOT.jar and looked for the included
app1-0.0.1-SNAPSHOT.jar file.
What does this mean?
On Sat, 24 Sept 2022 at 00:05, Bruno Melloni wrote:
> First, you are right... I misread. When I look at the maven plugins in
> pluginManagement I see v2 and v3:
First, you are right... I misread. When I look at the maven plugins in
pluginManagement I see v2 and v3: clean=3.1.0, compiler=3.8.1,
surefire=2.22.1, jar=3.0.2, install=2.5.2, deploy=2.8.2, site=3.7.1,
project-info-reports=3.0.0. Still, it is > 2.0 so LATEST is no longer
supported as a
Hi Bruno,
It’s not completely clear to me what your issue is exactly. Is ’the old cached
version from January’ that you refer to an artifact with a snapshot version or
a release version? If it is a snapshot version, it depends on the update policy
whether Maven will use a locally cached
I apologize for the length of this email, I could not think of a shorter
way to present the issue/questions that is clear enough.
---
My environment involves the usual many open source dependencies (which I
control by specifying the versions to use in a master POM), but also a
large number
