Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [platform-ui-dev] Question regarding semantic versioning

> Makes me wonder ... should it be API? 
> Dirk, was your intent to add API? 

As far as I can see, PerspectiveDescriptor is part of the compat layer. Therefore, no it was not my intention to add public API, as the whole class should be internal.

Regarding the exported packages, I also heard that it was due to laziness. But the only tooling I know that would make it easy is BND tools. And since all Eclipse projects are created using PDE, this would be a really huge task to switch. At some points not even possible because bnd doesn't know about features and products, and therefore a simple switch is not even possible for Eclipse projects.

I was thinking about a possible integration of bnd and pde in some way, but currently there are only solutions using Ant in the middle somehow, and that doesn't feel like a clean solution. For example, bnd generates the MANIFEST files with the correct semantic versioning for you. But as it is generated, it doesn't exist in the project. Therefore you can not use the PDE tooling for creating a feature, because at development time there are no bundles PDE can find. Quite complicated topic and gets even more complicated when thinking about automated builds.

On Thu, Jul 23, 2015 at 5:26 AM, David M Williams <david_williams@xxxxxxxxxx> wrote:

> From: Lars Vogel <lars.vogel@xxxxxxxxxxx>

>
> PerspectiveDescriptor is not API (see the x-internal flag in the
> corresponding package, hence no since tag.

Makes me wonder ... should it be API?
Dirk, was your intent to add API?
(That others use? or just internal use?)
If intent was API, is there another package it should be in?
(all asked, from a completely
naive point of view, about that package -- just asking).
 
> On Tue, Jul 21, 2015 at 8:51 AM, Dirk Fauth <dirk.fauth@xxxxxxxxx> wrote:

> > I also noticed that the exported packages doesn't export the version.
> > Regarding to correct OSGi semantic versioning, is this by design or by
> > mistake?

I do not know the history, but have heard some imply it was due to
laziness, more than design or mistake :)
There might have been a reason for it though ... perhaps some old timers
remember the reason?

In general, it seems a good idea, to me -- assuming the tools make it easy?
 


_______________________________________________
platform-ui-dev mailing list
platform-ui-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/platform-ui-dev


Back to the top