Support feedback:
For some reason IntelliJ keeps asking if I want to unlock (using Perforce) weblogic.xml, even when I am not trying to edit anything
related to the weblogic.xml. In the app I am working on there is a legacy weblogic.xml from when it was a Weblogic app, that I do
not want to delete nor edit.
The only way I can get it to shut-up about this file is either to open it for edit (which I do not want to do) or remove the
weblogic integration plug-in (which I can't get back without re-installing). I end up doing the latter, but I would prefer to not
have to.
If I let IntelliJ make weblogic.xml writable then it adds a context-root element to the file. If I then make weblogic.xml read only again then IntelliJ still wants to make it writable, even though it does not change the file if I allow it to make it writable.