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

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

Oops, I haven't checked it properly. It seems to be a TortoiseSVN issue when modified files are copied to another folder [https://stackoverflow.com/questions/39651820/duplicate-file-differences-when-creating-a-patch-with-tortoisesvn] - the new patch is created via cmdline: svn diff batik-svgbrowser > BATIK---1233.patch

As commented, this patch is not final. It is rather a starting point for further discussion: merge policies or not? If not, which plugin to use for file renaming? Once this is clear, the same approach will have to be implemented also for rasterizer.

> 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)