Mailing-List: contact avro-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: avro-dev@hadoop.apache.org
Message-ID: <60050645.1262287409515.JavaMail.jira@brutus.apache.org>
Date: Thu, 31 Dec 2009 19:23:29 +0000 (UTC)
From: "Doug Cutting (JIRA)" <jira@apache.org>
To: avro-dev@hadoop.apache.org
Subject: [jira] Resolved: (AVRO-269) Use system compiler to test
 SpecificCompiler's generated code.
In-Reply-To: <1360235728.1262200049408.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/AVRO-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Doug Cutting resolved AVRO-269.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 1.3.0
     Hadoop Flags: [Reviewed]

I just committed this, with java compiler-based tests disabled in TestSchema.  Thanks, Philip!

> Use system compiler to test SpecificCompiler's generated code.
> --------------------------------------------------------------
>
>                 Key: AVRO-269
>                 URL: https://issues.apache.org/jira/browse/AVRO-269
>             Project: Avro
>          Issue Type: Test
>          Components: java
>            Reporter: Philip Zeyliger
>            Assignee: Philip Zeyliger
>            Priority: Minor
>             Fix For: 1.3.0
>
>         Attachments: AVRO-269.patch.txt
>
>
> Using the javax.tools API (http://java.sun.com/javase/6/docs/api/javax/tools/JavaCompiler.html),
> it's possible to test SpecificCompiler's
> generated code by compiling it.  Doing so caught a couple of
> bugs.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.