You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "Suraj Acharya (JIRA)" <ji...@apache.org> on 2016/09/17 01:13:20 UTC
[jira] [Resolved] (AVRO-1920) formalize the presence of build.sh.
[ https://issues.apache.org/jira/browse/AVRO-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Suraj Acharya resolved AVRO-1920.
---------------------------------
Resolution: Duplicate
It created two issues.
> formalize the presence of build.sh.
> -----------------------------------
>
> Key: AVRO-1920
> URL: https://issues.apache.org/jira/browse/AVRO-1920
> Project: Avro
> Issue Type: Task
> Components: build
> Reporter: Suraj Acharya
> Priority: Minor
>
> After discussing with yetus community we will need a build.sh for every language.
> Currently it is present for a few and not for all
> {code}
> Busbey-MBA:avro busbey$ find . -name build.sh
> ./build.sh
> ./lang/c/build.sh
> ./lang/c++/build.sh
> ./lang/csharp/build.sh
> ./lang/js/build.sh
> ./lang/php/build.sh
> ./lang/ruby/build.sh
> {code}
> The objective of this task is to create a build.sh for each of the languages.
> It might be good idea to refactor the top level build.sh to use the new build.sh scripts like it does for other languages.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)