I know that maven doesn't use ant as of 2.0, but I would assume that the includes/excludes concepts are inherited from the ant fileset. The way that works, ALL files are included, unless one or more include elements are specified. If they are specified, than that is your base include. I'm also assuming that the compile plugin has some default excludes (.cvs, .svn, etc). But, I'm with Wendy, why not just move the properties file to a resources directory?
On 8/31/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
On 8/31/06, Andreas Guther <[EMAIL PROTECTED]> wrote: > To include files to the org.apache.maven.plugins compile process one has > to specify those files in the configuration/includes section. ... > Is this a general behavior in Maven with the includes section or is this > something specific to the compiler plug-in? I think that's how it always works. In particular I've noticed that if you have any includes, then you have to also re-state the default of src/main/resources if you also want that included. (It can be important during a conversion when you may have things in both places.) Of course, moving all non-Java files to src/main/resources fixes this. :) -- Wendy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
