Follow Techotopia on Twitter

On-line Guides
All Guides
eBook Store
iOS / Android
Linux for Beginners
Office Productivity
Linux Installation
Linux Security
Linux Utilities
Linux Virtualization
Linux Kernel
System/Network Admin
Programming
Scripting Languages
Development Tools
Web Development
GUI Toolkits/Desktop
Databases
Mail Systems
openSolaris
Eclipse Documentation
Techotopia.com
Virtuatopia.com

How To Guides
Virtualization
General System Admin
Linux Security
Linux Filesystems
Web Servers
Graphics & Desktop
PC Hardware
Windows
Problem Solutions
Privacy Policy

  




 

 

Eclipse Platform Plug-in Development Environment Guide
Previous Page Home Next Page

Plug-in Compiler Preferences

Syntactic errors in plugin.xml, fragment.xml and MANIFEST.MF are all flagged as errors by the plug-in manifest compiler. As for semantic problems in the plug-in manifests, the severity for each problem category can be set to Error, Warning or Ignore.

Workspace vs. Project Settings

The plug-in compiler preferences are set at a workspace level on the Open the compilers preference page Window > Preferences... > Plug-in Development > Compilers preference page and take effect on all plug-in projects in the workspace.

It is also possible to override the workspace-scope settings by having compiler settings at the plug-in project level. To do so, select Properties from the context menu of a plug-in project. In the Properties dialog, project-level manifest compiler settings can be customized on the Plug-in Development > Plug-in Manifest Compiler preference page.

Semantic Problems

PDE validates plugin.xml, fragment.xml, MANIFEST.MF and build.properties files to flag a variety of potential problems that may prevent the plug-in from running properly.

Note that some problems such as a missing plug-in ID, plug-in version, or plug-in name render a plug-in invalid. Therefore, these problems are flagged with a non-negotiable error marker and are not available for configuration on this preference page.

Plug-in Compiler Options

The following is a brief explanation for some of the non-obvious potential problems that are flagged by PDE:

  • Unresolved Dependencies:
    An unresolved dependency is a dependency on a plug-in (in the Require-Bundle MANIFEST.MF header) or on a package (in the Import-Package MANIFEST.MF header) where the plug-in or package in question does not exist.
  • Incompatible Environment:
    A plug-in or fragment has an incompatible environment if it has an Eclipse-PlatformFilter MANIFEST.MF header whose value is not compatible with the current Target Environment settings as they appear on the Plug-in Development > Target Platform > Environment preference page.
  • Unresolved Extension Points:
    An unresolved extension point is an extension point that does not exist or whose contributing plug-in is unchecked on the Plug-in Development > Target Platform preference page. Extensions contributing to such an extension point are flagged.

 
 
  Published under the terms of the Eclipse Public License Version 1.0 ("EPL") Design by Interspire