Jonny,
Can you please show build/resources and build/testResources section of
your effective pom.xml?
FYI, m2e does not follow includes/excludes rules (known limitation) so
you will see such build-on-java-file-save behaviour if your project has
overlapping resources and java sources folders. If this is the case, the
workaround is to disable incremental resource processing (right-click on
the project, maven, set Goals to run on resource changes to blank
string) and use project/clean... clean action to force m2e process the
resources.
Jonny Cavell wrote:
I have a standard Appfuse Maven project in Eclipse.
Every time I save a file (e.g. edit a Java class) in core, Eclipse starts
"Building Workspace", which a) takes a long time and b) results in none of
my project's classes being able to be resolved (although Maven dependencies
such as Spring libraries etc. are ok).
I need to clean the project to sort it out each time.
How do I prevent this?
I'm using the latest version of m2eclipse.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
