Howdy,
"I delete 3.12.0" -- you deleted the "3.12.0" directory?
"still downloads 3.12.0" -- means you got again the "3.12.0" directory?
As it _will_ download the POM during collection, but not the JAR (or at
least should not)
T
On Wed, Nov 1, 2023 at 6:37 AM yukai zhao wrote:
> Thank you for
On Wednesday, 1. November 2023, 06:37:31 CET yukai zhao wrote:
> Thank you for your response!
> Additionally, I've noticed that in this situation, if I delete 3.12.0 from
> my local repository and then recompile the project, Maven still downloads
> 3.12.0. Is this behavior normal?
In this case, ye
Thank you for your response!
Additionally, I've noticed that in this situation, if I delete 3.12.0 from my
local repository and then recompile the project, Maven still downloads 3.12.0.
Is this behavior normal?
On 2023/11/01 03:45:49 Greg Chabala wrote:
> On Tue, Oct 31, 2023 at 10:27 PM yukai z
On Tue, Oct 31, 2023 at 10:27 PM yukai zhao wrote:
> has the project actually introduced the org.apache.commons:commons-lang3
> with version 3.12.0 during the actual compilation process?
>
Well, no. It says 3.12.0 was omitted, due to being a duplicate, hence why
it was not even mentioned withou
I apologize for my unclear description! Allow me to explain my problem
specifically. You are right; it is indeed a confusion.
Firstly, I compiled a project using Maven. This step was completed with the
command mvn clean install. Below is part of the output (I have omitted some
information for br
On Tue, Oct 31, 2023 at 11:27 AM
wrote:
> Can't quite make sense of all this; given that you got no replies, maybe
> no one else understood either.
I second this sentiment. All I could tell is it seems like there's some
confusion about interpreting the dependency:tree output, and perhaps
confus
Can't quite make sense of all this; given that you got no replies, maybe no one
else understood either.
Could you explain a bit better?
-Original Message-
From: yukai zhao
Sent: Monday, October 30, 2023 9:10 PM
To: users@maven.apache.org
Subject: Version Management in 'mvn dependency:tr
Manfred Moser wrote:
>
> What about using dependency management in a parent pom?
>
I'm not sure I understand what you're suggesting. Do you mean all
dependency versions are provided by a common parent POM? Doesn't that
present the problem of needing to constantly release the parent POM which
w
On Fri, August 12, 2011 10:34 am, leonfranzen wrote:
> My organization has been using Maven and CI for a few years now. Although
> we
> have a process in place that works for us, it has always been difficult to
> come up with a successful approach to dependency version management in
> Maven
> at r
What do you mean by "version management"? We do use maven to add
specific tags at the end of project.xml with every Build something like
following.
1.0.2
1.0.2
LGB_reFUEL_ServiceOrchestration_DEVGRP_dev_JAVA14_051018_2
1.1
1.1
LGB_reFUEL_ServiceOrchest
Hi Hermant,
No, Maven cannot be used as a Version management tool. Maven is a build
tool, an advanced build tool. You can, however, interact with a version
management tool (like Subversion) from within Maven, so that Maven
performs checking in and checking out (commit and update) to and from
Subve
Yes, Maven can be used as a Version management tool.
The first time written POM file should have the version number and all
other file can include a relative path for the versions later on.
Thanks and Regards
Vaishali G.P. | Cognizant Technology Solutions, Pune-India | PSTN: +9120
40051735 | VN
Lee Meador wrote:
This does not work.
If you think about it you can see why.
You would define 'sensage-version' in the parent pom and use it in all
the
children. The problem is that as it is parsing the child pom, maven
has to
find the parent. To do that, it looks in the section and has
to
This does not work.
If you think about it you can see why.
You would define 'sensage-version' in the parent pom and use it in all the
children. The problem is that as it is parsing the child pom, maven has to
find the parent. To do that, it looks in the section and has to use
the value of "sens
14 matches
Mail list logo
