[BATIK-1233] Maven based build doesn't generate proper policy files for standalone tools

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.13
• Assignee: Simon Steiner
• Reporter: Jan Tošovský
• Created: 18/Jun/18 21:00
• Updated: 04/Sep/18 14:15
• Resolved: 04/Sep/18 14:15

Description

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.

 

No error should occur:

mvn clean install -DskipTests

ant dist-zip

cd batik-1.11.0-SNAPSHOT

java -jar batik-rasterizer-1.11.0-SNAPSHOT.jar