Rhino schrieb am 30.10.2011 um 13:14 (-0400):
>
> How do I tell the javadoc task which doctype I want for my
> generated Javadocs? It is generating HTML 4.01 but I want it to
> generate XHTML1.0.
Isn't javadoc always that rusty-trusty HTML 4.01? Take a look at the
source of this page, HTML 4.01,
I've solved this problem for myself. My objective was to be able to
display accented letters correctly in my Javadocs, such as the French "e
acute", and I managed to accomplish that by adding these options to the
Javadoc command:
encoding="UTF-8" docencoding="UTF-8" charset="UTF
How do I tell the javadoc task which doctype I want for my generated
Javadocs? It is generating HTML 4.01 but I want it to generate XHTML1.0.
I don't see anything in the javadoc parameters in the Ant Manual that
specifies the HTML doctype.
--
Rhino
Hi
I suddenly ran into the very same error when my fileset dir attribute was
set to a root path that was just a wee bit longer than before. As a result,
the arguments passed to the javadoc process get truncated, and the error
ensues.
I was able to work around the problem by using the usexterna
On 9/12/07, Prashant Reddy <[EMAIL PROTECTED]> wrote:
>
> On Wed, 2007-09-12 at 14:37 +0100, Peter Reilly wrote:
> > > Shouldn't javadoc task pick this artifact (package-info.java) given
> > that
> > > this file is meant only for the javadoc tool ? Why should the user
> > have
> > > to explicitly i
On Wed, 2007-09-12 at 14:37 +0100, Peter Reilly wrote:
> > Shouldn't javadoc task pick this artifact (package-info.java) given
> that
> > this file is meant only for the javadoc tool ? Why should the user
> have
> > to explicitly include it ?
> 1) the fileset is not only used in
I was thinking m
On 9/12/07, Prashant Reddy <[EMAIL PROTECTED]> wrote:
> Hello ANT Users,
>
> I have a lot of files from which javadoc needs to be generated.
>
> Not all java files from a package need to be published in javadoc.
>
> To enable this i use a number of s that provide input to
> javadoc task.
>
> Someth
Thank you all, that fixed it!! It was the links! Thank you again!
Deus Davis wrote:
>
> I have a build which will occasionally hang in the middle of running my
> javadoc task. I have increased memory usage to 1GB and still have the
> issue. I turned on verbose mode and still I am getting no ind
On 6/20/07, Deus Davis <[EMAIL PROTECTED]> wrote:
This doesn't happen every time I build bu frequently. The only links in the
javadoc task are the following.
Could this be the problem?
I would
This doesn't happen every time I build bu frequently. The only links in the
javadoc task are the following.
Could this be the problem?
Peter Reilly-2 wrote:
>
> It could be that you are behi
It could be that you are behind a proxy and you are trying
to link to some off-site http:// location.
Peter
On 6/19/07, Deus Davis <[EMAIL PROTECTED]> wrote:
I am compiling with version 1.5 and I am specifying 1.5 as my javac version
Qazwart wrote:
>
> Take a look at the "target" and "source"
I am compiling with version 1.5 and I am specifying 1.5 as my javac version
Qazwart wrote:
>
> Take a look at the "target" and "source" properties of the
> task. If you use a higher Java JDK than you want to compile to, you
> can set these properties to emulate the Java JDK you are compilin
Take a look at the "target" and "source" properties of the
task. If you use a higher Java JDK than you want to compile to, you
can set these properties to emulate the Java JDK you are compiling
for and the Java JDK you will be running on.
You can also set the "ant.build.javac.source" and
Hello Adrian,
I do not know where this problem is coming from.
What about filling in a bug report with a simple build.xml, specifying
your environment (OS, JDK version).
Regards,
Antoine
Rodriguez, Adrian wrote:
> Hi. I can't javadoc to generate my documentation using 1.7beta3. Here
> are the me
Yepp!
Tanks for your quick reply.
:)
/Klas
-Original Message-
From: Stefan Bodewig [mailto:[EMAIL PROTECTED]
Sent: den 2 maj 2005 16:26
To: user@ant.apache.org
Subject: Re: javadoc task
On Mon, 2 May 2005, Klas Nyman <[EMAIL PROTECTED]> wrote:
> the build suddenly broke
On Mon, 2 May 2005, Klas Nyman <[EMAIL PROTECTED]> wrote:
> the build suddenly broke when the project grew and some *.java files
> were added. it is a small numer of java files (<200) but quite many
> jars in the classpath.
Probably your command line has grown too long for your OS. Try
whether s
I'm using java 1.5.0_02 and ant 1.6.3 (also broken in 1.6.2)
/Klas
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: den 2 maj 2005 16:15
To: user@ant.apache.org
Subject: javadoc task
Hi!
I have a problem running the javadoc task; it stops with
C:\UTV\java\F
Ok. Problem solved.
The useexternalfile=yes option to the task reduced, as it said
it would in the docs ;), the command line length and bingo.
Next time Ill tell myself RTFM! :)
Greg.
From: Greg Irvine [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 8 Ma
On Wed, 2004-11-10 at 19:28, Charles Daniels wrote:
>
> ...
>
Yep
That did it.
Many thanks folks.
I now have impressive documentation!
--
Regards DaveP.
XSLT&Docbook FAQ
http://www.dpawson.co.uk/xsl
-
To unsubscribe
On Wed, 2004-11-10 at 19:36, Dominique Devienne wrote:
>
> It may be that by default like Javadoc doesn't pick up package
> private members. Unless you meant interface xyz instead of class xyz.
> And if not, then most likely your string, if it's a constant, should be
> declared as static final,
> From: Dave Pawson [mailto:[EMAIL PROTECTED]
>
> I have a java file I use simply to hold string
> values used elsewhere.
> public class xyz{
> /**
> * description
> */
> String x = "..";
> }
>
> javadoc is not picking up the docstrings for output.
>
> Is there an ant property I need to set
By default javadoc only includes docs for public and protected classes
and members. Since your variable is declared as package private, it's
javadoc will not be included by default. Using Ant's javadoc task, you
can specify a value for the access attribute. The default value is
protected, matchi
Kinda tough to be specific without seeing the buil.xml
Perhaps the addition of a core task within the target that is using
to test the source directory
and conditionally call javadoc based on the resulting property value .
-Original Message-
From: Matt [mailto:[EMAIL PROTECTED]
Sent
23 matches
Mail list logo
