Adopting 4.2 mechanisms and APIs

This section describes changes that are required if you are trying to change your 3.7 plug-in to adopt the 4.2 mechanisms and APIs.

  1. New member flag IContainer#DO_NOT_CHECK_EXISTENCE
  2. Large icons in product branding

1. New member flag IContainer#DO_NOT_CHECK_EXISTENCE

The new flag may be used in:

  • IResource#accept(IResourceProxyVisitor, int)
  • IResource#accept(IResourceVisitor, int, int)

to indicate whether the resource should be checked for existence. If the flag is not specified (recommended) and the resource does not exist, CoreException will be thrown. Children of the resource are never checked for existence.

2. Large icons in product branding

The Eclipse executable on Windows now includes a larger 256x256 icon image. If you are using a PDE product build or the p2 publisher to apply branding for your own product, you will now need to include a 256x256 image in the .ico file you specify for your product or build. Note that the p2 branding tool does not support compressed PNG images, so currently all of your branding images must be uncompressed bitmaps.