Eclipse Problems View: Only Show Problems for Project


Having many projects open the same time, and working on them in parallel is a challenge. Ok, the human brain is not built for multitasking, but I still try ;-). What I typically I end up in my Eclipse Problems View to have entries from multiple projects mixed up:

Problems View with Entries for multiple Projects

Problems View with Entries for multiple Projects

How to show it that I can fix the problems for ony project only, and not showing all problems from all projects?

Closing Projects

The Eclipse Problems view only shows the problems of (all) open projects. An easy way is to close the other projects using the (context) menu Project > Close Project:

Closing Project with Context Menu

Closing Project with Context Menu

But then I need to re-open that project later again, which will take time. So while this works, but this is not ideal.

Show Error/Warnings on Project

A better way in my view is to use this: There is an option in the Problems view to just show the messages for the currently active/selected project:

Option to Show Errors and Warnings on Project

Option to Show Errors and Warnings on Project

With this, only the messages for the currently active project are shown:

Problems View with Messages for the Active Project

Problems View with Messages for the Active Project

Summary

The Problems View has filtering and configuration capabilities which are easily overlooked. But knowing it and configuring the Problems view for my needs helped me to get more productive.

Happy Problem Solving :-)

About these ads

2 thoughts on “Eclipse Problems View: Only Show Problems for Project

  1. I have been using Eclipse for Java, Ruby and C development for several years and faced this problem many times. While the ability to focus on a single project can be useful, it’s not usually enough. I usually end up ignoring the problems view as it becomes too cluttered to be useful.

    Unlike many other IDEs, Eclipse encourages development in multiple related projects, yet it does not really have any way of grouping them together, so I can’t tell it to just show problems from a subset of open projects.

    There is not enough fine-grained control to hide or remove specific problems in specific projects or areas of the source code. Usually I like to fix problems as soon as possible rather than leaving them nagging at me, but I open find that I am working with third-party code which I cannot change. There is little point Eclipse filling up its problems display with errors that I cannot do anything about!

    I like Eclipse, and have become very productive with it, but it still annoys me sometimes with things such as this.

    Like

    • Yes, I face similar problems with 3rd party source code. Typically I end up fixing the warnings or using compiler settings to have them ignored as much as feasible. At least in MU10.3 Eclipse they made an extension so I can delete the errors/warnings from the problem view with deleting the root of the list (in stock Eclipse I have to select each message). The Problems view is more like a ‘bag of messages’, and what I find problematic is that messages are not uniform (same format). Some do have the project information, some don’t. This because the Problems view is trying to extract the information from the Console view. That approach is flawed, because that Console view parser slows down things, and never will be perfect because every tool vendor does its own thing. The proper solution would be a standard API for tools to report problems, the correct way. Until then, I’ll have to workaround all these issues.

      Like

What do you think?

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s