Em 27-03-2012 13:55, kristian escreveu:
On Tue, Mar 27, 2012 at 10:21 PM, Rodrigo Rosenfeld Rosas
<rr.ro...@gmail.com> wrote:
Sorry for picking a small part to comment but I need more time to read and
answer the other parts.
...
so a typical maven dependency is
<version>3.0.1</version>
but maven might use version 4.0.0 instead depending on the dependency
hull. but in can be the other way around as well and maven choose
version 2.0.5
What I meant is that you're only sure that it should work with 3.0.1 since
that is the version it was tested against. If Maven is going to resolve to
any other versions you can't be sure that it will still work and sometimes
it won't.
That is why I prefer the Bundler approach.
well, good catch but bundler does the same thing differently. you
specify ~>1.2 with testing you use 1.3 but in your bundler project
bundler resolves it to 1.4
similar but different to what can happen with maven :))
This is different. When you specify '~>1.2' it seems you know why you
specified this specific range and hopefully no matter what Bundler
choose if the project respects their promises it should end up all fine.
It doesn't mean you don't need your own applications tests for making it
sure that "bundle update" won't break your application.
But the difference is that you know when that dependency is upgraded as
you had to run "bundle update dependency" for instance. So you know that
you should re-run your application test suite or manually test the
relevant parts of the code that depend on that gem/artifact.
You just don't have this level of control with Maven.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
