Re: [babel-dev] Re: Build process, p2 metadata

[Kit Lo <kitlo@xxxxxxxxxx>]

Sean,

Thanks for the info. Do you have more
information about branding? How do we define that for Babel features and
plugins?

>Do you mean these fragments had
no hosts(?), or do you mean that the 
fragments didn't belong to any features?

To answer your question, I meant the
fragments didn't belong to any features.

Kit Lo
IBM Eclipse SDK Globalization Technical Lead
Eclipse Babel Project Co-lead

Sean Flanigan <sflaniga@xxxxxxxxxx>
Sent by: babel-dev-bounces@xxxxxxxxxxx

06/01/2009 08:02 PM

Please respond to
Babel committers mailing list <babel-dev@xxxxxxxxxxx>

To	Babel committers mailing list <babel-dev@xxxxxxxxxxx>
cc
Subject	Re: [babel-dev] Re: Build process, p2 metadata

On 06/02/2009 01:04 AM, Kit Lo wrote:
>  >Sean, if we don't include the features, do you know if we
will have
> any problems un-installing or disabling the languages packs in Eclipse.
> (A user who does not use the language packs may want to do that.)
>  >
>  >I'm going to test that.

I haven't tried in months, I'm afraid.  I'm sufficiently cynical about
p2 by now that I wouldn't count on it to do the right thing in this 
case.  These days, I'm just happy if it will let me manage dropins
externally.

> While testing the effect of not including the features in our language
> packs, I noticed that our features may have some problems. I unzipped
> the Babel language pack for the Eclipse project
> (BabelLanguagePack-eclipse-en_AA_3.5.0.v20090524043402.zip) into
> "eclipse-jee-galileo-RC1-win32.zip" and "eclipse-SDK-3.5RC1-win32.zip".
> Somehow, Eclipse does not list our Babel language pack features as
> installed features.

This might be due to a lack of branding plugins for the langpack 
features.  All 942 of them.  Without branding plugins, the features
don't show up everywhere you might expect.

Based on my experiences with 3.4, I think you'll find that the features
are listed in Eclipse's .log, even though they don't show up in the 
About windows.  I think the requirement for branding was introduced
in 
3.4/3.5 along with p2.

If the features don't show up in the UI, I suppose it would be pretty 
difficult to remove them through the UI, although updating might be 
possible if you go through the update site and just install the latest
version on top.

Perhaps we could define one super-feature for each language, which 
optionally includes all the other features, and just brand the 
super-feature?  Maybe we could even remove the other features from
the 
visible list in the update site, to cut down on the clutter.

 > The plug-in fragments were loaded though, as orphan
 > plug-ins with no parents.

Do you mean these fragments had no hosts(?), or do you mean that the 
fragments didn't belong to any features?

> That could be the reason why the p2 metadata generated by Gabe did
not
> include any features (that's just a guess).

I must have missed that.  Can you point me to an email or a bug?

Regards

Sean.

-- 
Sean Flanigan

Senior Software Engineer
Engineering - Internationalisation
Red Hat
_______________________________________________
babel-dev mailing list
babel-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/babel-dev