I don't think it has anything to do necessarily with framework or not. The class loading model is just much easier to deal with these situations. As Benson said, however, there are definitely other issues to contend with. On Thu, Jun 2, 2016 at 6:14 PM Benedikt Ritter <brit...@apache.org> wrote:
> James Carman <ja...@carmanconsulting.com> schrieb am Fr., 3. Juni 2016 um > 00:04 Uhr: > > > You've been in karaf land for too long! ;) > > > > It's probably a different story when you're working on a framework. It > pretty unlikely to end up with two version of Spring or Hibernate in your > app. But for a library as wildly used as commons-lang it becomes more > likely. > > > > > > On Thu, Jun 2, 2016 at 5:36 PM Benson Margulies <bimargul...@gmail.com> > > wrote: > > > > > I don't understand what's wrong with semantic versioning and keeping > > > the same maven coordinates. No sane person should be using RELEASE or > > > LATEST. > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > > > >
