Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mtj-dev] MTJ - Project plan

Dear Gorkem,

 

Setting up nightly build would be the best way to kick start the project as it would enable us to track and test daily changes and make the MTJ experience smoother.

 

I know we already have infrastructure ready. I would need you expertise to guide me on this further as I am not much aware about it. AFAIK, we are having Hudson to manage the builds.

 

Would you please guide me on the following.

-          Details of the Hudson server.

-          How are we managing the nightly builds?

 

Thanks

Pranav

 

From: Gothadiya Pranav (Nokia-DX/Bangalore)
Sent: 29 July 2013 10:55
To: 'ext Alexander Burdukov'; MTJ Developer discussions
Subject: RE: [mtj-dev] MTJ - Project plan

 

Very true. I believe, the infrastructure is already in the place. Just need to understand it and make it active again.

I will surely look into it after completing my current sequence of work.

 

 

Thanks

Pranav

 

From: ext Alexander Burdukov [mailto:Alexander.Burdukov@xxxxxxxxxx]
Sent: 26 July 2013 01:18
To: MTJ Developer discussions
Cc: Gothadiya Pranav (Nokia-DX/Bangalore)
Subject: Re: [mtj-dev] MTJ - Project plan

 

Pranav,

also, I guess we need to establish build infrastructure for MTJ to have regular nightly builds.
In this case ME SDK SQE team will be able to help with QA of MTJ plugin (at least indirectly by testing ME SDK plugins on top of MTJ).

Alex.

23.07.2013 9:38, pranav.gothadiya@xxxxxxxxx wrote:

Hi,

 

I spent some time on understanding the installable_sdk branch. Here it what I suggest as a plan further.

 

1.       At this moment, if you see, Oracle and Nokia seems to be the only active customers of MTJ.  I would suggest MTJ should use complete feature of Device SDK Manager (DSM) from Nokia which provides device details, screen size, etc. By doing this, MTJ will have default support of Nokia and Oracle SDKs through DSM. Of course other SDKs can be added  as there would be extension point provided to add SDKs to DSM. Also, as and when there is new J2ME SDK, either MTJ or the SDK owner can use the extension point to add their SDK to device SDK manager. For example: Tomorrow, ABC company wants to add the SDK to the DSM, they just need to use the extension point we provide and create the plugin. MTJ would fetch the information using p2 and display those SDKs along with other SDKs in DSM.

 

Note: default support if manual SDK integration would still be available, in case anybody wants to integrate the SDK manually.

 

I have started looking at this.

 

2.       Oracle can continue their changes on installable_sdk branch. As and when they are ready, we help to merge their code.

3.       Lots of new changes will be available in installable_sdk. Finally, installable_sdk branch to be merged with master.

4.       Code drag and drop feature: It would help developer to drag and drop the code snippet directly to the selected location.

 

For example: user is writing the SMS application. He can drag “SMS Send” option from the Code Snippet list and drop it to the selected location in the code. It would add the code of sending the SMS to the application.

 

I would appreciate your views.

 

Thanks,

Pranav

 



_______________________________________________
mtj-dev mailing list
mtj-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mtj-dev

 

Back to the top