On Sun, Nov 6, 2016 at 7:44 AM, Oliver Heger <oliver.he...@oliver-heger.de> wrote:
> Hi, > > sorry, I don't want to stand in the way of the release. It is just that > in the past we used to be very careful with artifacts deployed to Maven > central and their compatibility. When I did alpha and beta releases for > [configuration] 2.0 it was decided that these artifacts must not be > published to Maven central because incompatibilities between succeeding > alphas/betas or the final 2.0 version are likely. > > If the JCS betas are going to Maven central, I therefore assumed that > some means were taken to deal with incompatibilities. Otherwise, if some > 3rd party project has the (stupid) idea to depend on such a beta, we are > in jar hell. > That is a risk indeed. The alternatives would be: - Release betas under a beta package name - Not release betas at all but just tag the software in svn/git. This makes is effectively impossible to use from Maven/Ivy/AndSoOn. Gary > > Oliver > > Am 05.11.2016 um 23:52 schrieb Gary Gregory: > > There is no need to maintain BC since 2.0 is not out. Changing package > > names and Maven coordinates must also happen hand in hand. Changing one > > means changing the other. > > > > Gary > > > > On Nov 5, 2016 1:37 PM, "Thomas Vandahl" <t...@apache.org> wrote: > > > >> Hi Oliver, > >> > >> On 05.11.16 21:18, Oliver Heger wrote: > >>> It seems that there are many breaking changes between this release and > >>> beta1; for instance, the clirr report for the core component lists > >>> numerous errors. Is it not against Commons policy to publish > >>> incompatible artifacts with the same maven and package coordinates to > >>> Maven central? > >> > >> I thought that is why we call it "beta"? It basically boils down again > >> to the question what should be considered a public API (which btw hasn't > >> changed since beta-1). > >> I have no problem with changing the coordinates but I'm pretty sure that > >> the next iteration to 2.0 final will introduce more incompatibilities > >> and we may run out of coordinates... > >> > >> As I see it, we are still in the transition from 1.3 > >> (org.apache.jcs:jcs) to 2.0 (org.apache.commons.jcs:commons-jcs-core) > >> but I'm ready to change whatever is necessary to get this out of the > door. > >> > >> Bye, Thomas. > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > >> For additional commands, e-mail: dev-h...@commons.apache.org > >> > >> > > > > --------------------------------------------------------------------- > 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 <https://www.amazon.com/gp/product/1617290459/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1617290459&linkCode=as2&tag=garygregory-20&linkId=cadb800f39946ec62ea2b1af9fe6a2b8> <http:////ir-na.amazon-adsystem.com/e/ir?t=garygregory-20&l=am2&o=1&a=1617290459> JUnit in Action, Second Edition <https://www.amazon.com/gp/product/1935182021/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1935182021&linkCode=as2&tag=garygregory-20&linkId=31ecd1f6b6d1eaf8886ac902a24de418%22> <http:////ir-na.amazon-adsystem.com/e/ir?t=garygregory-20&l=am2&o=1&a=1935182021> Spring Batch in Action <https://www.amazon.com/gp/product/1935182951/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1935182951&linkCode=%7B%7BlinkCode%7D%7D&tag=garygregory-20&linkId=%7B%7Blink_id%7D%7D%22%3ESpring+Batch+in+Action> <http:////ir-na.amazon-adsystem.com/e/ir?t=garygregory-20&l=am2&o=1&a=1935182951> Blog: http://garygregory.wordpress.com Home: http://garygregory.com/ Tweet! http://twitter.com/GaryGregory
