[
http://jira.codehaus.org/browse/MTAGLIST-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_104492
]
Joerg Schaible commented on MTAGLIST-17:
----------------------------------------
What about an extended configuration supporting regular expressions?
{code:xml}
<regexpTags>
<regexpTag>\\* (.*)DOCUMENT_ME$<regexpTag>
<regexpTags>
{code}
The algorithm should match the regexp against each line. The first match of the
line is the hit and the first group defines the text of the tag. In this
situation you will avoid false positives for the standard tags and users like
me can define advanced search patterns.
- Jörg
> Tags not found if located in javadoc
> ------------------------------------
>
> Key: MTAGLIST-17
> URL: http://jira.codehaus.org/browse/MTAGLIST-17
> Project: Maven 2.x Taglist Plugin
> Issue Type: Bug
> Reporter: Joerg Schaible
> Attachments: MTAGLIST-17.zip
>
>
> A tag is not reported if it is located in the javadoc part of the source
> code. So it is not possible to report javadoc blocks or elements that have
> been auto-generated by a template and not filled by the programmer.
--
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
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
