It's not just the broken parts that your dependencies may be using. The strategy Commons uses is the only way any of us know to permit forward movement while avoiding jar hell.
Matt On Oct 17, 2014 8:35 AM, "Romain Manni-Bucau" <[email protected]> wrote: > 2014-10-17 15:28 GMT+02:00 Benedikt Ritter <[email protected]>: > > 2014-10-17 14:42 GMT+02:00 Romain Manni-Bucau <[email protected]>: > > > >> 2014-10-17 13:52 GMT+02:00 Gary Gregory <[email protected]>: > >> > On Fri, Oct 17, 2014 at 6:24 AM, Romain Manni-Bucau < > >> [email protected]> > >> > wrote: > >> > > >> >> 2014-10-17 12:23 GMT+02:00 Benedikt Ritter <[email protected]>: > >> >> > Hi, > >> >> > > >> >> > 2014-10-16 15:30 GMT+02:00 Romain Manni-Bucau < > [email protected] > >> >: > >> >> > > >> >> > <snip> > >> >> > > >> >> >> > >> >> >> In TomEE the stack uses [lang], then [lang3] was created and now > >> TomEE > >> >> >> needs [lang] + [lang3] where actually it only needs [lang] > features, > >> >> >> ie suppose package didn't change then we wouldn't have had any > issue. > >> >> >> So it means you tend to import multiple versions of the same lib > just > >> >> >> cause few parts were broken even if it doesn't affect you. That's > a > >> >> >> bit sad IMO. > >> >> >> > >> >> > > >> >> > If there is anything missing in lang3 that blocks you from > migrating > >> >> > completely, can you tell us what that is? Maybe we can fix that... > >> >> > > >> >> > >> >> Issue is not in [commons] but in dependencies. The code we own > >> >> migrated but not all our deps. > >> >> > >> > > >> > > >> > I suggest you ask/Jira each dep to update their [lang] to the latest. > >> That > >> > has worked for me in the past with different FOSS projects I've made > the > >> > request about this and that libraries. > >> > > >> > Some projects will be receptive and at least reply to you right away, > >> > others won't. Patches help of course since will require at least > import > >> > changes. > >> > > >> > >> yep, main issue ATM is some can't or doesn't maitain the version we > >> use - excepted for security issues (we are bound to a EE version for > >> instance). It meanse it will be forgotten in few years but it also > >> means we can get the same with [lang3] and [lang4] so clearly > >> something to tackle at [commons] level. We can't just ask everybody to > >> update each time IMHO. > >> > > > > The alternative is, that TomEE won't run at all because of incompatible > API > > changes. I would vote for the lesser evil ;-) > > > > No, if broken part are provided in a -legacy.jar or a > -compatibility.jar there would be no issue. > > > > >> > >> > Gary > >> > > >> > > >> >> > >> >> > Benedikt > >> >> > > >> >> > > >> >> > -- > >> >> > http://people.apache.org/~britter/ > >> >> > http://www.systemoutprintln.de/ > >> >> > http://twitter.com/BenediktRitter > >> >> > http://github.com/britter > >> >> > >> >> --------------------------------------------------------------------- > >> >> To unsubscribe, e-mail: [email protected] > >> >> For additional commands, e-mail: [email protected] > >> >> > >> >> > >> > > >> > > >> > -- > >> > E-Mail: [email protected] | [email protected] > >> > Java Persistence with Hibernate, Second Edition > >> > <http://www.manning.com/bauer3/> > >> > JUnit in Action, Second Edition <http://www.manning.com/tahchiev/> > >> > Spring Batch in Action <http://www.manning.com/templier/> > >> > Blog: http://garygregory.wordpress.com > >> > Home: http://garygregory.com/ > >> > Tweet! http://twitter.com/GaryGregory > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [email protected] > >> For additional commands, e-mail: [email protected] > >> > >> > > > > > > -- > > http://people.apache.org/~britter/ > > http://www.systemoutprintln.de/ > > http://twitter.com/BenediktRitter > > http://github.com/britter > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
