[hibernate-dev] [BVAL] POM Versions

[Steve Ebersole]

Are y'all using SNAPSHOT versioning in your development poms?  

By the same logic below y'all should be using SNAPSHOT in your poms and
explicitly setting a version during release.

-  

Steve Ebersole
Project Lead
http://hibernate.org
steve at hibernate.org

Principal Software Engineer
JBoss, a division of Red Hat
http://jboss.com
http://redhat.com
steve.ebersole at jboss.com
steve.ebersole at redhat.com


On Mon, 2009-03-16 at 16:59 +0100, Hardy Ferentschik wrote:
> On Mon, 16 Mar 2009 15:27:06 +0100, Alaa Mohsen <alaa.mohsen at egyptdc.com>  
> wrote:
> 
> > Well, we have our own integration server which installs the new builds to
> > our local repository. I uninstalled the new artifacts with the wrong
> > version, and got the ones from the older ones and we fixed our builds.  
> > What I meant by affecting the released version is for the people with  
> > cases like ours, where they rely on a CI server to be able to use/test  
> > different
> > snapshots.
> 
> I guess the best practise is to up the version number right after a  
> release. I am trying
> to do that in the reference implementation, but we should do the same for  
> the spec.
> 
> However, there is no guarantee that something like this happens again or  
> some other temporary problem.
> Maybe instead of installing all builds from your ci server into your local  
> repository you should
> consider to switch to an explicit install.
> 
> Of course it is great for us that you are pretty much testing all our  
> changes immediately ;-)
> 
> --Hardy
> 
> 
> 
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev