Skip to main content
This revision made November 07, 2011 19:45, by jpgough
« earlier revision revert to this later revision »

Getting Started working on JSR-310 TCK

The first part of this guide will go into how to download, setup and run the ThreeTen project from the main TCK branch. The second part of the guide will introduce some of the core classes and overall structure of the project. The final part will discuss how we will approach writing a TCK and which classes we believe are likely to change and will not be the focus of the phase 1 TCK effort.

How to get the code in a working state in Eclipse from GitHub

  • Firstly you need to get yourself a github account, this is where ThreeTen exists and therefore the fork for writing this TCK.
  • Secondly you will need to sign a JSPA before you can push to the main TCK branch. You can find more information on this here: JSPA Membership
  • Now you have your git account created and setup following these instructions. You are ready to start with the following guide.
  • Fork the repository using the github webpage, you will need to fork Richard's branch, which is the master as far as the TCK is concerned. This is forked from ThreeTen and will be merged back at regular intervals managed by us.
  • Clone the repository into your user account, i.e.
    • git clone<Your User Name>/threeten.git
  • Now the threeten folder has been cloned locally, you will notice that there are Eclipse .project files in the top level. You can import this straight into Eclipse, but this won't compile. Before doing that you must run the ant command in that folder, as this will remote retrieve some of the required libraries.
  • Import into Eclipse and you are good to go.

Running the TCK from Ant

We've added a new ant target for testing TCK acceptance. So if you've compiled the latest version of the existing source code, then in order to run the TCK against it you would execute:

   ant -Dtck.implementation=build/threeten-0.6.3.jar tck

You can substitute any arbitrary jar as the 'tck.implementation' variable and it tests against the classes in that jar.

Please Confirm