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

Hudson commented on AVRO-1384:
------------------------------

SUCCESS: Integrated in AvroJava #400 (See 
[https://builds.apache.org/job/AvroJava/400/])
AVRO-1384. Java: Permit Maven to find imports within project.  Contributed by 
Alexandre Normand. (cutting: rev 1539184)
* /avro/trunk/CHANGES.txt
* 
/avro/trunk/lang/java/maven-plugin/src/main/java/org/apache/avro/mojo/AbstractAvroMojo.java
* 
/avro/trunk/lang/java/maven-plugin/src/main/java/org/apache/avro/mojo/IDLProtocolMojo.java
* /avro/trunk/lang/java/maven-plugin/src/test/avro/AvdlClasspathImport.avdl
* 
/avro/trunk/lang/java/maven-plugin/src/test/java/org/apache/avro/mojo/TestIDLProtocolMojo.java
* /avro/trunk/lang/java/maven-plugin/src/test/resources/unit/idl/pom.xml


> avro-maven-plugin: Can't import idl files as classpath resources from the 
> same set of sources 
> ----------------------------------------------------------------------------------------------
>
>                 Key: AVRO-1384
>                 URL: https://issues.apache.org/jira/browse/AVRO-1384
>             Project: Avro
>          Issue Type: Improvement
>          Components: java
>    Affects Versions: 1.7.5
>            Reporter: Alexandre Normand
>            Assignee: Alexandre Normand
>             Fix For: 1.7.6
>
>         Attachments: AVRO-1384-rev1.patch, AVRO-1384.patch, AVRO-1384.patch
>
>
> We have a use case for importing idl files as classpath resources (it makes 
> possible to re-use idls in downstream artifacts if all imports use classpath 
> resources as opposed to a file-based reference). To enable this, the imports 
> in the same artifacts should be able to use classpath resources for other 
> avro files in the same source structure. 
> The proposed approach is to just add the source directory of avro files to 
> the classpath. The avro resources would then follow the directory structure. 
> This means that if someone configures the avro-maven-plugin with a source 
> directory like this:
> {code}
> <sourceDirectory>${project.basedir}/src/main/resources</sourceDirectory>
> {code}  
> And the idl files live under {{project.basedir/src/main/resources/avro}}, the 
> imports could be referencing other avro files like this: 
> {code}
> import idl "avro/otherSchema.avdl";
> {code}
> Things open for discussion: 
> * Any documentation required to make this clear to end-users?
> * Should I add the resources directories to the classpath as well? 



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Reply via email to