Community
Participate
Working Groups
When you have a product that includes a feature that then requires say a plugin Foo, if Foo is already built and in the destination repo, the product export fails saying it cannot install Foo even though Foo is available. I suspect that this has something to do with how PDE build is being invoked. If the destination repo was available to PDE Build when it runs the director to complete the packaging then these requirements would be found. Note that this is what would normally happen if the user ran the director as a separate step after the build so it is a bit odd that it does not work as one well integrated workflow.
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.
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.
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.
