Justin Deoliveira ha scritto:
> I can think of one minor downside. At times I run across errors when
> building with maven, but not with eclipse. But debugging the problem is
> hard because it involves firing up a remote debug session.
Setting up a remote debug session is not that hard nowadays,
I can think of one minor downside. At times I run across errors when
building with maven, but not with eclipse. But debugging the problem is
hard because it involves firing up a remote debug session.
However sometimes what i do is compile with maven, and then directly run
with eclipse without r
Hi Andrea:
This one got lost in the noise; I am also in favour of this patch. The
only thing I can think to add is a small note in the developers guide
to the effect that geotools will target the "bin" directory.
Jody
On 29/06/2009, at 2:24 AM, Andrea Aime wrote:
> Hi all,
> for a few days
Christian Müller ha scritto:
> 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, whic
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 s
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+Ecl
