"skajotde" wrote : I think it is great that library can be used outside EJB3 and provides model and metatada. But main purposes of this libraries are be part of EJB3 product so I think it should be versioned in one way with one version number for releases of all libraries. So change in library-a should increase version in all libraries ?
I have two arguments. 1) It takes time/resources away from dev to re-release projects with no changes. 2) If there's no difference in the code between 1.0.0 and 1.0.1, what does bumping the version number accomplish? You're labelling a new version, signalling that some change has been made. It seems like your concerns would be alleviated with another matrix showing all component versions that comprise an EJB3 release? S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4204744#4204744 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4204744 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
