[
https://issues.apache.org/jira/browse/AVRO-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16807128#comment-16807128
]
ASF subversion and git services commented on AVRO-2365:
-------------------------------------------------------
Commit 451deec474935db54824069dcf5cfe7ae49a1b11 in avro's branch
refs/heads/master from Ivan Greene
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=451deec ]
AVRO-2365 Enhancements to maven-plugin induce goal
> Enhancements to induce maven plugin goal
> ----------------------------------------
>
> Key: AVRO-2365
> URL: https://issues.apache.org/jira/browse/AVRO-2365
> Project: Apache Avro
> Issue Type: Improvement
> Components: java
> Reporter: Ivan Greene
> Priority: Major
> Fix For: 1.9.0, 1.8.3
>
>
> Before a release of 1.8.3 or 1.9.0 which will introduce the new 'induce'
> maven plugin goal (see AVRO-1749), there are a few issues with it which in my
> mind are critical to enable real-world use of the goal:
> * Allow excluding classes based on a pattern, and/or the ability to specify
> multiple sourceDirectories
> * Option to specify whether to use ReflectData.AllowNull or ReflectData
> * Throw MojoExecutionException with an informative message when appropriate,
> instead of just printing stacktraces. This is very important, we definitely
> need a build to fail when we hit a problem.
> * Use the current project defined encoding rather than hard coded UTF-8.
> * Use try-with-resources to ensure the PrintWriter gets closed in the event
> of exception
> Nice to haves:
> * Specify custom ReflectData implementation (i.e user declared extensions)
> to be used
> * Specify separate output directories for schemata and protocols (these
> could both default to the single output directory if not specified
> individually)
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
