Question: In previous versions of Idea, if I had the "development" or "production" Maven profiles checked, whenever I ran my unit tests, IntelliJ IDEA did not actually use these profiles. Instead, it didn't use any of them.

Since I am developing a Spring-based application, I use 3 profiles to configure various things, but mostly my `applicationContext.xml`. Whenever profiles were not used, because the property syntax was the same, Spring would conveniently fall back to `applicationContext.properties` when a Maven profile was not used to replace the values in my application context.

But with newer versions of IntelliJ, this fallback mechanism no longer happens. If 'production' is checked under the Maven tab in IntelliJ IDEA, then IDEA will actually use that profile whenever I run my unit tests. This means that before I run my unit tests, I have to ALWAYS make sure to both clean the project and check the Maven profile I have selected, which frankly adds a lot of overhead when I need to switch back and forth between "test" and "development"... and god forbid my dbunit tests start overwriting the "development" database because the wrong profile was actually selected!

Now, I'm a pretty lazy developer. I like my IDE to be smart enough to always use the "test" profile whenever I run my unit tests, even if "production" or "development" is selected. How can I tell IntelliJ IDEA to do just that? It used to do just that in older versions of IDEA, and I want to get the same behaviour - it works for me.

Answer: 
I think `click at` stopped working in 10.9. Or at least

```
tell application "System Events" to tell process "Safari"
    set frontmost to true
    click at {20, 20}
end tell

```

works for me in 10.8 but results in an error like `error "System Events got an error: Can’t make {20, 20} into type list." number -1700 from {20, 20} to list` in 10.9.

Try to use [MouseTools](http://www.hamsoftengineering.com/codeSharing/MouseTools/MouseTools.html) or [cliclick](http://www.bluem.net/en/mac/cliclick/) (or JavaScript) instead.
I just answered a quite similar problem with s.o. trying to "click at desktop" ([here](https://apple.stackexchange.com/questions/219088/activate-desktop-using-applescript/220536#220536)) ... 

System Events' sdef file says, that *"click at" still works **when sent to a "process" object** [at] the { x, y } location at which to click, in global coordinates* (meaning: in absolute screen coordinates, *NOT* relative to an app's window). 

So: you *cannot* "click at" a file visible on desktop (as a "file" there actually is: *image of group 1 of scroll area of process "Finder"*) but you still can click at any window / button. 

Every "click", anywhere on your screen must have an "aim". It won't work like a mouse pointer.