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?


On Wed, Sep 8, 2010 at 3:47 PM, Simon Pepping <spepp...@leverkruid.eu>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
> On Sat, Sep 04, 2010 at 06:42:56AM -0400, bugzi...@apache.org wrote:
> > https://issues.apache.org/bugzilla/show_bug.cgi?id=49881
> >
> > --- Comment #1 from Glenn Adams <gl...@skynav.com> 2010-09-04 06:42:53
> EDT ---
> > Created an attachment (id=25986)
> >  --> (https://issues.apache.org/bugzilla/attachment.cgi?id=25986)
> > Patch to add maven build support.
> >
> > This patch has been verified against repository version 992575.
> --
> Simon Pepping
> home page: http://www.leverkruid.eu

Reply via email to