Suraj Acharya commented on AVRO-1916:

If prior to running {{test}} someone has just made changes to the dev-tools 
then they can run {{mvn install}} to install dev-tools and then ./build will 
not reinstall dev-tools.
 I would say we keep it the way it currently is since the work around is easy.
Also, adding {{mvn install}} in python tests will mean that we will need to 
build and install dev-tools for python suite.

> Building python version uses wrong version avro-tools.
> ------------------------------------------------------
>                 Key: AVRO-1916
>                 URL: https://issues.apache.org/jira/browse/AVRO-1916
>             Project: Avro
>          Issue Type: Bug
>            Reporter: Niels Basjes
> During {{./build.sh test}} I see this during the build of {{lang/py}}
> {code}
> [ivy:retrieve]        found org.apache.avro#avro-tools;1.9.0-SNAPSHOT in 
> apache-snapshots
> [ivy:retrieve] downloading 
> https://repository.apache.org/content/groups/snapshots/org/apache/avro/avro-tools/1.9.0-SNAPSHOT/avro-tools-1.9.0-20160122.173016-35.jar
>  ...
> {code}
> So apparently the py build phase uses an external version of avro-tools.
> What if I just updated avro-tools? Then it is quite possible the test will 
> pass while in reality it should have failed.
> I suspect the fix can be as simple as doing a {{mvn install}} on the java 
> avro-tools before building/testing the rest of the languages.

This message was sent by Atlassian JIRA

Reply via email to