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

bhashit parikh edited comment on BIGTOP-1269 at 5/24/14 9:06 AM:
-----------------------------------------------------------------

# trailing whitespaces in {{build.gradle}}?
# I have added the capability for specifying the integration-test specific 
classpaths. I'll upload the new patch once I have dealt with the 
trailing-whitespace issue. 
# This is a known issue with using {{mavenLocal()}} repo. See [this 
issue|http://forums.gradle.org/gradle/topics/gradle_fails_to_download_dependencies_if_not_present_in_mavenlocal].
 We need to use {{mavenLocal}} since we are building {{mahout-core}} ourselves 
with support for {{hadoop 2.x}}. There are two workarounds here:
## Delete the directory of {{org.apache.avro}}, or any other artifact that 
causes this problem, from the local maven repo. If we go with this, I 
documented this issue in the {{README}} today.
## We specify custom logic in our {{build.gradle}} to checkout the {{mahout}} 
from {{github}}, do a local build against {{hadoop 2.x}} and allow gradle to 
find it. A {{bash}} script or some code in {{groovy}} should be able to handle 
that.


was (Author: bhashit):
# whitespace errors in {{build.gradle}}?
# I have added the capability for specifying the integration-test specific 
classpaths. I'll upload the new patch once I have dealt with the 
trailing-whitespace issue. 
# This is a known issue with using {{mavenLocal()}} repo. See [this 
issue|http://forums.gradle.org/gradle/topics/gradle_fails_to_download_dependencies_if_not_present_in_mavenlocal].
 We need to use {{mavenLocal}} since we are building {{mahout-core}} ourselves 
with support for {{hadoop 2.x}}. There are two workarounds here:
## Delete the directory of {{org.apache.avro}}, or any other artifact that 
causes this problem, from the local maven repo. If we go with this, I 
documented this issue in the {{README}} today.
## We specify custom logic in our {{build.gradle}} to checkout the {{mahout}} 
from {{github}}, do a local build against {{hadoop 2.x}} and allow gradle to 
find it. A {{bash}} script or some code in {{groovy}} should be able to handle 
that.

> BigPetStore: Create build w/ gradle
> -----------------------------------
>
>                 Key: BIGTOP-1269
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-1269
>             Project: Bigtop
>          Issue Type: Improvement
>          Components: Blueprints
>    Affects Versions: backlog
>            Reporter: jay vyas
>         Attachments: BIGTOP-1269.patch
>
>
> Lets port the BigPetStore build to gradle for all the obvious reasons.  This 
> port might cause some minor breakage of other parallel efforts that change 
> the pom file.
> The gradle ported build should contain: 
> - a "test" phase which runs the custom data set generator
> - a "integration test - pig" phase which runs the pig data cleaner + 
> aggrergator. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to