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
Hello,
Recently, I attempted to use ‘mvn dependency:tree’ to retrieve the project's
dependency tree. However, in the output, I noticed that for the same dependency
with different scopes, its version doesn't appear to be consistent. The
specific scenario is as follows:
(org.checkerframework:chec
e api modules and impl modules you
could do this even more beautifully by having B depend on an API artifact
which doesn't change that often.
/Anders
On Fri, Aug 18, 2017 at 2:34 AM, Halper, Andrew wrote:
> Greetings,
>
> I was wondering if someone might be able to help with a Maven v
PM, Halper, Andrew wrote:
>
> Greetings,
>
> I was wondering if someone might be able to help with a Maven version
> management problem we've encountered.
>
> We have several interdependent, legacy Java projects, that have recently
> been re-cast as Maven proj
Greetings,
I was wondering if someone might be able to help with a Maven version
management problem we've encountered.
We have several interdependent, legacy Java projects, that have recently
been re-cast as Maven projects. Now that we have the first iteration done,
it's apparen
as simple as "mvn release:prepare", "mvn release:perform". Since it's
not that simple, documentation of a real SCM-integrated, CI process seems to
be necessary.
--
View this message in context:
http://maven.40175.n5.nabble.com/Version-management-in-a-Maven-CI-environ
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
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 release-time. We use the release plugin extensively, are
Hi Phillip,
Phillip Hellewell wrote:
> I'm thinking about moving all our version management into the parent
> pom in a dependencyManagement section, but I'm trying to figure out if
> it will really make things easier or not.
>
> Of course each version number would onl
11:49 AM, Phillip Hellewell wrote:
I'm thinking about moving all our version management into the parent
pom in a dependencyManagement section, but I'm trying to figure out if
it will really make things easier or not.
Of course each version number would only be in one place instead of N
pl
t; I hope that this helps.
>
> Ron
>
> On 28/02/2011 11:49 AM, Phillip Hellewell wrote:
>>
>> I'm thinking about moving all our version management into the parent
>> pom in a dependencyManagement section, but I'm trying to figure out if
>> it will really make
simplifies the process.
I hope that this helps.
Ron
On 28/02/2011 11:49 AM, Phillip Hellewell wrote:
I'm thinking about moving all our version management into the parent
pom in a dependencyManagement section, but I'm trying to figure out if
it will really make things easier or not.
11:49 AM, Phillip Hellewell wrote:
I'm thinking about moving all our version management into the parent
pom in a dependencyManagement section, but I'm trying to figure out if
it will really make things easier or not.
Of course each version number would only be in one place instead o
On Mon, Feb 28, 2011 at 9:49 AM, Phillip Hellewell wrote:
> The problem I see with using a snapshot for the parent is it doesn't
> allow you to make changes in a safe way. I could update the version #
> of a lower component, and then a much higher component could build
> against that before all t
I'm thinking about moving all our version management into the parent
pom in a dependencyManagement section, but I'm trying to figure out if
it will really make things easier or not.
Of course each version number would only be in one place instead of N
places, where N is the avg #
Did you google for it?
http://jira.codehaus.org/browse/MSITE-490
Why the javadoc doesn't work I don't know...
-Lukas
Benson Margulies wrote:
Site:site says this over and over, in addition to running the javadoc
over and over.
INFO] Generating "Project License" report.
[WARNING] Deprecated
Site:site says this over and over, in addition to running the javadoc
over and over.
INFO] Generating "Project License" report.
[WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink
instance and no SinkFactory available. Please update this plugin.
What should I be specifying, an
nd where the versions of your projects are
> > defined because if the parents are enterprise pom, you are not allowed to
> > modify them !!!
> >
> > Jeff
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Parent%2C-Modules-an
versions of your projects are
> defined because if the parents are enterprise pom, you are not allowed to
> modify them !!!
>
> Jeff
>
>
--
View this message in context:
http://www.nabble.com/Parent%2C-Modules-and-version-management-tp25614127p25627113.html
Sent from the Mav
gt; > defining pom version, Maven does handle it correctly on some cases,
> > even if the properties are defined on the parent pom
> >
> > I recommand using version herited from the parent and updating the
> > parent version with the version plugin
> > Jeff MAURY
&
--
View this message in context:
http://www.nabble.com/Parent%2C-Modules-and-version-management-tp25614127p25625561.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.ap
versions (Codehaus), but I didn't
> find what I need.
>
>
>
> Has anybody a solution for this?
>
>
> Thank you very much,
>
> Emmanuel.
> --
> View this message in context:
> http://www.nabble.com/Parent%2C-Modules-and-version-management-tp25614127p25614
context:
http://www.nabble.com/Parent%2C-Modules-and-version-management-tp25614127p25614127.html
Sent from the Maven - Users mailing list archive at Nabble.com.
gt;> I currently have never use them because they aren't repeatable.
>>>
>>>
>>>
>>> From: Hayes, Peter [mailto:peter.ha...@fmr.com]
>>> Sent: Monday, April 06, 2009 12:12 PM
>>> To: Maven Users List
>>> Subject: RE: LATEST and R
From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com]
Sent: Wednesday, April 08, 2009 3:16 AM
To: Maven Users List
Cc: Maven Users List
Subject: Re: LATEST and RELEASE release version management
sounds like you want version ranges
[1.0,2.0-!)
Sent from my [rhymes with myPod] ;-)
On 8 Apr
.ha...@fmr.com]
Sent: Monday, April 06, 2009 12:12 PM
To: Maven Users List
Subject: RE: LATEST and RELEASE release version management
Graham Leggett wrote:
Having said that, it makes no sense to have the release plugin care
about LATEST, because by definition, building against LATEST isn't
validation build and tag is the only sane way to use them.
> I currently have never use them because they aren't repeatable.
>
>
>
> From: Hayes, Peter [mailto:peter.ha...@fmr.com]
> Sent: Monday, April 06, 2009 12:12 PM
> To: Maven Users List
> Subject: RE: LATEST and
PM
To: Maven Users List
Subject: RE: LATEST and RELEASE release version management
Graham Leggett wrote:
>Having said that, it makes no sense to have the release plugin care
>about LATEST, because by definition, building against LATEST isn't
>repeatable, and in order for there to be
If you are prepared to run maven multiple times as part of your CI build you
could achieve some of what you are looking for with the
versions-maven-plugin.
step 1. use versions-maven-plugin to update the pom to the latest releases
of all dependencies
step 2. use maven-scm-plugin to commit the modi
rtf1uqccPrltQ.rtf
Description: RTF file
smime.p7s
Description: S/MIME cryptographic signature
Hayes, Peter wrote:
> We use Maven in an enterprise environment and internally we are required
> to execute "release" builds whenever we want to install to our testing
> environment. We have found that executing many release builds can be
> tedious when we have in-development snapshot dependencie
We use Maven in an enterprise environment and internally we are required
to execute "release" builds whenever we want to install to our testing
environment. We have found that executing many release builds can be
tedious when we have in-development snapshot dependencies that also have
to be releas
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
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
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
Hi
Can Maven be used as a Version mangement tool? Is it possible to automate
the Version management using Maven?
Thanks and Regards
Hemant Ved
: maven version management in ant
>
> That seems to be working!
>
> Thank you so much for this!
>
> How was one to know that pathId existed?
>
> -Original Message-
> From: Chris Hilton [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, January 09, 2007 11:16 AM
> T
That seems to be working!
Thank you so much for this!
How was one to know that pathId existed?
-Original Message-
From: Chris Hilton [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 09, 2007 11:16 AM
To: Maven Users List
Subject: RE: maven version management in ant
Perhaps I'
Original Message-
> From: EJ Ciramella [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, 09 January, 2007 09:24
> To: Maven Users List
> Subject: RE: maven version management in ant
>
> All of these are blank:
> ${maven.dependency.classpath}
> ${maven.compile.classpath}
ality when using the following
technique to build with ant and manage dependencies with maven2:
-Original Message-
From: Barrett Nuzum [mailto:[EMAIL PROTECTED]
Sent: Monday, January 08, 2007 11:10 AM
To: Maven Users List
Subject: RE: maven version management in ant
EJ:
Unsure if it&
[snip]
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Monday, January 08, 2007 6:19 AM
To: Maven Users List
Subject: RE: maven version management in ant
Bump - I could really use some feed back here people, this has me
completely wedged...
-Ori
]
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Monday, January 08, 2007 6:19 AM
To: Maven Users List
Subject: RE: maven version management in ant
Bump - I could really use some feed back here people, this has me
completely wedged...
-Original Message
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Mon 1/8/2007 8:19 AM
To: Maven Users List
Subject: RE: maven version management in ant
Bump - I could really use some feed back here people, this has me
completely wedged...
-Original Message-
From: EJ Ciramella [mai
Bump - I could really use some feed back here people, this has me
completely wedged...
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Friday, January 05, 2007 3:56 PM
To: Maven Users List
Subject: RE: maven version management in ant
I made it a bit further
?
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Friday, January 05, 2007 2:07 PM
To: Maven Users List
Subject: RE: maven version management in ant
New question, so I'm loading via a pom.xml file, how can I reference the
classpath (filled with depende
m: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 03, 2007 3:49 PM
To: Maven Users List
Subject: RE: maven version management in ant
Sorry - I'm building with jdk 1.5.1 now and this is gone.
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Wednesda
Sorry - I'm building with jdk 1.5.1 now and this is gone.
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 03, 2007 1:03 PM
To: Maven Users List
Subject: RE: maven version management in ant
I'm trying this out with a VERY simple example
ecember 26, 2006 4:14 PM
To: Maven Users List
Subject: RE: maven version management in ant
That's it - thank you!
-Original Message-
From: Wendy Smoak [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 26, 2006 1:53 PM
To: Maven Users List
Subject: Re: maven version management in ant
That's it - thank you!
-Original Message-
From: Wendy Smoak [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 26, 2006 1:53 PM
To: Maven Users List
Subject: Re: maven version management in ant
On 12/26/06, EJ Ciramella <[EMAIL PROTECTED]> wrote:
> A while back, I stu
On 12/26/06, EJ Ciramella <[EMAIL PROTECTED]> wrote:
A while back, I stumbled across a page on the maven 2 site explaining
how to use maven's nice dependency management from within ant.
I can no longer find this link, has this functionality been abandoned or
can someone reply with the url?
Th
A while back, I stumbled across a page on the maven 2 site explaining
how to use maven's nice dependency management from within ant.
I can no longer find this link, has this functionality been abandoned or
can someone reply with the url?
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
I recently asked the question below, but no answer.
I was wondering whether I really need to edit all pom.xml files in all
my project whenever I bump version numbers.
I'm still new at this, so if this is a trivial question, please bear
with me...
--
cg
Christian Goetze wrote:
Why can't I
-
From: dan tran [mailto:[EMAIL PROTECTED]
Sent: Saturday, September 23, 2006 6:55 PM
To: Maven Users List
Subject: Re: Plug-in version management
http://jira.codehaus.org/browse/MNG-1931 you should have given the
search a
try ;)
On 9/23/06, Andreas Guther <[EMAIL PROTECTED]> wrote:
>
&
-in version management
http://jira.codehaus.org/browse/MNG-1931 you should have given the
search a
try ;)
On 9/23/06, Andreas Guther <[EMAIL PROTECTED]> wrote:
>
> The next question now is:
>
> Does this work for reporting as well? I looked at reporting but that
> does not ha
ndreas
-Original Message-
From: dan tran [mailto:[EMAIL PROTECTED]
Sent: Saturday, September 23, 2006 6:30 PM
To: Maven Users List
Subject: Re: Plug-in version management
On 9/23/06, Andreas Guther <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I started to manage my dependency v
: Plug-in version management
On 9/23/06, Andreas Guther <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I started to manage my dependency versions with
> and I am quite pleased on the outcome and control this configuration
> provides.
>
> We defined in a parent pom all de
]
Sent: Saturday, September 23, 2006 6:30 PM
To: Maven Users List
Subject: Re: Plug-in version management
On 9/23/06, Andreas Guther <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I started to manage my dependency versions with
> and I am quite pleased on the outcome and contr
On 9/23/06, Andreas Guther <[EMAIL PROTECTED]> wrote:
Hi,
I started to manage my dependency versions with
and I am quite pleased on the outcome and control this configuration
provides.
We defined in a parent pom all dependency versions we are using in the
section and in our sub-project
Hi,
I started to manage my dependency versions with
and I am quite pleased on the outcome and control this configuration
provides.
We defined in a parent pom all dependency versions we are using in the
section and in our sub-project we only define
what we need to use but not the version. This
Jose Gonzalez Gomez wrote:
I understand that you're deploying your snapshot versions for your
projects in your internal repository, but I don't fully understand
your environment (or maybe Maven's way of working)... let me explain:
I understand that you can publish snapshot versions of artifacts
z Gomez [mailto:[EMAIL PROTECTED]
Sent: Saturday, September 03, 2005 3:16 AM
To: Maven Users List
Subject: Re: Best practices for release and version management?
David,
I understand that you're deploying your snapshot versions for your projects in
your internal repository, but I don
ils very well.
>
> ..David..
>
>
> -Original Message-
> From: Trygve Laugstøl [mailto:[EMAIL PROTECTED]
> Sent: Friday, September 02, 2005 4:14 AM
> To: Maven Users List
> Subject: Re: Best practices for release and version management?
>
> On Fri, Sep 02,
2005/9/2, Trygve Laugstøl <[EMAIL PROTECTED]>:
> On Fri, Sep 02, 2005 at 10:54:37AM -0400, dohadwala, moiz wrote:
> > How does one do it for m2?
> >
> > I am new to maven and I have decided to skip maven 1.x and start with m2
> > directly.
>
> In Maven 2 there is the same off-line option as in Mav
g our internal process for releasing projects
> for our developers (since we're about to release the big project soon), so I
> know the details very well.
>
> ..David..
>
>
> -Original Message-
> From: Trygve Laugstøl [mailto:[EMAIL PROTECTED]
> Sent:
On Fri, Sep 02, 2005 at 10:54:37AM -0400, dohadwala, moiz wrote:
> How does one do it for m2?
>
> I am new to maven and I have decided to skip maven 1.x and start with m2
> directly.
In Maven 2 there is the same off-line option as in Maven 1 but you can
also say that repositories can contain snap
and version management?
We're pretty much doing what Jose is doing, but we don't see these timeouts.
I think it's because the Maven properties are set up to look in our internal
repository first and then go global from there. Just about everything is in
the internal repository
nt: Friday, September 02, 2005 4:14 AM
To: Maven Users List
Subject: Re: Best practices for release and version management?
On Fri, Sep 02, 2005 at 11:46:49AM +0200, Jose Gonzalez Gomez wrote:
> Hi there,
>
> How do you use to manage your project version among releases? I
> mean... wh
On Fri, Sep 02, 2005 at 11:46:49AM +0200, Jose Gonzalez Gomez wrote:
> Hi there,
>
> How do you use to manage your project version among releases? I
> mean... what do you exactly put in currentVersion in your pom and how
> do you change it among releases?
>
> I'm currently using the following app
2005/9/2, Jose Gonzalez Gomez <[EMAIL PROTECTED]>:
> Hi there,
>
> How do you use to manage your project version among releases? I
> mean... what do you exactly put in currentVersion in your pom and how
> do you change it among releases?
>
> I'm currently using the following approach:
>
> 1. Dev
Hi there,
How do you use to manage your project version among releases? I
mean... what do you exactly put in currentVersion in your pom and how
do you change it among releases?
I'm currently using the following approach:
1. Developing version 0.1 - currentVersion = 0.1-SNAPSHOT
2. V0.1 release:
78 matches
Mail list logo
