Re: [M2]Compile includes/excludes - was Re: Confusion about plugin section of project descriptor & id's

[Brett Porter <br...@apache.org>]

Kris Bravo wrote:

>Interesting. I have one project of type ejb where imposing filters the
>way I described does affect the standard compiles, but another of type
>jar where the filters are ignored as you suggested. A moot point given
>on the change you are explaining, but interesting anyway.
>  
>
That sounds like a bug :)

>Back to what your saying, having includes, testIncludes, excludes and
>testExcludes is more difficult. Instead of adding parameters to the
>AbstractCompilerMojo each subclass must be changed, as does the
>signature of computerStaleSources. No big deal effort-wise, but I'll
>have to update the patch to the ticket and it prompts a question:
>  
>
this makes it consistent with the provision of the source roots
themselves, which are in the individual mojos.

>Will (is?) M2 forever restricted to a compile/testCompile, or will other
>compile types be supported as well, and would filter support require
>more include/exclude sets? I ask because of the potential explosion of
>tags such as unitTestIncludes, systemTestIncludes, etc...
>  
>
I have an open ticket to resolve how we can extend to more than one type
of test, and compiling sources from mojos is certainly a desirable
feature. All I can say at this point is that it will be taken into
consideration, but I haven't thought it right through yet.

- Brett


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org