Don't know why. From one day to the next, the file was reverted back to its installed contents. I had dozens of library definitions in that file. Were this file stored in CVS (eg, like jbuilder *.library files) it would have been no problem.
I can send the log file if jetbrains wishes, but there are literally hundreds of stack traces in it. --- I know this is eap, and thus I know that I take these risks willingly. But when the eap goes production, should half the project settings continue to be stored in the install directory (like a windows app that blifully jams files into system32) this problem will be incured again. Also, I mentioned to eap support (before then sent me over the eap newsgroup) that this is the single issue that is major enough for my team--other than myself--to not switch from jbuilder. _______________________________________________ Eap-bugs mailing list [EMAIL PROTECTED] http://lists.jetbrains.com/mailman/listinfo/eap-bugs
