[
https://jira.codehaus.org/browse/MRELEASE-861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MRELEASE-861.
-----------------------------------
Resolution: Won't Fix
Assignee: Robert Scholte
This is not directly related to the maven-release-plugin. Such rules should be
checked during every build or any time you want, not only during a release.
{quote}... if there was a rule to enforce ... {quote}
Now there's this plugin called the [Maven Enforcer
Plugin|http://maven.apache.org/enforcer/maven-enforcer-plugin/] for which you
can specify rules. Sounds like a 100% match, right?
This plugin has a standard set of rules, but these are all Maven related, while
yours is JSP related. So such a rule won't become part of the standard rules.
However, there's an
[API|http://maven.apache.org/enforcer/enforcer-api/writing-a-custom-rule.html]
with which you can write your own rules. That would be the best solution for
you. If you want to share it, maybe the [Codehaus Mojo
team|http://mojo.codehaus.org/extra-enforcer-rules/] is interested.
> Rule for JSP comments
> ---------------------
>
> Key: MRELEASE-861
> URL: https://jira.codehaus.org/browse/MRELEASE-861
> Project: Maven Release Plugin
> Issue Type: Wish
> Affects Versions: 2.1
> Reporter: Marc Pompl
> Assignee: Robert Scholte
> Priority: Minor
>
> It would be really nice if there was a rule to enforce JSP style comments
> instead of HTML comments. JSP comments have the benefit of be stripped from
> the rendered HTML. For this, it increases security since developers leave
> regularly hints for attackers.
> So, the rule has to find usages of i.e.
> <!-- set this to X and the server crashes -->
> and suggest the usage of
> <%-- no my clue is hidden from any browser -->
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
