# Eclipse Platform Build Notes
Core Expressions

### Mai 7, 2004

#### Problem Reports Fixed

#### Implemenation Changes

- The ability to resolve a plug-in descriptor via the resolve expression has been removed from the expression language. This was necessary since IPluginDescriptor is deprecated for 3.0 and the functionality was new in 3.0 anyways.

### March 23, 2004

#### Problem Reports Fixed

#### Implemenation Changes

- removed the constructor public EvaluationContext(IEvaluationContext parent, Object defaultVariable, Object selection). Instead of calling this constructor, the following code has to be written:

           EvaluationContext evalContext= new EvaluationContext(null, cunit);
           evalContext.addVariable("selection", cunit); //$NON-NLS-1$

- removed the two string constants:

           public static final String SYSTEM= "System";  //$NON-NLS-1$
           public static final String SELECTION= "selection";  //$NON-NLS-1$

- added support for custom variable resolver (see new class IVariableResolver). So there is no need to subclass EvaluationContext anymore to add your own resolving strategy.
- added support for an equals expression.

### March 16, 2004

#### Problem Reports Fixed

#### Implemenation Changes

The adapt expression now uses the new IAdapterManager API hasAdapter(Object, String) and getAdapter(Object, String). This ensures that the right class loader is used to convert the string representing a type into a corresponding Class. However, this change now requires that the adapters requested via an adapt expression must be declared in XML using the new org.eclipse.core.runtime.adapters extension point.