The Eclipse IDE makes searching for code very easy, both with built-in functionality and third-party plugins such as Ctrlflow Code Search Professional. This is even more true when using the various shortcuts, which this post will introduce you to. When searching for code, developers typically want to either find locations where, e.g., a [...]Ctrlflow
The Ctrlflow blog covers insights about Automated Error Reporting & Code Search for Java in Eclipse, including exception handling, code snippets, bug tracking, etc.
TL;DR This article describes four standard workflows by which you can quickly and effectively analyze and process incoming problems. As a rule each error report falls into one of the following 4 categories: Known Bug: The user reports a problem that the team already knows about and which is already tracked in the bug tracker. [...]Ctrlflow
You can use Ctrlflow Automated Error Reporting in two ways. Either you use it as a minimal bug tracker for your error reports or you can use it’s Bug Tracker Integration in order to load the found problems into your company’s bug tracker. This article presents both possibilities to you. How to use Ctrlflow Automated Error Reporting [...]Ctrlflow
As of 2.0.0 Ctrlflow Automated Error Reporting UI allows editing of multiple problems at once. This feature was requested by many of you and has now been implemented, finally! Editing multiple problems at once is now pretty straight forward: Go to the problems overview page or problem search results page, Click on “Edit Multiple Problems [...]Ctrlflow
What exactly does Ctrlflow Automated Error Reporting mean by terms like error reports, problems, bugs, and projects? In this article, you will learn about these core concepts. Overview of the four core concepts of Ctrlflow Automated Error Reporting By default, automated error reports contain: a random reporter ID an error message, and a [...]Ctrlflow