Man, I can't hide from this guy anywhere! :))
- Original Message -
From: "Peter Donald" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, February 03, 2002 3:09 PM
Subject: Re: [Xdoclet-devel] XDoclet file restrictions
> On Mon, 4 Feb 2002 00:
> It's also in the process of being adopted by a few other projects. We
> haven't
> integrated it fully yet and are waiting on some performance
improvements
> that
> Eriks said were coming our way soon (ie don't javadoc if don't need
to) -
> yay.
To tackle those performance issues atm you can mak
On Mon, 4 Feb 2002 00:43, Erik Hatcher wrote:
> By the way, Jakarta folks are starting to take serious note of XDoclet.
> I've put it into use in one of the Ant2 proposals to generate descriptor
> XML files. I'm now attempting to put at leasts @todo and
> defaults.properties generation into the An
- Original Message -
From: "Ara Abrahamian" <[EMAIL PROTECTED]>
> > - Most importantly - is there a way to fix the command-line length
> issue
> > when spawning javadoc? How do folks handle this constraint?
>
> I run it on win2k/xp and *very long* list of arguments and no problems.
> I t
> - Most importantly - is there a way to fix the command-line length
issue
> when spawning javadoc? How do folks handle this constraint?
I run it on win2k/xp and *very long* list of arguments and no problems.
I think you need to enhance the size of command line arguments (in win98
you can right
I've just attempted to run on Ant's complete source tree (394 .java
files) and I get the error shown below.
A few questions:
- Most importantly - is there a way to fix the command-line length issue
when spawning javadoc? How do folks handle this constraint?
- How can I get rid of the log4j er
