[news.eclipse.tools] Re: javadoc: why does Main.execute not work in plug

["Martin Aeschlimann" <martin_aeschlimann@xxxxxxxxxx>]

The Javadoc wizard starts the Javadoc command as a new process (e.g.
javadoc.exe ...): This has nothing to do with plugin classloader. To find
out what is the problem open the debug view, select the process created by
the Javadoc wizard and open the properties to see the command line.
Make sure that the docletpath is complete.

I just made a test, and the start method of my doclet was found
(public static boolean start(RootDoc root))

Martin

"Student" <boheme42@xxxxxxxx> wrote in message
news:b2ampg$mf7$1@xxxxxxxxxxxxxxxx
> I'm using M5, sun jdk1.4.1_01 on W2k. If I try to start javadoc with
> a special doclet (derived from doclet Standard) via com.sun.tools.javadoc
> Main.execute(arguments) inside a plugin, javadoc
> complains about a missing start method (which is present).
>
> Console output:
> Loading source files for package test...
> Constructing Javadoc information...
> javadoc: Doclet class documentation.doclet.SpecialDoclet does not contain
a
> start method
> 1 error
>
> If I start the same doclet-code in an other process by calling
> Runtime.getRuntime().exec(arguments), the start-method is
> found and executed.
>
> To aviod building another process and handle concurrency issues
> I want to use Main.execute(String[]).
>
> I'm going slightly mad by trying to get this running.
>
> When I try to debug this, no source is attached, because I
> don't have the javadoc source.
> I suspect the plugin-classloader to play a mayor role in this case,
because
> it seems to be the only big difference (of the two start-methods). Am I
> wrong?
>
> To get access to Main.execute(...) I've copied tools.jar form sun jdk into
> my projekt directory
> and make a <runtime> <library>-entry in plugin.xml. I hope this is not
> causing any problems.
>
> Please help.
>
> Grateful for any hint
>   Hilger
>
>