From Fedora Project Wiki

Revision as of 19:05, 26 June 2009 by Overholt (talk | contribs) (Created page with 'For Fedora 12, the Fedora Eclipse group of contributors would like to focus on polish items. We have a lot of great plugins with awesome functionality but we would like to smoot...')
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

For Fedora 12, the Fedora Eclipse group of contributors would like to focus on polish items. We have a lot of great plugins with awesome functionality but we would like to smooth some rough edges to ease the development process. We are collecting a list of items here. It is preferable for items to have upstream (bugs.eclipse.org) bug report links, but if not, team members can probably be coerced into filing them.

  • C Build console should have a stop button
  • Running a C/C++ binary prompts for gdb type
  • Importing a project from existing sources could be smoother
  • Sometimes, building a single project blocks the entire workspace
  • Automatic build (CDT) is sometimes too eager
  • ~ should be expanded to /home/username in dialogues, etc.
  • Grab pkg-config macros from configure.ac and install missing -devel packages with PackageKit
  • Buffers for configure/build are often too small; log to file by default? bigger?
  • Search in the console view would be very nice
  • In EGit, Clone repository should use new project wizard if no .project files exist in repo
  • Disable building before running (CDT)
  • If automatic build is on, only changed projects should be built
  • Sometimes autotool'd projects don't build and this snowballs into other problems
    • Mis-placed warnings for header files not found (-I statements not correctly scraped)
    • Builds failing
    • Missing make targets
  • The autotools project could use some unit tests for building to increase its robustness and help to avoid regressions