Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "PDE/Plan/3.6"

< PDE‎ | Plan
Line 3: Line 3:
 
</div></div>
 
</div></div>
  
= Schedule =
+
== Schedule ==
  
 
Dates are listed in the Eclipse Platform Releng Calendar (view as [http://www.google.com/calendar/ical/kq3ed9c0latktst29lrl8nffu0%40group.calendar.google.com/public/basic.ics iCal])
 
Dates are listed in the Eclipse Platform Releng Calendar (view as [http://www.google.com/calendar/ical/kq3ed9c0latktst29lrl8nffu0%40group.calendar.google.com/public/basic.ics iCal])
  
= Overall Goals =  
+
== Overall Goals ==
  
=== Improve PDE code quality ===
+
==== Improve PDE code quality ====
  
 
* Better testing
 
* Better testing
 
* Better milestone/release ramp down
 
* Better milestone/release ramp down
  
=== MORE TO COME ===
+
==== More to come... ====
  
= Work Items =  
+
== Work Items ==
  
== PDE General ==
+
=== PDE General ===
  
=== Bundles or Plug-ins ===
+
==== Bundles or Plug-ins ====
  
 
* Rename PDE to Bundle Development Environment
 
* Rename PDE to Bundle Development Environment
 
* Use of the word plug-in in UI
 
* Use of the word plug-in in UI
  
=== Improve PDE communications ===
+
==== Improve PDE communications ====
  
 
* Continued web page improvements
 
* Continued web page improvements
Line 34: Line 34:
 
* Integrate wiki based documentation
 
* Integrate wiki based documentation
  
=== Graduate PDE Dependency Visualizer ===
+
==== Graduate PDE Dependency Visualizer ====
 
* {{bug|106676}}: [pde viz] Graduate
 
* {{bug|106676}}: [pde viz] Graduate
  
== PDE UI ==
+
=== PDE UI ===
  
=== Improve code quality ===
+
==== Improve code quality ====
  
 
* Write tests for core components
 
* Write tests for core components
Line 45: Line 45:
 
* Consider code coverage in tests
 
* Consider code coverage in tests
  
=== Target Platform ===
+
==== Target Platform ====
  
 
* Continue target platform definition enhancements.  
 
* Continue target platform definition enhancements.  
Line 57: Line 57:
 
** {{bug|159072}}: [target] associate target definitions on a per-project basis (multiple target platforms per workspace)
 
** {{bug|159072}}: [target] associate target definitions on a per-project basis (multiple target platforms per workspace)
  
== API Tools ==
+
=== API Tools ===
  
=== API Use Scans ===
+
==== API Use Scans ====
  
 
* Make it really easy to generate API use scans
 
* Make it really easy to generate API use scans
Line 68: Line 68:
 
* Performance improvements
 
* Performance improvements
  
== Build ==
+
=== Build ===
  
 
* {{bug|154083}}: Incremental Plug-in Build
 
* {{bug|154083}}: Incremental Plug-in Build
Line 74: Line 74:
 
* {{bug|222965}}: Use frameworkadmin to generate config.ini / eclipse.ini
 
* {{bug|222965}}: Use frameworkadmin to generate config.ini / eclipse.ini
  
 
+
== Platform Support ==
= Platform Support =
+
  
 
* Eclipse: 3.6
 
* Eclipse: 3.6

Revision as of 12:44, 16 July 2009

Note: This is an unofficial document used by the PDE team to help with the planning process. Items on this list aren't guaranteed to be found in a release.

Schedule

Dates are listed in the Eclipse Platform Releng Calendar (view as iCal)

Overall Goals

Improve PDE code quality

  • Better testing
  • Better milestone/release ramp down

More to come...

Work Items

PDE General

Bundles or Plug-ins

  • Rename PDE to Bundle Development Environment
  • Use of the word plug-in in UI

Improve PDE communications

  • Continued web page improvements
  • Use of wiki for meetings/planning
  • Combine mailing lists
    • Completed
  • Involve incubator projects such as Picasso to the webpage, and use Athena/Hudson to propose builds/update-sites of these projects
  • Integrate wiki based documentation

Graduate PDE Dependency Visualizer

PDE UI

Improve code quality

  • Write tests for core components
  • Improve code readability and javadoc of APIs
  • Consider code coverage in tests

Target Platform

  • Continue target platform definition enhancements.
  • Target platform/definition contents could be managed entirely with p2 profiles for improved performance and for proper persistence/restoration.
  • OSGi state could be associated with target definitions and leveraged for per-project target build paths.
  • Remove dependency on preferences
  • Improved APIs
    • bug 169340: [API] [target] Expose a means to programmatically set and load a Target Platform
  • Multiple target platforms
    • bug 159072: [target] associate target definitions on a per-project basis (multiple target platforms per workspace)

API Tools

API Use Scans

  • Make it really easy to generate API use scans
  • Output can be HTML report or search results in the IDE (with attached source)
  • Compare API use scans to see summary of dependencies added/removed between successive scans
  • Analyze scans for potential breakage (internal dependencies) when moving to a new version of required components (for example WTP moving to a new version of the Eclipse SDK).
  • Consider scans taylored to show API use based on frequency of use - i.e. what APIs internals are used most heavily.
  • Performance improvements

Build

Platform Support

  • Eclipse: 3.6
  • Target Platforms back to 3.0 supported
  • Java: J2SE 1.4 or later required
  • Operating Systems: all supported by Eclipse

Back to the top