> Let me rephrase to make sure we talk about the same thing
>
> m2eclipse runs (approximate) maven build lifecicle during eclipse build
> to filter resources, (re)generate sources, deployment descriptors and so
> on.
>
> And you want an option to have "pure" eclipse build which will only
> generate .class files and copy resources to non-maven output and
> test-output folders. To reiterate, m2eclipse will not automatically
> (re)generate source and will not make available at runtime any other
> files produced during normal maven build.
>
> Right?
Yes. And let see if I did predict the following well: yes I know that I
can already do that. I just have to change the build directory in my
project settings. That is what I did until version 0.9.4.
My problem is that in this version (0.9.4), when I launch an
application or a test, that eclipse classpath is not the project one, it
is ${project}/target/classes and ${project}/target/test-classes, and
because eclipse is not compiling into those directories, the launch will
fail to get changes if I don't do a mvn compile or mvn test before. So I
need an option to have m2eclipse *not* changing the classpath of the
launches.
--
Benjamin LERMAN
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
