You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@gump.apache.org by Jochen Wiedmann <jo...@freenet.de> on 2004/10/07 11:46:31 UTC
One step forward: ws-jaxme requires new jar file
Hi,
thanks to all who helped, the addition of src/jaxme as a working directory
did indeed solve the ClassNotFoundException. We have now another problem,
which relates to the use of a new jar file (beaver.jar), see the attached
message for details.
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 so, can anyone point me to an existing
project descriptor file, which could serve as a start? Otherwise, how do I
add the dependency to the existing project descriptor?
Regards,
Jochen
Re: jaxme on gump (cont)
Posted by Jochen Wiedmann <jo...@freenet.de>.
Adam R. B. Jack wrote:
> It is more Gump-like to move forward, but it is your choice.
>
> Tell you what, if you point me to a 0.9.2 I can install that for today.
Ok, have upgraded to 0.9.3.4.
Jochen
--
http://lilypie.com/baby1/050423/1/5/1/+1
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: jaxme on gump (cont)
Posted by "Adam R. B. Jack" <aj...@apache.org>.
> > No beaver.Make. Do we have a Beaver version issue?
>
> Seems so. JaxMe is currently using 0.9.2. We can upgrade the JaxMe
> version (probably tomorrow) or downgrade the gump version. Which way to
go?
It is more Gump-like to move forward, but it is your choice.
Tell you what, if you point me to a 0.9.2 I can install that for today.
regards,
Adam
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: jaxme on gump (cont)
Posted by Jochen Wiedmann <jo...@freenet.de>.
Adam R. B. Jack wrote:
> No beaver.Make. Do we have a Beaver version issue?
Seems so. JaxMe is currently using 0.9.2. We can upgrade the JaxMe
version (probably tomorrow) or downgrade the gump version. Which way to go?
Jochen
--
http://lilypie.com/baby1/050423/1/5/1/+1
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
jaxme on gump (cont)
Posted by "Adam R. B. Jack" <aj...@apache.org>.
> > 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?
Stefano was quoting from here (dependees):
http://brutus.apache.org/gump/public/project_todos.html
Sure, dom4j is the only direct dependency on jaxme, but upon that are
plenty...
http://brutus.apache.org/gump/public/dom4j/dom4j/details.html
... and on it goes. So, JaxMe is a popular beastie. :-)
----------------------------------------------------------------------------
----
Now, to the build...
JM.compile:
[javac] Compiling 193 source files to
/usr/local/gump/test/workspace/ws-jaxme/build/jm/classes
[javac]
/usr/local/gump/test/workspace/ws-jaxme/src/jaxme/org/apache/ws/jaxme/spg/im
pl/BeaverSPG.java:21: cannot resolve symbol
[javac] symbol : class Make
[javac] location: package beaver
[javac] import beaver.Make;
[javac] ^
[javac]
/usr/local/gump/test/workspace/ws-jaxme/src/jaxme/org/apache/ws/jaxme/spg/im
pl/BeaverSPG.java:54: cannot resolve symbol
[javac] symbol : variable Make
[javac] location: class org.apache.ws.jaxme.spg.impl.BeaverSPG
[javac] Make.main(new String[]{getGrammarFile().getAbsolutePath()});
[javac] ^
[javac] 2 errors
I did an unzip -t beaver*.jar | grep Make (or on beaver.jar and
beaver-rt.jar separately) and found only:
gump@brutus:/usr/local/gump/packages/beaver-0.9.3.4/lib$ unzip -t beaver.jar
| grep Make
testing: beaver/comp/Action$Reduce$Maker.class OK
testing: beaver/comp/run/Make.class OK
No beaver.Make. Do we have a Beaver version issue?
regards,
Adam
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: One step forward: ws-jaxme requires new jar file
Posted by Jochen Wiedmann <jo...@freenet.de>.
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: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: One step forward: ws-jaxme requires new jar file
Posted by Stefan Bodewig <bo...@apache.org>.
On Thu, 07 Oct 2004, Jochen Wiedmann <jo...@freenet.de>
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: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: One step forward: ws-jaxme requires new jar file
Posted by Jochen Wiedmann <jo...@freenet.de>.
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: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: One step forward: ws-jaxme requires new jar file
Posted by Stefan Bodewig <bo...@apache.org>.
On Thu, 07 Oct 2004, Jochen Wiedmann <jo...@freenet.de>
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: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: One step forward: ws-jaxme requires new jar file
Posted by Jochen Wiedmann <jo...@freenet.de>.
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: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: One step forward: ws-jaxme requires new jar file
Posted by Stefano Mazzocchi <st...@apache.org>.
Jochen Wiedmann wrote:
> Stefan Bodewig wrote:
>
>> Hmm, no CVS repo hosting the sources?
>
>
> I have filed a bug report, see
>
> http://sourceforge.net/tracker/index.php?func=detail&aid=1042208&group_id=96950&atid=616484
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.
--
Stefano.
Re: One step forward: ws-jaxme requires new jar file
Posted by Jochen Wiedmann <jo...@freenet.de>.
Stefan Bodewig wrote:
> Hmm, no CVS repo hosting the sources?
I have filed a bug report, see
http://sourceforge.net/tracker/index.php?func=detail&aid=1042208&group_id=96950&atid=616484
Regards,
Jochen
--
http://lilypie.com/baby1/050423/1/5/1/+1
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: One step forward: ws-jaxme requires new jar file
Posted by Stefan Bodewig <bo...@apache.org>.
On Thu, 07 Oct 2004, Stefan Bodewig <bo...@apache.org> wrote:
> On Thu, 7 Oct 2004, Davanum Srinivas <da...@gmail.com> wrote:
>
>> http://beaver.sourceforge.net/?
>
> OK, I'll give it a shot.
Hmm, no CVS repo hosting the sources?
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: One step forward: ws-jaxme requires new jar file
Posted by Stefan Bodewig <bo...@apache.org>.
On Thu, 7 Oct 2004, Davanum Srinivas <da...@gmail.com> wrote:
> http://beaver.sourceforge.net/?
OK, I'll give it a shot.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: One step forward: ws-jaxme requires new jar file
Posted by Davanum Srinivas <da...@gmail.com>.
http://beaver.sourceforge.net/?
-- dims
On Thu, 07 Oct 2004 13:31:27 +0200, Stefan Bodewig <bo...@apache.org> wrote:
> On Thu, 07 Oct 2004, Jochen Wiedmann <jo...@freenet.de>
> 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: general-unsubscribe@gump.apache.org
> For additional commands, e-mail: general-help@gump.apache.org
>
>
--
Davanum Srinivas - http://webservices.apache.org/~dims/
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: One step forward: ws-jaxme requires new jar file
Posted by Stefan Bodewig <bo...@apache.org>.
On Thu, 07 Oct 2004, Jochen Wiedmann <jo...@freenet.de>
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: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org