Re: [Dev] [DEV][EMM] Android enrollment production readiness

2015-08-17 Thread Kasun Dananjaya Delgolla 
+1 to use Gradle invocations. It will be the ideal way to handle this. And
also we should finalize gradle build (generating APK) as well. Gradle lib
is getting downloaded during the build at the moment which can result in
intermittent build failure. So we should make this an orbit bundle IMO. And
that lib is downloading a 50+ MB file which we must decide where to keep.

Thanks

On Mon, Aug 17, 2015 at 12:23 PM, Milan Perera  wrote:

> Hi Dulitha,
>
> +1 for building from Gradle.
>
> On Mon, Aug 17, 2015 at 11:20 AM, Dulitha Wijewantha 
> wrote:
>
>> Hi Inosh,
>> +1 for the property file. We also can trigger the build from Gradle for
>> environments right? [1]. We can pass in an environment parameter to build
>> an artifact.
>>
>> [1] -
>> http://tobiasbayer.com/blog/2011/04/16/building-for-different-environments-with-gradle/
>> Cheers~
>>
>> On Mon, Aug 17, 2015 at 3:08 PM, Dilshan Edirisuriya 
>> wrote:
>>
>>> Hi,
>>>
>>> Better make the IP configurable so that it can be hidden anytime
>>> specially when it comes to a production environment. When it comes to
>>> domain also same thing is applicable since for most of the deployment it
>>> will only need just one tenant.
>>>
>>> Regards,
>>>
>>> Dilshan
>>>
>>> On Mon, Aug 17, 2015 at 10:07 AM, Inosh Perera  wrote:
>>>
 Hi Milan/Kasun,

 During the EMM registration[1], Step 3 and 4 where the user has to
 enter the IP/domain;
  should be designed in a way where in a production scenario, this step
 can be bypassed. In other words, the IP can be hard coded and the step can
 be hidden from the user, since in production the user is not expected to
 know about the backend IPs/Domains. Same can be applicable to step
 5 Ownership type selection. Once option would be to maintain these in a
 configuration file.

 [1].
 https://docs.wso2.com/display/EMM200/End-user+Registering+an+Android+Device

 Regards,
 Inosh

 --
 Inosh Perera
 Software Engineer, WSO2 Inc.
 Tel: 0785293686

>>>
>>>
>>>
>>> --
>>> Dilshan Edirisuriya
>>> Senior Software Engineer - WSO2
>>> Mob: + 94 777878905
>>> http://wso2.com/
>>> https://www.linkedin.com/profile/view?id=50486426
>>>
>>
>>
>>
>> --
>> Dulitha Wijewantha (Chan)
>> Software Engineer - Mobile Development
>> WSO2 Inc
>> Lean.Enterprise.Middleware
>>  * ~Email   duli...@wso2.com *
>> *  ~Mobile +94712112165 <%2B94712112165>*
>> *  ~Website   dulitha.me *
>> *  ~Twitter @dulitharw *
>>   *~Github @dulichan *
>>   *~SO @chan *
>>
>
>
>
> --
> Milan Harindu Perera
> Software Engineer
> *WSO2, Inc*
> (+94) 77 309 7088
> lean . enterprise . middleware
> 
>



-- 
Kasun Dananjaya Delgolla

Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware
Tel:  +94 11 214 5345
Fax: +94 11 2145300
Mob: + 94 771 771 015
Blog: http://kddcodingparadise.blogspot.com
Linkedin: *http://lk.linkedin.com/in/kasundananjaya
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV][EMM] Android enrollment production readiness

2015-08-16 Thread Milan Perera 
Hi Dulitha,

+1 for building from Gradle.

On Mon, Aug 17, 2015 at 11:20 AM, Dulitha Wijewantha 
wrote:

> Hi Inosh,
> +1 for the property file. We also can trigger the build from Gradle for
> environments right? [1]. We can pass in an environment parameter to build
> an artifact.
>
> [1] -
> http://tobiasbayer.com/blog/2011/04/16/building-for-different-environments-with-gradle/
> Cheers~
>
> On Mon, Aug 17, 2015 at 3:08 PM, Dilshan Edirisuriya 
> wrote:
>
>> Hi,
>>
>> Better make the IP configurable so that it can be hidden anytime
>> specially when it comes to a production environment. When it comes to
>> domain also same thing is applicable since for most of the deployment it
>> will only need just one tenant.
>>
>> Regards,
>>
>> Dilshan
>>
>> On Mon, Aug 17, 2015 at 10:07 AM, Inosh Perera  wrote:
>>
>>> Hi Milan/Kasun,
>>>
>>> During the EMM registration[1], Step 3 and 4 where the user has to enter
>>> the IP/domain;
>>>  should be designed in a way where in a production scenario, this step
>>> can be bypassed. In other words, the IP can be hard coded and the step can
>>> be hidden from the user, since in production the user is not expected to
>>> know about the backend IPs/Domains. Same can be applicable to step
>>> 5 Ownership type selection. Once option would be to maintain these in a
>>> configuration file.
>>>
>>> [1].
>>> https://docs.wso2.com/display/EMM200/End-user+Registering+an+Android+Device
>>>
>>> Regards,
>>> Inosh
>>>
>>> --
>>> Inosh Perera
>>> Software Engineer, WSO2 Inc.
>>> Tel: 0785293686
>>>
>>
>>
>>
>> --
>> Dilshan Edirisuriya
>> Senior Software Engineer - WSO2
>> Mob: + 94 777878905
>> http://wso2.com/
>> https://www.linkedin.com/profile/view?id=50486426
>>
>
>
>
> --
> Dulitha Wijewantha (Chan)
> Software Engineer - Mobile Development
> WSO2 Inc
> Lean.Enterprise.Middleware
>  * ~Email   duli...@wso2.com *
> *  ~Mobile +94712112165 <%2B94712112165>*
> *  ~Website   dulitha.me *
> *  ~Twitter @dulitharw *
>   *~Github @dulichan *
>   *~SO @chan *
>



-- 
Milan Harindu Perera
Software Engineer
*WSO2, Inc*
(+94) 77 309 7088
lean . enterprise . middleware

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV][EMM] Android enrollment production readiness

2015-08-16 Thread Dulitha Wijewantha 
Hi Inosh,
+1 for the property file. We also can trigger the build from Gradle for
environments right? [1]. We can pass in an environment parameter to build
an artifact.

[1] -
http://tobiasbayer.com/blog/2011/04/16/building-for-different-environments-with-gradle/
Cheers~

On Mon, Aug 17, 2015 at 3:08 PM, Dilshan Edirisuriya 
wrote:

> Hi,
>
> Better make the IP configurable so that it can be hidden anytime specially
> when it comes to a production environment. When it comes to domain also
> same thing is applicable since for most of the deployment it will only need
> just one tenant.
>
> Regards,
>
> Dilshan
>
> On Mon, Aug 17, 2015 at 10:07 AM, Inosh Perera  wrote:
>
>> Hi Milan/Kasun,
>>
>> During the EMM registration[1], Step 3 and 4 where the user has to enter
>> the IP/domain;
>>  should be designed in a way where in a production scenario, this step
>> can be bypassed. In other words, the IP can be hard coded and the step can
>> be hidden from the user, since in production the user is not expected to
>> know about the backend IPs/Domains. Same can be applicable to step
>> 5 Ownership type selection. Once option would be to maintain these in a
>> configuration file.
>>
>> [1].
>> https://docs.wso2.com/display/EMM200/End-user+Registering+an+Android+Device
>>
>> Regards,
>> Inosh
>>
>> --
>> Inosh Perera
>> Software Engineer, WSO2 Inc.
>> Tel: 0785293686
>>
>
>
>
> --
> Dilshan Edirisuriya
> Senior Software Engineer - WSO2
> Mob: + 94 777878905
> http://wso2.com/
> https://www.linkedin.com/profile/view?id=50486426
>



-- 
Dulitha Wijewantha (Chan)
Software Engineer - Mobile Development
WSO2 Inc
Lean.Enterprise.Middleware
 * ~Email   duli...@wso2.com *
*  ~Mobile +94712112165*
*  ~Website   dulitha.me *
*  ~Twitter @dulitharw *
  *~Github @dulichan *
  *~SO @chan *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV][EMM] Android enrollment production readiness

2015-08-16 Thread Dilshan Edirisuriya 
Hi,

Better make the IP configurable so that it can be hidden anytime specially
when it comes to a production environment. When it comes to domain also
same thing is applicable since for most of the deployment it will only need
just one tenant.

Regards,

Dilshan

On Mon, Aug 17, 2015 at 10:07 AM, Inosh Perera  wrote:

> Hi Milan/Kasun,
>
> During the EMM registration[1], Step 3 and 4 where the user has to enter
> the IP/domain;
>  should be designed in a way where in a production scenario, this step can
> be bypassed. In other words, the IP can be hard coded and the step can be
> hidden from the user, since in production the user is not expected to know
> about the backend IPs/Domains. Same can be applicable to step 5 Ownership
> type selection. Once option would be to maintain these in a configuration
> file.
>
> [1].
> https://docs.wso2.com/display/EMM200/End-user+Registering+an+Android+Device
>
> Regards,
> Inosh
>
> --
> Inosh Perera
> Software Engineer, WSO2 Inc.
> Tel: 0785293686
>



-- 
Dilshan Edirisuriya
Senior Software Engineer - WSO2
Mob: + 94 777878905
http://wso2.com/
https://www.linkedin.com/profile/view?id=50486426
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [DEV][EMM] Android enrollment production readiness

2015-08-16 Thread Inosh Perera 
Hi Milan/Kasun,

During the EMM registration[1], Step 3 and 4 where the user has to enter
the IP/domain;
 should be designed in a way where in a production scenario, this step can
be bypassed. In other words, the IP can be hard coded and the step can be
hidden from the user, since in production the user is not expected to know
about the backend IPs/Domains. Same can be applicable to step 5 Ownership
type selection. Once option would be to maintain these in a configuration
file.

[1].
https://docs.wso2.com/display/EMM200/End-user+Registering+an+Android+Device

Regards,
Inosh

-- 
Inosh Perera
Software Engineer, WSO2 Inc.
Tel: 0785293686
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev