Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 327705 - [publisher] FeaturesAction does not generate links
Summary: [publisher] FeaturesAction does not generate links
Status: CLOSED WONTFIX
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: p2 (show other bugs)
Version: 3.6.1   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: P2 Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks: 331974
  Show dependency tree
 
Reported: 2010-10-13 14:51 EDT by Jeff McAffer CLA
Modified: 2019-09-04 16:44 EDT (History)
5 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jeff McAffer CLA 2010-10-13 14:51:12 EDT
If you have a feature whose build.properties sets a root.*.link, (or a perm for that matter), metadata is not published unless there are also root files for the same configuration.  For example, the following works

root.macosx.cocoa.x86_64=file:pom.xml
root.macosx.cocoa.x86_64.link=Eclipse.app/Contents/MacOS/eclipse,eclipse

whereas the following does NOT
root.macosx.cocoa.x86_64.link=Eclipse.app/Contents/MacOS/eclipse,eclipse

FeaturesAction#generateRootFileIUs line 451 (in 3.6.1) has the following conditional around all the IU creation code

			FileSetDescriptor descriptor = advice.getDescriptor(config);
			if (descriptor != null && descriptor.size() > 0) {

It appears that links and perms are not taken into account.
Comment 1 Tobias Oberlies CLA 2011-12-02 07:28:24 EST
Is this supposed to work? The question behind this is also: Should it be allowed to link to files that don't exist?

So in your example, where does the Eclipse.app/Contents/MacOS/eclipse file come from?
Comment 2 Eclipse Genie CLA 2019-09-04 16:44:50 EDT
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.