> >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?
I'm no expert on it, but there are a heap of people doing workarounds for the javadoc and javac engines calling System.exit, so I'm assuming there's no such nice answer :( > >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. On a per build file basis? Yeah, that could work. So each build file could control the location/name of the tmp file. Maybe just allowing an override of the tmp file might be cleaner. Do you want to have a look at a patch? (o: cheers dim _______________________________________________ Xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
