Uploaded image for project: 'Batik'
  1. Batik
  2. BATIK-1233

Maven based build doesn't generate proper policy files for standalone tools

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.13
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      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

        Attachments

        1. BATIK-1233.patch
          19 kB
          Jan Tošovský
        2. batik-svgbrowser.zip
          399 kB
          Jan Tošovský

          Activity

            People

            • Assignee:
              ssteiner Simon Steiner
              Reporter:
              jan.tosovsky.cz Jan Tošovský
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: