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

Dennis Lundberg updated MTAGLIST-22:
------------------------------------

    Description: 
Background: Modern IDEs offer code templates for new files or new methods. Also 
some code formatters add automatically template-based javadoc comments. 
Typically such templates use tags as placeholders for the real description 
which are located at the end of the line. Enhancing the standard tag detection 
to support EOL tags might trigger too many false positives, especially if the 
tag comment has to be extracted too.

Therefore this proposal is about the support of an extension to the 
configuration to support tags defined as regular expression:

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

Background of this issue are the comments at MTAGLIST-17, see the attachment 
there for code with such tags.

  was:
Background: Modern IDEs offer code templates for new files or new methods. Also 
some code formatters add automatically template-based javadoc comments. 
Typically such templates use tags as placeholders for the real description 
which are located at the end of the line. Enhancing the standard tag detection 
to support EOL tags might trigger too many false positives, especially if the 
tag comment has to be extracted too.

Therefore this proposal is about the support of an extension to the 
configuration to support tags defined as regular expression:

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

Background of this issue are the comments at TAGLIST-17, see the attachment 
there for code with such tags.


> Regular expression support for tags
> -----------------------------------
>
>                 Key: MTAGLIST-22
>                 URL: http://jira.codehaus.org/browse/MTAGLIST-22
>             Project: Maven 2.x Taglist Plugin
>          Issue Type: New Feature
>    Affects Versions: 2.1
>            Reporter: Joerg Schaible
>
> Background: Modern IDEs offer code templates for new files or new methods. 
> Also some code formatters add automatically template-based javadoc comments. 
> Typically such templates use tags as placeholders for the real description 
> which are located at the end of the line. Enhancing the standard tag 
> detection to support EOL tags might trigger too many false positives, 
> especially if the tag comment has to be extracted too.
> Therefore this proposal is about the support of an extension to the 
> configuration to support tags defined as regular expression:
> {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.
> Background of this issue are the comments at MTAGLIST-17, see the attachment 
> there for code with such tags.

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

Reply via email to