Re: One step forward: ws-jaxme requires new jar file
On Thu, 07 Oct 2004, Jochen Wiedmann [EMAIL PROTECTED] wrote: I have just checked. Dom4j is dependent on jaxmeapi.jar. Most probably it depends only on the Java 5 XML classes like XMLConstants, QName, or NamespaceContext. We have long ago suggested, that these be moved to a separate jar file in xml-general or jakarta-general. :-( xml-commons? Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: One step forward: ws-jaxme requires new jar file
Stefan Bodewig wrote: xml-commons? Sorry, of course I meant xml-commons or jakarta-commons. Jochen -- http://lilypie.com/baby1/050423/1/5/1/+1 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: One step forward: ws-jaxme requires new jar file
On Thu, 07 Oct 2004, Jochen Wiedmann [EMAIL PROTECTED] wrote: Beaver is a Java parser generator subject to the BSD license. In other words, it would most probably be possible to add a Beaver project to Gump. Is this the suggested way to go? If possible, yes. If so, can anyone point me to an existing project descriptor file, which could serve as a start? If it is an sourceforge project, httpunit may be a good starting point. Otherwise it may get a bit more complex when we need to add a repository definition. Where can I get more information about Beaver? Otherwise, how do I add the dependency to the existing project descriptor? There are (at least) three more options - in decreasing order of Stefan's personal preference: * turn it into an installed dependency (like jaf.xml for example). Requires write access to Brutus to actually work. * add a project to jaxme's module descriptor that points to the jar in your CVS module. * add a work to the ws-jaxme project that points to the jar in your CVS module. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: One step forward: ws-jaxme requires new jar file
http://beaver.sourceforge.net/? -- dims On Thu, 07 Oct 2004 13:31:27 +0200, Stefan Bodewig [EMAIL PROTECTED] wrote: On Thu, 07 Oct 2004, Jochen Wiedmann [EMAIL PROTECTED] wrote: Beaver is a Java parser generator subject to the BSD license. In other words, it would most probably be possible to add a Beaver project to Gump. Is this the suggested way to go? If possible, yes. If so, can anyone point me to an existing project descriptor file, which could serve as a start? If it is an sourceforge project, httpunit may be a good starting point. Otherwise it may get a bit more complex when we need to add a repository definition. Where can I get more information about Beaver? Otherwise, how do I add the dependency to the existing project descriptor? There are (at least) three more options - in decreasing order of Stefan's personal preference: * turn it into an installed dependency (like jaf.xml for example). Requires write access to Brutus to actually work. * add a project to jaxme's module descriptor that points to the jar in your CVS module. * add a work to the ws-jaxme project that points to the jar in your CVS module. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas - http://webservices.apache.org/~dims/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: One step forward: ws-jaxme requires new jar file
On Thu, 7 Oct 2004, Davanum Srinivas [EMAIL PROTECTED] wrote: http://beaver.sourceforge.net/? OK, I'll give it a shot. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: One step forward: ws-jaxme requires new jar file
On Thu, 07 Oct 2004, Stefan Bodewig [EMAIL PROTECTED] wrote: On Thu, 7 Oct 2004, Davanum Srinivas [EMAIL PROTECTED] wrote: http://beaver.sourceforge.net/? OK, I'll give it a shot. Hmm, no CVS repo hosting the sources? Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: One step forward: ws-jaxme requires new jar file
Stefan Bodewig wrote: Hmm, no CVS repo hosting the sources? I have filed a bug report, see http://sourceforge.net/tracker/index.php?func=detailaid=1042208group_id=96950atid=616484 Regards, Jochen -- http://lilypie.com/baby1/050423/1/5/1/+1 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: One step forward: ws-jaxme requires new jar file
Stefano Mazzocchi wrote: I would suggest we just add the package, then. jaxme is holding up 134 projects, let's not add anymore potentially shaky dependencies for now. May I ask a silly question: How come the number 134? I can hardly imagine, that more than two or three of them are actually using JaxMe right now? Regards, Jochen -- http://lilypie.com/baby1/050423/1/5/1/+1 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: One step forward: ws-jaxme requires new jar file
On Thu, 07 Oct 2004, Jochen Wiedmann [EMAIL PROTECTED] wrote: May I ask a silly question: How come the number 134? I can hardly imagine, that more than two or three of them are actually using JaxMe right now? dom4j does. jaxen depends on dom4j and an insane amount of projects depend on jaxen. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: One step forward: ws-jaxme requires new jar file
Stefan Bodewig wrote: dom4j does. jaxen depends on dom4j and an insane amount of projects depend on jaxen. I have just checked. Dom4j is dependent on jaxmeapi.jar. Most probably it depends only on the Java 5 XML classes like XMLConstants, QName, or NamespaceContext. We have long ago suggested, that these be moved to a separate jar file in xml-general or jakarta-general. :-( Jochen -- http://lilypie.com/baby1/050423/1/5/1/+1 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
