On Wed, Jan 18, 2012 at 3:29 PM, Eric Yang <eric...@gmail.com> wrote: > I propose to enhance mvn eclipse:eclipse support which creates a > integrated runtime environment for developer to compile and run code > directly within eclipse and let this be the default standard > environment for developer. The shell script can completely remove > support of running development structure and focus on packaged runtime > structure. This will provide a cleaner separation for developer and > packager to focus on their tasks at hand.
I personally develop and unit-test in Eclipse but I find managing Eclipse's "run configurations" a giant pain in the butt. I'd rather have my daemons running in separate JVMs and logging to their normal log4j style logs, use normal conf directories, etc. FWIW, my workflow is to do the full tarball build once a day or so, and then when I want to test a change in a pseudo-distributed environment, I simply run "mvn -DskipTests install" and then cp the hadoop-hdfs jar from my target/ directory into the "deployed" directory. Much faster than the full tar build, and assuming my changes are confined to one subproject, not too painful. -Todd -- Todd Lipcon Software Engineer, Cloudera
