On 21.01.2007 22:56:26 Jason Johnston wrote: > OK, got some questions: > > 1) When I do a build, there are several artifacts created in the build/ > directory: > > fop-hyph.jar > fop.jar > fop-sandbox.jar > fop-transcoder-allinone.jar > fop-transcoder.jar > > Obviously fop.jar is the main artifact, but should any of the others be > uploaded as Maven artifacts as well?
At the moment, Batik needs fop-transcoder-allinone.jar (circular reference between the two products). The JAR provides PDF and EPS production capabilities for Batik's Transcoder API (SVG to * conversion). But this dependendy will be resolved within the next months. fop-hyph.jar only contains stuff if someone adds custom hyphenation patterns. Normally, it's quite empty. fop-sandbox.jar currently doesn't contain anything that is usable. In short: no, I currently don't see a need to publish any JAR other than fop.jar. > 2) I notice that the FOP binary downloads provide a download for JDK1.3 > and one for JDK1.4. Do we need to create Maven artifacts for both, or > would choosing one suffice? If just the JDK1.3 jar is uploaded, would > users running JDK1.4+ be able to use it? Yes, it should work. This stuff is mostly a compile-time thing. So far, I haven't found a case where the JDK 1.3 binary didn't work with later versions. But I could be wrong here. > 3) Batik 1.6 is released to the Maven repository as many separate > artifacts rather than one monolithic JAR. Are there any of these that > FOP does not depend on, that we can exclude from the dependency list? > Here are all the artifacts: > > batik-awt-util > batik-bridge > batik-css > batik-dom > batik-ext > batik-extension > batik-gui-util > batik-gvt > batik-parser > batik-rasterizer > batik-rasterizer-ext > batik-script > batik-slideshow > batik-squiggle > batik-squiggle-ext > batik-svg-dom > batik-svggen > batik-svgpp > batik-swing > batik-transcoder > batik-ttf2svg > batik-util > batik-xml AFAICT, FOP doesn't need: - batik-rasterizer - batik-rasterizer-ext - batik-slideshow - batik-squiggle - batik-squiggle-ext - batik-svgpp - batik-swing - batik-ttf2svg ATM, we don't need batik-svggen, either, but I plan to use it to cheaply reestablish SVG rendering capabilities for FOP. When Batik 1.7 is out, we will also depend on batik-codec and batik-anim which are not available from Batik 1.6. batik-anim may sound a little strange since we don't do animation but in a short test with Batik Trunk & FOP Trunk batik-anim was necessary. Jeremias Maerki
