Andrea Aime wrote:
> Justin Deoliveira ha scritto:
>> Was bin intentionally kept out of target so that it is not susceptible
>> to being wiped out in a mvn clean? I can see pros and cons both ways I
>> suppose.
[...]
> Wondering if it's possible to automate the bin folders cleaning
> somehow with
I am now getting unit test failures that pass in maven and used to pass
in Eclipse. I suspect modules using testResources might be affected.
Eclipse may have been relying on maven testResources to set up the
classpath with everything in it.
--
Ben Caradoc-Davies
Software Engineer, CSIRO Explo
"mvn clean" in the eclipse environment is "Clean all Projects". In my
opinion, it is not a good idea to mix these two kinds of building.
Things are easier to understand if mvn does its own build/clean and eclipse
does its own build/clean.
Justin Deoliveira writes:
> Was bin intentionally ke
Andrea Aime ha scritto:
> Justin Deoliveira ha scritto:
>> Was bin intentionally kept out of target so that it is not susceptible
>> to being wiped out in a mvn clean? I can see pros and cons both ways I
>> suppose.
>
> Eclipse goes mad when someone fiddles with its class files and, at least
> o
Justin Deoliveira ha scritto:
> Was bin intentionally kept out of target so that it is not susceptible
> to being wiped out in a mvn clean? I can see pros and cons both ways I
> suppose.
Eclipse goes mad when someone fiddles with its class files and, at least
on my pc, I had to do a mvn eclipse:
Was bin intentionally kept out of target so that it is not susceptible
to being wiped out in a mvn clean? I can see pros and cons both ways I
suppose.
The other nice thing about putting it under target is would be it gets
caught by svn:ignore, currently when I do an "svn st" i get all the bin
