Yes.
The ./build.sh test
<https://github.com/apache/avro/blob/master/build.sh#L40> command helps run
all the tests from the top level.
However, I am not sure if we need to run all the tests when a change is
made?
I was thinking of running language specific tests for changes in the
specific directory.
For example for changes in python will trigger ant test
<https://github.com/apache/avro/blob/master/build.sh#L43>.
If this is not a good idea let me know. Ill start another tread on dev@avro
to see what the community thinks about it

Thanks

-Suraj Acharya

On Sat, Sep 10, 2016 at 5:45 PM, Sean Busbey <[email protected]> wrote:

> my understanding of Avro's build system is that there are per-language
> build tools and everything gets unified via shell scripts. is there
> just the top level build.sh file, or do the individual components have
> their own?
>
> On Sat, Sep 10, 2016 at 11:48 AM, suraj acharya <[email protected]>
> wrote:
> > Hi,
> > I have been working on AVRO-1887
> > <https://issues.apache.org/jira/browse/AVRO-1887> to add pre-commit
> test to
> > avro.
> > I have been successful in adding the personality for java file using
> maven.
> > I having some questions about the other plugins.
> > Example :ant
> >
> > The structure of avro is that there is a top level pom.
> > And then there is different langs in subdirectory below it.
> > So there is avro/lang/py
> > <https://github.com/apache/avro/tree/master/lang/py>which has python
> code
> > in it. The build tool for that is ant.
> > My understanding is running add_test ant will run ant test.
> > However, that doesn't actually run any tests. My assumption is that since
> > there is no build.xml present there it is unable to run any ant tests.
> >
> > I tried cd to lang/py and run add_test ant from there. However, it throws
> > an error saying unable to find pom.xml.
> >
> > Can someone give me some pointers on how to continue?
> >
> >
> > Thanks
> > -Suraj Acharya
>

Reply via email to