Re: [Cp-tools-discuss] Re: Planning to check-in new branch: the GIOP extensions for rmic.

Hi, On Wed, 2006-02-08 at 13:25 -0700, Tom Tromey wrote: > > "Tom" == Thomas Fitzsimmons <[EMAIL PROTECTED]> writes: > > Tom> In fact, long term, I'd rather see all of the tools in cp-tools > Tom> merged into cvs.savannah.gnu.org:/sources/classpath and used by > Tom> all bundlers of GNU Class

Re: [Cp-tools-discuss] Re: Planning to check-in new branch: the GIOP extensions for rmic.

Hi, On Wed, 2006-02-08 at 13:25 -0700, Tom Tromey wrote: > In particular, I think we want to be sure that the various > tools are usable in a typical java environment -- so for instance I > think we want it to be clear to end users, packagers, etc, that it is > fine for 'ant' to load gjdoc (or an

Re: [Cp-tools-discuss] Re: Planning to check-in new branch: the GIOP extensions for rmic.

> "Tom" == Thomas Fitzsimmons <[EMAIL PROTECTED]> writes: Tom> In fact, long term, I'd rather see all of the tools in cp-tools Tom> merged into cvs.savannah.gnu.org:/sources/classpath and used by Tom> all bundlers of GNU Classpath. Yeah, I agree. This has a number of benefits, and I can't th

Re: [Cp-tools-discuss] gjdoc-0.7.1-pre1

On Feb 5, 2005, at 11:48, Mark Wielaard wrote: Note the new crisp stylesheet, better Use pages, improved documentation, full command line flags compatibility, and the colored source code! that really is nice. i was wondering just yesterday why Sun's JavaDoc still looks like something designed by

Re: [Fwd: Re: [Cp-tools-discuss] Cp-tools Javadoc Overview (was Re:Classpath API javadoc)]

Hi, On Sun, 2002-05-05 at 22:40, Julian Scheid wrote: > Julian Scheid wrote: > > but perhaps it is better to wait with that > > until the files contain the appropriate (C) lines. So perhaps > > take it down again? > > Didn't notice that you already included the correct (C) > statement, my fau

[Fwd: Re: [Cp-tools-discuss] Cp-tools Javadoc Overview (was Re: ClasspathAPI javadoc)]

Julian Scheid wrote: > but perhaps it is better to wait with that > until the files contain the appropriate (C) lines. So perhaps > take it down again? Didn't notice that you already included the correct (C) statement, my fault. ___ Classpath maili

Re: [Cp-tools-discuss] Cp-tools Javadoc Overview (was Re: Classpath API javadoc)

Original Message Subject: Re: [Cp-tools-discuss] Cp-tools Javadoc Overview (was Re: ClasspathAPI javadoc) Date: Sun, 05 May 2002 20:04:27 +0200 From: Julian Scheid <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] CC: Mark Wielaard <[EMAIL PROTECTED]>, [EMA

Re: [Cp-tools-discuss] Cp-tools Javadoc Overview (was Re: Classpath API javadoc)

> "Mark" == Mark Wielaard <[EMAIL PROTECTED]> writes: Mark> (For people that are interested in a sneak preview you can see it Mark> on .) Is there a way to get the display without frames? With the Sun javadoc there is. Tom ___

Re: [Cp-tools-discuss] Cp-tools Javadoc Overview (was Re: ClasspathAPI javadoc)

Hi, On Sun, 2002-05-05 at 14:06, Julian Scheid wrote: > The XML doclet will now produce multiple XML files (one index file > and one for each class documented.) > This can speed up XSLT processing by orders of magnitude when you > are documenting large trees (like the full Classpath source.) > Th

Re: [Cp-tools-discuss] Cp-tools Javadoc Overview (was Re: ClasspathAPI javadoc)

Hi Mark, great that you gave it a try. First of all: I've to admit that I didn't check in my recent changes, and there were a lot of them. I just did that... sorry, I'm not very used to working on a CVS repository. I'll make sure that I check in future changes without delay. However, build and

Re: [Cp-tools-discuss] Cp-tools Javadoc Overview (was Re: ClasspathAPI javadoc)

Mark Wielaard wrote: > - The file gnu/classpath/tools/doclets/xmldoclet/HtmlWell.java > contains an unreadable (on my system) character on like 53. I fixed that in CVS. Note that HtmlWell is currently not used. Julian ___ Classpath mailing list

Re: [Cp-tools-discuss] Cp-tools Javadoc Overview (was Re: ClasspathAPI javadoc)

Hi, On Sun, 2002-04-28 at 15:08, Julian Scheid wrote: > > If there are any build issues with the tools (especially with > Gjdoc and the XML doclet, which are not yet autoconf'ing AFAIK) > I'll be glad to help - just post to <[EMAIL PROTECTED]>. Just a quick note for people trying out gjdoc sinc

Re: cp-tools

Phillip Morelock <[EMAIL PROTECTED]> writes: > hi, > > i'm still kind of newwhat is the "cp-tools" list and those of you who've > been reading my messages over the past week can maybe answer: should I join > that list too? > > cheers > fillup http://savannah.gnu.org/projects/cp-tools/ is e

Re: Cp-tools Javadoc Overview (was Re: Classpath API javadoc)

John Leuner wrote: > >- "Gjdoc" is an alternative javadoc driver. [...] > > How do we compile and run this driver? It's a bunch of Java classes, jikes path/*.java should do for now. I think the package also includes a dirty development Makefile. It's fairly command line compatible to Sun Javad

Re: Cp-tools Javadoc Overview (was Re: Classpath API javadoc)

> Mark Wielaard wrote: > > > > I have not tried out the texidoclet for the Classpath Tools project yet. > > Source can be found > > I don't know if there has been an official release yet. > > > Hi there, > > let me take this opportunity and giv