Daniel Kulp wrote: >> 2: Ensure that projects can build against a single version of a >> dependency, rather than multiple. >> > > This bothers me the most. If my project's pom.xml says I depend on "foo > version 1.1.3", it better be built and installed with "foo version 1.1.3", > not "foo version 1.2" or "foo version 1.1.5" of "foo version 2.0". If I > wanted to say "any 1.x version", I would have used a version range in my pom. > > If redhat or rpm or whatever cannot install multiple versions of a resource, > that seems like a deficiency in those and I don't think maven should go out > of it's way to work around that. Maven's dependency management is > definitely one of it's strong point. That type of change bypasses all of > that. > > Also, this changes the "names" of the jars which affects things like > classpaths and such. "foo-1.1.3.jar" is very different than "foo.jar" in > things like scripts, paths, etc.... > (just an observation)
on my fedora installation i have multiple kernels versions installed and multiple versions of various libs installed right now. They were all installed via rpm. Seems to me that the multiple versions of a resource can be done with rpm. - Joakim --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
