Re: Dependence on specific versions
On Feb 10, 2011, at 10:02 PM, Torsten Werner wrote:
> On Thu, Feb 10, 2011 at 9:47 PM, Stefane Fermigier <sf@nuxeo.com> wrote:
>> On Feb 10, 2011, at 9:38 PM, Torsten Werner wrote:
>>> a.jar (0.1) depends on b.jar (0.1)
>>> c.jar (0.3) depends on b.jar (0.2)
>>> d.jar (0.4) depends on a.jar (0.1) and c.jar (0.3)
>>
>> A lot of things are wrong in Maven, but it this case, you just ask maven to use a fixed version of the dependency in the dependencyManagement section of your POM, and voila.
>
> No, if you choose b.jar (0.1) then c.jar (0.3) does not git its
> preferred version. If you choose b.jar (0.2) then a.jar (0.1) does not
> get its preferred version. That means either a.jar or c.jar will get a
> non preferred version. What is the point of specifying fixed versions
> if you cannot rely on getting them?
As the developer of d.jar, I get to choose which version of a.jar, b.jar and c.jar I will assemble in my application.
When a situation such as the one you describe occurs, I have to make a choice, even if it's not the one advertised by the dependencies authors.
Then it's my responsibility to test the hell out of the application and make sure that it's working.
Do not confuse application development and library development, BTW.
S.
--
Stefane Fermigier, Founder and Chairman, Nuxeo
Open Source, Java EE based, Enterprise Content Management (ECM)
http://www.nuxeo.com/ - +33 1 40 33 79 87 - http://twitter.com/sfermigier
Join the Nuxeo Group on LinkedIn: http://linkedin.com/groups?gid=43314
New Nuxeo release: http://nuxeo.com/dm54
"There's no such thing as can't. You always have a choice."
Reply to: