[jira] Commented: (AVRO-676) Avro IDL can't process includes from disparate src trees

["Doug Cutting (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AVRO-676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12918079#action_12918079 ] 

Doug Cutting commented on AVRO-676:
-----------------------------------

IDL import statements are relative to the IDL file they're in:

http://avro.apache.org/docs/current/idl.html#imports

This is by analogy with CPP:

http://gcc.gnu.org/onlinedocs/cpp/Include-Syntax.html

So, in your example, I believe you should use something like:

{code}
import idl "../../../foo/main/avro/a.genavro"
{code}

The patch you've provided makes all imports relative to the connected directory of the compiler's JVM, which is not desired.

> Avro IDL can't process includes from disparate src trees
> --------------------------------------------------------
>
>                 Key: AVRO-676
>                 URL: https://issues.apache.org/jira/browse/AVRO-676
>             Project: Avro
>          Issue Type: Bug
>          Components: java
>    Affects Versions: 1.4.0
>            Reporter: Arun C Murthy
>         Attachments: AVRO-676.patch
>
>
> AVRO-495 introduced support from includes in IDL. However it turns out that a bug in the implementation, which assumes that the path for the included path is in the same src tree causes it to not support includes from different source trees.
> E.g.
> src/foo/main/avro/a.genavro
> // something here
> ...
> src/foobar/main/avro/b.genavro
> protocol foobar {
>   import idl "src/foo/main/avro/a.genavro";
>   ...
> }.

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