As a modular end user application, Eclipse has always been able to update itself and install new content. Under the covers, Eclipse has always consisted of a number of plug-ins as well as a number of features (a way of aggregating plug-ins). The original update mechanism, the classic update manager, provided a simple way to install and update features and plug-ins (bundles). In Eclipse 3.4, a mechanism called P2 was created that allowed more powerful update mechanisms and included the ability to update native code and configuration files. P2 provides a means to provision, run, update, and configure Eclipse-based applications.