2014-10-14 23:22 GMT+02:00 Gary Gregory <garydgreg...@gmail.com>: > The package name and Maven coords must be kept in sync to avoid jar hell. > > You cannot change one without changing the other. > > If 2.0 is to be compatible with 1.3, then the same Maven coords must be > kept.
Well that's where it is ambiguous. It is without being. If you have a dep built with 1.3 then it can be broken but if your project was integrating with 1.3 then rebuilding it with 2.0 should work (that said we changed - relaxed few signature and really changed few ones but shouldn't be that impacting in practice). So to summarize keeping same packages is mainly to avoid a lot of work for users. > > If 2.0 is not binary compatible, then you must change the package and and > Maven coords. > > That's how all Commons project do it AFAIK. > > I am sure Sebb can elaborate if needed. > > Gary > > > On Tue, Oct 14, 2014 at 5:13 PM, Romain Manni-Bucau <rmannibu...@gmail.com> > wrote: > >> Well coord changed for multiple reasons IIRC: >> >> 1) be aligned with commons projects >> 2) we upgraded to 2 (for binary + jcache reasons) so it seemd the >> moment to accept such a change >> 3) we upgraded to java 6 IIRC >> 4) project structure changed >> >> That said if you replace old jcs coord by commons-jcs-core module ones >> compatibility should be ok while you run/compile on java 6 so I don't >> think we should change the packages. >> >> >> >> Romain Manni-Bucau >> @rmannibucau >> http://www.tomitribe.com >> http://rmannibucau.wordpress.com >> https://github.com/rmannibucau >> >> >> 2014-10-14 23:04 GMT+02:00 Gary Gregory <garydgreg...@gmail.com>: >> > It looks like the Maven coords have changed which means the package name >> > must change, probably to ...jcs2, which means the artifact ID could >> > probably stand to be post-fixed with a 2 as well. >> > >> > Did the Maven coords change because version 2 breaks binary compatibility >> > with 1.3? >> > >> > Gary >> > >> > On Tue, Oct 14, 2014 at 4:23 PM, Romain Manni-Bucau < >> rmannibu...@gmail.com> >> > wrote: >> > >> >> Hello guys, >> >> >> >> seems we are good regarding dependencies now >> >> >> >> do we try a release this week? 2.0-alpha-1? Anything blocking? >> >> >> >> >> >> Romain Manni-Bucau >> >> @rmannibucau >> >> http://www.tomitribe.com >> >> http://rmannibucau.wordpress.com >> >> https://github.com/rmannibucau >> >> >> >> --------------------------------------------------------------------- >> >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> >> For additional commands, e-mail: dev-h...@commons.apache.org >> >> >> >> >> > >> > >> > -- >> > E-Mail: garydgreg...@gmail.com | ggreg...@apache.org >> > 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: dev-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org >> >> > > > -- > E-Mail: garydgreg...@gmail.com | ggreg...@apache.org > 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: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
