You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 9, 2018. It is now read-only.
The "Export Package Details" pane in the bnd editor allows you to set a version for a package. However, this does not set or change the "packageinfo" file that is in the package, but creates an override (Export-Package: foo;version=2).
First of all, this confuses users, and the graphical editors are supposed to make simple things easy to configure. Overrides are a very special case, so they don't belong in this editor.
Secondly, the override also contains a bug that further complicates matters. I'll explain this with an example:
Create a project with 2 subbundles, one api and one implementation bundle. Add an interface to an api package, go with the default 1.0 packageinfo version, and package it in the api bundle. For the implementation bundle, create an implementation package with a class that implements the interface and go with the defaults. Now, create an override for the api version, make it version 2, and look at the generated manifest for the implementation bundle. You'd expect the import range for the api package to be [2,3) but it is still [1,2).
This issue is about removing the pane from the bnd editor UI, which avoids all of the confusion. I discussed this with @njbartlett and he agrees this is a good first step.
The text was updated successfully, but these errors were encountered:
The "Export Package Details" pane in the bnd editor allows you to set a version for a package. However, this does not set or change the "packageinfo" file that is in the package, but creates an override (Export-Package: foo;version=2).
First of all, this confuses users, and the graphical editors are supposed to make simple things easy to configure. Overrides are a very special case, so they don't belong in this editor.
Secondly, the override also contains a bug that further complicates matters. I'll explain this with an example:
Create a project with 2 subbundles, one api and one implementation bundle. Add an interface to an api package, go with the default 1.0 packageinfo version, and package it in the api bundle. For the implementation bundle, create an implementation package with a class that implements the interface and go with the defaults. Now, create an override for the api version, make it version 2, and look at the generated manifest for the implementation bundle. You'd expect the import range for the api package to be [2,3) but it is still [1,2).
This issue is about removing the pane from the bnd editor UI, which avoids all of the confusion. I discussed this with @njbartlett and he agrees this is a good first step.
The text was updated successfully, but these errors were encountered: