Andy Cutright said:
> as an observer, i'd like to second that. we're leveraging the core in a
> server, the server may be operating in an environment that has no GUI
> sytem installed, in which case, any GUI initialization that's causing
> say the AWT to fire up is going to cause the VM to fail to start,
Read the patch, especially the dialog hooking and the AutoAddJob code.
You will find that if the ui plugin isn't started the auto-add
functionallity will fail gracefully, cancelling the job after some
I didn't make that code because I claimed to know anything about the
ui<->core dependencies, but more as a safety measure proven to be useful
If you think otherwise, send me an detailed mail and I will fix it.
(But I seriously doubt you will find anything)
Also, if you're using the core package standalone you probably know what
youre doing, and never let core ask you for passwords and such things.
There's alotta code related to core that could spawn UI dialogs like
asking for file/project overwriting.
Received on Thu Apr 7 10:15:48 2005