Hi,
What if a released component on remote repository has any bugs?
This just underscores my point, no? Generally, I think upgrading (or
downgrading) a dependency is always something that should be done very
carefully and very consciously, I wouldn't want to have that done
automatically.
Indicating a SNAPSHOT dependency is only useful if you know that a
project is currently under heavy development and you want to stay up to
date with changes on a, say, day-to-day basis (assuming the project
publishes SNAPSHOTs that often). This implies that your project itself
is currently changing frequently, and if something breaks from one day
to the other, you know it might not be due to your own code, but to a
changed dependency. As soon as a stable release gets out, you have to
indicate explicitly (after testing) that you no longer want to use
SNAPSHOTs, but stick to a particular stable version.
If features of a component do not have to be changed to fix bugs, I
think it's
useful to replace this bad component on local repository with bug fixed
component
on remote repository automatically (after agreement).
But how would you indicate which component is the good one? A SNAPSHOT
always gets you the _latest_ development version, which is actually very
rarely the most bug-free one! ;)
-Lukas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
