On Thu, 03 Jul 2008 19:30:58 Jörg Schaible wrote:
> > project.deployable uses implementation.[1,2-!) and consumer.[1,2-!)
> > obviously in the real world things aren't this simple and for
> > simple cases
> > this seems like excessive overhead
>
> We do not use ranges at all. Works great without.
Define great... You have no real definition of a build... its transient as
saying i would like something that kinda resembles 3.4.5 of an artifacts does
not really mean much at the end of the day. It would be possible for maven to
resolve 2.0.5. (just look at our xml apis/xerces versions in dependency:tree)
where as saying i can only use any 1.X version of an artifact is a lot more
constraining. I would never get a deliverable which had version 3, or 2 etc.
For the same reason that static type checking is good so are ranges.
--
Michael McCallum
Enterprise Engineer
mailto:
gholam@...
---------------------------------------------------------------------
To unsubscribe, e-mail:
users-unsubscribe@...
For additional commands, e-mail:
users-help@...
