For example, if I want to depend on the latest version of the artifact un the 1.1.x version range, I would put:
<dependency> <groupId>test</groupId> <artifactId>myartifact</artifactId> <version>[1.1,1.1.999999999] </dependency> This says give me the latest version whose number is greater than or equal to 1.1 and less than or equal to 1.1. 999999999 (where I randomly chose 999999999 to be greater than any incremental version I will ever create. This version range can also be written [1.1, 1.2) where the close parent indicates a non-inclusive range end (i.e., less than 1.2). The thing to be aware of with this syntax is that it also includes any pre-release versions of 1.2 (e.g., 1.2-alpha-1 is included). For more information, please see section 3.4.3 of http://books.sonatype.com/mvnref-book/reference/pom-relationships-sect-project-dependencies.html and http://maven.apache.org/enforcer/enforcer-rules/versionRanges.html -- Robert Patrick <robert.patr...@oracle.com> VP, OPC Development, Oracle Corporation 7460 Warren Pkwy, Ste. 300 Office: +1.972.963.2872 Frisco, TX 75034, USA Mobile: +1.469.556.9450 Professional Oracle WebLogic Server by Robert Patrick, Gregory Nyberg, and Philip Aston with Josh Bregman and Paul Done Book Home Page: http://www.wrox.com/ Kindle Version: http://www.amazon.com/ -----Original Message----- From: Magnanao, Hector [mailto:hector.magna...@sap.com] Sent: Friday, April 07, 2017 10:28 AM To: Maven Users List Subject: RE: dependency question Can you give me an example of using a range in the pom file as a dependency ? -----Original Message----- From: Robert Patrick [mailto:robert.patr...@oracle.com] Sent: Thursday, April 6, 2017 2:34 PM To: Maven Users List <users@maven.apache.org> Subject: RE: dependency question The other way is to use a version range in your dependency, which gives you a similar behavior as using a snapshot dependency. Both approaches have their advantages and drawbacks... -----Original Message----- From: Russell Gold Sent: Thursday, April 06, 2017 2:27 PM To: Maven Users List Subject: Re: dependency question The simplest way is simply to use a snapshot version of A. That way B will always use the latest snapshot. When you finally release A, you can have B point to the released version instead of the snapshot. > On Apr 6, 2017, at 2:52 PM, Magnanao, Hector <hector.magna...@sap.com> wrote: > > I have to 2 java projects a and b in maven. The B project uses the A build > as a dependency. How do I ensure the whenever the A project has a new build, > the B project will always use that latest build in A. A is being built with > a unique build number each time it gets built. So is A has build # 10 as the > newest build, the B project has to use build #10 of A. > > > Hector Magnanao Jr. > SCM Analyst > SAP Fieldglass > Skype: (331) 702-6142 > Mobile: (847) 857-8401 > Email: hector.magna...@sap.com > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org