[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [eclipse-dev] Planning Meeting Notes - Nov 23, 2005
|
Correction...
The discussion topic regarding 2.1 backward compatibility has been proposed
by PDE, not UA.
Wassim.
Mike
Wilson/Ottawa/IBM
@IBMCA To
Sent by: eclipse-dev@xxxxxxxxxxx
eclipse-dev-bounc cc
es@xxxxxxxxxxx
Subject
[eclipse-dev] Planning Meeting
11/22/2005 03:09 Notes - Nov 23, 2005
PM
Please respond to
"General
development
mailing list of
the Eclipse
project."
-------------------
Discussion Topics
-------------------
UA:
- 2.1 Backward Compatiblity:
- How long are we committed to maintaining it?
--------
Status
--------
Debug:
- merged "flexible debug platform" support back to HEAD for integration
build
- test pass and bug fixing for new support
- experimenting with textual display of runtime classpath on Classpath tab
- continued work to associate launch configs with resources
- bug fixing
JDT UI:
- refactorings:
- worked on update derived elements refactoring (local variables)
- looked at performance issues in move static members
- finished work on empty parent package and non-empty sub-package
deletion features
- working implementation of refactoring-aware update based on team
model support
- various improvements and optimizations of the refactoring history
- Clean Up action:
- wrote performance tests for clean-ups and improve performance
- found more stable solution for clean up actions that interfere with
work on the same region
- new API:
- work in progress: import rewrite as API
- JDT actions to work on non-Java elements: pluggable SelectionProvider
for actions
- JUnit:
- worked on model for JUnit view
- make JDT .java agnostic
- updated jdt.ui code to work with complation units with file name
suffix other than '.java'
- miscellaneous:
- code review of Common Navigator framework and JDT extension
- open type dialog now picks up current selection if it looks like a
type name
- API discussions with JDT/Core
- bug fixing
Platform/JDT Text:
- started to investigate impact of StyledText changes
- bug fixing (including a 3.1.2 fix)
- bug inbox tracking
- military service
JDT Core:
- JavaCore#initializeAfterLoad(IProgressMonitor) used to
schedule a job to do its work. It now does it in the
same thread. Note this is not an API change as the spec
allows both scenarii.
- DOM type bindings for generics got adjusted. There were
situations where a reference to a generic type from within
itself would expose the declared generic type binding,
instead of a parameterized type binding (using its own type
parameters as type arguments). This is now corrected, clients
should ensure they did not rely on the previous inconsistency
(note: no change was required from direct JDT dependents).
- added APIs on JavaCore to leverage support for Java-like
file extensions (from the Java source content-type).
@see JavaCore#getJavaLikeExtensions()
@see JavaCore#isJavaLikeFileName(String)
@see JavaCore#removeJavaLikeExtension(String)
- working on builder integration of compiler participant
(enabling APT as preprocessor, but should also allow
postprocessors)
- working on more robust DOM AST. Tuning recovery to
common cases, but could consider using syntax diagnosis
to drive some recovery action.
- working on null reference analysis. Reached code review
stage. Code to be made available for M4.
- adding compiler support for StackMapTable attribute
(Java SE 6 requirement)
- working on model support for secondary types, tuning
performance
- working on providing additional element info on search
match (e.g. local var decl if any, siblings in multi
var decl if any)
- bug fixing
Platform UI:
- bug fixing:
- problems with themes when using certain 2.0 workspaces in 3.1.X
- preference leak testing
- problems view bugs
- logged performance bugs, some improvements made in performance
- builds:
- Platform UI has a bot machine that runs test builds and is downright
friendly and helpful on IRC it needed some fixing up this week to
support
the new Bugzilla 2.20 etc.
- Commands:
- working on legacy Action persistence parsing
- Common Navigator:
- port the ActionExpression enablement classes to
org.eclipse.core.expressions:
- https://bugs.eclipse.org/bugs/show_bug.cgi?id=115130
- update extension point schema doc for navigatorContent:
- https://bugs.eclipse.org/bugs/show_bug.cgi?id=115123
- flexible workspaces:
- investigation into using more support in wizards etc.
- JFace:
- reviewed data binding API
- logical model support:
- gathering editor opening requirements (see bug 42643)
- worked on editor opening scenarios for Library example
- NL/Accessibility:
- Mac OS/X accessibility and NL investigation
- RCP:
- investigation into adding support for window types (aka personalities)
- investigated whether Equinox refactoring will work for standalone
JFace dependencies on runtime utility classes (looks good)
- tests:
- dynamic test synch problems
- working sets:
- working set patches for other teams
- general:
- working on more flexible trim support in the workbench
- review of Tabbed Properties framework and example from WTP
User Assistance:
- linkability:
- writing a first draft of a proposal for adding general-purpose
linking capability that acts as a broker between link providers and
consumers:
- the draft should be done by the end of this week
- solution guides:
- writing a first draft of a proposal to introduce high level UA tool
(solution guide) that can guides through large tasks:
- the draft should be done by the end of this week
- M4 planning
- work continues on dynamic help content and search enhancements
- a solution for a problem where cheatsheets are blocked by modal dialogs
is near completion (cheat sheets that reuse aux. help window)
- bug fixes
PDE:
- launching:
- support for new startup sequence due to refactored runtime
- provide backward compatibility for pre-runtime-breakup targets
- participation in refactoring:
- manifest files will now be updated correctly when:
- multiple packages/classes are moved in a single operation
- a package and all its subpackages are renamed
- new pretty schema editor nearing completion:
- in addition to being easy on the eyes, the editor will expose
new important features; more details next week
- target management:
- relaxed the criteria to discard plugins/fragments when resolving the
target platform
- this, for example, will allow you to see all platform-specific
fragments on the target platform preference page when the rcp delta
pack is installed
- classpath computation:
- the "is this package coming from the host or the fragment?" problem
has been solved
- the "imported package is split across multiple plug-ins" problem
also solved
- bug fixes
Update:
- verification and installation of bundles can now be done in the
background
- automatic server-side mirror support planned to come online this week
- bug fixes_______________________________________________
eclipse-dev mailing list
eclipse-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/eclipse-dev