On Fri, 2003-03-07 at 17:45, Hunter Hillegas wrote:
> Yeah, I didn't have the Commons logging in the classpath. Got that fixed,
> but now I get this action:
>
> ejbdoclet:
> [echo] +---------------------------------------------------+
> [echo] | |
> [echo] | R U N N I N G E J B D O C L E T |
> [echo] | |
> [echo] +---------------------------------------------------+
>
> BUILD FAILED
> file:/Users/hunter/Desktop/groundswell-commerce/build.xml:81: Can't create a
> localinterface element under ejbdoclet. Make sure the jar file containing
> the corresponding subtask class is on the classpath specified in the
> <taskdef> that defined {2}.
Okay, and now we're back to the same error message that came up (and was
answered) on the list just a few days ago (subject "Re: [Xdoclet-user]
xdoclet problem on Mac OSX")
As I said then, the message has a bug (now fixed) with incorrect
placeholder nos. which is why it shows the "{2}". In your case, the
task is complaining that it can find javax.ejb.EntityBean, as it needs
the EJB classes available to satisfy various dependencies. Have you
ensured the EJB API classes (either from the J2EE reference
implementation, or your own app server's copy of them) are in the
classpath for the ejbdoclet task?
Andrew.
-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger
for complex code. Debugging C/C++ programs can leave you feeling lost and
disoriented. TotalView can help you find your way. Available on major UNIX
and Linux platforms. Try it free. www.etnus.com
_______________________________________________
xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user
