[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=16542247#comment-16542247 ] 

Jan Tošovský commented on BATIK-1233:
-------------------------------------

I am unable to create patch, so here are my steps: I created \batik-svgbrowser\src\main\resources-filtered\org\apache\batik\apps\svgbrowser\resources folder structure and moved there svgbrowser.bin.policy and svgbrowser.policy files from \batik-svgbrowser\src\main\resources\org\apache\batik\apps\svgbrowser\resources folder. In the latter folder I deleted unused svgbrowser.policy.ref file and then modified the content of policy files in the new location. Then I and also tweaked the content of pom.xml. I've attached the zipped result.

> 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, batik-svgbrowser.zip
>
>
> 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)