> On May 29, 2008, at 07:02, Max Bowsher wrote: >> As there is a mislabelled hibernate-commons-annotations 3.3.0.ga in the >> wild (Maven2 central and possibly other places), perhaps it might be >> worth arbitrarily bumping that project's version number up to 3.4.0 for >> new releases, in the interests of avoiding confusion?
Emmanuel Bernard wrote: > I added a README here > (http://repository.jboss.org/maven2/org/hibernate/hibernate-commons-annotations/README.TXT) > and there > (http://repository.jboss.org/maven2/org/hibernate/hibernate-commons-annotations/3.3.0.ga/README.TXT) > > I am uncomfortable about the idea of artificially bumping versions > because of maven. Let's ee how it goes I agree it's rather irksome that any project has to modify itself to cope with a 3rd party distributor mistake - but I think it would be a really bad idea to ever release a 3.3.0 version of commons-annotations, given the confusion that would be caused. With that in mind, I suppose you could go: 3.1.0, 3.2.0, 3.4.0 - but that isn't any less artificial. Max.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
