Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Plugin Development Environment (PDE) » P2 and source feature
P2 and source feature [message #29457] Mon, 27 October 2008 08:20 Go to next message
Markus Barchfeld is currently offline Markus BarchfeldFriend
Messages: 27
Registered: July 2009
Junior Member
Hello,

A source features which has been generated via generate.feature has the
same label as the containing feature. With the old update-site mechanism
this did not come to my attention since the old (3.3.) update manager does
not show the source feature. It is automatically installed with its
containing feature but it does not show up in the list of installable
features.

Now, with Eclipse 3.4, when I generate the p2 repository with the PDE
build and then update via this repository, the update manager also shows
included features which includes the source feature. This is quite
confusing because the source feature can not be discriminated from its
containing feature. Both have the same label and version.

How could this situation be handled? Is there a way to modify the label of
the source feature? Or could the p2 generation be modified so that the
update manager does not display included features? So far I have used the
following properties: generate.p2.metadata, p2.metadata.repo,
p2.artifact.repo, p2.metadata.repo.name,p2.artifact.repo.name, p2.flavor,
p2.publish.artifacts

Thanks
Markus
Re: P2 and source feature [message #29607 is a reply to message #29457] Tue, 28 October 2008 15:23 Go to previous messageGo to next message
Andrew Niefer is currently offline Andrew NieferFriend
Messages: 990
Registered: July 2009
Senior Member
Markus,
You need to get the source feature generated with a different label.
The way to do this is for your normal feature to have its label
externalized: <feature id="foo" label="%label" >
The feature must include a "feature.properties" file that would have
"label=My Feature Label".

Then, you can contribute a different feature.properties (label=My
Source) to the generated source feature. Do this by having a directory
"sourceTemplateFeature" in the normal feature, the contents of this
directory will be copied into the generated source feature.

org.foo.feature/sourceTemplateFeature/feature.properties
/feature.xml
/feature.properties

-Andrew

Markus Barchfeld wrote:
> Hello,
>
> A source features which has been generated via generate.feature has the
> same label as the containing feature. With the old update-site mechanism
> this did not come to my attention since the old (3.3.) update manager
> does not show the source feature. It is automatically installed with its
> containing feature but it does not show up in the list of installable
> features.
>
> Now, with Eclipse 3.4, when I generate the p2 repository with the PDE
> build and then update via this repository, the update manager also shows
> included features which includes the source feature. This is quite
> confusing because the source feature can not be discriminated from its
> containing feature. Both have the same label and version.
>
> How could this situation be handled? Is there a way to modify the label
> of the source feature? Or could the p2 generation be modified so that
> the update manager does not display included features? So far I have
> used the following properties: generate.p2.metadata, p2.metadata.repo,
> p2.artifact.repo, p2.metadata.repo.name,p2.artifact.repo.name,
> p2.flavor, p2.publish.artifacts
>
> Thanks
> Markus
>
Re: P2 and source feature [message #30169 is a reply to message #29607] Wed, 29 October 2008 19:18 Go to previous message
Markus Barchfeld is currently offline Markus BarchfeldFriend
Messages: 27
Registered: July 2009
Junior Member
Andrew, thanks for the detailed answer. It is exactly what I needed. There
was not much left for me to do wrong, but I found it: Make sure that
org.foo.feature/feature.properties is part of bin.includes in
build.properties

> Markus,
> You need to get the source feature generated with a different label.
> The way to do this is for your normal feature to have its label
> externalized: <feature id="foo" label="%label" >
> The feature must include a "feature.properties" file that would have
> "label=My Feature Label".

> Then, you can contribute a different feature.properties (label=My
> Source) to the generated source feature. Do this by having a directory
> "sourceTemplateFeature" in the normal feature, the contents of this
> directory will be copied into the generated source feature.

> org.foo.feature/sourceTemplateFeature/feature.properties
> /feature.xml
> /feature.properties

> -Andrew

> Markus Barchfeld wrote:
>> Hello,
>>
>> A source features which has been generated via generate.feature has the
>> same label as the containing feature. With the old update-site mechanism
>> this did not come to my attention since the old (3.3.) update manager
>> does not show the source feature. It is automatically installed with its
>> containing feature but it does not show up in the list of installable
>> features.
>>
>> Now, with Eclipse 3.4, when I generate the p2 repository with the PDE
>> build and then update via this repository, the update manager also shows
>> included features which includes the source feature. This is quite
>> confusing because the source feature can not be discriminated from its
>> containing feature. Both have the same label and version.
>>
>> How could this situation be handled? Is there a way to modify the label
>> of the source feature? Or could the p2 generation be modified so that
>> the update manager does not display included features? So far I have
>> used the following properties: generate.p2.metadata, p2.metadata.repo,
>> p2.artifact.repo, p2.metadata.repo.name,p2.artifact.repo.name,
>> p2.flavor, p2.publish.artifacts
>>
>> Thanks
>> Markus
>>
Re: P2 and source feature [message #583735 is a reply to message #29457] Tue, 28 October 2008 15:23 Go to previous message
Andrew Niefer is currently offline Andrew NieferFriend
Messages: 990
Registered: July 2009
Senior Member
Markus,
You need to get the source feature generated with a different label.
The way to do this is for your normal feature to have its label
externalized: <feature id="foo" label="%label" >
The feature must include a "feature.properties" file that would have
"label=My Feature Label".

Then, you can contribute a different feature.properties (label=My
Source) to the generated source feature. Do this by having a directory
"sourceTemplateFeature" in the normal feature, the contents of this
directory will be copied into the generated source feature.

org.foo.feature/sourceTemplateFeature/feature.properties
/feature.xml
/feature.properties

-Andrew

Markus Barchfeld wrote:
> Hello,
>
> A source features which has been generated via generate.feature has the
> same label as the containing feature. With the old update-site mechanism
> this did not come to my attention since the old (3.3.) update manager
> does not show the source feature. It is automatically installed with its
> containing feature but it does not show up in the list of installable
> features.
>
> Now, with Eclipse 3.4, when I generate the p2 repository with the PDE
> build and then update via this repository, the update manager also shows
> included features which includes the source feature. This is quite
> confusing because the source feature can not be discriminated from its
> containing feature. Both have the same label and version.
>
> How could this situation be handled? Is there a way to modify the label
> of the source feature? Or could the p2 generation be modified so that
> the update manager does not display included features? So far I have
> used the following properties: generate.p2.metadata, p2.metadata.repo,
> p2.artifact.repo, p2.metadata.repo.name,p2.artifact.repo.name,
> p2.flavor, p2.publish.artifacts
>
> Thanks
> Markus
>
Re: P2 and source feature [message #583823 is a reply to message #29607] Wed, 29 October 2008 19:18 Go to previous message
Markus Barchfeld is currently offline Markus BarchfeldFriend
Messages: 27
Registered: July 2009
Junior Member
Andrew, thanks for the detailed answer. It is exactly what I needed. There
was not much left for me to do wrong, but I found it: Make sure that
org.foo.feature/feature.properties is part of bin.includes in
build.properties

> Markus,
> You need to get the source feature generated with a different label.
> The way to do this is for your normal feature to have its label
> externalized: <feature id="foo" label="%label" >
> The feature must include a "feature.properties" file that would have
> "label=My Feature Label".

> Then, you can contribute a different feature.properties (label=My
> Source) to the generated source feature. Do this by having a directory
> "sourceTemplateFeature" in the normal feature, the contents of this
> directory will be copied into the generated source feature.

> org.foo.feature/sourceTemplateFeature/feature.properties
> /feature.xml
> /feature.properties

> -Andrew

> Markus Barchfeld wrote:
>> Hello,
>>
>> A source features which has been generated via generate.feature has the
>> same label as the containing feature. With the old update-site mechanism
>> this did not come to my attention since the old (3.3.) update manager
>> does not show the source feature. It is automatically installed with its
>> containing feature but it does not show up in the list of installable
>> features.
>>
>> Now, with Eclipse 3.4, when I generate the p2 repository with the PDE
>> build and then update via this repository, the update manager also shows
>> included features which includes the source feature. This is quite
>> confusing because the source feature can not be discriminated from its
>> containing feature. Both have the same label and version.
>>
>> How could this situation be handled? Is there a way to modify the label
>> of the source feature? Or could the p2 generation be modified so that
>> the update manager does not display included features? So far I have
>> used the following properties: generate.p2.metadata, p2.metadata.repo,
>> p2.artifact.repo, p2.metadata.repo.name,p2.artifact.repo.name,
>> p2.flavor, p2.publish.artifacts
>>
>> Thanks
>> Markus
>>
Previous Topic:Why would pde build fail to jar sign 1 out of 6 plug-ins
Next Topic:Installed plugin application is unable to display icons and images
Goto Forum:
  


Current Time: Sat Apr 20 00:37:19 GMT 2024

Powered by FUDForum. Page generated in 0.03279 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top