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
st...@hibernate.org
Principal Software Engineer
JBoss, a divi
On Mon, 16 Mar 2009 15:27:06 +0100, Alaa Mohsen
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 affect
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
Ah year that's my fault. But Isn't beta4 up in the maven cloud? I
don't understand why what I commit in trunk does affect released
versions?
On Mar 15, 2009, at 04:46, Alaa Mohsen wrote:
Hello guys,
I'm facing a problem right now, and the problem is that we
currently have Hibernate
