[jira] [Commented] (BATIK-1233) Maven based build doesn't generate proper policy files for standalone tools

    [ https://issues.apache.org/jira/browse/BATIK-1233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16538304#comment-16538304 ] 

simon steiner commented on BATIK-1233:
--------------------------------------

Patch has diff for batik-svgbrowser/src/main/resources-filtered/org/apache/batik/apps/svgbrowser/resources/svgbrowser.policy

but this file doesnt exist in batik, how can this patch be applied?

> Maven based build doesn't generate proper policy files for standalone tools
> ---------------------------------------------------------------------------
>
>                 Key: BATIK-1233
>                 URL: https://issues.apache.org/jira/browse/BATIK-1233
>             Project: Batik
>          Issue Type: Bug
>    Affects Versions: trunk
>            Reporter: Jan Tošovský
>            Priority: Major
>         Attachments: BATIK-1233.patch
>
>
> When using maven build in favor of ant scripts as recommended in https://issues.apache.org/jira/browse/BATIK-1232 I cannot run SNAPSHOT versions of standalone tools (Squiggle, Rasterizer) because of java.security.AccessControlException. It is caused by using default 'policy' file with hardcoded library names, while those do not match the SNAPSHOT names. In the ant script there is replacement procedure which ensures proper names regardless the version.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)