From a99d844de5aac4f51be0e2305b4016937b6349f5 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" Date: Mon, 27 Jul 2026 12:28:28 +0000 Subject: [PATCH] docs: auto-generated content --- docs/_instructions/buildpath.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/docs/_instructions/buildpath.md b/docs/_instructions/buildpath.md index 05a1ae20e4..62ef83c27e 100644 --- a/docs/_instructions/buildpath.md +++ b/docs/_instructions/buildpath.md @@ -36,6 +36,17 @@ An example of the `-buildpath` could be the following, where three dependencies osgi.core;version=4.3.1,\ osgi.cmpn;version=4.3.1 +## Eclipse Features + +An entry can reference an Eclipse feature from a [p2 repository](/plugins/p2.html) by adding the `type=org.eclipse.update.feature` attribute. The `type` attribute is required because a feature can share its name and version with a bundle; without it the entry is resolved as a bundle. + + -buildpath: \ + org.eclipse.e4.rcp;version='4.40.0.v20260516-1214';type=org.eclipse.update.feature + +A feature is a container of bundles: on the build path it expands to its member bundles, i.e. the `` references of its `feature.xml` and, recursively, the members of its `` referenced features. `` imports are dependencies, not members, and are not expanded. Members whose `os`/`ws`/`arch` attributes do not match the running platform are skipped. The versions pinned in the feature are resolved exactly; when a pinned version is not present in the repositories, the highest available version is used and a warning is issued. + +Feature entries are supported on all container paths, i.e. also on `-testpath`, `-runpath` and `-runbundles`. + ## See Also * [-testpath] for setting the test path.