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
test-artifacts.
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
test-artifacts.
As of now, if i run "mvn eclipse:eclipse" from test-artifacts, i get a
classpath like this:
<classpathentry excluding="java/" kind="src"
path="datafu/src/main/groovy"/>
<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"
path="hadoop/src/main/resources/cachedir.jar"/>
<classpathentry kind="lib"
path="sqoop/src/main/resources/shell_tests/mysql-connector-java-5.1.23-bin.jar"/>
<classpathentry kind="con"
path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
<classpathentry exported="true" kind="con" path="GROOVY_SUPPORT"/>
<classpathentry exported="true" kind="con"
path="GROOVY_DSL_SUPPORT"/>
<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?
Thanks!
--
Jay Vyas
http://jayunit100.blogspot.com
