Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 293111 - Warn when product id conflicts with a bundle
Summary: Warn when product id conflicts with a bundle
Status: RESOLVED WORKSFORME
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.5   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-22 17:07 EDT by Michael Yara CLA
Modified: 2019-09-02 15:10 EDT (History)
1 user (show)

See Also:


Attachments
Workspace that demonstrates the issue. (20.67 MB, application/x-gzip)
2009-10-22 17:12 EDT, Michael Yara CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Yara CLA 2009-10-22 17:07:29 EDT
User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.14) Gecko/2009090217 Ubuntu/9.04 (jaunty) Firefox/3.0.14
Build Identifier: 20090920-1017

When exporting a RCP app based on features via PDE with repository export the contents of the export folder are incomplete. On some occasions it will build properly but not all the time. No errors are thrown during the build process. This will build properly if "Generate metadata repository" is deselected. The following shows the ls command on the failed exported folder. 

michaely@lappy:~/Desktop/eclipsetest$ ls
artifacts.xml  p2  plugins

I have attached my test workspace. 

When I try to export my actual application this error occurs


 Cannot complete the install because one or more required items could not be found.
   Software being installed: MYApp 2.1.14.1666 (myapp 2.1.14.1666)
   Missing requirement: MYApp 2.1.14.1666 (myapp 2.1.14.1666) requires 'MYAppFeature.feature.group [2.1.14.1666]' but it could not be found

This is what led me to perform a test on an export of the RCPMailApp template which is what is contained in my attached workspace and in the reproduction steps. Even though my actual application does not behave in a similar fashion as the mailTemplate export I believe the issue is related since I can get my actual RCP app to export properly with no error when "Generate metadata repository" is deselected.

Best Regards,
Mike


Reproducible: Always

Steps to Reproduce:
1.Fresh eclipse install with fresh workspace
2.Create a RCP plugin via the mailTemplate
3.Create feature containing the mailTemplate plugin.
4.Create a product configuration based on features with the rcp and mailTemplate features included.
5.Export with "Generate metadata repository" selected.

Note: This will work on occasion.
Comment 1 Michael Yara CLA 2009-10-22 17:12:27 EDT
Created attachment 150312 [details]
Workspace that demonstrates the issue.
Comment 2 Andrew Niefer CLA 2010-02-18 17:04:44 EST
This is caused by having a product-id that is the same as a bundle that is also included in the export.

We should give an error or warning or something in the product editor.
Comment 3 Andrew Niefer CLA 2010-02-18 18:08:16 EST
Conflicting with features can also be bad, see bug 285514
Comment 4 Eclipse Genie CLA 2019-02-13 02:24:26 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 5 Lars Vogel CLA 2019-09-02 15:01:43 EDT
This bug was marked as stalebug a while ago. Marking as worksforme.

If this report is still relevant for the current release, please reopen and remove the stalebug whiteboard tag.
Comment 6 Lars Vogel CLA 2019-09-02 15:10:04 EDT
This bug has been marked as stalebug a while ago without any further interaction.

If this report is still relevant for the current release, please reopen and remove the stalebug whiteboard flag.