[GUMP@brutus]: Project xml-batik (in module xml-batik) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project xml-batik has an issue affecting its community integration. This issue affects 5

[GUMP@brutus]: Project xml-batik (in module xml-batik) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project xml-batik has an issue affecting its community integration. This issue affects 10

[GUMP@brutus]: Project xml-batik (in module xml-batik) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project xml-batik has an issue affecting its community integration. This issue affects 5

[GUMP@brutus]: Project xml-batik (in module xml-batik) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project xml-batik has an issue affecting its community integration. This issue affects 8

[GUMP@brutus]: Project xml-batik (in module xml-batik) success

To whom it may satisfy... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project xml-batik *no longer* has an issue. The current state of this project is 'Succes

[GUMP@brutus]: Project xml-batik (in module xml-batik) success

To whom it may satisfy... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project xml-batik *no longer* has an issue. The current state of this project is 'Succes

[GUMP@brutus]: Project xml-batik (in module xml-batik) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project xml-batik has an issue affecting its community integration. This issue affects 6

[GUMP@brutus]: Project xml-batik (in module xml-batik) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project xml-batik has an issue affecting its community integration. This issue affects 6

[GUMP@brutus]: Project xml-batik (in module xml-batik) success

To whom it may satisfy... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project xml-batik *no longer* has an issue. The current state of this project is 'Succes

[GUMP@brutus]: Project xml-batik (in module xml-batik) success

To whom it may satisfy... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project xml-batik *no longer* has an issue. The current state of this project is 'Succes

[GUMP@brutus]: Project xml-batik (in module xml-batik) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project xml-batik has an issue affecting its community integration. This issue affects 1

[GUMP@brutus]: Project xml-batik (in module xml-batik) success

To whom it may satisfy... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project xml-batik *no longer* has an issue. The current state of this project is 'Succes

[GUMP@brutus]: xml-batik/xml-batik success

To whom it may satisfy... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact folk at [EMAIL PROTECTED] Project xml-batik *no longer* has an issue. Project State : 'Success' Full details are avai

[GUMP@brutus]: xml-batik/xml-batik prerequisite failed

To whom it may satisfy... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact folk at [EMAIL PROTECTED] Project xml-batik *no longer* has an issue. Project State : 'Prerequisite Failed', Reason 'B

[GUMP@brutus]: xml-batik/xml-batik failed

To whom it may engage... This is an automated request, but not an unsolicited one. For help understanding the request please visit http://gump.apache.org/nagged.html, and/or contact [EMAIL PROTECTED] Project xml-batik has an issue affecting its community integration. This issue affects

[GUMP@brutus]: xml-batik/xml-batik failed

To whom it may engage... This is an automated request, but not an unsolicited one. For help understanding the request please visit http://gump.apache.org/nagged.html, and/or contact [EMAIL PROTECTED] Project xml-batik has an issue affecting its community integration. This issue affects

[GUMP@brutus]: xml-batik/xml-batik failed

To whom it may engage... This is an automated request, but not an unsolicited one. For help understanding the request please visit http://gump.apache.org/nagged.html, and/or contact [EMAIL PROTECTED] Project xml-batik has an issue affecting its community integration. This issue affects

[GUMP@lsd]: xml-batik/xml-batik failed

To whom it may engage... This is an automated request, but not an unsolicited one. For help understanding the request please visit http://gump.apache.org/nagged.html, and/or contact [EMAIL PROTECTED] Project xml-batik has an issue affecting its community integration. This issue affects

[GUMP@lsd]: xml-batik/xml-batik failed

To whom it may engage... This is an automated request, but not an unsolicited one. For help understanding the request please visit http://gump.apache.org/nagged.html, and/or contact [EMAIL PROTECTED] Project xml-batik has an issue affecting its community integration. This issue affects

[GUMP@lsd]: xml-batik/xml-batik failed

To whom it may engage... This is an automated request, but not an unsolicited one. For help understanding the request please visit http://gump.apache.org/nagged.html, and/or contact [EMAIL PROTECTED] Project xml-batik has an issue affecting its community integration. This issue affects

[GUMP@lsd]: xml-batik/xml-batik failed

To whom it may engage... This is an automated request, but not an unsolicited one. For help understanding the request please visit http://gump.apache.org/nagged.html, and/or contact [EMAIL PROTECTED] Project xml-batik has an issue affecting its community integration. This issue affects

[GUMP@lsd]: xml-batik/xml-batik failed

To whom it may engage... This is an automated request, but not an unsolicited one. For help understanding the request please visit http://gump.apache.org/nagged.html, and/or contact [EMAIL PROTECTED] Project xml-batik has an issue affecting its community integration. This issue affects

[GUMP@lsd]: xml-batik/xml-batik failed

To whom it may engage... This is an automated request, but not an unsolicited one. For help understanding the request please visit http://gump.apache.org/nagged.html, and/or contact [EMAIL PROTECTED] Project xml-batik has an issue affecting its community integration. This issue affects

[GUMP@lsd]: xml-batik/xml-batik failed

Project: xml-batik State: Failed URL: http://lsd.student.utwente.nl/gump/xml-batik/xml-batik.html - G U M P Y Annotations: - Error - Failed with reason build failed - G U M P Y Work Name: build_xml-

[GUMP@lsd]: xml-batik/xml-batik failed

Project: xml-batik State: Failed URL: http://lsd.student.utwente.nl/gump/xml-batik/xml-batik.html - G U M P Y Annotations: - Error - Failed with reason build failed - G U M P Y Work Name: build_xml-

[GUMP@lsd]: xml-batik/xml-batik failed

Project: xml-batik State: Failed URL: http://lsd.student.utwente.nl/gump/xml-batik/xml-batik.html - G U M P Y Annotations: - Error - Failed with reason build failed - G U M P Y Work Name: build_xml-

[GUMP@lsd]: xml-batik/xml-batik failed

Project: xml-batik State: Failed URL: http://lsd.student.utwente.nl/gump/xml-batik/xml-batik.html - G U M P Y Annotations: - Error - Failed with reason build failed - G U M P Y Work Name: build_xml-

[GUMP@lsd]: xml-batik/xml-batik failed

Project: xml-batik State: Failed URL: http://lsd.student.utwente.nl/gump/xml-batik/xml-batik.html - G U M P Y Annotations: - Error - Failed with reason build failed - G U M P Y Work Name: build_xml-

[GUMP@lsd]: xml-batik/xml-batik failed

Project: xml-batik State: Failed URL: http://lsd.student.utwente.nl/gump/xml-batik/xml-batik.html - G U M P Y Annotations: - Error - Failed with reason build failed - G U M P Y Work Name: build_xml-

[GUMP@lsd]: xml-batik/xml-batik failed

Project: xml-batik State: Failed URL: http://lsd.student.utwente.nl/gump/xml-batik/xml-batik.html RSS: http://lsd.student.utwente.nl/gump/xml-batik/xml-batik.rss Atom: http://lsd.student.utwente.nl/gump/xml-batik/xml-batik.atom - G U M P Y Annotatio

[Gump@dotnot.org]: xml-batik/xml-batik failed

Project: xml-batik State: Failed URL: http://gump.dotnot.org/xml-batik/xml-batik.html RSS: http://gump.dotnot.org/xml-batik/xml-batik.rss Atom: http://gump.dotnot.org/xml-batik/xml-batik.atom - G U M P Y Annotations: - Error - Failed with reason bu

[GUMP] Build Failure - xml-batik

This email is autogenerated from the output from: Build results exceed maximum length. Please see URL above for details. Last 50 l

[GUMP] Build Failure - xml-batik

This email is autogenerated from the output from: Build results exceed maximum length. Please see URL above for details. Last 50 l

[GUMP] Build Failure - xml-batik

This email is autogenerated from the output from: Build results exceed maximum length. Please see URL above for details. Last 50 l

[GUMP] Build Failure - xml-batik

This email is autogenerated from the output from: Build results exceed maximum length. Please see URL above for details. Last 50 l

[GUMP] Build Failure - xml-batik

This email is autogenerated from the output from: Build results exceed maximum length. Please see URL above for details. Last 50 l

[GUMP] Build Failure - xml-batik

This email is autogenerated from the output from: Build results exceed maximum length. Please see URL above for details. Last 50 l

[GUMP] Build Failure - xml-batik

This email is autogenerated from the output from: Build results exceed maximum length. Please see URL above for details. Last 50 l

[GUMP] Build Failure - xml-batik

This email is autogenerated from the output from: Build results exceed maximum length. Please see URL above for details. Last 50 l

[GUMP] Build Failure - xml-batik

This email is autogenerated from the output from: Build results exceed maximum length. Please see URL above for details. Last 50 l

Re: The organization of xml.apache.org

t wish to participate will be encouraged to form their own separate projects (or move into incubation). What I like most about such a proposal is that it is completely up to the commiters to decide whether they want opt in or

[GUMP] Build Failure - xml-batik

This email is autogenerated from the output from: Build results exceed maximum length. Please see URL above for details. Last

[GUMP] Build Failure - xml-batik

This email is autogenerated from the output from: Build results exceed maximum length. Please see URL above for details. Last

Outlook for an official release?

See below for context. Also, would it be possible and make sense to move org.w3c.css and org.w3c.dom.svg from xml-batik/sources to xml-commons/java/external ? - Sam Ruby -- Forwarded by Sam Ruby/Raleigh/IBM on 04/03/2002 03:03 PM --- "Ste

RE: Gump logo

ail). Is there any hope that batik can cooperate with the xml-commons initiative? Both the latest Apache xml-crimson and xml-xerces2 are based on the sax interfaces contained in there. - Sam Ruby - To unsubscribe, e-mail: [EMAIL

RE: Gump logo

Stephane Hillion wrote: > >> From: Sam Ruby [mailto:[EMAIL PROTECTED]] >> Sent: Wednesday, April 03, 2002 4:09 PM >> To: [EMAIL PROTECTED] >> Cc: [EMAIL PROTECTED] >> Subject: RE: Gump logo >> >> The conflict appears to be between batik-ext.jar and xml

RE: Gump logo

various org.w3c org.xml interfaces only invites integration problems such as these. This will likely also cause problems with future versions of the JDK. Is there any hope that batik can cooperate with the xml-commons initiative? - Sam Ruby --

Re: Gump logo

go.svg file you are referencing is the same as the one in > xml-batik/samples. Apparently if I run using the -jar option it works. But when I construct my classpath and happen to have xml-api.jar from xml-commons and xml-xerces2 xercesImpl.jar and xmlParserAPIs.jar from xerces2 earlier in the

Gump logo

/bench.svg http://cvs.apache.org/viewcvs/~checkout~/jakarta-alexandria/proposal/gump/site/build.xml http://jakarta.apache.org/builds/gump/latest/gump.html Can anybody help? - Sam Ruby - To unsubscribe, e-mail: [EMAIL PROT

coerceType has a new Parameter?

that work with the existing released version, I will be happy to champion that these changes be made. Otherwise, I would like to ask that you consider adding deprecated overloads that you could remove after your next release. - Sam

[GUMP] Build Failure - Batik

This email is autogenerated from the output from: Buildfile: build.xml init-args: init: prepare-docs: [mkdir] Created

[GUMP] Build Failure - Batik

This email is autogenerated from the output from: Buildfile: build.xml init-args: init: prepare-docs: [mkdir] Created

[GUMP] Build Failure - Batik

This email is autogenerated from the output from: Buildfile: build.xml init-args: init: prepare-docs: [mkdir] Created

[GUMP] Build Failure - Batik

This email is autogenerated from the output from: Buildfile: build.xml init-args: init: prepare-docs: [mkdir] Created

Re: Early warning: potential breaking interface change ahead

As I said from the outset - my purpose was to initiate a conversation. That goal apparently has been achieved. If the daily reminders (in the form of [GUMP] build failure notices) become a nuisance, let me know. - Sam Ruby P.S. Today the number of errors jumped from 13 to 37. It appears that

Re: Early warning: potential breaking interface change ahead

e the upgrade of every user of an open source project. The overall strategy which I recommend is that every time a breaking change is required, try to have at least one public release in which both the old and new interfaces are supported, with the old interfaces deprecated. - Sam Ruby

Re: Early warning: potential breaking interface change ahead

s support for both batik and fop. If fop decides to hold back on supporting the next release of fop for a while and standardize on the current release, then cocoon will either have do to likewise or temporarily drop support for fop. Thats why I strongly believe that changes to public

Early warning: potential breaking interface change ahead

http://nagoya.apache.org/~rubys/gump/xml-fop.html Standard disclaimer: I'm not making value judgements here, just simply trying to get projects to talk through potential integration issues early in the cycle... - Sam

[PATCH] allow batik to build using the upcoming Ant 1.4

Would it help if I said "please"? ;-) - Sam Ruby -- Forwarded by Sam Ruby/Raleigh/IBM on 07/19/2001 07:56 AM ------- Sam Ruby 07/16/2001 04:29 PM To: [EMAIL PROTECTED] cc: [EMAIL PROTECTED] From: Sam Ruby/Raleigh/IBM@IBMUS Subject: [PA

[PATCH] allow batik to build using the upcoming Ant 1.4

2001/07/16 20:26:01 @@ -228,9 +228,9 @@ - - - + + + - Sam Ruby - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

[GUMP] Build Failure - batik

lures. In any case, if the exclude is changed to (and a similar change is made for jacl and rhino), then these files are excluded as expected with the current (from CVS) version of Ant. - Sam Ruby - To unsubscribe, e

Re: jsGet_name

FYI - Sam Ruby -- Forwarded by Sam Ruby/Raleigh/IBM on 05/30/2001 03:22 PM --- Norris Boyd <[EMAIL PROTECTED]> on 05/30/2001 01:30:36 PM To: Sam Ruby/Raleigh/IBM@IBMUS cc: Subject: Re: jsGet_name I just checked a fix into CVS. Thanks,