I think I mean something different. When XGC adds something new and FOP uses that, a new XGC jar file must be used by builds. We do that by having a new jar file in /lib, typically called xmlgraphics-commons-1.5-svn.jar (which may be updated a few times during development of the next release). How would that be handled by the maven build? Would it require the deployment of a snapshot to Maven central? And would the version number in the pom file be updated?
Simon On Wed, Sep 08, 2010 at 05:13:07PM +0800, Glenn Adams wrote: > If I understand you correctly, the answer is no. The file maven/pom.xml in > the patch explicitly references revision 1.7 of the batik artifacts. So any > use of upward revisions of those artifacts would require updating the > pom.xml file to reflect use of a newer revision. > > At present, I worked around the headless problem (testWMF) by specifying > java.awt.headless as false in the pom.xml configuration for those test > suites that invoke testWMF. Of course, that also means that the this patch > will fail those tests when invoked on a truly headless platform. > > Does that answer your query? Or are you asking if I can adjust the > configuration to make automatic use of snapshot updates? > > Regards, > Glenn > > On Wed, Sep 8, 2010 at 3:47 PM, Simon Pepping <[email protected]>wrote: > > > Does this build system require us to deploy snapshots of > > xmlgraphics-commons and batik to the maven repository, whenever we use > > snapshot versions in our lib directory? We do routinely for xgc, and > > we may need to do so for batik if the headless problem is fixed (see > > https://issues.apache.org/bugzilla/show_bug.cgi?id=42408#c13). -- Simon Pepping home page: http://www.leverkruid.eu
