> > 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:
[EMAIL PROTECTED]:/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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
