>From: "Ara Abrahamian" <[EMAIL PROTECTED]>
>Date: Mon, 13 May 2002 15:11:20 +0430
>
>No. The old xjavadoc.jar is somewhere in lib or classpath.
Thanks, found it (in lib). Unfortunately, I'm getting the following
instead. Some experimentation indicates it's the jboss task that's the
problem,
- Original Message -
From: Mathias Bogaert <[EMAIL PROTECTED]>
Date: Monday, May 13, 2002 1:00 pm
Subject: RE: [Xdoclet-devel] build scripts
> Yeah.
>
> 1. it seems that the Messages are not included in the jar
> file...someoneshould look into this
>
> 2. th
file etc) and if they rely on
each other.
Could someone explain this to the mailing list? Thanks
Mathias
-Original Message-
From: Ara Abrahamian [mailto:[EMAIL PROTECTED]]
Sent: maandag 13 mei 2002 12:41
To: 'Andrew Stevens'; [EMAIL PROTECTED]
Subject: RE: [Xdoclet-devel] bui
Yeah, I had this one too.
Remove xjavadoc.jar from the the class path (lib dir), and try again. It's
probably an old version of xjavadoc (XJavaDocMain class was removed).
Mathias
-Original Message-
From: Andrew Stevens [mailto:[EMAIL PROTECTED]]
Sent: maandag 13 mei 2002 12:29
To: [EMAIL
No. The old xjavadoc.jar is somewhere in lib or classpath. I'm getting
this one:
[ejbdoclet] XDoclet BUG: Can't locate resource
'generating_template_output_singl
e_file' for bundle 'xdoclet.Messages'.
[ejbdoclet] generating_template_output_single_file
compile:
[mkdir] Created dir:
D:\Project
> Yeah, so am I. I think it was a bd desicion to extend from Ant's Java
> task.
Yes, that is a bad idea! :)
Actually the best thing to do (and maybe how you do it?) is to encapsulate
an instance of the Java task and control it internally.
Erik
__
> I forgot to mention that it's taken care of too. ModuleFinder is
> rewritten,
> and it now looks at the classpath. It gets the classpath from a system
> property (xdoclet.class.path) which is set by DocletTask. This
classpath
> is
> the same as the one passed into the taskdef. (It doesn't work w
> What's the status of changing modulejar/loading system? I can handle it
> if you're busy but not before Monday. The other day we had an online
> conference regarding the problems we have with the class loading system.
> We found a neat way to tackle it. Basically we won't have any
> or finding
