This sample project demonstrates some of the features of the OT/Equinox project.
This sample project utilizes Eclipse Object Teams to add some extra features to your Eclipse installation. OT/Equinox will be used to pimp the existing MANIFEST.MF editor - which is part of the Eclipse PDE - in a pragmatic and easy manner.
- Does it distract you to have preset the version / build qualifier of required Plug-In dependencies automatically by Eclipse?
- Do you remove the version / build qualifier of required Plug-ins again and again to gain more flexibility while programming?
The sample project adds a Button labeled "Remove versions" to the "Dependencies" Tab of the MANIFEST.MF editor. It implements several Teams and Roles to achieve its purpose. When clicking the "Remove versions" button the version / build qualifier of all added required Plug-Ins will be removed.
This project was started during the "2. Eclipse Plug-In Fest" (10/13/2012) in Dresden.
Eclipse Public License - v 1.0
- Eclipse Juno >= 4.2
- ObjectTeam / Development Tools >= 2.1.1 (for developers only)
- ObjectTeam / Equinox >= 2.1.0 (for developers and users)
This sample project utilizes Maven Tycho.
mvn package
When running from the project root directory 4 Maven sub modules will be build and the
result will be found in directory net.bluwings.eclipse.pde.ui.repository/target. The
built ZIP archive in there contains a valid Eclipse p2 Repository that can be used to
install software.
From within your Eclipse Development Environment you simply start the included launch
configuration OT-Equinox Sample.launch. Of course you have to clone the Git repository
and import the provided Eclipse plug-in projects in preparation.
From within your Eclipse Runtime Environment you have to install the built software. To
do so add a new Software Site (Help -> Install New Software... -> Add...) and choose
the built p2 Repository archive (see section Building). After installing the software
you have to restart Eclipse.