Hi Sumedha, New parent pom is at [1]. According to the mail thread, current definition is correct.
[1] https://github.com/wso2/carbon-parent/blob/master/pom.xml Thanks Geeth *G. K. S. Munasinghe* *Software Engineer,* *WSO2, Inc. http://wso2.com <http://wso2.com/> * *lean.enterprise.middleware.* email: [email protected] phone:(+94) 777911226 On Fri, Dec 5, 2014 at 11:59 AM, Niranjan Karunanandham <[email protected]> wrote: > Hi Geeth and Sumedha, > > In carbon kernel 4.3.0, the parent pom is changed as mentioned in [1]. > > [1] - Mail Subject: [Carbon-4.3.0] WSO2 Parent pom Released > > Regards, > Nira > > > On Fri, Dec 5, 2014 at 11:49 AM, Geeth Munasinghe <[email protected]> wrote: > >> Hi Sumedha, >> >> I will do the change accordingly. >> >> Thanks >> Geeth >> >> >> *G. K. S. Munasinghe* >> *Software Engineer,* >> *WSO2, Inc. http://wso2.com <http://wso2.com/> * >> *lean.enterprise.middleware.* >> >> email: [email protected] >> phone:(+94) 777911226 >> >> On Fri, Dec 5, 2014 at 11:35 AM, Sumedha Rubasinghe <[email protected]> >> wrote: >> >>> Guys, >>> The parent pom definition is not following the standard. It is as >>> follows now. >>> >>> <parent> >>> <groupId>org.wso2</groupId> >>> <artifactId>wso2</artifactId> >>> <version>1</version> >>> </parent> >>> >>> It should be something like following: >>> >>> <parent> >>> <groupId>org.wso2.carbon</groupId> >>> <artifactId>platform-parent</artifactId> >>> <version>4.2.0</version> >>> <relativePath>../parent/pom.xml</relativePath> >>> </parent> >>> >>> >>> Please refer 'parent' section >>> http://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/components/pom.xml >>> for example. >>> >>> On Wed, Dec 3, 2014 at 11:23 AM, Manoj Gunawardena <[email protected]> >>> wrote: >>> >>>> Hi All, >>>> >>>> Few Corrections. >>>> >>>> This is December 2nd meeting minutes. Also need to add two things, >>>> >>>> 12. In the device table: >>>> need to change 'byod' field name to 'ownership'. >>>> >>>> 13. The current policy definition is just a set of actions that do not >>>> contain any >>>> applicable conditions, it was suggested to rename it as 'profile'. >>>> >>>> Thanks >>>> >>>> On Wed, Dec 3, 2014 at 11:06 AM, Manoj Gunawardena <[email protected]> >>>> wrote: >>>> >>>>> Hi All, >>>>> >>>>> *Dec 03rd meeting minutes.* >>>>> >>>>> *Attendees* : Sameera Perera, Kasun Dananjaya, Prabath Abeysekera, Asok >>>>> Perera, Afkham Azeez, Geeth Munasinghe, Inosh Perera, Sumedha >>>>> Rubasinghe, Srinath Perera, Manoj Gunawardena >>>>> >>>>> >>>>> 1. Develop components in a separate repo, But for the movement it's >>>>> develop as a module inside CDM. Later move to a separate repo. >>>>> >>>>> 2.Develop common interface in the core, to cater all core >>>>> functionalities. Develop plugins for each device type. >>>>> >>>>> Ex -: Android, IOS, windows or other device type >>>>> >>>>> 3. For IOS and android develop a common enrollment data set and common >>>>> method. >>>>> For windows or other specific devices develop specific services. >>>>> >>>>> 4. Policy handling discussion - Not completed. Decided to keep >>>>> existing functionality for 1st release. >>>>> >>>>> 5. Policy rename as profile suggested. >>>>> >>>>> 6. IOT devices enrollment mechanism discussed. The device should >>>>> develop It's own agent to communicate with CDM, In such cases >>>>> authentication mechanism should be implement using OAUTH custom grant >>>>> type. >>>>> >>>>> 7. Sumeda will do a demonstration on IOT devices connectivity with CDM. >>>>> >>>>> 8. For mobile agents, the existing authentication flow should change. >>>>> The authentication mechanism decided to change using service >>>>> provider. >>>>> >>>>> 9. The existing agent download mechanism has security falls. Decided >>>>> to change and display login page and authenticate user at the downloading. >>>>> >>>>> 10. The team is working on listing interfaces and creating the repo, >>>>> modules and structure >>>>> The new CDM repo. >>>>> https://github.com/geethkokila/product-cdm/ >>>>> >>>>> >>>>> 11. New concept "event "should add for dynamic policies. >>>>> >>>>> >>>>> Kindly append if I have missed anything here >>>>> >>>>> Thanks >>>>> Manoj >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> On Tue, Dec 2, 2014 at 11:05 AM, Sameera Perera <[email protected]> >>>>> wrote: >>>>> >>>>>> Appending.... >>>>>> >>>>>> Day 1 Notes: >>>>>> >>>>>> *Goals* >>>>>> >>>>>> 1. Identify a CDM Core that's device/platform agnostic >>>>>> 2. Properly modularize the product (continuing the discussion in >>>>>> the thread [1]) >>>>>> 3. Evaluate how CDM can able to support Dynamic policies and >>>>>> policy merging which are frequently requested features >>>>>> >>>>>> *Terminology* >>>>>> >>>>>> - Feature (more accurately Device Management Feature): This is an >>>>>> operation that the CDM can instruct the device to perform. A MDM >>>>>> example of >>>>>> this would be to "Put ringer in silent mode". On a smart thermostat, >>>>>> this >>>>>> could be "Reduce Air Conditioning" >>>>>> - Policy: A policy is a collection of features. The CDM Core, >>>>>> maintains the policy in a canonical format. Platform bundles may >>>>>> translate >>>>>> the policy in to a device dependent format. >>>>>> >>>>>> Both terms (feature and policy) are misnomers and may better termed >>>>>> as operations and profiles. However, we decided to stick to the terms as >>>>>> these are standard across the MDM industry. >>>>>> >>>>>> >>>>>> - Platform Bundle: Refer [1] >>>>>> >>>>>> >>>>>> *CDM Core* >>>>>> >>>>>> - Instructs the platform bundle to apply a policy to the device >>>>>> - The core determines which policy needs to be applied to the >>>>>> device through a "Trigger". EMM 1.0 used 3 types of triggers: >>>>>> Platform, >>>>>> User and Role. CDM will introduce Location and Time. >>>>>> - When device calls back to the CDM, validates whether the device >>>>>> is violating its policy >>>>>> >>>>>> The Core will contain policy management and policy enforcement >>>>>> components as well as a policy editor. >>>>>> >>>>>> *MDM Module* >>>>>> >>>>>> - A MDM Module will sit on top of the core to enable feature >>>>>> parity with EMM 1.1. It will be written specifically with the >>>>>> knowledge >>>>>> that platform bundles for Android, iOS are available. >>>>>> - The MDM will define a common set of features that are available >>>>>> across all phones. >>>>>> >>>>>> By introducing this layer of abstraction we are able to keep manage >>>>>> mobile devices across mobile platforms as we've done in EMM without >>>>>> complicating the device agnostic capabilities of the core. Similar >>>>>> modules >>>>>> can be built by 3rd parties to manage other device categories such as >>>>>> thermostats, smart TVs etc. from different vendors/platforms. >>>>>> >>>>>> *Other notes* >>>>>> >>>>>> - We have demoted the following concepts to second class citizens >>>>>> and pulled them out of the core >>>>>> 1. OS Platform, version >>>>>> 2. Device Platform, version >>>>>> 3. Roles >>>>>> >>>>>> 1 and 2 only matter to the extend that they help us define a set of >>>>>> available features. Bundles will be responsible for managing this set >>>>>> based >>>>>> on these factors. The core will only be aware of the set. >>>>>> Roles were used in the EMM only to select the policy to apply on a >>>>>> user's device. We have moved this responsibility to the Trigger (or >>>>>> handler) chain. The core will only be aware of the chain, not what logic >>>>>> is >>>>>> applied to generate the policy. >>>>>> >>>>>> *For further discussions:* >>>>>> >>>>>> - More discussion around Trigger concept >>>>>> - Policy merging >>>>>> - Feature permissions >>>>>> >>>>>> [1] "Proposed Architecture of CDM" - architecture@ >>>>>> >>>>>> >>>>>> On Tue, Dec 2, 2014 at 10:10 AM, Asok Perera <[email protected]> wrote: >>>>>> >>>>>>> Hi All, >>>>>>> >>>>>>> Please find the meeting minutes for the yesterday meeting. >>>>>>> >>>>>>> *Attendees* : Sameera Perera, Kasun Dananjaya, Prabath Abeysekera, Asok >>>>>>> Perera, Afkham Azeez, Geeth Munasinghe, Inosh Perera, Harshan >>>>>>> Liyanage, Niranjan Karunanandham, Sumedha Rubasinghe, Srinath >>>>>>> Perera, Manoj Dilshan >>>>>>> >>>>>>> >>>>>>> - Knowledge transfer of the current EMM architecture >>>>>>> - Moving all the device specific entries from Core EER to >>>>>>> bundles (bundles will have their own EERs) >>>>>>> - Checked the possibility of separating Mobile phone devices >>>>>>> implementation from IoT as too much generalisation seems to make the >>>>>>> architecture too complex (Not finalised yet) >>>>>>> - Checked the possibility of moving device specific feature >>>>>>> information to bundles, and keeping only the definition of features >>>>>>> in core >>>>>>> for managing policy information (Not finalised yet) >>>>>>> - generalising core EER by removing/moving entries like IMEI, >>>>>>> MAC etc >>>>>>> - Checked the possibility of renaming some entries(role, policy, >>>>>>> feature etc) according to the standard >>>>>>> >>>>>>> Kindly append if I have missed anything here. >>>>>>> >>>>>>> Regards >>>>>>> >>>>>>> *Asok Aravinda Perera* >>>>>>> Software Engineer >>>>>>> WSO2, Inc.;http://wso2.com/ >>>>>>> <http://www.google.com/url?q=http%3A%2F%2Fwso2.com%2F&sa=D&sntz=1&usg=AFQjCNGJuLRux6KkJwXKVUCYOtEsNCmIAQ> >>>>>>> lean.enterprise.middleware >>>>>>> >>>>>>> Mobile: +94722241032 >>>>>>> >>>>>>> On Mon, Dec 1, 2014 at 12:25 PM, Sameera Perera <[email protected]> >>>>>>> wrote: >>>>>>> >>>>>>>> more details » >>>>>>>> <https://www.google.com/calendar/event?action=VIEW&eid=cjdjYmFnamZjdWY5dTFqYTEzdm5ibDlzaDAgZW5naW5lZXJpbmctZ3JvdXBAd3NvMi5jb20&tok=MTcjc2FtZWVyYXBAd3NvMi5jb201OTJhZGJmZWMzM2Q4NmViNDczZWFiYzRmNzYyZTFhOTk4MjFhMWJj&ctz=Asia/Colombo&hl=en> >>>>>>>> CDM Hackathon >>>>>>>> *When* >>>>>>>> Mon Dec 1, 2014 1:30pm – 5:30pm Colombo >>>>>>>> *Where* >>>>>>>> LK 3rd Floor Meeting Room - Kernel (map >>>>>>>> <https://maps.google.lk/maps?q=LK+3rd+Floor+Meeting+Room+-+Kernel&hl=en> >>>>>>>> ) >>>>>>>> *Video call* >>>>>>>> https://plus.google.com/hangouts/_/wso2.com/cdm-hackathon >>>>>>>> <https://plus.google.com/hangouts/_/wso2.com/cdm-hackathon?hceid=c2FtZWVyYXBAd3NvMi5jb20.r7cbagjfcuf9u1ja13vnbl9sh0> >>>>>>>> *Calendar* >>>>>>>> Sameera Perera >>>>>>>> *Who* >>>>>>>> • >>>>>>>> Sameera Perera - organizer >>>>>>>> • >>>>>>>> Kasun Dananjaya Delgolla >>>>>>>> • >>>>>>>> Prabath Abeysekera >>>>>>>> • >>>>>>>> Asok Perera >>>>>>>> • >>>>>>>> Dulitha Wijewantha >>>>>>>> • >>>>>>>> Afkham Azeez >>>>>>>> • >>>>>>>> Dilan Udara Ariyaratne >>>>>>>> • >>>>>>>> Geeth Munasinghe >>>>>>>> • >>>>>>>> Inosh Perera >>>>>>>> • >>>>>>>> Harshan Liyanage >>>>>>>> • >>>>>>>> Dilshan Edirisuriya >>>>>>>> • >>>>>>>> Niranjan Karunanandham >>>>>>>> • >>>>>>>> Sumedha Rubasinghe >>>>>>>> • >>>>>>>> Srinath Perera >>>>>>>> • >>>>>>>> WSO2 Engineering Group >>>>>>>> >>>>>>>> Going? *Yes >>>>>>>> <https://www.google.com/calendar/event?action=RESPOND&eid=cjdjYmFnamZjdWY5dTFqYTEzdm5ibDlzaDAgZW5naW5lZXJpbmctZ3JvdXBAd3NvMi5jb20&rst=1&tok=MTcjc2FtZWVyYXBAd3NvMi5jb201OTJhZGJmZWMzM2Q4NmViNDczZWFiYzRmNzYyZTFhOTk4MjFhMWJj&ctz=Asia/Colombo&hl=en> >>>>>>>> - Maybe >>>>>>>> <https://www.google.com/calendar/event?action=RESPOND&eid=cjdjYmFnamZjdWY5dTFqYTEzdm5ibDlzaDAgZW5naW5lZXJpbmctZ3JvdXBAd3NvMi5jb20&rst=3&tok=MTcjc2FtZWVyYXBAd3NvMi5jb201OTJhZGJmZWMzM2Q4NmViNDczZWFiYzRmNzYyZTFhOTk4MjFhMWJj&ctz=Asia/Colombo&hl=en> >>>>>>>> - No >>>>>>>> <https://www.google.com/calendar/event?action=RESPOND&eid=cjdjYmFnamZjdWY5dTFqYTEzdm5ibDlzaDAgZW5naW5lZXJpbmctZ3JvdXBAd3NvMi5jb20&rst=2&tok=MTcjc2FtZWVyYXBAd3NvMi5jb201OTJhZGJmZWMzM2Q4NmViNDczZWFiYzRmNzYyZTFhOTk4MjFhMWJj&ctz=Asia/Colombo&hl=en>* >>>>>>>> more options » >>>>>>>> <https://www.google.com/calendar/event?action=VIEW&eid=cjdjYmFnamZjdWY5dTFqYTEzdm5ibDlzaDAgZW5naW5lZXJpbmctZ3JvdXBAd3NvMi5jb20&tok=MTcjc2FtZWVyYXBAd3NvMi5jb201OTJhZGJmZWMzM2Q4NmViNDczZWFiYzRmNzYyZTFhOTk4MjFhMWJj&ctz=Asia/Colombo&hl=en> >>>>>>>> >>>>>>>> Invitation from Google Calendar <https://www.google.com/calendar/> >>>>>>>> >>>>>>>> You are receiving this courtesy email at the account >>>>>>>> [email protected] because you are an attendee of this >>>>>>>> event. >>>>>>>> >>>>>>>> To stop receiving future updates for this event, decline this >>>>>>>> event. Alternatively you can sign up for a Google account at >>>>>>>> https://www.google.com/calendar/ and control your notification >>>>>>>> settings for your entire calendar. >>>>>>>> >>>>>>>> -- >>>>>>>> You received this message because you are subscribed to the Google >>>>>>>> Groups "WSO2 Engineering Group" group. >>>>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>>>> send an email to [email protected]. >>>>>>>> For more options, visit >>>>>>>> https://groups.google.com/a/wso2.com/d/optout. >>>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> >>>>>> ------------------------------ >>>>>> >>>>>> *Sameera Perera* >>>>>> Director of Engineering >>>>>> gtalk: [email protected] >>>>>> Tel : 94 11 214 5345 >>>>>> Fax :94 11 2145300 >>>>>> *WSO2, Inc.* <http://wso2.com/> >>>>>> lean.enterprise.middleware >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Architecture mailing list >>>>>> [email protected] >>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Manoj Gunawardena >>>>> Tech Lead >>>>> WSO2, Inc.: http://wso2.com >>>>> lean.enterprise.middleware >>>>> Mobile : +94 77 2291643 >>>>> >>>> >>>> >>>> >>>> -- >>>> Manoj Gunawardena >>>> Tech Lead >>>> WSO2, Inc.: http://wso2.com >>>> lean.enterprise.middleware >>>> Mobile : +94 77 2291643 >>>> >>>> _______________________________________________ >>>> Architecture mailing list >>>> [email protected] >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>> >>>> >>> >>> >>> -- >>> /sumedha >>> m: +94 773017743 >>> b : bit.ly/sumedha >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > > *Niranjan Karunanandham* > Senior Software Engineer - WSO2 Inc. > WSO2 Inc.: http://www.wso2.com > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > >
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
