Author Topic: Java: refactoring, jdk selection, debugger improvements  (Read 653 times)

Tree

  • Community Member
  • Posts: 79
  • Hero Points: 2
Java: refactoring, jdk selection, debugger improvements
« on: July 23, 2009, 02:48:09 pm »
- general java cleanup.
- more java refactoring support
- per-project jdk selection
- java debugging include support for pausing one thread, and/or resuming all others.
- java breakpoints include option for pausing only target thread (see the api)
- java debug symbol browsing should use "toString" for most types. Finding a Long's value is annoying.
- java debugger should short-cut to populated members of a sparse Map, like a HashMap
- include import package order in adaptive filtering

carlpmiller

  • Community Member
  • Posts: 33
  • Hero Points: 1
Re: Java: refactoring, jdk selection, debugger improvements
« Reply #1 on: September 24, 2009, 08:03:19 pm »
- general java cleanup.
- more java refactoring support
- per-project jdk selection
- java debugging include support for pausing one thread, and/or resuming all others.
- java breakpoints include option for pausing only target thread (see the api)
- java debug symbol browsing should use "toString" for most types. Finding a Long's value is annoying.
- java debugger should short-cut to populated members of a sparse Map, like a HashMap
- include import package order in adaptive filtering


I second all the above suggestions. I primarily work in Java and the IDE's are getting much better/slicker at these types of tasks, especially when it comes to refactoring names.

+1+ for native Mac support.

+1 for faster autolookups.

Saw another suggestion for better searching across all code one may have available (not just within a single project). I often boast how Slick to me often serves the same purpose as SQL does for a database - it allows me to find things in ways that I just can't easily do otherwise. To span that across ones repository of code bases, that would be yet another level of power. Sort of like the Google code search but more unique to the end user (me).