Hi Dinusha,

AFAIR in the feature manager it will check the license (feature.properties)
for each feature and display it. In the above scenario, I mentioned when
developing the features in a repo. IMO the carbon-p2-plugin should merge
multiple licenses mentioned for a feature into a single one.

Regards,
Nira

On Wed, Nov 18, 2015 at 3:43 PM, Dinusha Boteju <[email protected]> wrote:

> Hi Niranjan,
>
> If this is a valid requirement then we can incorporate in to the plugin.
> However, assume this feature which composed of multiple licenses needs to
> be installed through the feature manager console. Currently before a
> feature being installed, the user is shown with the license which is
> included in the feature. In this special scenario of having multiple
> license, how can this scenario be addressed when installing through the
> feature manager?
>
> Regards,
> Dinusha
>
> On Wed, Nov 18, 2015 at 3:09 PM, Niranjan Karunanandham <[email protected]
> > wrote:
>
>> Hi Dinusha,
>>
>> This is a valid requirement. Lets say for instance we have 4 features in
>> a repo where feature F1 has three license L1, L2 and L3, feature F2 has 2
>> license L1 and L2, feature F3 has 2 licenses L2 and L3 and feature F4 has
>> only license L1. If we merge the licenses for each feature then we would be
>> duplicating the licenses. IMO we need to improve this and allow to add
>> multiple licenses for a feature. WDYT?
>>
>> Regards,
>> Nira
>>
>> On Wed, Nov 18, 2015 at 3:03 PM, Dinusha Boteju <[email protected]>
>> wrote:
>>
>>> Hi Aruna,
>>>
>>> Current version of the carbon p2 plugin allows you to provide maximum of
>>> 2 properties files in 2 ways.
>>>
>>>    - Provide the properties file as a configuration parameter to the
>>>    plugin (through <propertyFile> tag you can specify the location)
>>>    - The plugin check for a file named *feature.properties* inside
>>>    {project location}/src/main/resources folder.
>>>
>>> If both 2 files exists, the properties are merged as the final output
>>> file. At least one property file should exist for the plugin to work. In
>>> addition, mandatory keys should exist in the final output (mandatory keys
>>> are *copyright* and *license*).
>>>
>>> For your requirement, as a workaround you can merge your properties
>>> files into one and feed into the plugin. However, if your properties files
>>> contain duplicate keys (which is most likely), then it will cause issues
>>> during merging these files.
>>>
>>> You can also try creating different features based on different bundles.
>>> However, I'm not sure that will address your issue.
>>>
>>> -Dinusha
>>>
>>> On Wed, Nov 18, 2015 at 2:32 PM, Aruna Karunarathna <[email protected]>
>>> wrote:
>>>
>>>> Hi all,
>>>>
>>>>
>>>> Currently I am creating a feature for carbon-5, in my feature I have
>>>> bundles which contains multiple licenses.
>>>> So my question is how to add those multiple licenses in the
>>>> feature.properties file?. Or Is there any other way to achieve this?
>>>>
>>>> Regards,
>>>> Aruna
>>>> --
>>>>
>>>> *Aruna Sujith Karunarathna *| Software Engineer
>>>> WSO2, Inc | lean. enterprise. middleware.
>>>> #20, Palm Grove, Colombo 03, Sri Lanka
>>>> Mobile: +94 71 9040362 | Work: +94 112145345
>>>> Email: [email protected] | Web: www.wso2.com
>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> *Dinusha Boteju*
>>> *WSO2, Inc. http://wso2.com <http://wso2.com/> *
>>> *lean.enterprise.middleware.*
>>>
>>> email: [email protected] <[email protected]>
>>> phone:(+94) 776640275 <%28%2B94%29%20777739736>
>>>
>>> _______________________________________________
>>> Dev mailing list
>>> [email protected]
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> *Niranjan Karunanandham*
>> Senior Software Engineer - WSO2 Inc.
>> WSO2 Inc.: http://www.wso2.com
>>
>
>
>
> --
> *Dinusha Boteju*
> *WSO2, Inc. http://wso2.com <http://wso2.com/> *
> *lean.enterprise.middleware.*
>
> email: [email protected] <[email protected]>
> phone:(+94) 776640275 <%28%2B94%29%20777739736>
>



-- 

*Niranjan Karunanandham*
Senior Software Engineer - WSO2 Inc.
WSO2 Inc.: http://www.wso2.com
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to