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] [Assigned] (BATIK-1233) Maven based build doesn't generate proper policy files for standalone tools
Date Tue, 04 Sep 2018 13:54:00 GMT

     [ https://issues.apache.org/jira/browse/BATIK-1233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

simon steiner reassigned BATIK-1233:
------------------------------------

    Assignee: simon steiner

> 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ý
>            Assignee: simon steiner
>            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)

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


Mime
View raw message