Return-Path: X-Original-To: apmail-flex-dev-archive@www.apache.org Delivered-To: apmail-flex-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 16DE918830 for ; Fri, 31 Jul 2015 20:54:34 +0000 (UTC) Received: (qmail 49187 invoked by uid 500); 31 Jul 2015 20:54:33 -0000 Delivered-To: apmail-flex-dev-archive@flex.apache.org Received: (qmail 49148 invoked by uid 500); 31 Jul 2015 20:54:33 -0000 Mailing-List: contact dev-help@flex.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@flex.apache.org Delivered-To: mailing list dev@flex.apache.org Received: (qmail 49136 invoked by uid 99); 31 Jul 2015 20:54:33 -0000 Received: from Unknown (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 31 Jul 2015 20:54:33 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 07E89D95BF for ; Fri, 31 Jul 2015 20:54:33 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3.001 X-Spam-Level: *** X-Spam-Status: No, score=3.001 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id 8jBRFK08e9OM for ; Fri, 31 Jul 2015 20:54:21 +0000 (UTC) Received: from mail-la0-f43.google.com (mail-la0-f43.google.com [209.85.215.43]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id CC83543CCD for ; Fri, 31 Jul 2015 20:54:20 +0000 (UTC) Received: by labks4 with SMTP id ks4so5686979lab.0 for ; Fri, 31 Jul 2015 13:54:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=4nvftQqPkRAQX5M5foNL/GLVn1nCDbHecsAPF0dQeCI=; b=L4XrFqqCR+OCvZzSNEDpuk4+GtGKhKocKUoZGxusustlzw7cd8S3pRZm46D99bhdxg G1hrGx7UqS37+0mN6vvNSpmtCd0gjeCIeLDvuDJoDtGSya1cEIq44ZESi1iKjsLH9Nct CVOz7T5w9MPWiyrq/tBb2CXeBpLZtSrPTkG6Rpd5YwNrXlMLDjx8Wz394EPpOqEoK6Qj uOYMezRjAa0bDMy29cLbYK35MArqhAaDgBdBpPVtSdqxIrSNskJuzz2RRxZFUOktmLJL E3QZPaCqNjh2nObYJtEehe++t+B/+687q6TxoeZCdbALqfvvqAuEM8qpcKL2esBYTVMB VqWA== MIME-Version: 1.0 X-Received: by 10.112.151.178 with SMTP id ur18mr5332438lbb.59.1438376053724; Fri, 31 Jul 2015 13:54:13 -0700 (PDT) Sender: carlos.rovira@gmail.com Received: by 10.25.16.229 with HTTP; Fri, 31 Jul 2015 13:54:13 -0700 (PDT) In-Reply-To: References: Date: Fri, 31 Jul 2015 22:54:13 +0200 X-Google-Sender-Auth: 2wo43I532ElXBApHG4i-1_eiOSU Message-ID: Subject: Re: [FlexJS] FlexJS installation - bundle Google Closure Library? From: Carlos Rovira To: "dev@flex.apache.org" Content-Type: multipart/alternative; boundary=047d7beb98aabc6d21051c3205d7 --047d7beb98aabc6d21051c3205d7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable This is one of the things we could do to ease development with FlexJs. As Om said, there is no real adventage on use latest GCL, but it would cause lots of users failure downloading and testing. So we this things are easy to fix and was in the set I was referring to. We should take into account that rest of devs approaching FlexJS haven't the high level knowledge of this technology that people in this project have. So they must read , search an figure what we did, so we should make this labor super easy or this guys would fail in his try and would never return. Just my thoughts... El viernes, 31 de julio de 2015, OmPrakash Muppirala escribi=C3=B3: > On Thu, Jul 30, 2015 at 6:09 AM, Alex Harui > wrote: > > > If someone wants to make these changes, I won=E2=80=99t object, but IMO= , Google > > Closure Library changes often, usually for the better. Bundling will t= ie > > a FlexJS release to a particular version of GCL and that may not always > be > > desirable at this point. > > > From what I have seen, GCL is used behind the scenes by the FlexJS > compiler, i.e. there is no way for the user to do anything directly with > GCL. I am not sure what advantage we get by getting the latest GCL libra= ry > all the time. > > I believe tying a FlexJS release to a particular version of GCL is a good > thing. > > > > I believe we have the option of changing the > > installer so it downloads GCL without asking for license approval as > well. > > > > > That does not solve the problem of the FlexJS installation failing. The > GCL download step can still fail, which seems to be happening a lot. > > Thanks, > Om > > > > -Alex > > > > On 7/30/15, 4:26 AM, "Kessler CTR Mark J" > > > wrote: > > > > >+1 > > > > > >-Mark > > > > > >-----Original Message----- > > >From: Justin Mclean [mailto:justin@classsoftware.com ] > > >Sent: Wednesday, July 29, 2015 8:40 PM > > >To: dev@flex.apache.org > > >Subject: Re: [FlexJS] FlexJS installation - bundle Google Closure > Library? > > > > > >Hi, > > > > > >> Since Google Closure Library is also Apache licensed, can we package > it > > >> with the binary release instead of having the Installer download it > > >> separately? > > > > > >+1 and also any other MIT or BSD licensed stuff. Mean will have to mak= e > > >some minor mods to NOTICE/LICENSE but it's straight forward. > > > > > >Justin > > > > > --=20 Carlos Rovira Director General M: +34 607 22 60 05 http://www.codeoscopic.com http://www.avant2.es Este mensaje se dirige exclusivamente a su destinatario y puede contener informaci=C3=B3n privilegiada o confidencial. Si ha recibido este mensaje p= or error, le rogamos que nos lo comunique inmediatamente por esta misma v=C3= =ADa y proceda a su destrucci=C3=B3n. De la vigente Ley Org=C3=A1nica de Protecci=C3=B3n de Datos (15/1999), le c= omunicamos que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC S.A. La finalidad de dicho tratamiento es facilitar la prestaci=C3=B3n del servicio o informaci=C3=B3n solicitados, teniendo usted derecho de acceso, rectificaci=C3=B3n, cancelaci=C3=B3n y oposici=C3=B3n de sus datos dirigi= =C3=A9ndose a nuestras oficinas c/ Tres Creus, n=C2=BA 104, 2-1, 08202 de Sabadell (Barcelona) con= la documentaci=C3=B3n necesaria. --047d7beb98aabc6d21051c3205d7--