Marcus Better wrote:
Matthias Klose wrote:
Assuming that the doc is installed in /usr/share/doc/libfoo-java/api,
a reference to a class Bar should point to ../../libbar-java/api. Not
yet sure how to find the location for this reference
I seem to remember that javadoc can be given a command
Hi,
Mark Wielaard said:
You can use the -link option to do this. It works very well with
Sun's
Javadoc, but I have not tried it with gjdoc. I can't remember the
details, but it's integrated with ant's javadoc target.
For Debian packages we need -linkoffline to link to the locally
On Sun, 2007-01-14 at 01:12 +0100, Michael Koch wrote:
On Sat, Jan 13, 2007 at 09:19:31PM +, Paul Cager wrote:
Marcus Better wrote:
Matthias Klose wrote:
Assuming that the doc is installed in /usr/share/doc/libfoo-java/api,
a reference to a class Bar should point to
Michael Koch wrote:
On Sat, Jan 13, 2007 at 09:19:31PM +, Paul Cager wrote:
Marcus Better wrote:
Matthias Klose wrote:
Assuming that the doc is installed in /usr/share/doc/libfoo-java/api,
a reference to a class Bar should point to ../../libbar-java/api. Not
yet sure how to find the
On Sat, Jan 13, 2007 at 11:54:14PM +, Paul Cager wrote:
Michael Koch wrote:
On Sat, Jan 13, 2007 at 09:19:31PM +, Paul Cager wrote:
Marcus Better wrote:
Matthias Klose wrote:
Assuming that the doc is installed in /usr/share/doc/libfoo-java/api,
a reference to a class Bar should
On Sun, Jan 14, 2007 at 12:31:11AM +, Matthew Johnson wrote:
Another question: Where th package uses a standard API (e.g.
java.util.Map), should I link to
http://java.sun.com/j2se/1.5.0/docs/api/ or what?
No, please depend on classpath-doc and use these. We dont wanna link to
Another question: Where th package uses a standard API (e.g.
java.util.Map), should I link to
http://java.sun.com/j2se/1.5.0/docs/api/ or what?
No, please depend on classpath-doc and use these. We dont wanna link to
resources on the net. The idea is to have all on your hard disk when you
Matthias Klose wrote:
How come? I thought we put api docs in the -doc package, if there is
one.
exactly, but into the /usr/share/doc/$package/api directory, not into
the /usr/share/doc/$package-doc/api directory.
Oh, I wasn't aware of that. I've been doing it the other way around. But it
Hi,
Marcus Better said:
Matthias Klose wrote:
How come? I thought we put api docs in the -doc package, if there is
one.
exactly, but into the /usr/share/doc/$package/api directory, not into
the /usr/share/doc/$package-doc/api directory.
[...]
Is it really better to put the docs in
Hi Matthias,
On Thu, 2007-01-11 at 21:11 +0100, Matthias Klose wrote:
The idea was to make the -doc packages depend on other -doc packages
so that references to other packages can be resolved; unfortunately
gjdoc doesn't support that yet.
What would you need from gjdoc to support 'that'?
Paul Cager wrote:
which seems more sensible to me. Should I change it to
/usr/share/doc/$package/api? I assume I should also create a doc-base.
Yes, sounds reasonable.
The draft policy [1] suggests /usr/share/doc/package/api. Check this
thread [2] about how to write the doc-base file.
Marcus
Paul Cager writes:
I am updating the BCEL library to the new upstream version. The old
version installed the Javadocs into:
/usr/share/doc/$package/doc/api
Daniel Baumann queried this last night on IRC, and it seems that other
(newer) packages (e.g. libxalan2-java-doc) install into
I am updating the BCEL library to the new upstream version. The old
version installed the Javadocs into:
/usr/share/doc/$package/doc/api
Daniel Baumann queried this last night on IRC, and it seems that other
(newer) packages (e.g. libxalan2-java-doc) install into
/usr/share/doc/$package/api
13 matches
Mail list logo
