I wouldn't mind seeing this one fixed if it's easy.

In the meantime I'm attaching a simple shell script I use to add the exclusion for the .svn directory to the generated .classpath files. It should be easy enough to modify if you use CVS

The patch I provided is probably useless at this point, there's been so much refactoring since I did this.

Oh well, can't say I didn't try.

BTW – Thanks for the script!

Two things:

1) the script I provided will bork your .classpath files by adding an extra excluding= attribute on the classpathentry elements for resource directories. I could fix that but..

2) Under Window/Preferences... Java>Compiler>Building there is an Output folder expandable section. Under there there is an entry for Filtered resources. Just add the appropriate filter for your SCM.

An updated version of the patch.

It's pretty trivial, so it would be nice if it could be applied before it bitrots this time!

Can you try the latest snapshot please?

Source exclusions can be specified with the excludes tag in the configuration section for the eclipse plugin.
Correction source exclusions are still not possible EclipsePlugin.extractSourceDirs() does not pass through any values for includes/excludes.

Resource exclusions are specified via normal pom syntax for resources.

However the default behavior of the classpath writer is to specify an includes of */.java for source directories and therefore your .svn and CVS directories will never match this.

I would need to know more details about the problem you are facing, but I think the current behavior should be acceptable and we can mark this as already fixed.

The problem I am facing is that some of the .java files in my source tree won't build against the dependency versions maven chooses for me.

Unfortunately fixing this isn't an option. It would require moving lots of stuff around in CVS which I really don't have time for.

The compiler plugin allows me to exclude classes with the <excludes> tag. It therefore seems to make sense for the eclipse plugin to do so as well.

Here is yet another version of this patch, updated to trunk as of 2009-03-26.

Have you tried 2.6-SNAPSHOT, or the proposed release 2.6?

MECLIPSE-443 has added includes ="***.java" to the classpath entry - which will do a similar thing, i.e constrain the source folder to only use .java files.

Yes - just before patching the proposed 2.6 to fix the problem and uploading the patch here.

As I mentioned before, I need to exclude some .java files from my build; including only "*/.java" is therefore insufficient to resolve the issue.

Committed to trunk for 2.6.1

The configuration for EclipsePlugin now accepts
<sourceInclusions>
<sourceInclusion>XXX</sourceInclusion>
<sourceInclusions>
(same for sourceExclusions)

to modifiy the classpath entries for source directories.

*/.java is always added if it is a java (or pde) project
*/.aj is always added if it is an ajdt project.

Still need to add documentation before I close this.

Site documentation added