Return-Path: X-Original-To: apmail-avro-user-archive@www.apache.org Delivered-To: apmail-avro-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 79BBD7E89 for ; Thu, 8 Dec 2011 00:33:33 +0000 (UTC) Received: (qmail 53298 invoked by uid 500); 8 Dec 2011 00:33:33 -0000 Delivered-To: apmail-avro-user-archive@avro.apache.org Received: (qmail 53257 invoked by uid 500); 8 Dec 2011 00:33:33 -0000 Mailing-List: contact user-help@avro.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@avro.apache.org Delivered-To: mailing list user@avro.apache.org Received: (qmail 53249 invoked by uid 99); 8 Dec 2011 00:33:33 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Dec 2011 00:33:33 +0000 X-ASF-Spam-Status: No, hits=-2.8 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_HI,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of victor@x.com designates 216.33.244.6 as permitted sender) Received: from [216.33.244.6] (HELO rhv-mipot-001.corp.ebay.com) (216.33.244.6) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Dec 2011 00:33:28 +0000 DomainKey-Signature: s=xcorp; d=x.com; c=simple; q=dns; h=X-EBay-Corp:X-IronPort-AV:Received:Received:From:To:Date: Subject:Thread-Topic:Thread-Index:Message-ID:References: In-Reply-To:Accept-Language:Content-Language: X-MS-Has-Attach:X-MS-TNEF-Correlator:acceptlanguage: x-ems-proccessed:x-ems-stamp:Content-Type:MIME-Version: X-CFilter; b=RhCjJwmIPVKltGF6XfOBNiOqgb0bYhVyRDPUIvbN39h/AeiZ8sxrvVes D33bh7xK1vAexPhhhJEnDXaqdpUBv88f1xXh2DtJi6JQIq2N9unkeOsPH MOb6VAK2vgLZC+Y; X-EBay-Corp: Yes X-IronPort-AV: E=Sophos;i="4.71,316,1320652800"; d="scan'208,217";a="40883295" Received: from rhv-vtenf-001.corp.ebay.com (HELO RHV-MEXHT-001.corp.ebay.com) ([10.112.113.52]) by rhv-mipot-001.corp.ebay.com with ESMTP; 07 Dec 2011 16:33:07 -0800 Received: from RHV-MEXMS-002.corp.ebay.com ([10.245.17.115]) by RHV-MEXHT-001.corp.ebay.com ([10.245.24.100]) with mapi; Wed, 7 Dec 2011 16:33:07 -0800 From: "Chau, Victor" To: "user@avro.apache.org" Date: Wed, 7 Dec 2011 16:33:03 -0800 Subject: RE: Importing in avdl from classpath of project Thread-Topic: Importing in avdl from classpath of project Thread-Index: Acy1ENKrxWRsSTqlSgeDj3wHh8GZnAAMAhOA Message-ID: <27C62F5A08B21249A9D4731C1B6B0B6602B1151052@RHV-MEXMS-002.corp.ebay.com> References: <27C62F5A08B21249A9D4731C1B6B0B6602B1150DC8@RHV-MEXMS-002.corp.ebay.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US x-ems-proccessed: 10SqDH0iR7ekR7SRpKqm5A== x-ems-stamp: 1b735Gux0zeLniHCJl2kRw== Content-Type: multipart/alternative; boundary="_000_27C62F5A08B21249A9D4731C1B6B0B6602B1151052RHVMEXMS002co_" MIME-Version: 1.0 X-CFilter: Scanned --_000_27C62F5A08B21249A9D4731C1B6B0B6602B1151052RHVMEXMS002co_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Scott, I created JIRA issue AVRO-971. From: Scott Carey [mailto:scott@richrelevance.com] On Behalf Of Scott Carey Sent: Wednesday, December 07, 2011 10:50 AM To: user@avro.apache.org Subject: Re: Importing in avdl from classpath of project I think that at minimum, it would be useful to have an option to 'also look= in the classpath' in the maven plugin, and have the option to do so in gen= eral with the IDL compiler. I would gladly review the patch in a JIRA. -Scott On 12/7/11 10:13 AM, "Chau, Victor" > wro= te: Hello, I am trying to address a shortcoming of the way that the import feature wor= ks in IDL. Currently, it looks like the only option is to place the file b= eing imported inside the same directory as that of the importing avdl. In our setup, we have avdl's that are spread among several maven projects t= hat are owned by different teams. I would like to be able to just create a= dependency on another jar that contains the avdl I am want to import and h= ave Avro be smart enough to look for it in the classpath of the project con= taining the avdl. The main problem is to make all of this work with the avro-maven-plugin. T= he plugin's runtime classpath is not the same as that of the maven project'= s classpath. Through the magic of Stackoverflow, I figured out how to get = the project's classpath and construct a new classloader and pass it to the = Idl compiler for it to lookup the file if it is not available in the local = directory. Is this a feature that people think would be useful? Essentially, the IDL = syntax would not change but the behavior is: 1. If imported file is available locally (in the current input path),= use it 2. Else look for it on the project's classpath. If so, I have a working patch that needs some cleanup but I can submit it a= s a feature request in JIRA. --_000_27C62F5A08B21249A9D4731C1B6B0B6602B1151052RHVMEXMS002co_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi Scott,

 

I created JIRA issue AVRO-97= 1.

=  

 

From:<= /b> Scot= t Carey [mailto:scott@richrelevance.com] On Behalf Of Scott CareySent: Wednesday, December 07, 2011 10:50 AM
To: user@avro= .apache.org
Subject: Re: Importing in avdl from classpath of proj= ect

 =

= I think that at minimum, it would be useful to have an option to 'also look= in the classpath' in the maven plugin, and have the option to do so in gen= eral with the IDL compiler.   I would gladly review the patch in a JIR= A.

 

-Scott=

 

On 12/7/11 10:13 AM, "= Chau, Victor" <victor@x.com>= wrote:

 

= Hello,

 

I am trying to address a shortcoming of the way that the import feature= works in IDL.  Currently, it looks like the only option is to place t= he file being imported inside the same directory as that of the importing a= vdl.

=  

In our setup, we have avdl’s that are spread among several maven pr= ojects that are owned by different teams.  I would like to be able to = just create a dependency on another jar that contains the avdl I am want to= import and have Avro be smart enough to look for it in the classpath of th= e project containing the avdl.

 

= The main problem is to make all of this work wi= th the avro-maven-plugin.  The plugin’s runtime classpath is not= the same as that of the maven project’s classpath.  Through the= magic of Stackoverflow, I figured out how to get the project’s class= path and construct a new classloader and pass it to the Idl compiler for it= to lookup the file if it is not available in the local directory. 

 =

Is t= his a feature that people think would be useful?  Essentially, the IDL= syntax would not change but the behavior is:

 

= 1.   &nbs= p;   I= f imported file is available locally (in the current input path), use it

<= span style=3D'mso-list:Ignore'>2.