FOP Maven artifacts
Hello FOP devs-- Over at the Cocoon project we've got a fop-ng module that uses the new FOP 0.9x series to serialize XSL-FO to various output formats. However, since our switch to using Maven2 as build system, this module has had to be excluded from the build due to the fact that FOP 0.9x artifacts do not appear in any public Maven repository (that we can find). I see that there was a recent mention[1] about publishing 0.93 to the central Maven repository. Has there been any action on that? I am willing to do the legwork to put together a POM and submit the bundle to the maven upload queue, but I don't want to step on any toes. Thanks --Jason [1] http://marc.theaimsgroup.com/?l=fop-devm=116841113615715w=2
Re: FOP Maven artifacts
Jeremias Maerki wrote: You're welcome to help, especially since we don't know much about Maven. It's not only FOP that has to be deployed to the Maven repository but also XML Graphics Commons which FOP depends on. For that, I've already started some work on its build.xml [1] so that we can generate an upload bundle as described in [2]. I've also started a POM [3] for it. If that looks good to you, the same pattern could be applied to FOP, too. Thanks for the pointers. The stuff you've started for xmlgraphics-commons looks good, so I'll start from there. I didn't finish all that since I didn't have much time and don't work with Maven so my motivation was a little small. So please see what you can use and send us a patch for the rest. At one point I got confused: There was [2] which looks pretty straight-forward, but then I found [4] which I really can't make head or tail of especially in relation to [2]. If you can clear that up, that would probably help us. I mean if you can help us do this right, maybe we can do the whole thing ourselves next time. Yes unfortunately the [4] document is not at all clear. From what I understand, the procedure at [2] is the basic one for normal open source projects. However the ASF has a special rsync system set up so that ASF projects can simply place their artifacts in the rsync sructure and it will get pushed to Maven Central without having to go through the normal submission process. That is what [4] refers to, and probably what you'll want to end up doing just to make things easier. Thanks, Jason! [1] http://svn.apache.org/repos/asf/xmlgraphics/commons/trunk/build.xml [2] http://maven.apache.org/guides/mini/guide-ibiblio-upload.html [3] http://svn.apache.org/repos/asf/xmlgraphics/commons/trunk/xmlgraphics-commons-pom-template.pom [4] http://www.apache.org/dev/repository-faq.html On 21.01.2007 17:24:39 Jason Johnston wrote: Hello FOP devs-- Over at the Cocoon project we've got a fop-ng module that uses the new FOP 0.9x series to serialize XSL-FO to various output formats. However, since our switch to using Maven2 as build system, this module has had to be excluded from the build due to the fact that FOP 0.9x artifacts do not appear in any public Maven repository (that we can find). I see that there was a recent mention[1] about publishing 0.93 to the central Maven repository. Has there been any action on that? I am willing to do the legwork to put together a POM and submit the bundle to the maven upload queue, but I don't want to step on any toes. Thanks --Jason [1] http://marc.theaimsgroup.com/?l=fop-devm=116841113615715w=2 Jeremias Maerki
Re: FOP Maven artifacts
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? 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? 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 Thanks --Jason
Re: FOP Maven artifacts
Simon Pepping wrote: On Mon, Jan 22, 2007 at 09:12:18AM +0100, Jeremias Maerki wrote: 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. Users would like to use a meaningful fop-hyph.jar in order to get hyphenation for a number of languages. You can use fop-hyph.jar from the Offo project, http://downloads.sourceforge.net/offo/offo-hyphenation-fop-stable.zip?modtime=1168687293big_mirror=0. I do not know how this should be deployed in a Maven repository. How do the hyph/*.hyp definitions within the JAR get read... is just having them in the classpath enough or is there something special about the file being named fop-hyph.jar? If just being in the classpath is enough, then Offo could publish its hyph JAR as a Maven artifact under its own Group ID, and users could just declare a dependency on that artifact. I think that's out of the scope of the work I'm doing here though. ;-) I'm willing to give advice if someone else wants to take that on. --Jason
Re: Maven artifacts for Commons 1.1 and FOP 0.93 submitted
Jeremias Maerki wrote: Thanks to the help of Lars Trieloff this week, I've been able to prepare Maven artifacts for upload to the Maven2 repository. Thank you Jeremias for taking the time to do this! I had started at one point to do this but never finished. I've tested the artifacts as far as my knowledge for Maven2 goes. A small Maven-built application seems to work fine. Cocoon's fop-ng block works just fine with your bundles as well. I'm anxious for them to be deployed to repo1.maven.org so we can finally enable the block in our build! :-)
Re: FOP and XML Graphics Commons Maven artifacts
Jeremias Maerki wrote: Dear Maven-users, I've had enough. I've lost enough time on something I don't need. I'm sorry for your frustration, and want you to know that I greatly appreciate the work you've put in. I'm sure many others do as well. So thank you! I've prepared Maven bundles as per http://maven.apache.org/guides/mini/guide-ibiblio-upload.html and tried to submit them. Carlos closes those requests [1][2] with a pointer to the ASF's repository FAQ. I guess that's fine for projects using Maven. We are not. At any rate, it looks like the layout of the staging directory is totally different to what I prepared in the bundle. So I'd have to start all over and have to adjust the build scripts again. I have no time for that. You have the bundles. Do with them as you please. If anyone wants to send patches to Batik, FOP and XML Graphics Commons for producing Maven artifacts, feel welcome to do so. I'll take a crack at it. It doesn't look like it's very far off. --Jason
