(Say Test environment) and v0.2 gets deployed on another
Environment2(Say Development)
Thanks and Regards
Hemant Ved
From: Bob Aiello [mailto:[EMAIL PROTECTED]
Sent: 16 August 2007 13:29
To: Maven Developers List; Ved, Dhr. H. (Ved)
Subject: RE: Version Management
Well I guess it depends
PROTECTED] in regards.
Bob
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thu 8/16/2007 7:48 AM
To: Bob Aiello; dev@maven.apache.org
Cc:
Subject: RE: Version Management
By Version
Well I guess it depends upon your definition of
version management. Some people (mistakenly) think that the shared
repository actually "versions" objects that are deployed
(as if it were a version control tool such as
Accurev or ClearCase). The shared repository is just
a file system where you pr
Hi.
You can either use and version range to
minimize constant update to your dependencies.
Regards,
Edward Yakop
Note:
http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+Resolution#DependencyMediationandConflictResolution-DependencyVersionRanges
http://docs.codehaus.org/di
No but maven interfaces with many version control tools
(which means that you can checkout your code from within maven)
I recommend that you keep them completely separate to avoid
wasting time on script glitches. In other words checkout your
code and then execute your build.
-Original Messag
