-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for Eclipse-BundleShape in Manifest-Editor #864
Comments
Instead of a checkbox it would be better to have a drop down (or Radiobuttons) with
see for why one would explicitly configure the "default", also I'm not sure if it is really "Unpack this plug-in during installation" if one just installs it into OSGi (@tjwatson ?) I think this is only performed by P2. |
Isn't the default value simply not specifying the header at all? The framework pays no attention to this header, so it must be p2 that does anything with it. |
That's what I mean, therefor I find "Unpack this plug-in during installation" a bit misleading, and maybe not suitable for the main Manifest tab at all... |
Hi, |
Three modes are supported: jar, dir and default. First two are self-explanatory, third option removes the header which is the default behaviour. Fixes: eclipse-pde#864
Three modes are supported: jar, dir and default. First two are self-explanatory, third option removes the header which is the default behaviour. Fixes: eclipse-pde#864
Three modes are supported: jar, dir and default. First two are self-explanatory, third option removes the header which is the default behaviour. Fixes: eclipse-pde#864
Three modes are supported: jar, dir and default. First two are self-explanatory, third option removes the header which is the default behaviour. Fixes: eclipse-pde#864
Three modes are supported: jar, dir and default. First two are self-explanatory, third option removes the header which is the default behaviour. Fixes: eclipse-pde#864
Three modes are supported: jar, dir and default. First two are self-explanatory, third option removes the header which is the default behaviour. Co-authored-by: Hannes Wellmann <[email protected]> Fixes: eclipse-pde#864
Three modes are supported: jar, dir and default. First two are self-explanatory, third option removes the header which is the default behaviour. Co-authored-by: Hannes Wellmann <[email protected]> Fixes: eclipse-pde#864
Three modes are supported: jar, dir and default. First two are self-explanatory, third option removes the header which is the default behaviour. Co-authored-by: Hannes Wellmann <[email protected]> Fixes: eclipse-pde#864
Three modes are supported: jar, dir and default. First two are self-explanatory, third option removes the header which is the default behaviour. Co-authored-by: Hannes Wellmann <[email protected]> Fixes: eclipse-pde#864
Three modes are supported: jar, dir and default. First two are self-explanatory, third option removes the header which is the default behavior. Fixes: eclipse-pde#864 Co-authored-by: Hannes Wellmann <[email protected]>
Three modes are supported: jar, dir and default. First two are self-explanatory, third option removes the header which is the default behavior. Fixes: #864 Co-authored-by: Hannes Wellmann <[email protected]>
The PDE Manifest-Editor should support the
Eclipse-BundleShape
header similiar to how it for example supportsBundle-ActivationPolicy
.In the Overview page there should be a check-box labeled with
Unpack this plug-in during installation
or similar.And when it is checked the
Eclipse-BundleShape; dir
should be added. Unchecking it can simplify remove the header, sincejar
is the default.The check-box should have a tool-tip indicating that this option is usually not required, only if the code relys on that embedded resources are available as files directly.
This is a follow-up on #730.
The text was updated successfully, but these errors were encountered: