[
http://jira.codehaus.org/browse/MTAGLIST-46?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=189561#action_189561
]
Nate Stoddard commented on MTAGLIST-46:
---------------------------------------
One more item, but it is more toward the Taglist future plans then this
specific feature request. How will Taglist handle languages with different
comment strings? For example the "mxml" file could have an XML comment (<!--
TODO: add validation to this form field -->), but the current Taglist logic is
looking for /* or // to start a comment.
My first thought was that the selectable file extensions and selectable
comments should be in separate Jira tickets, but I don't know if users will
want to have these combined in the configuration. They could then mix multiple
languages in the same build. E.g. Java, XML and HTML. In that mix language
case, we could use a configuration like this...
<languageExtensions>
<languageExtension>
<fileExts>
<fileExt>java</fileExt>
</fileExts>
<commentDelims>
<commentDelim>
<start><![CDATA[/*]]></start>
<end><![CDATA[*/]]></end>
</commentDelim>
<commentDelim>
<start><![CDATA[//]]></start>
</commentDelim>
</commentDelims>
</languageExtension>
<languageExtension>
<fileExts>
<fileExt>xml</fileExt>
<fileExt>html</fileExt>
</fileExts>
<commentDelims>
<commentDelim>
<start><![CDATA[<!--]]></start>
<end><![CDATA[-->]]></end>
</commentDelim>
</commentDelims>
</languageExtension>
</languageExtensions>
This is much more complex then a simple file extension list, but the user has
flexibility. Not sure sure what is the best approach.
> Support for other programming languages as well
> -----------------------------------------------
>
> Key: MTAGLIST-46
> URL: http://jira.codehaus.org/browse/MTAGLIST-46
> Project: Maven 2.x Taglist Plugin
> Issue Type: New Feature
> Environment: environment independent
> Reporter: Christoph Pickl
> Priority: Minor
> Attachments: patch-taglist-cpickl_2009_09_02.txt
>
>
> currently only java files are supported. but as the syntax of many other
> languages are similar to java's, it should not be that hard to adjust the
> plugin for these other languages.
> changes which have to be made:
> 1) TagListReport#hasSources() ... change ".java"
> 2) FileAnalyser#findFilesToScan() ... change "**/*.java"
> in the attached eclipse patch you will find these changes, plus a
> SourceFileFilter class which handles proper filtering depending on a new
> maven configuration "languageMode" (which can now be either "java" which is
> the default, or "flex" which looks for *.as and *.mxml files).
--
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
