Spotlight goes out for Maven
For the Wicket project we use Maven as a build tool. Today I was building a new release candidate for the 1.2.1 Wicket branch, and I noticed that my MacBookPro was having a difficult time building it.
Looking in the activity monitor, I saw some weird process claiming half my CPU time, thus greatly exercising my CPU. This appeared to be the Mac OS-X spotlight importer. Googling for the process I found a way to shut that process off for a particular directory, so I told Spotlight *NOT* to index my (Java) workspace. This should be a great improvement in performance.
You can tell spotlight to stop indexing particular folders in the settings preference panel for spotlight, on the tab for privacy. Just drag your folder to the list you don’t want to be indexed.
June 30th, 2006 at 10:29 pm
Wow, what a nuisance. So every target dir of every project should be configured. The age of agent-based intelligent behavior beckons here; the OS should be able to either learn what is transitive or let you provide some kind of mask.
(Part of the reason I say this is that having it index the java parts of the workspace is not a bad idea…).
July 3rd, 2006 at 10:30 am
Hmm, that is a matter of preference. I think my IDE is much better suited for indexing and searching for Java related files than a generic searching tool like spotlight. I typically only search for Java files/classes when I’m in a development process, and as such working inside an IDE.
Therefore I don’t mind not having spotlight index my workspace.