|
| Re: No component named xxx.yyy.zzz:eclipse.feature is known [message #500316 is a reply to message #500284] |
Wed, 25 November 2009 16:07   |
|
Hi Toby,
On 2009-11-25 16:07, TW wrote:
> Hi,
>
> I´m getting the error I used as the title of my thread if I try to
> export a p2 site using the buckminster action.
>
> I thought, that exporting p2 sites should be quite easy using buckminster.
>
> I have an existing project.
> This project has a main feature which is named de.wagner.product
>
> It includes 5 different product files, because i need to have products
> which connect to different databases.
>
> The de.wagner.product includes the org.eclipse.rcp feature and all the
> other plugins I need for my application.
>
> According to some tutorials on the web I just have to add a new feature,
> lets say I add a feature called de.wagner.product.site
> This feature includes the de.wagner.product feature.
>
> Now I should be able to export the p2 site by right clicking my new
> de.wagner.product.site feature "Buckminster -> invoke action". Then I
> choose p2.site and add a target.properties which has the standard entries.
>
> When I try to create the p2.site The log says: No component named
> de.wagner.product:eclipse.feature is known to Buckminster
>
> I also noticed, that when I click on "buckminster -> invoke actions" the
> list of available actions is much smaller than on some other projects I
> have.
>
> For example the actions :
> -source.feature.jars
> -site.repacked
> -feature.jars
> ..
> are missing.
>
It sounds like the meta-data is only partially extracted. Does the feature have all the required fields filled in (id,
version in particular)? Is the feature id different from the actual project name?
- thomas
|
|
|
| Re: No component named xxx.yyy.zzz:eclipse.feature is known [message #500430 is a reply to message #500316] |
Thu, 26 November 2009 07:14 |
 TW 
Messages: 62
Registered: November 2009 |
Member |
|
|
Hi,
yes my feature does have an ID which is de.wagner.product. It also has a Version, a Name, a Provider and a Branding Plug-in.
The file names of the five different products are different .
They include different features, but all have the same Version, ID, and Name (in the product configuration editor)
If I temporary move all products except one to a tmp folder outside the project, the site.p2 buckminster action works. So I think this has something to do with more than one product.
Is it not possible to create a p2.site when having more than one product, or are the names versions and ids the problems in this case?
[Updated on: Thu, 26 November 2009 10:20] Report message to a moderator |
|
|
| Re: No component named xxx.yyy.zzz:eclipse.feature is known [message #500483 is a reply to message #500430] |
Thu, 26 November 2009 10:22 |
|
On 2009-11-26 08:14, TW wrote:
> Hi,
>
> yes my feature does have an ID which is de.wagner.product. It also has a
> Version, a Name, a Provider and a Branding Plug-in.
>
> The file names of the five different products have a different name. But
> in the feature.xml the ID,Version and Name is the same. They are
> different because each product includes a unique connection feature
> which has informations about the database.
>
> How can I check if I have correct meta data?
Right-click on the project and choose "Buckminster" -> "View Cspec". That will tell show you what meta-data Buckminster
was able to extract.
- thomas
|
|
|
|
| Re: No component named xxx.yyy.zzz:eclipse.feature is known [message #500494 is a reply to message #500487] |
Thu, 26 November 2009 12:01 |
|
On 2009-11-26 11:51, TW wrote:
> Hi Thomas,
>
> I compared the metadata of my de.wagner.product.site feature. The
> matadata is exactly the same if I have one product in my
> de.wagner.product feature or five products.
>
> So I checked the metadata of the de.wagner.product feature. When I have
> five products in my feature I cant even access the buckminster metadata.
> When I have only one product in my feature I can access the metadata.
>
> So I think the five produts in the feature mess up the metadata.
>
> Do I have to create a feature for each product or is there a way to keep
> my architecture with five products in one feature or do I have to
> redesign everything?
>
Multiple products in one feature should work. Can you please create a bugzilla and attach a sample feature that
reproduces the problem?
Thanks,
- thomas
|
|
|
|
| Re: No component named xxx.yyy.zzz:eclipse.feature is known [message #500533 is a reply to message #500498] |
Thu, 26 November 2009 14:35 |
|
On 2009-11-26 13:38, TW wrote:
> Hi Thomas,
>
> I have inspected this problem more detailed and found out 2 major things
> that lead to this error. I think this is not a bug, maybe my products
> are not defined well enought.
>
> First of all, more usefull information about my producs.
>
> The 5 products are:
> WAGNER.product (Main Product)
> WAGNER.dai.dev.product (Product with dai.dev config)
> WAGNER.dai.prod.product (Product with dai.prod config)
> WAGNER.twt.dev.product (Product with twt.dev config)
> WAGNER.twt.prod.product (Product with twt.prod config)
>
> All of them have ID= WAGNER
> NAME = WAGNER
>
> 1. Rroblem: The IDs of the products matches
>
> Attribute WAGNER is defined more then once in component de.wagner.product
>
> This error should be fixable by changing each products ID to a unique one.
>
Yes, that's an absolute must.
> 2. Problem: Same Dependencies
>
> As I mentioned before, each product includes a dependency to a feature
> de.wagner.configuration.<productname>
>
> But the main feature (WAGNER.product) and the WAGNER.twt.dev.product
> feature connect to the same database and because of this they include a
> dependency to the same feature "de.wagner.configuration.twt.dev"
>
> Dependency de.wagner.configuration.twt.dev is defined more than once in
> component de.wagner.product
>
> So 1. could be fixed easily but I don´t know how to fix 2. without
> adding a separate feature or deleting one of the two products.
>
> So is this a bug or just some specific issue with my project?
>
This sounds like a bug. The fact that several products have the same dependency shouldn't be problem.
- thomas
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04060 seconds
] 
Search
Help
Register
Login
Home
