Return-Path: X-Original-To: apmail-legal-discuss-archive@www.apache.org Delivered-To: apmail-legal-discuss-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2443910DD1 for ; Thu, 20 Feb 2014 10:42:25 +0000 (UTC) Received: (qmail 2147 invoked by uid 500); 20 Feb 2014 10:42:12 -0000 Delivered-To: apmail-legal-discuss-archive@apache.org Received: (qmail 1578 invoked by uid 500); 20 Feb 2014 10:42:11 -0000 Mailing-List: contact legal-discuss-help@apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: Reply-To: legal-discuss@apache.org List-Id: Delivered-To: mailing list legal-discuss@apache.org Received: (qmail 1550 invoked by uid 99); 20 Feb 2014 10:42:09 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Feb 2014 10:42:09 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of stephen.alan.connolly@gmail.com designates 209.85.220.47 as permitted sender) Received: from [209.85.220.47] (HELO mail-pa0-f47.google.com) (209.85.220.47) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Feb 2014 10:42:04 +0000 Received: by mail-pa0-f47.google.com with SMTP id kp14so1736195pab.6 for ; Thu, 20 Feb 2014 02:41:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=4rgyhhP3iXc5WMfBmS0keCWjyRI3JccR/WhHv5CGcNc=; b=mcpIsHlItB8uzEsCGIGUehKidluvLqQSaxcQSr3rE91XxyDbaPO8tC34osSxl6zDUK 6PKBWPKNYAwpeH+778VN7tx3VPM60+3Zjvg2nEFafVdUSCL+AxplwFM3KK/4n2SfhIQv dXhjVSYr4nABenFr1N9B9K7QtHerCOTRMOgfJ0ezrYBHvehatWdykSz0wVfJRSyScst3 w2AvG2n5tXT5h+DElNQuw+bHuAsNiHYHxLJjdvbgvd4OCvTY/KjzXtjKPWvmb15LOgT+ Obu0ZV2/BK66q11G+EhKFA/sKIUevwF/2OS71K3+8KTI9nubM88iXqP2TRjZEWBfBoOh c7jQ== MIME-Version: 1.0 X-Received: by 10.66.50.105 with SMTP id b9mr1170532pao.9.1392892903081; Thu, 20 Feb 2014 02:41:43 -0800 (PST) Received: by 10.68.147.102 with HTTP; Thu, 20 Feb 2014 02:41:43 -0800 (PST) In-Reply-To: References: Date: Thu, 20 Feb 2014 10:41:43 +0000 Message-ID: Subject: Re: Creating compiler stubs From: Stephen Connolly To: "legal-discuss@apache.org" Content-Type: multipart/alternative; boundary=bcaec53f92adb2ce0604f2d42623 X-Virus-Checked: Checked by ClamAV on apache.org --bcaec53f92adb2ce0604f2d42623 Content-Type: text/plain; charset=ISO-8859-1 On 20 February 2014 10:11, Jochen Wiedmann wrote: > > > > On Thu, Feb 20, 2014 at 10:36 AM, Stephen Connolly < > stephen.alan.connolly@gmail.com> wrote: > > >> From a technical point of view, please do NOT do this. >> >> The Glassfish team at Sun did this very thing in producing a stub >> javaee.jar. Because it was a stub you could compile against it. But you >> could not run tests against it in any way shape or form. Worse still, you >> couldn't even unit test the bits of your code that did not call through to >> javaee APIs because the classloading would barf out. >> >> > Hi, Stephen, > > I am fully aware of the problems you are mentioning and believe that I can > handle them (for my limited use cases), perhaps by indeed implementing more > than a generated stub from time to time. > > However, I am specifically asking for legal concerns, because those are > what I'm unable to deal with. > > Btw: Is the software that created the stub javaee.jar available? I'm not > interested in reinventing the wheel... > I think all they did was use an ASM based class rewriter that stripped all the implementations out. The quick and dirty one they wrote would take about 15 minutes to write IIRC > > > Jochen > --bcaec53f92adb2ce0604f2d42623 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On 2= 0 February 2014 10:11, Jochen Wiedmann <jochen.wiedmann@gmail.com<= /a>> wrote:



On Thu, Feb 20, 2014= at 10:36 AM, Stephen Connolly <stephen.alan.connolly@gmail.= com> wrote:
=A0
From a technical point of view, pl= ease do NOT do this.

The Glassfish team at Sun did this very thing in producing a= stub javaee.jar. Because it was a stub you could compile against it. But y= ou could not run tests against it in any way shape or form. Worse still, yo= u couldn't even unit test the bits of your code that did not call throu= gh to javaee APIs because the classloading would barf out.


Hi, Stephen,

I am fully aware of the problems you are mentioning and believe that = I can handle them (for my limited use cases), perhaps by indeed implementin= g more than a generated stub from time to time.

However, I am specifically asking for legal concerns, becaus= e those are what I'm unable to deal with.

Btw: Is the= software that created the stub javaee.jar available? I'm not intereste= d in reinventing the wheel...

I think all they did was= use an ASM based class rewriter that stripped all the implementations out.= The quick and dirty one they wrote would take about 15 minutes to write II= RC
=A0


Jochen

--bcaec53f92adb2ce0604f2d42623--