I've got no time to invest in this. I'm too busy finding an alternative for Reader and seriously looking at alternatives for Gmail because I'm just plain torqued at Google right now.
Also, you can make a one time rollover from a 401K or IRA to an HSA account. So if they switched to the HSA they could start it off by rolling over the amount of their deductible from their retirement account to their HSA account.
Best part about this is the link to my home town newspaper. I used to deliver the Enterprise Record every afternoon on my bike after school. Yes, in the 70s the Enterprise Record was an afternoon paper.
Eclipse's Maven support is not great. IntelliJ's is better but Netbean's is the best in my opinion. The problem with IntelliJ's Maven support is it doesn't handle multiple non-nested projects well.
If I were able to set up global Maven build configurations without having to jin up a dummy parent project, I'd make the switch. IntelliJ has superior support for running and debugging individual JUnit tests and application debugging in general.
I also like the ability to set up a variety of "runners" in IntelliJ and then execute them with a fuzzy find as if I were on the command line.
I use IntelliJ with multiple non-nested Maven projects all the time.
I typically have a projects directory under which I have many subfolders containing Maven projects. In IntelliJ I create a single module rooted at my "projects" folder but for this module do not set up any sources. Then it is just a matter of right-clicking any POM and selecting "Add as Maven project..." I can enable/disable these projects at whim.
You can also simply add each module at a time.
I've always been impressed that it "just works". It'll even do in-IDE compilation against latest sources if it detects a snapshot dependency across (even non-nested!) modules/projects.
This paradigm is very powerful. The only thing I see missing from these types of interfaces is the ability to select part or all of the output and use it as input for a new command.
Think of it as an intermediate step of piping where the user has the ability to manually filter content. This UI concept would cover the vast majority of UI needs as almost any workflow could be captured with the following...
1.) Issue command that produces 0..N results.
2.) View results in list format.
3.) Select individual results for details view.
4.) Select 0..N results as input to a subsequent command.