You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Mike Youngstrom (JIRA)" <ji...@codehaus.org> on 2007/05/18 22:41:58 UTC
[jira] Created: (MCLOVER-78) Excludes should not take higher
presedence than includes
Excludes should not take higher presedence than includes
--------------------------------------------------------
Key: MCLOVER-78
URL: http://jira.codehaus.org/browse/MCLOVER-78
Project: Maven 2.x Clover Plugin
Issue Type: Bug
Affects Versions: 2.4
Reporter: Mike Youngstrom
Fix For: 2.5
If I do:
<includes>
<include>**/somefile.java</include>
</includes>
<excludes>
<exclude>**/*.java</exclude>
</excludes>
Then it appears no files get instrumented. I think the include and exclude rules should work the same way they do with the surefire plugin where includes have a higher precedence than excludes
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCLOVER-78) Excludes should not take higher
presedence than includes
Posted by "Mike Youngstrom (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCLOVER-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_96308 ]
Mike Youngstrom commented on MCLOVER-78:
----------------------------------------
The example should read:
<includes>
<include>**/somefile.java</include>
</includes>
<excludes>
<exclude>**/*.java</exclude>
</excludes>
> Excludes should not take higher presedence than includes
> --------------------------------------------------------
>
> Key: MCLOVER-78
> URL: http://jira.codehaus.org/browse/MCLOVER-78
> Project: Maven 2.x Clover Plugin
> Issue Type: Bug
> Affects Versions: 2.4
> Reporter: Mike Youngstrom
> Fix For: 2.5
>
>
> If I do:
> <includes>
> <include>**/somefile.java</include>
> </includes>
> <excludes>
> <exclude>**/*.java</exclude>
> </excludes>
> Then it appears no files get instrumented. I think the include and exclude rules should work the same way they do with the surefire plugin where includes have a higher precedence than excludes
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCLOVER-78) Excludes should not take higher
presedence than includes
Posted by "Mike Youngstrom (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCLOVER-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_96309 ]
Mike Youngstrom commented on MCLOVER-78:
----------------------------------------
Well, nevermind my '*'s are getting escaped. :) Trust me it is correct.
> Excludes should not take higher presedence than includes
> --------------------------------------------------------
>
> Key: MCLOVER-78
> URL: http://jira.codehaus.org/browse/MCLOVER-78
> Project: Maven 2.x Clover Plugin
> Issue Type: Bug
> Affects Versions: 2.4
> Reporter: Mike Youngstrom
> Fix For: 2.5
>
>
> If I do:
> <includes>
> <include>**/somefile.java</include>
> </includes>
> <excludes>
> <exclude>**/*.java</exclude>
> </excludes>
> Then it appears no files get instrumented. I think the include and exclude rules should work the same way they do with the surefire plugin where includes have a higher precedence than excludes
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira