- 1 Device Software Development Platform / Mobile Tools for the Java Platform
Device Software Development Platform / Mobile Tools for the Java Platform
Welcome to the Mobile Tools for the Java Platform (MTJ) Project Wiki.
These pages are meant as an open, collaborative platform for discussions and exchanging ideas.
For official information and documents, see the Official DSDP-MTJ Website.
The discussion section list some topics that need to be discussed inside MTJ Project. For each topic that one specific wiki page. Feel free to edit each page and add your contribution to the discussion.
Planning & Minutes
For each release that is planned on MTJ, it is necessary to add a separated WiKi page that details its scope.
This section lists the main requirements that are supported on MTJ (both functional and non functional) and after that details each use case. Besides that the test procedures that should be used on MTJ are also detailed here.
Refer to the Developer Resources pages for information for guides on adopted standards, the releng process and how to document things.
- Configuring the Workspace
- Coding Standards
- Copyright Standards
- Contributor Checklist before submitting a patch
- Contributor Confirmations via Bugzilla Bug
- How to add things to the Developer Guide doc
MTJ was rebooted in the beginning of this year. The project aimed at first to provide at least the same functionality that is currently available on EclipseME
MTJ 0.7 WiKi (before reboot)
There was a lot of content produced on MTJ before the project as rebooted. All this content is linked from this WiKi page. We don't plan to maintain this content and it is listed here mostly for reference
The purpose of the Mobile Tools for the Java Platform (MTJ) project is to extend the Eclipse platform to enable developers to develop, debug, and deploy mobile Java applications to emulators and real devices. The project will develop frameworks that can be extended by tool vendors and tools that can be used by third-party developers.
MTJ 1.1.0 New & Noteworthy
This release focus mainly in migrating MTJ to Helios Release.
The declared APIs in MTJ are provided as public and documented. New APIs should be approved by the project lead. Deprecated APIs should also be approved by the project lead. They should be notified for the community, and not be removed for at least 2 major releases.
Provisional and Internal API
Provisional APIs should be used while development is occurring. If successfully adopted, they might become declared APIs. If not, they can be removed. In any situation, the community should be notified.
Formal releases are kept forever on both the main download page and update site.
While developing a new release, milestone and its related nightly builds will be kept. Once we move to a next Milestone, the nightly builds related to the previous Milestone will be deleted, and the previous Milestone will be moved to Archive.
This way, the main page will always contain the latest release and the current milestone and nightly builds under development.
This policy applies to the update site as well.
ATTENTION: A specific build might be kept if a product depends on it. If this is the case, contact MTJ team in order to warn them that you depend on such build.
What if these policies don't work for you?
Just ask. Open a bug or post an email in our mailing list (web) and request what you need.
Number of bundles
* Features: 3 * Plugins: 25
Number of committers
* 5 (Craig Setera, Diego Sandin, Daniel Pastore, Gorkem Ercan, Gustavo de Paula)
Lines of code
Not available yet
Number of bugs
* Fixed in 1.1 release: 22 (as of May 14) * Closed or Resolved: 677 (as of May 14)