Re: [hibernate-dev] [BVAL] POM Versions
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.
On Mon, Mar 16, 2009 at 3:30 PM, Emmanuel Bernard <emmanuel(a)hibernate.org>wrote:
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 Validator Alpha 2 as a dependency in our project, which has
> the Validation API Beta 4 as a dependency. The problem is that the latest
> changes in the API (including those in the Message Interpolator) were
> committed to Validation API Beta 4, and hence it made HV Alpha 2 unusable,
> since it calls metheods that were changed in the API. I guess that the
> current version should have been Beta 5 SNAPSHOT or something so that not to
> break the older builds that depend on Beta 4.
>
> Regards
> Alaa Nassef
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
Attachments:
- attachment.html (text/html — 2.1 KB)