| Summary: | [publisher] FeaturesAction does not generate links | ||
|---|---|---|---|
| Product: | [Eclipse Project] Equinox | Reporter: | Jeff McAffer <jeffmcaffer> |
| Component: | p2 | Assignee: | P2 Inbox <equinox.p2-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | aniefer, irbull, oliver.oo.schaefer, pwebster, t-oberlies |
| Version: | 3.6.1 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Mac OS X - Carbon (unsup.) | ||
| Whiteboard: | stalebug | ||
| Bug Depends on: | |||
| Bug Blocks: | 331974 | ||
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? 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. |
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.