Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 274654 - a capabiltiies 'license' is missing
Summary: a capabiltiies 'license' is missing
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Buckminster (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: buckminster.core-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 274695
Blocks:
  Show dependency tree
 
Reported: 2009-05-01 11:34 EDT by David Williams CLA
Modified: 2019-02-25 14:40 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Williams CLA 2009-05-01 11:34:12 EDT
I assume this is the "generated" capabilities feature? 

To reproduce, install software and pick "Galileo Capabilities" (in 'Goodies' category). After 'next', there's two features listed. One of them has a normal name and license displayed. 

The other, is named "org.eclipse.galileo.feature.jar" (should probably have a real name there, not just the id) but the bigger problem is that the license page just says "license" (instead of actually containing a license). 

I assume this belongs to 'builder' code?
Comment 1 Thomas Hallgren CLA 2009-05-01 11:36:34 EDT
A rough guess would be that the org.eclipse.galileo feaure doesn't include the license in a binary build. I'll check...
Comment 2 Thomas Hallgren CLA 2009-05-01 11:40:05 EDT
Nope, the feature is correct. Then something must be wrong with the way it's published. I'll investigate.
Comment 3 Thomas Hallgren CLA 2009-05-01 12:56:25 EDT
The problem is that the "org.eclipse.galieo.feature.jar" should not be listed at all. That must be a P2 bug since that IU doesn't represent a feature at all. It's just P2 specific container representing the actual jar file of the feature.

I'll bring this up with the P2 team. It's not something that I can fix in the builder. The problem is most likely in the new publisher since Buckminster features seems to suffer from the same problem.
Comment 4 Thomas Hallgren CLA 2009-06-04 12:03:06 EDT
Closing this as fixed since the problem was addressed and fixed in P2.