[
https://issues.apache.org/jira/browse/FOP-3150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17765664#comment-17765664
]
Tom Habing commented on FOP-3150:
-
[~ssteiner] I have existing code (C# .NET) that has been invoking FOP as an
external process using the executable jar method. To avoid the extra layer of
complexity and to keep the code as cross-platform as possible, I would prefer
to avoid invoking the bat or shell scripts. If I have to, I can rewrite my
'JavaRunner' code to use the classpath and mainclass command line params.
Based on the documentation,
[https://xmlgraphics.apache.org/fop/2.9/running.html#jar-option], I assumed
that the inconsistency between the releases was an oversight, but if the
executable jar is going away, rewriting my JavaRunner wouldn't be overly
difficult.
> Binary distribution used to include an executable jar file
> --
>
> Key: FOP-3150
> URL: https://issues.apache.org/jira/browse/FOP-3150
> Project: FOP
> Issue Type: Bug
> Components: unqualified
>Affects Versions: 2.9
> Environment: Windows 10
>Reporter: Tom Habing
>Priority: Major
>
> With version 2.8 there was a single executable jar file in the build
> directory, allowing it to be run like so:
>
> {code:java}
> C:\Program Files\Apache FOP\fop-2.8\fop\build>java -jar fop.jar -version
> FOP Version 2.8{code}
> With version 2.9 this seems to no longer be the case. Now it seems like the
> full class path and the main class need to be specified on the command line:
> {code:java}
> C:\Program Files\Apache FOP\fop-2.9\fop\build>java -cp ";C:\Program
> Files\Apache FOP\fop-2.9\fop\build\fop-2.9.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\build\fop-core-2.9.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\build\fop-events-2.9.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\build\fop-util-2.9.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-anim-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-awt-util-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-bridge-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-codec-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-constants-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-css-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-dom-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-ext-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-extension-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-gvt-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-i18n-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-parser-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-script-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-shared-resources-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-svg-dom-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-svggen-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-transcoder-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-util-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\batik-xml-1.17.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\commons-io-2.11.0.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\commons-logging-1.0.4.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\fontbox-2.0.27.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\xml-apis-1.4.01.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\xml-apis-ext-1.3.04.jar;C:\Program Files\Apache
> FOP\fop-2.9\fop\lib\xmlgraphics-commons-2.9.jar" org.apache.fop.cli.Main
> -version
> FOP Version SVN{code}
>
> An executable jar file for 2.9 would be appreciated.
> Also, as you can see above, 2.9 does not report a valid version number.
> (I'll file a separate ticket for this.)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
