2009/5/15 Christian Schulte <c...@schulte.it> > Joerg Hohwiller schrieb: > > Why? In SCM there should never be a non-snapshot module with snapshot > > dependencies. Further a non-snapshot module should not be modified except > > for pom.xml > > /trunk at revision 4 > +root(1.2-SNAPSHOT) > +A(1.0) > +B(1.3-SNAPSHOT) > > If the pom of A(1.0) inherits from root(1.2-SNAPSHOT) and > root(1.2-SNAPSHOT) declares a dependency management with snapshot > versions and A(1.0) declares a dependency without an explicit version, > than A(1.0) may start depending on a snapshot. If you do 'mvn deploy' at > root(1.2-SNAPSHOT) then A(1.0) will be deployed to the release > repository, everything else to the snapshot repository. >
If A(1.0) has root(1.2-SNAPSHOT) as a parent it should never have been released as the pom for A(1.0) is based on content from root(1.2-SNAPSHOT) which is subject to change... which means that a released pom does not have a definitive content... bad karma -Stephen
