At 19:23 2002-02-22 +1100, Dmitri Colebatch wrote: > > At 11:23 2002-02-22 +1100, Dmitri Colebatch wrote: > > >That wont be needed for much longer though... with XJavadoc - yes? > > > > But XJavadoc is an undetermined time into the future, no? My experience of > > software projects tells me that it might be ready in a month and it might > > be delayed until 2006 so is it possible for another smaller change? > >true, its always possible... but I've heard the 2months timeframe >mentioned by a very reliable man (o:
I guess I have to trust you. :-) > > I might be able to provide a patch if you give me a pointer in the right > > direction (if it's not requires patching javadoc. :-) ). > >the problem is that javadoc _must_ run in a separate vm 'cause it calls >System.exit - so the way the ant javadoc task works is that it spawns a >new vm. Now, the thing is that we get our configuration before the new vm >starts, and need it in the new vm. The way we do this is by having a file >written to by the ant vm, and read from by the javadoc vm. Maybe it's possible to set a securitymanager that denies javadoc access to System.exit? >If you can think of another way to get around the problem then I'm happy >to apply a patch. My thoughts were to create a random number and pass that random number to javadoc in the system properties. That random number would give the name of the file so no temporary files could get same name. /Daniel _______________________________________________ Xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
