Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 10680200C0F for ; Thu, 2 Feb 2017 10:18:11 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 0EE15160B57; Thu, 2 Feb 2017 09:18:11 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 0F124160B54 for ; Thu, 2 Feb 2017 10:18:08 +0100 (CET) Received: (qmail 64099 invoked by uid 500); 2 Feb 2017 09:18:07 -0000 Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list dev@ignite.apache.org Received: (qmail 64087 invoked by uid 99); 2 Feb 2017 09:18:06 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Feb 2017 09:18:06 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 75204C0258 for ; Thu, 2 Feb 2017 09:18:06 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.479 X-Spam-Level: ** X-Spam-Status: No, score=2.479 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gridgain-com.20150623.gappssmtp.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id c6s4eVdeI_QL for ; Thu, 2 Feb 2017 09:18:01 +0000 (UTC) Received: from mail-oi0-f54.google.com (mail-oi0-f54.google.com [209.85.218.54]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id E7F735FDAA for ; Thu, 2 Feb 2017 09:18:00 +0000 (UTC) Received: by mail-oi0-f54.google.com with SMTP id w204so5824883oiw.0 for ; Thu, 02 Feb 2017 01:18:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gridgain-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=M3U4mfC1KgLJdZmKJFus/l/K5kW9E8mRiclOdvKLr6Y=; b=oPjMtA9WK6SxaRUlM+IKY1sP5lV5QajzWaZzdZTAvo5jEZuI/m0tz4hg+l7xLgXD5x qW54WiJvYYwFZFtTGXM38u7dEEZYiJ8bv5HPdOxv0kOwQu+og3EX6OEYxugEm6zoXzL2 1J65I53NjxBBjQsCavc2gDwoIJbZjOorm/EKV5RF27H3Aqg1uRYergrno/gZYjUFUuPr sy5Nbhm3UT0Qj7mLR8VAl9EUc5vpZRJmnLJPUovYbfBJ7Eq0e6l0hun14dG9Rk1ybKni 0PH0coUMnkz2xNorCHSAtMxcDmpu8/wRw0o/ZfxnPYcVvxNgBGm8pYeQSm6b3zfkNVBO bvIw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=M3U4mfC1KgLJdZmKJFus/l/K5kW9E8mRiclOdvKLr6Y=; b=UQk4YhKt2ZRazTDNphC6DS4Hl33NwzEf0SrxatQe5ybd+FnfYAMPaV2B95naMVj9tp 08JHYhabXTbJ9upD9hZw7DUWSrRakfmQHfxf92xRDyP5CUfxXwGXCD+PuvIX4O2s41Xb OLBrrNuA8RG8vIgiOUolZtakYD0/UlZw0AUoSEMTE/lRmCQZF7T0jJ46VslS7wLaWpQi Ofba1gz4A3TIc+/xC9EfgcPIMLnW6uclsjl4A0hZCy9EJuD+yRPCKvYDIgFXvlPqi10f 11piikFlR1Gt/W6FJlxyamQABM4BXcBC5BaGd5ESKeln+Oxho1jTvHCrw/2DrgA40N45 4f7Q== X-Gm-Message-State: AIkVDXKPF7sbgDe4QamgoLFmx+y5Yh3haxpmXhjYpq9hT2SuIz4S05LZODgWzhihWWwSxoA71XQcYqe7huHAMu7D X-Received: by 10.202.181.11 with SMTP id e11mr3679601oif.57.1486027073828; Thu, 02 Feb 2017 01:17:53 -0800 (PST) MIME-Version: 1.0 Received: by 10.157.39.71 with HTTP; Thu, 2 Feb 2017 01:17:53 -0800 (PST) In-Reply-To: <414CCEB4-26A8-4BD9-89BF-AAB2F850EA04@apache.org> References: <70D04D83-487C-4E43-A442-90537C2AC30F@apache.org> <03FEEAF9-6DA8-44FD-B7D9-AF108CC05F21@apache.org> <101D53C9-67E6-44E5-9721-ACDC81F56A3B@apache.org> <414CCEB4-26A8-4BD9-89BF-AAB2F850EA04@apache.org> From: Anton Vinogradov Date: Thu, 2 Feb 2017 12:17:53 +0300 Message-ID: Subject: Re: moving to geronimo JCache jar To: dev@ignite.apache.org Content-Type: multipart/alternative; boundary=001a113cfef8dcd106054788a301 archived-at: Thu, 02 Feb 2017 09:18:11 -0000 --001a113cfef8dcd106054788a301 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Val, cache-api lib license at maven now looks like JSR-000107 JCACHE 2.9 Public Review - Updated Specification License > https://raw.github.com/jsr107/jsr107spec/master/LICENSE.txt and I see replacement at pull-request related to this thread #if ( $license.name.contains("JSR-000107 JCACHE 2.9 Public Review") ) #set( $licenseName =3D "Apache License, Version 2.0" ) and I don't like it :) Denis, As you can see https://github.com/jsr107/jsr107spec/blob/master/pom.xml has version 1.*1*.0-SNAPSHOT and it's just not released at maven. Can we ask cache-api team to release it? Anyways, I see no issues here, we just have to keep current license JSR-000107 JCACHE 2.9 Public Review - Updated Specification License > https://raw.github.com/jsr107/jsr107spec/master/LICENSE.txt and wait for cache-api 1.*1*.0 release. On Wed, Feb 1, 2017 at 11:03 PM, Denis Magda wrote: > Guys, > > JSR 107 spec as well as the reference implementation were updated in all > the places: > https://github.com/jsr107/jsr107spec/blob/master/LICENSE.txt < > https://github.com/jsr107/jsr107spec/blob/master/LICENSE.txt> > https://github.com/jsr107/jsr107spec/blob/master/pom.xml < > https://github.com/jsr107/jsr107spec/blob/master/pom.xml> > https://github.com/jsr107/RI/blob/master/LICENSE.txt < > https://github.com/jsr107/RI/blob/master/LICENSE.txt> > https://github.com/jsr107/RI/blob/master/pom.xml < > https://github.com/jsr107/RI/blob/master/pom.xml> > > Even if you go to Maven > https://mvnrepository.com/artifact/javax.cache/cache-api/1.0.0 < > https://mvnrepository.com/artifact/javax.cache/cache-api/1.0.0> > > and scroll down to Licenses section then you will see the following > > License URL > JSR-000107 JCACHE 2.9 Public Review - Updated Specification License > https://raw.github.com/jsr107/jsr107spec/master/LICENSE.txt < > https://raw.github.com/jsr107/jsr107spec/master/LICENSE.txt> > > But if anyone clicks on the link he will see that, in fact, Maven shows > outdated information. > > So, it=E2=80=99s Maven=E2=80=99s issue not ours. It might be fixed soon. = We as a product > that uses JSR 107 are free to claim in our license files that this JSR > already conforms to Apache 2.0. > > =E2=80=94 > Denis > > > On Feb 1, 2017, at 3:08 AM, Alexander Fedotov < > alexander.fedotoff@gmail.com> wrote: > > > > Igniters, please advise on it. > > > > Also, does anyone know whether it's allowable by Apache License, Versio= n > > 2.0 to create a custom build and provide it via > > Nexus, Artifactory, you name it. Currently, both the license and POM at > > JSR107 GitHub are conformant, so it's just a matter > > of a build being provided. > > > > On Wed, Feb 1, 2017 at 1:52 PM, Anton Vinogradov < > avinogradov@gridgain.com> > > wrote: > > > >> Guys, > >> > >> I've checked review and I don't like replacement "JSR 107 .... " with > >> "Apache 2.0" even given they are equals. > >> We should provide licenses way it is, even in case it so sophisticated > :) > >> > >> On Wed, Feb 1, 2017 at 1:20 PM, Alexander Fedotov < > >> alexander.fedotoff@gmail.com> wrote: > >> > >>> PR updated > >>> > >>> On Tue, Jan 31, 2017 at 10:42 PM, Alexander Fedotov < > >>> alexander.fedotoff@gmail.com> wrote: > >>> > >>>> Denis, it is my mistake to leave the header unchanged. > >>>> It should be fixed because from now on the generation of license not= es > >>> for > >>>> dependencies under Apache Software License is enabled according to t= he > >>>> point 3 in JIRA . > >>>> I'll fix it and your notes in Upsource and update the PR. > >>>> > >>>> > >>>> > >>>> On Tue, Jan 31, 2017 at 10:30 PM, Denis Magda > >> wrote: > >>>> > >>>>> Alexander, provided review notes in the Upsource. > >>>>> > >>>>> However, I=E2=80=99m still a bit concerned about the content of > >>>>> ignite-core-licenses.txt (see attached). The file says that it > >> contains > >>>>> licenses different from the Apache Software license but in fact lis= ts > >>>>> shmem, Intellij IDEA annotations and JSR 107 all of which are > >> available > >>>>> under Apache 2.0. > >>>>> > >>>>> Why is this so? Can someone explain? Dmitriy, probable you know the > >>>>> reason. > >>>>> > >>>>> > >>>>> =E2=80=94 > >>>>> Denis > >>>>> > >>>>> > >>>>>> On Jan 30, 2017, at 12:19 PM, Denis Magda > >> wrote: > >>>>>> > >>>>>> Alexander, thanks! > >>>>>> > >>>>>> I=E2=80=99ll review it in the nearest couple of days. > >>>>>> > >>>>>> =E2=80=94 > >>>>>> Denis > >>>>>> > >>>>>>> On Jan 30, 2017, at 5:10 AM, Alexander Fedotov < > >>>>> alexander.fedotoff@gmail.com> wrote: > >>>>>>> > >>>>>>> Hi, > >>>>>>> > >>>>>>> Created Upsource review for the subject: > >>>>>>> http://reviews.ignite.apache.org/ignite/review/IGNT-CR-82 > >>>>>>> > >>>>>>> On Mon, Jan 30, 2017 at 11:52 AM, Alexander Fedotov < > >>>>>>> alexander.fedotoff@gmail.com> wrote: > >>>>>>> > >>>>>>>> Hi all, > >>>>>>>> > >>>>>>>> https://issues.apache.org/jira/browse/IGNITE-3793 is completed. > >>>>>>>> Kindly take a look at the corresponding PR > >>>>> https://github.com/apache/i > >>>>>>>> gnite/pull/1475 . > >>>>>>>> > >>>>>>>> On Wed, Jan 25, 2017 at 8:04 PM, Denis Magda > >>>>> wrote: > >>>>>>>> > >>>>>>>>> We need to replace content of ignite-core-licenses.txt file whi= ch > >>> is > >>>>> the > >>>>>>>>> following at the moment > >>>>>>>>> > >>>>>>>>> // ------------------------------------------------------------ > >>>>> ------ > >>>>>>>>> // List of ignite-core module's dependencies provided as a part > >> of > >>>>> this > >>>>>>>>> distribution > >>>>>>>>> // which licenses differ from Apache Software License. > >>>>>>>>> // ------------------------------------------------------------ > >>>>> ------ > >>>>>>>>> > >>>>>>>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > >>>>>>>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > >>>>>>>>> For JSR107 API and SPI (https://github.com/jsr107/jsr107spec) > >>>>>>>>> javax.cache:cache-api:jar:1.0.0 > >>>>>>>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > >>>>>>>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > >>>>>>>>> This product bundles JSR107 API and SPI which is available unde= r > >> a: > >>>>>>>>> JSR-000107 JCACHE 2.9 Public Review - Updated Specification > >>> License. > >>>>> For > >>>>>>>>> details, see https://raw.github.com/jsr107/ > >>>>> jsr107spec/master/LICENSE.txt. > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> Updated this ticket description: https://issues.apache.org/jira > >>>>>>>>> /browse/IGNITE-3793 > >>>>>>>>> > >>>>>>>>> =E2=80=94 > >>>>>>>>> Denis > >>>>>>>>>> On Jan 24, 2017, at 8:24 PM, Dmitriy Setrakyan < > >>>>> dsetrakyan@apache.org> > >>>>>>>>> wrote: > >>>>>>>>>> > >>>>>>>>>> Awesome, you are right. I just checked and the license is inde= ed > >>>>> Apache > >>>>>>>>>> 2.0. Is there anything we need to do at all right now? > >>>>>>>>>> > >>>>>>>>>> On Tue, Jan 24, 2017 at 8:17 PM, Valentin Kulichenko < > >>>>>>>>>> valentin.kulichenko@gmail.com> wrote: > >>>>>>>>>> > >>>>>>>>>>> This change was incorporated in this ticket: > >>> https://issues.apache > >>>>> . > >>>>>>>>>>> org/jira/browse/IGNITE-3793. We can't do it before 2.0 for > >>>>>>>>> compatibility > >>>>>>>>>>> reasons. > >>>>>>>>>>> > >>>>>>>>>>> However, my point is that they changed the license to Apache > >> 2.0, > >>>>> so > >>>>>>>>> I'm > >>>>>>>>>>> not sure that licensing issue still exists. > >>>>>>>>>>> > >>>>>>>>>>> -Val > >>>>>>>>>>> > >>>>>>>>>>> On Tue, Jan 24, 2017 at 7:04 PM, Dmitriy Setrakyan < > >>>>>>>>> dsetrakyan@apache.org> > >>>>>>>>>>> wrote: > >>>>>>>>>>> > >>>>>>>>>>>> Any reason why we need to wait for 2.0? Sorry if this has > >>> already > >>>>> been > >>>>>>>>>>>> discussed. > >>>>>>>>>>>> > >>>>>>>>>>>> On Tue, Jan 24, 2017 at 7:02 PM, Denis Magda < > >> dmagda@apache.org > >>>> > >>>>>>>>> wrote: > >>>>>>>>>>>> > >>>>>>>>>>>>> Yes, we planned to do that in 2.0. Val, the ticket is close= d > >>>>>>>>>>>>> https://issues.apache.org/jira/browse/IGNITE-2949 < > >>>>>>>>>>>>> https://issues.apache.org/jira/browse/IGNITE-2949> > >>>>>>>>>>>>> > >>>>>>>>>>>>> Do we need to reopen it making sure that geronimo jar is > >> added > >>> to > >>>>>>>>> 2.0? > >>>>>>>>>>>>> > >>>>>>>>>>>>> =E2=80=94 > >>>>>>>>>>>>> Denis > >>>>>>>>>>>>> > >>>>>>>>>>>>>> On Jan 24, 2017, at 6:36 PM, Dmitriy Setrakyan < > >>>>>>>>>>> dsetrakyan@apache.org> > >>>>>>>>>>>>> wrote: > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> We absolutely need to upgrade to the geronimo jcache libra= ry > >>> in > >>>>> the > >>>>>>>>>>>> next > >>>>>>>>>>>>>> release. > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> On Tue, Jan 24, 2017 at 3:45 PM, Valentin Kulichenko < > >>>>>>>>>>>>>> valentin.kulichenko@gmail.com> wrote: > >>>>>>>>>>>>>> > >>>>>>>>>>>>>>> Guys, > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>>> I noticed that the JCache license was updated to Apache 2= .0 > >>>>> several > >>>>>>>>>>>>> months > >>>>>>>>>>>>>>> ago [1]. However, there was no release with the new licen= se > >>> and > >>>>>>>>>>> 1.0.0 > >>>>>>>>>>>>> still > >>>>>>>>>>>>>>> has the old license name in the POM file [2] (the link is > >>>>> pointing > >>>>>>>>>>> to > >>>>>>>>>>>>> the > >>>>>>>>>>>>>>> new one though). > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>>> Is this enough from legal standpoint? Do we still need to > >>> move > >>>>> to > >>>>>>>>>>>>> Geronimo? > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>>> [1] https://github.com/jsr107/jsr1 > >>>>> 07spec/blob/master/LICENSE.txt > >>>>>>>>>>>>>>> [2] http://mvnrepository.com/artif > >>>>> act/javax.cache/cache-api/1.0.0 > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>>> -Val > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>>> On Mon, Apr 11, 2016 at 5:43 PM, Dmitriy Setrakyan < > >>>>>>>>>>>>> dsetrakyan@apache.org> > >>>>>>>>>>>>>>> wrote: > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> I would say that we are OK with alpha for now, as there = is > >>> no > >>>>> real > >>>>>>>>>>>>>>>> difference between 1.0-alpha and 1.0. We can switch to 1= .0 > >>>>>>>>> whenever > >>>>>>>>>>>>>>>> geronimo project updates the JAR. > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> D. > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> On Mon, Apr 11, 2016 at 5:10 PM, Valentin Kulichenko < > >>>>>>>>>>>>>>>> valentin.kulichenko@gmail.com> wrote: > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> Folks, > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> I tried to switch to Geronimo and it works fine for me. > >> Are > >>>>> we > >>>>>>>>>>> going > >>>>>>>>>>>>> to > >>>>>>>>>>>>>>>>> wait for version 1.0, or we're OK with alpha? > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> -Val > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> On Mon, Mar 28, 2016 at 7:37 AM, Dmitriy Setrakyan < > >>>>>>>>>>>>>>>> dsetrakyan@apache.org> > >>>>>>>>>>>>>>>>> wrote: > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> Igniters, > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> Can someone check if the Geronimo JCache jar is the sa= me > >>> as > >>>>> the > >>>>>>>>>>>>>>> JSR107? > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> http://mvnrepository.com/artifact/org.apache.geronimo. > >>>>>>>>>>>>>>>> specs/geronimo-jcache_1.0_spec > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> We should try switching to the Geronimo JAR starting > >> next > >>>>>>>>>>> release, > >>>>>>>>>>>> as > >>>>>>>>>>>>>>>> it > >>>>>>>>>>>>>>>>> is > >>>>>>>>>>>>>>>>>> licensed under Apache 2.0. > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> D. > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>> > >>>>>>>>>>>>> > >>>>>>>>>>>>> > >>>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> -- > >>>>>>>> Kind regards, > >>>>>>>> Alexander. > >>>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> -- > >>>>>>> Kind regards, > >>>>>>> Alexander. > >>>>>> > >>>>> > >>>>> > >>>>> > >>>> > >>>> > >>>> -- > >>>> Kind regards, > >>>> Alexander. > >>>> > >>> > >>> > >>> > >>> -- > >>> Kind regards, > >>> Alexander. > >>> > >> > > > > > > > > -- > > Kind regards, > > Alexander. > > --001a113cfef8dcd106054788a301--