Often stack traces can get so verbose from long class paths that they are very painful to read. Here's an example: 1) No implementation for java.util.Set< com.mydomain.myapp.android.activities.catbrowser.generalizedbrowser.listview. helpers.databaseitem.itemmanipulators.ItemManipulator< com.mydomain.myapp.flash.Cat>> annotated with @com.google.inject.assistedinject.Assisted(value=) was bound. while locating java.util.Set< com.mydomain.myapp.android.activities.catbrowser.generalizedbrowser.listview. helpers.databaseitem.itemmanipulators.ItemManipulator< com.mydomain.myapp.flash.Cat>> annotated with @com.google.inject.assistedinject.Assisted(value=) ... If I could trim the class path, only showing class names and methods, it would look like this: 1) No implementation for Set<ItemManipulator<Cat>> annotated with @Assisted(value=) was bound. while locating Set<ItemManipulator<Cat>> annotated with @Assisted(v