bigtop-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jay Vyas <>
Subject Setting up Dev environment for Test-Artifacts.
Date Tue, 08 Oct 2013 16:52:05 GMT
Most of my test-artifacts patches take quite a while:  I edit the code in
vim and then test it using a full bigtop build.

Any way to shorten my development lifecycle so that i can use eclispe to
run my groovy code in bigtop-tests/test-artifacts in place?

I guess this involves setting up a eclipse project specific for

Does anyone use eclipse to edit bigtop code in place?  Im not sure how to
get the maven pom file to build a proper eclipse project for

As of now, if i run "mvn eclipse:eclipse" from test-artifacts, i get a
classpath like this:

        <classpathentry excluding="java/" kind="src"
        <classpathentry kind="src" path="datafu/src/main/groovy/java"/>
        <classpathentry kind="src" path="flume/src/main/groovy"/>
        <classpathentry kind="src" path="hadoop/src/main/groovy"/>
        <classpathentry kind="src" path="hbase/src/main/groovy"/>
        <classpathentry kind="src" path="hcatalog/src/main/groovy"/>
        <classpathentry kind="src" path="hive/src/main/groovy"/>
        <classpathentry kind="src" path="mahout/src/main/groovy"/>
        <classpathentry kind="src" path="oozie/src/main/groovy"/>
        <classpathentry kind="src" path="package/src/main/groovy"/>
        <classpathentry kind="src" path="solr/src/main/groovy"/>
        <classpathentry kind="src" path="sqoop/src/main/groovy"/>
        <classpathentry kind="lib"
        <classpathentry kind="lib"
        <classpathentry kind="con"
        <classpathentry exported="true" kind="con" path="GROOVY_SUPPORT"/>
        <classpathentry exported="true" kind="con"
        <classpathentry kind="output" path="bin"/>

Any way to add all the junit/and other maven dependencies in bigtop jars
into the classpath at the eclipse level?


Jay Vyas

View raw message