[
https://issues.apache.org/jira/browse/BATIK-1233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16517558#comment-16517558
]
Jan Tošovský commented on BATIK-1233:
-------------------------------------
We could employ 'filtering' in the process-resources phase, which can replace
variables specified in POM properties. To prevent filtering binary files all
policy files were moved into resources-filtered folder.
But there are two policy files for either source or binary distributions
[https://xmlgraphics.apache.org/batik/using/scripting/security.html] which
makes things a bit complicated. For binary distribution, when copying
resources, we have to exclude the original svgbrowser.policy and use
svgbrowser.bin.policy instead (renamed to svgbrowser.policy). This can be
achieved by maven-ant-plugin or 3rd party maven-file-rename-plugin
https://stackoverflow.com/questions/3998596/renaming-resources-in-maven
But the question is if we really need two separate files. Would it be Ok to
merge the content of both files?
> 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)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
