This is best illustrated with an example: If the plugin code itself is not enclosed in a nested JAR, expansion will result in a directory structure containing class files. This situation is often referred to as "nested JARs". In rare cases it may be necessary to symlink to something inside a JAR. Eclipse features also work nicely with rpmstubby (see below), but not all plugins have features. We generally try to make binary RPMs mirror upstream features. They are preferred, but not required since they provide nice demarcation lines for binary RPMs. For IDE features, the most common requirement will be eclipse-platform.Įclipse features are groups of plugins. Until rpmstubby (see below) is released and/or more widespread, Requires on bits provided by the Eclipse SDK (RCP, SWT, Platform, JDT, PDE, CVS, etc.) should only be on the binary package providing the required functionality (ex. linux.$/eclipse/dropins/plugin-b \īuild/rpmBuild/_feature.zip Fragment: A bundle with native elements ex.Colloquially, among non-Eclipse developers, the term is used to refer to a set of functional Eclipse plugins ex. ![]() ![]() Post-Eclipse 3.0, the term "plugin" can almost always be interchanged with the term "bundle". Plugin: A functional unit of Eclipse functionality.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |