apt-get has some very disturbing properties, such as the default being system install.
Bundler (an extension of rubygems) and Maven (for Java) and SBT (for Scala) have the nice property that different applications can have different versions of the same libs. And this is the default behavior.
Actually Java, through OSGI, goes out of its way, into allowing different parts of the same application to require different versions of the same libs.
Developing software is more complicated than using it. Therefore it needs more specialized tools.
As far as I can tell, maven was invented for java devs to be able to download any jar from any where without any concern for where it actually came from or any requirements for it to be a replicable process.
More importantly, the project descriptions, like bundler's Gemfile, is a local decryption of the dependencies. And this allows you to have project scope libs, instead of system scope libs.
Comments
apt-get has some very disturbing properties, such as the default being system install.
Bundler (an extension of rubygems) and Maven (for Java) and SBT (for Scala) have the nice property that different applications can have different versions of the same libs. And this is the default behavior.
Actually Java, through OSGI, goes out of its way, into allowing different parts of the same application to require different versions of the same libs.
Developing software is more complicated than using it. Therefore it needs more specialized tools.
As far as I can tell, maven was invented for java devs to be able to download any jar from any where without any concern for where it actually came from or any requirements for it to be a replicable process.
More importantly, the project descriptions, like bundler's Gemfile, is a local decryption of the dependencies. And this allows you to have project scope libs, instead of system scope libs.