Community
Participate
Working Groups
User-Agent: Opera/9.80 (Windows NT 5.1; U; de) Presto/2.2.15 Version/10.10 Build Identifier: 20090920-1017 If you have more than one product and these products have a dependency to the same feature, the site.p2 action fails. If all products have a dependency to the feature in which they are saved this is not a problem. But if they share a same dependency to another feature with the same feature id and version, the site.p2 actions fails. Reproducible: Always Steps to Reproduce: 1. Create a new Plugin-Project with the Mail Template RCP Application 2. Create a new Feature and add the Mail Template Plugin to the Feature 3. Add the "org.eclipse.rcp" feature to included features 4. Create a new product configuration, select "use an existing product" and select your plugin from the combobox. 5. Change the product to be based on features and add a dependency to the feature where the products are located (Product should no launch application - you maybe have to synchronize). 6. Create another product configuration, select "use an existing product" and select your plugin from the combobox. 7. Change the product to be based on features and add a dependency to the feature where the products are located (Product should no launch application - you maybe have to synchronize). 8. Ensure that the products have different ID's 9. Create a new feature, which represents the p2 site. and add your product feature to included features -> You should now be able to right click on the p2 site feature and use the site.p2 action successfully. 10. Create a new feature 11. Go to your .product files and add a dependency to this new feature for both products -> Save and restart Eclipse to ensure that everything is refreshed 12. Try to invoke action on you p2 site feature again and select the site.p2 action -> Now it fails
I have a similar problem as described in the thread: http://www.eclipse.org/forums/index.php?t=msg&th=157645&start=0&S=24ad5e375031bdf02a726789e214a9b7 It's the fourth post with the questions Q1 and Q2. In my case the problem already happens during import/resolve. /John
