You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Dan Fabulich (JIRA)" <ji...@codehaus.org> on 2007/11/26 03:28:57 UTC

[jira] Closed: (SUREFIRE-45) Include/Exclude by class name, not file name

     [ http://jira.codehaus.org/browse/SUREFIRE-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dan Fabulich closed SUREFIRE-45.
--------------------------------

       Resolution: Cannot Reproduce
    Fix Version/s:     (was: 2.x)

Under the hood, Surefire matches by class file name.  (THOSE are guaranteed to be classes.)  For example, we exclude inner classes by default by excluding **/*$*.  The best of both worlds!

> Include/Exclude by class name, not file name
> --------------------------------------------
>
>                 Key: SUREFIRE-45
>                 URL: http://jira.codehaus.org/browse/SUREFIRE-45
>             Project: Maven Surefire
>          Issue Type: New Feature
>            Reporter: Ken Arnold
>
> Right now I include/exclude based on file names.  But file names are not class names -- see nested classes or non-public classes.  (A class file can contain only one public class, and its name must match its file name, but it can have any number of package-accessible top-level classes.)
> I would like to be able to specify by class name, not file name.  Possibly this a new pair of tags (e.g., <excludeClass>).

-- 
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