Community
Participate
Working Groups
The publisher currently doesn't parse or generate metadata for the license information in a .product file. Should it? Do products have licenses, or should we just use the licenses of the bundles / features that constitute the project?
Actually, it appears PDE export doesn't do anything with this either (not sure if it should). For example, I just created a product, gave it a GPL license, exported it and rgreped the dir for GPL. nothing. Chris, do you have thoughts on this?
The publisher should take care of this imho. A product can have an all encompassing license.
I agree the publisher should take care of this when generating IUs. Is this license only meant for IUs though?
*** Bug 229880 has been marked as a duplicate of this bug. ***
Much like the license of the feature ends up in the IU, this license text should end up in the product IU. This would be a nice to have functionality.
Created attachment 133033 [details] Adds the license section to the product parser This patch adds the parsing of licenses to the product parser. I still have to put this in the product publishing action.
Created attachment 133204 [details] publisher patch for product license This patch adds the product license support to the publisher. This is done through ILicenseAdvice.
Since the license doesn't actually appear in the running product, it's not needed in the plugin.
Fixed in HEAD.