xmlgraphics-batik-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "simon steiner (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BATIK-1233) Maven based build doesn't generate proper policy files for standalone tools
Date Wed, 20 Jun 2018 10:31:00 GMT

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

simon steiner commented on BATIK-1233:

Your patch has batik-svgbrowser/src/main/resources-filtered/org/apache/batik/apps/svgbrowser/resources/svgbrowser.bin.policy
multiple times

> 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

To unsubscribe, e-mail: batik-dev-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: batik-dev-help@xmlgraphics.apache.org

View raw message