I think the thinking behind this is that you may have multiple branches
which are in SNAPSHOT. But, I doubt that will be a common scenario for
the ws commons. Either way though I really don't care... so +0 :-)
- Dan
Eran Chinthaka wrote:
Hi all,
We have a slight problem with SNAPSHOT dependencies.
Consider the two points.
1. When other projects depend on SNAPSHOTs, that means they are
working against the current working head of the project. So they
do not worry abt the version of the SNAPSHOT jar they are using.
2. With the current state, say policy was in 0.90-SNAPSHOT state.
After the 0.9 release, policy-0.90-SNAPSHOT was not available
(which is fine), and was named to policy-0.92-SNAPSHOT.jar. This
cause problems to dependent projects.
So due to above reasons, I feel putting the version number in to the
SNAPSHOT jar is not a good idea at all. So I'd like propose not to put
the version number with any of the commons projects jars. For example,
the latest policy jar will be policy-SNAPSHOT.jar.
What do you all think ?
-- Chinthaka
--
Dan Diephouse
Envoi Solutions
http://envoisolutions.com
http://netzooid.com/blog
