Re: POM versions

[White, G. <gr...@sl...>]

I see, thanks Matej. Yes, that’s exactly what I had in mind. 

So, when this document was written Dependency Version Ranges were a requirement
for Maven 2, but presumably they are not now yet implemented? And when they are, we would use the 
half open interval on the major identifier - the 5th example. That would indicate A is dependent on (and therefore may
use) any version of B where B only makes functional changes or adds entry points, but not any where 
backward compatibility is broken (protocol, removes entry points, changes memory assumptions).

eg for exampleJava dependency on pvDataJava

     <version>4.0.2</version>
     <artifactId>exampleJava</artifactId>
     …
          <dependency>
            <groupId>${project.groupId}</groupId>
            <artifactId>pvDataJava</artifactId>
            <version>[4.0.2,5.0.0)</version>
          </dependency>
   

That would be great.

Greg

  
On Nov 25, 2014, at 5:21 PM, Matej Sekoranja <mat...@co...> wrote:

> http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+Resolution#DependencyMediationandConflictResolution-DependencyVersionRanges
> 
> 
> 
> ------------------------------------------------------------------------------
> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
> with Interactivity, Sharing, Native Excel Exports, App Integration & more
> Get technology previously reserved for billion-dollar corporations, FREE
> http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk