View and category names should be extermanized for translation

[merks]

These should be externalized

Is it really a good idea to create a new separate category for these rather than using PDE's existing category? In my opinion, it makes them harder to find.

[merks]

@chrisrueger

Could you please have a look.

@laeubi

Personally I think it would be better to keep all the PDE views in the Plug-in Development category...

[chrisrueger]

@merks sure I can have a look. I just adopted it from Bundle Repositories which was migrated first by @laeubi

I personally like the idea of having an "OSGi" Category since we plan to migrate more stuff over from Bndtools and in the end it is about OSGi - but I will change it to whatever you tell me :)

[merks]

In the end, it's just an opinion, not something that's objectively right or wrong. So best we seek more opinions.

@HannesWell do you have an opinion?

[laeubi]

Personally I think it would be better to keep all the PDE views in the Plug-in Development category...

Plug-in is a pure PDE/Eclipse term and of course you can develop not only Eclipse Plugins here. OSGi category is meant to be used for views that are not tied to a certain tooling (e.g PDE or Bndtools) as for example also m2e could leverage these views (see for example here) and maven has nothing to do with Plugin-Devlopment in general so it would be rather odd to have suddenly the need to install PDE just to get a category name when m2e just shows some extra information derived from bnd-lib...

[chrisrueger]

@merks almost done, but cannot get the externalize to work. Can you point me what I am missing?

• I have created a plugins.properties with variables and reference them in plugin.xml

• and also have added plugins.properties to build.properties

• but I see the placeholders

[merks]

The magical header is needed.

Bundle-Localization: plugin

[laeubi]

The magical header is needed.

Unless one would use the default what is OSGI-INF/l10n/bundle

[merks]

Thanks for the quick action!! 🥇

[HannesWell]

Personally I think it would be better to keep all the PDE views in the Plug-in Development category...

Plug-in is a pure PDE/Eclipse term and of course you can develop not only Eclipse Plugins here. OSGi category is meant to be used for views that are not tied to a certain tooling (e.g PDE or Bndtools) as for example also m2e could leverage these views (see for example here) and maven has nothing to do with Plugin-Devlopment in general so it would be rather odd to have suddenly the need to install PDE just to get a category name when m2e just shows some extra information derived from bnd-lib...

On one hand I agree that a more general OSGi category is reasonable, on the other hand it would be good to make it obvious that this also usable for PDE Plugin projects (which are a specific kind of OSGi bundles). Maybe the label of the existing PDE category should be adjusted to mention OSGi too). Otherwise some users might be confused if the general OSGi views can also be used for their (specific) Eclipse Plugins.