Looking at your patch the only thing what is happening is that the class files are going into the "bin" folder and not into the target/classes folder.
At the end of the day this means that within eclipse I can switch between different sdks for testing, which would make my job (porting to ibm sdk) a lot easier. In this case, +1 Andrea Aime writes: > Hi all, > for a few days I've tried to use the eclipse plugin so that the output > directory of Eclipse is separate from the maven one. > The rationale for why this may be beneficial is explained here (bottom of > the document for a pro/cons list): > http://docs.codehaus.org/display/M2ECLIPSE/Separate+Eclipse+and+Maven+outp > ut+folders > > From where I stand the biggest pro is that I don't have to kick the > refresh in Eclipse as often and I can safely build in maven using > "mvn install" without the clean part, which is otherwise necessary > since Eclipse builds .class files also with errors. > > The latter alone shaves a few minutes out of the build, for example, > on 2.5.x (both "hot" builds, no downloads besides the usual few xml > tests downloading stuff, I guess schemas): > > mvn clean install -Dall -> 9:37s > mvn install -Dall -> 5:26s (!!!) > > The biggest downside is the extra space consumption, if I got > the script right (du -csh `find gt2.5.x/ -name "bin" -type d`) > it's 95MB thrown into the dustbin... > > I'm curious to hear other people experience and how would people feel > about having Eclipse use a separate directory by default (patch > attached for those that want to try out) > > Cheers > Andrea > > -- > Andrea Aime > OpenGeo - http://opengeo.org > Expert service straight from the developers. ------------------------------------------------------------------------------ _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
