Configuring Local History Directories
526321Aug 15 2006 — edited Aug 23 2006Using JDeveloper w/ Perforce. When I went to "Mark for Add" in Perforce, surprise, surprise, every single local history file version shows up in my changelist.
This is because JDeveloper appears to simply take whatever the project root is and then make a "peer-level" directory called ".history" to store the revisions.
However, since my Java dev is happening well within my source tree, all of these files show up as adds.
my source tree looks like:
webapp/
--java/
----myProject/
....
with /webapp/ mapping to the root of the Perforce depot.
...JDeveloper inserts a .history folder at the "myProject" level:
webapp/
--java/
----.history/
----myProject/
Options:
a) Configure Perforce depot to workspace mappings with an exception to leave out the .history folder - not optimal because it relies on my memory - which is not optimal.
b) Purge local history each time before check-in - again, not optimal. Too easy to forget and leave garbage in the depot.
c) Turn off local history. Not optimal because this is a really neat feature.
d) Configure where JDeveloper stores history - i.e. outside of the source tree. This is the optimal solution.
However, after searching a long time on Oracle site, the web JDeveloper help, looking through the .conf files, etc. I am unable to locate anywhere to configure where JDeveloper decides to arbitrarily place this folder.
Any suggestions?