[jira] (MENFORCER-100) Strings generated through ExpressionEvaluator aren't BeanShell-escaped

["Veit Guna (JIRA)" <ji...@codehaus.org>]

    [ https://jira.codehaus.org/browse/MENFORCER-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=329471#comment-329471 ] 

Veit Guna commented on MENFORCER-100:
-------------------------------------

I stumbled across the same problem.

I guess what he means is, that when you use maven variables like ${project.build.directory} in a <condition>, the backslashes in it won't be escaped properly. That leads to an evalutation error during execution. Since like String literals in normal Javacode, these must be escaped properly.

A problem like this is discussed here: http://xwiki.475771.n2.nabble.com/Notice-For-contrib-developers-td7583961.html

Maybe that clears it a bit...

                
> Strings generated through ExpressionEvaluator aren't BeanShell-escaped
> ----------------------------------------------------------------------
>
>                 Key: MENFORCER-100
>                 URL: https://jira.codehaus.org/browse/MENFORCER-100
>             Project: Maven 2.x Enforcer Plugin
>          Issue Type: Bug
>            Reporter: luke w patterson
>
> ... moving over from mailing list http://old.nabble.com/enforcer-BeanShell-script%2C-retrieving-escaped-stuff-from-ExpressionEvaluator-td28626298.html
> characters like '/' and such need to be escaped properly when injected into BeanShell Interpreter
> expressions like ${project.basedir} could easily contain the '/' character
> '/' info for BeanShell: http://www.beanshell.org/manual/bshmanual.html#Working_with_Dirctories_and_Paths

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