JDTF FAQ |
[+] [–] |
Common questions about the JDTF project are answered here.
| [+] [–] |
Questions About the JDTF Project |
A: The JDTF framework, a project on java.net at http://jdtf.java.net/. A binary copy can be downloaded from here. You can browse or download the source code here.
A: The JDTF framework is a sub-project of the cqME project. As such, it shares licensing and participation guidelines with other cqME sub-projects such as ME Framework.
A: JDTF source code is licensed under the GNU Public License, version 2, with the Classpath Exception. See the licensing section of the download page for more information. If you have questions about this or any other aspect of the project, please post them on the JDTF forum.
For information about the commercial version of the product, contact one of the Oracle worldwide sales offices.
A: The classpath exception was developed by the Free Software Foundation's GNU/Classpath Project (see http://www.gnu.org/software/classpath/license.html). It allows you to link an application available under any license to a library that is part of software licensed under GPL v2, without that application being subject to the GPL's requirement to be itself offered to the public under the GPL.
A: If the project was distributed under GPL v2, that application could be subject to the requirements of the GPL that all code that is shipped as part of a "work based on the [GPL] program" also be GPL licensed. Accordingly, a GPL license exception is needed that specifically excludes from this licensing requirement any application that links to the GPL implementation. The classpath exception accomplishes this.
A: There are a number of ways you can participate in the project. Refer to the cqME Project Participation Handbook for details.
A: In accordance with the cqME project governance process, you can submit code to the project leader either as a user, a developer, or as a committer. If your code is accepted to be integrated into the source tree, you will be asked to sign a Contributor's Agreement similar to the one used by the Apache Software Foundation. For more information about the governance process and the various roles for members in the community, please review Mobile & Embedded Community Governance.
A: See JDTF Documentation for links to all relevant documentation.
| [+] [–] |
Questions About How to Install and Run the JDTF Framework |
A: Refer to the Installation chapter of Java Device Test Framework Getting Started Guide [PDF].
A: Refer to the Launching the Administrator Harness chapter of Java Device Test Framework Getting Started Guide [PDF].
A: JDTF was not formally tested with Linux, however experiments have shown it to work on some Linux distributions. There should be no problems running the JDTF framework and the NetBeans IDE on Linux. A problem might occur when running the CLDC preverifier executable (native code) on some Linux platforms. The Java ME SDK 3.0 currently does not support the Linux platform, however the Wireless Toolkit for CLDC version 2.5.2_01 does. Please refer to Wireless Toolkit documentation for more information.
| [+] [–] |
Questions About Using the JDTF to Create a Test Pack |
A: Follow these steps:
A: In the NetBeans IDE Projects view, right-click on your project and choose the Pack menu item.
A: In the NetBeans IDE Projects view, right-click on your project and choose the Install menu item.
A: Refer to Install Basic Test Packs section of Java Device Test Framework Getting Started Guide [PDF]
A: In the administrator harness, select Configure > Test Packs and follow the on-screen instructions.
A: Refer to Running Tests chapter of Java Device Test Framework Getting Started Guide [PDF]
A: Refer to the JavaTest Command-Line Interface User's Guide available here from the JDTS documentation on java.sun.com.
A: Refer to the "Debugging Example" chapter in the JDTF NetBeans IDE plugin online help
A: Yes. Use the corresponding all,
pack and install targets of the Ant build
script created by the NetBeans IDE plugin. The generated Ant build
script is located at <Your JDTF Test Pack
Project>/build/build.xml)