Re: Namespace validation/requirements

[Ryan Skraba]

I'm certain that the Java implementation doesn't validate full names
correctly (https://issues.apache.org/jira/browse/AVRO-2659 has a fun
example).  This should be an easy fix, I'll give it a go.

A PR to clarify the spec on this point would be welcome!

On Thu, May 28, 2020 at 6:47 PM Micah Kornfield  wrote:
>
> I'm happy to make PR clarifying this.  I'm a little bit concerned that if
> validation doesn't exist in Java (and maybe other languages today) if we
> make the spec stricter it could break users.  How has the community handled
> issues like this in the past?
>
> Would someone familiar with the Java implementation be able to comment if
> there is validation around this (I couldn't find it on a quick search)?
>
> Thanks,
> Micah
>
> On Thu, May 28, 2020 at 9:23 AM Doug Cutting  wrote:
>
> > Yes, the intent was to prohibit namespaces starting with a dot.
> >
> >  | ((()*))  was the intended grammar.
> >
> > Doug
> >
> > On Thu, May 28, 2020 at 1:50 AM Ryan Skraba  wrote:
> >
> > > Hello!  Hmmm... reading through the spec (again), there is a small
> > > ambiguous point!  Good catch!
> > >
> > > Specifically, it specifically says that ".a" is not a valid namespace
> > > attribute:
> > >
> > > "A namespace is a dot-separated sequence of such [non-empty] names.
> > > The empty string may also be used as a namespace ..."
> > >
> > > But it could be a valid full name: made from a valid namespace (the
> > > empty string) and a valid name.
> > >
> > > I suspect that the original intention was that it should not be a
> > > valid fullname, with the consequence that all valid fullnames are
> > > valid Java class names.
> > >
> > > If it *were* a valid fullname, however, it would be useful to
> > > distinguish between specifying the default namespace versus inheriting
> > > a namespace from a parent record!  As far as I can tell, this
> > > behaviour isn't implemented anywhere or specified in the spec either.
> > >
> > > What do you think?  The spec could be clarified either way.
> > >
> > > Ryan
> > >
> > >
> > > On Wed, May 27, 2020 at 7:20 PM Micah Kornfield 
> > > wrote:
> > > >
> > > > Hi Avro Dev,
> > > > I think there is a little bit of ambiguity in the requirements for the
> > > > namespace component of a full name in the specification [1].  In
> > > particular
> > > > it isn't clear whether namespaces like:
> > > > ".namespace" should be considered valid (i.e. a "null" namespace
> > > followed a
> > > > valid name).
> > > >
> > > > It appears the the C++ implementation does not think this is valid [2]
> > > but
> > > > I couldn't find a corresponding check in the Java code base (I'm still
> > > > familiarizing myself with both).
> > > >
> > > > Should ".namespace" be considered valid?
> > > >
> > > > Thanks,
> > > > Micah
> > > >
> > > > [1] https://avro.apache.org/docs/current/spec.html
> > > > [2]
> > > https://github.com/apache/avro/blob/master/lang/c%2B%2B/impl/Node.cc#L72
> > >
> >

[GitHub] [avro] RyanSkraba merged pull request #685: AVRO-2514:Making Avro serialization error message more actionable with...

[GitBox]

RyanSkraba merged pull request #685:
URL: https://github.com/apache/avro/pull/685


   



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[jira] [Commented] (AVRO-2514) Making Avro serialization error message more actionable with schema name and field name

[ASF subversion and git services (Jira)]

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

ASF subversion and git services commented on AVRO-2514:
---

Commit e3b06fb914abc05c0fc232e54be94883b784dff6 in avro's branch 
refs/heads/master from Zezeng Wang
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=e3b06fb ]

AVRO-2514:Making Avro serialization error message more actionable with... (#685)

* AVRO-2514:Making Avro serialization error message more actionable with field 
name

* Update GenericDatumWriter.java

Update to runtime exception

* Update ReflectDatumWriter.java

* AVRO-2514:Update GennericDatumWriter method

> Making Avro serialization error message more actionable with schema name and 
> field name
> ---
>
> Key: AVRO-2514
> URL: https://issues.apache.org/jira/browse/AVRO-2514
> Project: Apache Avro
>  Issue Type: Improvement
>  Components: java
>Affects Versions: 1.6.3, 1.9.0, 1.8.2
>Reporter: Jagannathrao Mudda
>Priority: Major
> Fix For: 1.10.0
>
>
> In certain scenarios when there is a serialization error, avro serializer 
> gives following error messages that are not actionable without any schema 
> name and/field name in it.
>  * java.lang.Double cannot be cast to java.lang.Long
>  * Not an enum: null
>  * ClassCastException 
>  * ..
> If there is a filed name of specific schema that is causing these 
> serialization errors, that helps to fix such issues quickly.
>  
> *Proposed Changes:*
> The "writeWithoutConversion" method of "GenericDatumWriter"  class can be 
> updated to handle "ClassCastException" along with "NullPointerException" to 
> throw an exception with schema name and field name.
> The "writeEnum", "writeField", and "error" method can be enhanced to add 
> field names so that error message can have the field that is causing the 
> issue.
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (AVRO-2514) Making Avro serialization error message more actionable with schema name and field name

[ASF subversion and git services (Jira)]

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

ASF subversion and git services commented on AVRO-2514:
---

Commit e3b06fb914abc05c0fc232e54be94883b784dff6 in avro's branch 
refs/heads/master from Zezeng Wang
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=e3b06fb ]

AVRO-2514:Making Avro serialization error message more actionable with... (#685)

* AVRO-2514:Making Avro serialization error message more actionable with field 
name

* Update GenericDatumWriter.java

Update to runtime exception

* Update ReflectDatumWriter.java

* AVRO-2514:Update GennericDatumWriter method

> Making Avro serialization error message more actionable with schema name and 
> field name
> ---
>
> Key: AVRO-2514
> URL: https://issues.apache.org/jira/browse/AVRO-2514
> Project: Apache Avro
>  Issue Type: Improvement
>  Components: java
>Affects Versions: 1.6.3, 1.9.0, 1.8.2
>Reporter: Jagannathrao Mudda
>Priority: Major
> Fix For: 1.10.0
>
>
> In certain scenarios when there is a serialization error, avro serializer 
> gives following error messages that are not actionable without any schema 
> name and/field name in it.
>  * java.lang.Double cannot be cast to java.lang.Long
>  * Not an enum: null
>  * ClassCastException 
>  * ..
> If there is a filed name of specific schema that is causing these 
> serialization errors, that helps to fix such issues quickly.
>  
> *Proposed Changes:*
> The "writeWithoutConversion" method of "GenericDatumWriter"  class can be 
> updated to handle "ClassCastException" along with "NullPointerException" to 
> throw an exception with schema name and field name.
> The "writeEnum", "writeField", and "error" method can be enhanced to add 
> field names so that error message can have the field that is causing the 
> issue.
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (AVRO-2514) Making Avro serialization error message more actionable with schema name and field name

[Ryan Skraba (Jira)]

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

Ryan Skraba resolved AVRO-2514.
---
  Assignee: Zezeng Wang
Resolution: Fixed

> Making Avro serialization error message more actionable with schema name and 
> field name
> ---
>
> Key: AVRO-2514
> URL: https://issues.apache.org/jira/browse/AVRO-2514
> Project: Apache Avro
>  Issue Type: Improvement
>  Components: java
>Affects Versions: 1.6.3, 1.9.0, 1.8.2
>Reporter: Jagannathrao Mudda
>Assignee: Zezeng Wang
>Priority: Major
> Fix For: 1.10.0
>
>
> In certain scenarios when there is a serialization error, avro serializer 
> gives following error messages that are not actionable without any schema 
> name and/field name in it.
>  * java.lang.Double cannot be cast to java.lang.Long
>  * Not an enum: null
>  * ClassCastException 
>  * ..
> If there is a filed name of specific schema that is causing these 
> serialization errors, that helps to fix such issues quickly.
>  
> *Proposed Changes:*
> The "writeWithoutConversion" method of "GenericDatumWriter"  class can be 
> updated to handle "ClassCastException" along with "NullPointerException" to 
> throw an exception with schema name and field name.
> The "writeEnum", "writeField", and "error" method can be enhanced to add 
> field names so that error message can have the field that is causing the 
> issue.
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (AVRO-2514) Making Avro serialization error message more actionable with schema name and field name

[ASF subversion and git services (Jira)]

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

ASF subversion and git services commented on AVRO-2514:
---

Commit e3b06fb914abc05c0fc232e54be94883b784dff6 in avro's branch 
refs/heads/master from Zezeng Wang
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=e3b06fb ]

AVRO-2514:Making Avro serialization error message more actionable with... (#685)

* AVRO-2514:Making Avro serialization error message more actionable with field 
name

* Update GenericDatumWriter.java

Update to runtime exception

* Update ReflectDatumWriter.java

* AVRO-2514:Update GennericDatumWriter method

> Making Avro serialization error message more actionable with schema name and 
> field name
> ---
>
> Key: AVRO-2514
> URL: https://issues.apache.org/jira/browse/AVRO-2514
> Project: Apache Avro
>  Issue Type: Improvement
>  Components: java
>Affects Versions: 1.6.3, 1.9.0, 1.8.2
>Reporter: Jagannathrao Mudda
>Priority: Major
> Fix For: 1.10.0
>
>
> In certain scenarios when there is a serialization error, avro serializer 
> gives following error messages that are not actionable without any schema 
> name and/field name in it.
>  * java.lang.Double cannot be cast to java.lang.Long
>  * Not an enum: null
>  * ClassCastException 
>  * ..
> If there is a filed name of specific schema that is causing these 
> serialization errors, that helps to fix such issues quickly.
>  
> *Proposed Changes:*
> The "writeWithoutConversion" method of "GenericDatumWriter"  class can be 
> updated to handle "ClassCastException" along with "NullPointerException" to 
> throw an exception with schema name and field name.
> The "writeEnum", "writeField", and "error" method can be enhanced to add 
> field names so that error message can have the field that is causing the 
> issue.
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[GitHub] [avro] RyanSkraba opened a new pull request #895: Fix spotless format

[GitBox]

RyanSkraba opened a new pull request #895:
URL: https://github.com/apache/avro/pull/895


   Simply ran `mvn spotless:apply`
   
   Make sure you have checked _all_ steps below.
   
   ### Jira
   
   - [ ] My PR addresses the following [Avro 
Jira](https://issues.apache.org/jira/browse/AVRO/) issues and references them 
in the PR title. For example, "AVRO-1234: My Avro PR"
 - https://issues.apache.org/jira/browse/AVRO-XXX
 - In case you are adding a dependency, check if the license complies with 
the [ASF 3rd Party License 
Policy](https://www.apache.org/legal/resolved.html#category-x).
   
   ### Tests
   
   - [ ] My PR adds the following unit tests __OR__ does not need testing for 
this extremely good reason:
   
   ### Commits
   
   - [ ] My commits all reference Jira issues in their subject lines. In 
addition, my commits follow the guidelines from "[How to write a good git 
commit message](https://chris.beams.io/posts/git-commit/)":
 1. Subject is separated from body by a blank line
 1. Subject is limited to 50 characters (not including Jira issue reference)
 1. Subject does not end with a period
 1. Subject uses the imperative mood ("add", not "adding")
 1. Body wraps at 72 characters
 1. Body explains "what" and "why", not "how"
   
   ### Documentation
   
   - [ ] In case of new functionality, my PR adds documentation that describes 
how to use it.
 - All the public functions and the classes in the PR contain Javadoc that 
explain what it does
   



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Build failed in Jenkins: AvroJava #893

[Apache Jenkins Server]

See 

Changes:

[github] AVRO-2514:Making Avro serialization error message more actionable


--
[...truncated 1.54 KB...]
 > git rev-list --no-walk ccbbb8353fcc168563c567580cb773d5fe442704 # timeout=10
[AvroJava] $ /home/jenkins/tools/maven/apache-maven-3.5.4/bin/mvn clean 
source:jar-no-fork deploy
[INFO] Scanning for projects...
Downloading from central: 
https://repo.maven.apache.org/maven2/io/netty/netty-bom/4.1.50.Final/netty-bom-4.1.50.Final.pom
Progress (1): 1.4/7.9 kBProgress (1): 2.7/7.9 kBProgress (1): 4.1/7.9 
kBProgress (1): 5.5/7.9 kBProgress (1): 6.9/7.9 kBProgress (1): 7.9 kB  
  Downloaded from central: 
https://repo.maven.apache.org/maven2/io/netty/netty-bom/4.1.50.Final/netty-bom-4.1.50.Final.pom
 (7.9 kB at 17 kB/s)
Downloading from central: 
https://repo.maven.apache.org/maven2/org/apache/maven/archetype/archetype-packaging/3.1.2/archetype-packaging-3.1.2.pom
Progress (1): 1.4/1.4 kBProgress (1): 1.4 kBDownloaded 
from central: 
https://repo.maven.apache.org/maven2/org/apache/maven/archetype/archetype-packaging/3.1.2/archetype-packaging-3.1.2.pom
 (1.4 kB at 60 kB/s)
Downloading from central: 
https://repo.maven.apache.org/maven2/org/apache/maven/archetype/archetype-packaging/3.1.2/archetype-packaging-3.1.2.jar
Progress (1): 1.4/7.5 kBProgress (1): 2.7/7.5 kBProgress (1): 4.1/7.5 
kBProgress (1): 5.5/7.5 kBProgress (1): 6.9/7.5 kBProgress (1): 7.5 kB  
  Downloaded from central: 
https://repo.maven.apache.org/maven2/org/apache/maven/archetype/archetype-packaging/3.1.2/archetype-packaging-3.1.2.jar
 (7.5 kB at 313 kB/s)
[INFO] 
[INFO] Reactor Build Order:
[INFO] 
[INFO] Apache Avro Toplevel   [pom]
[INFO] Apache Avro Java   [pom]
[INFO] Apache Avro [bundle]
[INFO] Apache Avro Compiler[bundle]
[INFO] Apache Avro Maven Plugin  [maven-plugin]
[INFO] Apache Avro IPC [bundle]
[INFO] Apache Avro IPC Jetty   [bundle]
[INFO] Apache Avro IPC Netty   [bundle]
[INFO] Trevni Java[pom]
[INFO] Trevni Java Core   [jar]
[INFO] Apache Avro Mapred API  [bundle]
[INFO] Trevni Java Avro   [jar]
[INFO] Trevni Specification   [pom]
[INFO] Apache Avro Tools  [jar]
[INFO] Apache Avro Protobuf Compatibility  [bundle]
[INFO] Apache Avro Thrift Compatibility[bundle]
[INFO] Apache Avro Maven Archetypes   [pom]
[INFO] Apache Avro Maven Service Archetype[maven-archetype]
[INFO] Apache Avro gRPC[bundle]
[INFO] Avro Integration Tests [pom]
[INFO] Apache Avro Codegen Test dependencies  [jar]
[INFO] Apache Avro Codegen Test   [jar]
[INFO] Apache Avro Performance Test Suite [jar]
[INFO] 
[INFO] ---< org.apache.avro:avro-toplevel >
[INFO] Building Apache Avro Toplevel 1.10.0-SNAPSHOT [1/23]
[INFO] [ pom ]-
[INFO] 
[INFO] --- maven-clean-plugin:3.1.0:clean (default-clean) @ avro-toplevel ---
[INFO] 
[INFO] --- maven-source-plugin:3.2.1:jar-no-fork (default-cli) @ avro-toplevel 
---
[INFO] 
[INFO] --- maven-enforcer-plugin:3.0.0-M3:enforce (enforce-maven-version) @ 
avro-toplevel ---
[INFO] 
[INFO] --- maven-enforcer-plugin:3.0.0-M3:enforce (enforce) @ avro-toplevel ---
[INFO] Adding ignore: module-info
[INFO] 
[INFO] --- maven-enforcer-plugin:3.0.0-M3:enforce (enforce-banned-dependencies) 
@ avro-toplevel ---
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.7.0:process 
(process-resource-bundles) @ avro-toplevel ---
[INFO] Preparing remote bundle org.apache:apache-jar-resource-bundle:1.4
[INFO] Copying 3 resources from 1 bundle.
[INFO] 
[INFO] --- apache-rat-plugin:0.13:check (default) @ avro-toplevel ---
[INFO] Added 1 additional default licenses.
[INFO] Enabled default license matchers.
[INFO] Will parse SCM ignores for exclusions...
[INFO] Parsing exclusions from 

[INFO] Finished 

[jira] [Commented] (AVRO-2514) Making Avro serialization error message more actionable with schema name and field name

[Hudson (Jira)]

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

Hudson commented on AVRO-2514:
--

FAILURE: Integrated in Jenkins build AvroJava #893 (See 
[https://builds.apache.org/job/AvroJava/893/])
AVRO-2514:Making Avro serialization error message more actionable (github: 
[https://github.com/apache/avro/commit/e3b06fb914abc05c0fc232e54be94883b784dff6])
* (edit) 
lang/java/avro/src/main/java/org/apache/avro/generic/GenericDatumWriter.java
* (edit) 
lang/java/avro/src/main/java/org/apache/avro/reflect/ReflectDatumWriter.java


> Making Avro serialization error message more actionable with schema name and 
> field name
> ---
>
> Key: AVRO-2514
> URL: https://issues.apache.org/jira/browse/AVRO-2514
> Project: Apache Avro
>  Issue Type: Improvement
>  Components: java
>Affects Versions: 1.6.3, 1.9.0, 1.8.2
>Reporter: Jagannathrao Mudda
>Assignee: Zezeng Wang
>Priority: Major
> Fix For: 1.10.0
>
>
> In certain scenarios when there is a serialization error, avro serializer 
> gives following error messages that are not actionable without any schema 
> name and/field name in it.
>  * java.lang.Double cannot be cast to java.lang.Long
>  * Not an enum: null
>  * ClassCastException 
>  * ..
> If there is a filed name of specific schema that is causing these 
> serialization errors, that helps to fix such issues quickly.
>  
> *Proposed Changes:*
> The "writeWithoutConversion" method of "GenericDatumWriter"  class can be 
> updated to handle "ClassCastException" along with "NullPointerException" to 
> throw an exception with schema name and field name.
> The "writeEnum", "writeField", and "error" method can be enhanced to add 
> field names so that error message can have the field that is causing the 
> issue.
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[GitHub] [avro] RyanSkraba opened a new pull request #896: Revert "AVRO-2649 Made argument order non-enforceable avro-tools cli"

[GitBox]

RyanSkraba opened a new pull request #896:
URL: https://github.com/apache/avro/pull/896


   Reverts apache/avro#741



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[jira] [Commented] (AVRO-2649) [Java] Argument order enforced in avro-tools cli.

[ASF subversion and git services (Jira)]

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

ASF subversion and git services commented on AVRO-2649:
---

Commit 6233f475a7a26ca5e08e6d300d683accd3993bc6 in avro's branch 
refs/heads/revert-741-AVRO-2649 from RyanSkraba
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=6233f47 ]

Revert "AVRO-2649 Made argument order non-enforceable avro-tools cli (#741)"

This reverts commit 7fd098a56064ece218c66ba1d2ad78bd358f6009.


> [Java] Argument order enforced in avro-tools cli.
> -
>
> Key: AVRO-2649
> URL: https://issues.apache.org/jira/browse/AVRO-2649
> Project: Apache Avro
>  Issue Type: Improvement
>Affects Versions: 1.9.1
>Reporter: Ryan Skraba
>Priority: Minor
> Fix For: 1.10.0
>
>
> The following command line works:
> {code}
> $ avrotool compile -string -bigDecimal schema 
> ./lang/java/tools/src/test/compiler/input/fieldtest.avsc /tmp/output
> Input files to compile:
>   ./lang/java/tools/src/test/compiler/input/fieldtest.avsc
> {code}
> Switching the first two flags causes an error:
> {code}
> $ avrotool compile -bigDecimal -string schema 
> ./lang/java/tools/src/test/compiler/input/fieldtest.avsc /tmp/output
> Expected "schema" or "protocol".
> {code}
> There's really no need to enforce a command line option order, especially for 
> flags, and it's not user friendly.  Most CLI tools don't.  There's several 
> good command line parsers to help.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (AVRO-2649) [Java] Argument order enforced in avro-tools cli.

[ASF subversion and git services (Jira)]

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

ASF subversion and git services commented on AVRO-2649:
---

Commit 1c5e32d2b98e193ea048f8ece8ee3984c6165bfe in avro's branch 
refs/heads/master from Daniel Kulp
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=1c5e32d ]

[AVRO-2649] Better fix for allowing args in various orders


> [Java] Argument order enforced in avro-tools cli.
> -
>
> Key: AVRO-2649
> URL: https://issues.apache.org/jira/browse/AVRO-2649
> Project: Apache Avro
>  Issue Type: Improvement
>Affects Versions: 1.9.1
>Reporter: Ryan Skraba
>Priority: Minor
> Fix For: 1.10.0
>
>
> The following command line works:
> {code}
> $ avrotool compile -string -bigDecimal schema 
> ./lang/java/tools/src/test/compiler/input/fieldtest.avsc /tmp/output
> Input files to compile:
>   ./lang/java/tools/src/test/compiler/input/fieldtest.avsc
> {code}
> Switching the first two flags causes an error:
> {code}
> $ avrotool compile -bigDecimal -string schema 
> ./lang/java/tools/src/test/compiler/input/fieldtest.avsc /tmp/output
> Expected "schema" or "protocol".
> {code}
> There's really no need to enforce a command line option order, especially for 
> flags, and it's not user friendly.  Most CLI tools don't.  There's several 
> good command line parsers to help.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[GitHub] [avro] RyanSkraba closed pull request #896: Revert "AVRO-2649 Made argument order non-enforceable avro-tools cli"

[GitBox]

RyanSkraba closed pull request #896:
URL: https://github.com/apache/avro/pull/896


   



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [avro] iemejia merged pull request #895: Fix spotless format

[GitBox]

iemejia merged pull request #895:
URL: https://github.com/apache/avro/pull/895


   



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Build failed in Jenkins: AvroJava #894

[Apache Jenkins Server]

See 

Changes:

[dkulp] [AVRO-2649] Better fix for allowing args in various orders


--
Started by an SCM change
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on H38 (ubuntu) in workspace 

No credentials specified
 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url https://github.com/apache/avro # timeout=10
Fetching upstream changes from https://github.com/apache/avro
 > git --version # timeout=10
 > git fetch --tags --progress -- https://github.com/apache/avro 
 > +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 1c5e32d2b98e193ea048f8ece8ee3984c6165bfe 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 1c5e32d2b98e193ea048f8ece8ee3984c6165bfe
Commit message: "[AVRO-2649] Better fix for allowing args in various orders"
 > git rev-list --no-walk e3b06fb914abc05c0fc232e54be94883b784dff6 # timeout=10
[AvroJava] $ /home/jenkins/tools/maven/apache-maven-3.5.4/bin/mvn clean 
source:jar-no-fork deploy
[INFO] Scanning for projects...
[INFO] 
[INFO] Reactor Build Order:
[INFO] 
[INFO] Apache Avro Toplevel   [pom]
[INFO] Apache Avro Java   [pom]
[INFO] Apache Avro [bundle]
[INFO] Apache Avro Compiler[bundle]
[INFO] Apache Avro Maven Plugin  [maven-plugin]
[INFO] Apache Avro IPC [bundle]
[INFO] Apache Avro IPC Jetty   [bundle]
[INFO] Apache Avro IPC Netty   [bundle]
[INFO] Trevni Java[pom]
[INFO] Trevni Java Core   [jar]
[INFO] Apache Avro Mapred API  [bundle]
[INFO] Trevni Java Avro   [jar]
[INFO] Trevni Specification   [pom]
[INFO] Apache Avro Tools  [jar]
[INFO] Apache Avro Protobuf Compatibility  [bundle]
[INFO] Apache Avro Thrift Compatibility[bundle]
[INFO] Apache Avro Maven Archetypes   [pom]
[INFO] Apache Avro Maven Service Archetype[maven-archetype]
[INFO] Apache Avro gRPC[bundle]
[INFO] Avro Integration Tests [pom]
[INFO] Apache Avro Codegen Test dependencies  [jar]
[INFO] Apache Avro Codegen Test   [jar]
[INFO] Apache Avro Performance Test Suite [jar]
[INFO] 
[INFO] ---< org.apache.avro:avro-toplevel >
[INFO] Building Apache Avro Toplevel 1.10.0-SNAPSHOT [1/23]
[INFO] [ pom ]-
[INFO] 
[INFO] --- maven-clean-plugin:3.1.0:clean (default-clean) @ avro-toplevel ---
[INFO] Deleting 
[INFO] 
[INFO] --- maven-source-plugin:3.2.1:jar-no-fork (default-cli) @ avro-toplevel 
---
[INFO] 
[INFO] --- maven-enforcer-plugin:3.0.0-M3:enforce (enforce-maven-version) @ 
avro-toplevel ---
[INFO] 
[INFO] --- maven-enforcer-plugin:3.0.0-M3:enforce (enforce) @ avro-toplevel ---
[INFO] Adding ignore: module-info
[INFO] 
[INFO] --- maven-enforcer-plugin:3.0.0-M3:enforce (enforce-banned-dependencies) 
@ avro-toplevel ---
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.7.0:process 
(process-resource-bundles) @ avro-toplevel ---
[INFO] Preparing remote bundle org.apache:apache-jar-resource-bundle:1.4
[INFO] Copying 3 resources from 1 bundle.
[INFO] 
[INFO] --- apache-rat-plugin:0.13:check (default) @ avro-toplevel ---
[INFO] Added 1 additional default licenses.
[INFO] Enabled default license matchers.
[INFO] Will parse SCM ignores for exclusions...
[INFO] Parsing exclusions from 

[INFO] Finished adding exclusions from SCM ignore files.
[INFO] 86 implicit excludes (use -debug for more details).
[INFO] 110 explicit excludes (use -debug for more details).
[INFO] 1398 resources included (use -debug for more details)
[INFO] Rat check: Summary over all files. 

[jira] [Commented] (AVRO-2649) [Java] Argument order enforced in avro-tools cli.

[Hudson (Jira)]

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

Hudson commented on AVRO-2649:
--

FAILURE: Integrated in Jenkins build AvroJava #894 (See 
[https://builds.apache.org/job/AvroJava/894/])
[AVRO-2649] Better fix for allowing args in various orders (dkulp: 
[https://github.com/apache/avro/commit/1c5e32d2b98e193ea048f8ece8ee3984c6165bfe])
* (edit) 
lang/java/tools/src/main/java/org/apache/avro/tool/SpecificCompilerTool.java


> [Java] Argument order enforced in avro-tools cli.
> -
>
> Key: AVRO-2649
> URL: https://issues.apache.org/jira/browse/AVRO-2649
> Project: Apache Avro
>  Issue Type: Improvement
>Affects Versions: 1.9.1
>Reporter: Ryan Skraba
>Priority: Minor
> Fix For: 1.10.0
>
>
> The following command line works:
> {code}
> $ avrotool compile -string -bigDecimal schema 
> ./lang/java/tools/src/test/compiler/input/fieldtest.avsc /tmp/output
> Input files to compile:
>   ./lang/java/tools/src/test/compiler/input/fieldtest.avsc
> {code}
> Switching the first two flags causes an error:
> {code}
> $ avrotool compile -bigDecimal -string schema 
> ./lang/java/tools/src/test/compiler/input/fieldtest.avsc /tmp/output
> Expected "schema" or "protocol".
> {code}
> There's really no need to enforce a command line option order, especially for 
> flags, and it's not user friendly.  Most CLI tools don't.  There's several 
> good command line parsers to help.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (AVRO-2668) Build failure without a C++ compiler

[Jira]

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

Ismaël Mejía resolved AVRO-2668.

Resolution: Fixed

> Build failure without a C++ compiler
> 
>
> Key: AVRO-2668
> URL: https://issues.apache.org/jira/browse/AVRO-2668
> Project: Apache Avro
>  Issue Type: Bug
>  Components: c
>Reporter: Fabrice Fontaine
>Priority: Minor
> Fix For: 1.10.0
>
>
> Build of AvroC fails without a C++ compiler:
> CMake Error at CMakeLists.txt:20 (project):
>  The CMAKE_CXX_COMPILER:
> /home/naourr/work/instance-2/output-1/host/bin/microblazeel-buildroot-linux-uclibc-g++
> is not a full path to an existing compiler tool.
> Tell CMake where to find the compiler by setting either the environment
>  variable "CXX" or the CMake cache entry CMAKE_CXX_COMPILER to the full path
>  to the compiler, or to the compiler name if it is in the PATH.
> More information on build failure can be found here:
>  - 
> http://autobuild.buildroot.org/results/135e246aa70f28c6b9aea5fd6b0eb9c7b45ebfe7



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (AVRO-2667) Update bundler to a more recent version

[Jira]

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

Ismaël Mejía updated AVRO-2667:
---
Fix Version/s: (was: 1.10.0)

> Update bundler to a more recent version
> ---
>
> Key: AVRO-2667
> URL: https://issues.apache.org/jira/browse/AVRO-2667
> Project: Apache Avro
>  Issue Type: Bug
>  Components: ruby
>Affects Versions: 1.9.1
>Reporter: Fokko Driesprong
>Priority: Major
>
> The version of bundler that the build is picking up (v1.13.6 - Oct 2016) is 
> also pretty old. Newer versions of bundler correctly identify that the new 
> rdoc version is incompatible with ruby < 2.4.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (AVRO-2665) Move to Ruby 2.5

[Jira]

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

Ismaël Mejía updated AVRO-2665:
---
Summary: Move to Ruby 2.5  (was: Move to Ruby 2.4)

> Move to Ruby 2.5
> 
>
> Key: AVRO-2665
> URL: https://issues.apache.org/jira/browse/AVRO-2665
> Project: Apache Avro
>  Issue Type: Bug
>  Components: ruby
>Affects Versions: 1.9.1
>Reporter: Fokko Driesprong
>Priority: Major
> Fix For: 1.10.0
>
>
> Drop Ruby 2.3 support in favor of Ruby 2.4. Support for ruby 2.3 ended in 
> March 2019, and support for ruby 2.4 will end March 2020.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (AVRO-2665) Move to Ruby 2.5

[Jira]

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

Ismaël Mejía updated AVRO-2665:
---
Fix Version/s: (was: 1.10.0)

> Move to Ruby 2.5
> 
>
> Key: AVRO-2665
> URL: https://issues.apache.org/jira/browse/AVRO-2665
> Project: Apache Avro
>  Issue Type: Bug
>  Components: ruby
>Affects Versions: 1.9.1
>Reporter: Fokko Driesprong
>Priority: Major
>
> Drop Ruby 2.3 support in favor of Ruby 2.4. Support for ruby 2.3 ended in 
> March 2019, and support for ruby 2.4 will end March 2020.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[GitHub] [avro] RyanSkraba opened a new pull request #897: AVRO-2822: Add warning to an experimental method.

[GitBox]

RyanSkraba opened a new pull request #897:
URL: https://github.com/apache/avro/pull/897


   Adds a warning to the new toString(...) method.  This is currently the only 
way to accomplish what the user is looking to do, but we'd like to provide a 
better solution in the short term (but after the 1.10.0 release).
   
   ### Jira
   
   - [ ] My PR addresses the following [Avro 
Jira](https://issues.apache.org/jira/browse/AVRO/) issues and references them 
in the PR title. For example, "AVRO-1234: My Avro PR"
 - https://issues.apache.org/jira/browse/AVRO-2822
 - In case you are adding a dependency, check if the license complies with 
the [ASF 3rd Party License 
Policy](https://www.apache.org/legal/resolved.html#category-x).
   
   ### Tests
   
   - [ ] My PR adds the following unit tests __OR__ does not need testing for 
this extremely good reason:
   
   ### Commits
   
   - [ ] My commits all reference Jira issues in their subject lines. In 
addition, my commits follow the guidelines from "[How to write a good git 
commit message](https://chris.beams.io/posts/git-commit/)":
 1. Subject is separated from body by a blank line
 1. Subject is limited to 50 characters (not including Jira issue reference)
 1. Subject does not end with a period
 1. Subject uses the imperative mood ("add", not "adding")
 1. Body wraps at 72 characters
 1. Body explains "what" and "why", not "how"
   
   ### Documentation
   
   - [ ] In case of new functionality, my PR adds documentation that describes 
how to use it.
 - All the public functions and the classes in the PR contain Javadoc that 
explain what it does
   



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Jenkins build is back to normal : AvroJava #895

[Apache Jenkins Server]

See 

[jira] [Updated] (AVRO-2733) [Ruby] mistakenly requiring rubygems

[Jira]

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

Ismaël Mejía updated AVRO-2733:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> [Ruby] mistakenly requiring rubygems
> 
>
> Key: AVRO-2733
> URL: https://issues.apache.org/jira/browse/AVRO-2733
> Project: Apache Avro
>  Issue Type: Task
>Reporter: Ryan Skraba
>Assignee: Ryan Skraba
>Priority: Major
> Fix For: 1.10.0
>
>
> It looks like we are seeing two issues with running interop tests since the 
> openjdk bump that updates ruby from
> *{{ruby 2.3.3p222 (2016-11-21) [x86_64-linux-gnu]}}*
> to
> *{{ruby 2.5.5p157 (2019-03-15 revision 67260) [x86_64-linux-gnu]}}*
>  # The command line for interop tests includes {{-rubygems}} when it probably 
> means {{-rrubygems}}
>  # Rubygems should be automatically required since Ruby 1.9 (released 2007)
> We should fix this option in the 
> [test_rpc_interop.sh|https://github.com/apache/avro/blob/master/share/test/interop/bin/test_rpc_interop.sh]
>  file.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[GitHub] [avro] iemejia merged pull request #894: AVRO-2733: No longer explicitly require rubygems

[GitBox]

iemejia merged pull request #894:
URL: https://github.com/apache/avro/pull/894


   



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[jira] [Commented] (AVRO-2733) [Ruby] mistakenly requiring rubygems

[ASF subversion and git services (Jira)]

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

ASF subversion and git services commented on AVRO-2733:
---

Commit 34c5e7b3b542c0e0b33747086c3cba7bc73b4904 in avro's branch 
refs/heads/master from Ryan Skraba
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=34c5e7b ]

AVRO-2733: No longer explicitly require rubygems


> [Ruby] mistakenly requiring rubygems
> 
>
> Key: AVRO-2733
> URL: https://issues.apache.org/jira/browse/AVRO-2733
> Project: Apache Avro
>  Issue Type: Task
>Reporter: Ryan Skraba
>Assignee: Ryan Skraba
>Priority: Major
> Fix For: 1.10.0
>
>
> It looks like we are seeing two issues with running interop tests since the 
> openjdk bump that updates ruby from
> *{{ruby 2.3.3p222 (2016-11-21) [x86_64-linux-gnu]}}*
> to
> *{{ruby 2.5.5p157 (2019-03-15 revision 67260) [x86_64-linux-gnu]}}*
>  # The command line for interop tests includes {{-rubygems}} when it probably 
> means {{-rrubygems}}
>  # Rubygems should be automatically required since Ruby 1.9 (released 2007)
> We should fix this option in the 
> [test_rpc_interop.sh|https://github.com/apache/avro/blob/master/share/test/interop/bin/test_rpc_interop.sh]
>  file.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[GitHub] [avro] iemejia opened a new pull request #898: AVRO-2596 Bump ant from 1.10.5 to 1.10.7

[GitBox]

iemejia opened a new pull request #898:
URL: https://github.com/apache/avro/pull/898


   



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[jira] [Assigned] (AVRO-2665) Move to Ruby 2.5

[Jira]

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

Ismaël Mejía reassigned AVRO-2665:
--

Assignee: Ismaël Mejía

> Move to Ruby 2.5
> 
>
> Key: AVRO-2665
> URL: https://issues.apache.org/jira/browse/AVRO-2665
> Project: Apache Avro
>  Issue Type: Bug
>  Components: ruby
>Affects Versions: 1.9.1
>Reporter: Fokko Driesprong
>Assignee: Ismaël Mejía
>Priority: Major
>
> Drop Ruby 2.3 support in favor of Ruby 2.4. Support for ruby 2.3 ended in 
> March 2019, and support for ruby 2.4 will end March 2020.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (AVRO-2596) Upgrade ant to version 1.10.8

[Jira]

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

Ismaël Mejía updated AVRO-2596:
---
Summary: Upgrade ant to version 1.10.8  (was: Bump ant from 1.10.5 to 
1.10.7)

> Upgrade ant to version 1.10.8
> -
>
> Key: AVRO-2596
> URL: https://issues.apache.org/jira/browse/AVRO-2596
> Project: Apache Avro
>  Issue Type: Improvement
>Affects Versions: 1.9.1
>Reporter: Fokko Driesprong
>Assignee: Fokko Driesprong
>Priority: Major
> Fix For: 1.10.0
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (AVRO-2435) Cleanup doc/NOTICE

[Jira]

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

Ismaël Mejía reassigned AVRO-2435:
--

Assignee: Ismaël Mejía

> Cleanup doc/NOTICE
> --
>
> Key: AVRO-2435
> URL: https://issues.apache.org/jira/browse/AVRO-2435
> Project: Apache Avro
>  Issue Type: Improvement
>Affects Versions: 1.9.0
>Reporter: Fokko Driesprong
>Assignee: Ismaël Mejía
>Priority: Major
> Fix For: 1.10.0
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (AVRO-2393) C#: Add examples for new users

[Jira]

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

Ismaël Mejía updated AVRO-2393:
---
Fix Version/s: (was: 1.10.0)

> C#: Add examples for new users
> --
>
> Key: AVRO-2393
> URL: https://issues.apache.org/jira/browse/AVRO-2393
> Project: Apache Avro
>  Issue Type: Improvement
>  Components: csharp
>Reporter: Brian Lachniet
>Assignee: Brian Lachniet
>Priority: Minor
>  Labels: documentation
>
> Add examples of usage for the C# API. The goal of this documentation and/or 
> code examples is to make it easier for those new to the C# API to hit the 
> ground running.
> Ideas for example locations:
>  * In the README.md
>  ** (y) Highly and immediately visible
>  ** (n) Not automatically tested
>  ** (n) Not automatically built
>  * In specially designated "example" projects (for example, like 
> [confluent-kafka-dotnet|https://github.com/confluentinc/confluent-kafka-dotnet/tree/master/examples]
>  ** (n) Not immediately visible, harder to find. Would need to mention  in 
> README.md
>  ** (n) Not automatically tested
>  ** (y) Automatically built
>  * In unit tests designed especially for readability
>  ** (n) Not immediately visible, harder to find. Would need to mention in 
> README.md
>  ** (y) Automatically tested
>  ** (y) Automatically built



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (AVRO-2733) [Ruby] mistakenly requiring rubygems

[Hudson (Jira)]

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

Hudson commented on AVRO-2733:
--

SUCCESS: Integrated in Jenkins build AvroJava #896 (See 
[https://builds.apache.org/job/AvroJava/896/])
AVRO-2733: No longer explicitly require rubygems (iemejia: 
[https://github.com/apache/avro/commit/34c5e7b3b542c0e0b33747086c3cba7bc73b4904])
* (edit) share/test/interop/bin/test_rpc_interop.sh


> [Ruby] mistakenly requiring rubygems
> 
>
> Key: AVRO-2733
> URL: https://issues.apache.org/jira/browse/AVRO-2733
> Project: Apache Avro
>  Issue Type: Task
>Reporter: Ryan Skraba
>Assignee: Ryan Skraba
>Priority: Major
> Fix For: 1.10.0
>
>
> It looks like we are seeing two issues with running interop tests since the 
> openjdk bump that updates ruby from
> *{{ruby 2.3.3p222 (2016-11-21) [x86_64-linux-gnu]}}*
> to
> *{{ruby 2.5.5p157 (2019-03-15 revision 67260) [x86_64-linux-gnu]}}*
>  # The command line for interop tests includes {{-rubygems}} when it probably 
> means {{-rrubygems}}
>  # Rubygems should be automatically required since Ruby 1.9 (released 2007)
> We should fix this option in the 
> [test_rpc_interop.sh|https://github.com/apache/avro/blob/master/share/test/interop/bin/test_rpc_interop.sh]
>  file.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[GitHub] [avro] dkulp merged pull request #898: AVRO-2596: Upgrade ant to version 1.10.8

[GitBox]

dkulp merged pull request #898:
URL: https://github.com/apache/avro/pull/898


   



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[jira] [Commented] (AVRO-2596) Upgrade ant to version 1.10.8

[ASF subversion and git services (Jira)]

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

ASF subversion and git services commented on AVRO-2596:
---

Commit 09f8afe0faa0a846b2537b0b5aff9ef05d0ce072 in avro's branch 
refs/heads/master from Ismaël Mejía
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=09f8afe ]

AVRO-2596: Upgrade ant to version 1.10.8


> Upgrade ant to version 1.10.8
> -
>
> Key: AVRO-2596
> URL: https://issues.apache.org/jira/browse/AVRO-2596
> Project: Apache Avro
>  Issue Type: Improvement
>Affects Versions: 1.9.1
>Reporter: Fokko Driesprong
>Assignee: Fokko Driesprong
>Priority: Major
> Fix For: 1.10.0
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (AVRO-2596) Upgrade ant to version 1.10.8

[Daniel Kulp (Jira)]

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

Daniel Kulp resolved AVRO-2596.
---
  Assignee: Ismaël Mejía  (was: Fokko Driesprong)
Resolution: Fixed

> Upgrade ant to version 1.10.8
> -
>
> Key: AVRO-2596
> URL: https://issues.apache.org/jira/browse/AVRO-2596
> Project: Apache Avro
>  Issue Type: Improvement
>Affects Versions: 1.9.1
>Reporter: Fokko Driesprong
>Assignee: Ismaël Mejía
>Priority: Major
> Fix For: 1.10.0
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (AVRO-2596) Upgrade ant to version 1.10.8

[Hudson (Jira)]

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

Hudson commented on AVRO-2596:
--

SUCCESS: Integrated in Jenkins build AvroJava #898 (See 
[https://builds.apache.org/job/AvroJava/898/])
AVRO-2596: Upgrade ant to version 1.10.8 (dan: 
[https://github.com/apache/avro/commit/09f8afe0faa0a846b2537b0b5aff9ef05d0ce072])
* (edit) lang/java/pom.xml


> Upgrade ant to version 1.10.8
> -
>
> Key: AVRO-2596
> URL: https://issues.apache.org/jira/browse/AVRO-2596
> Project: Apache Avro
>  Issue Type: Improvement
>Affects Versions: 1.9.1
>Reporter: Fokko Driesprong
>Assignee: Ismaël Mejía
>Priority: Major
> Fix For: 1.10.0
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)