TruffleSigtest
From APIDesign
(→The Right Tool) |
|||
| Line 5: | Line 5: | ||
First and foremost one needs to select a [[SignatureTests#Java|signature testing tool]]. As [[I|my]] background is related to [[NetBeans]], my choice was almost guaranteed. [[I]] decided to use [[NetBeans]] [[netbeans:APITest|APITest]]. | First and foremost one needs to select a [[SignatureTests#Java|signature testing tool]]. As [[I|my]] background is related to [[NetBeans]], my choice was almost guaranteed. [[I]] decided to use [[NetBeans]] [[netbeans:APITest|APITest]]. | ||
| - | Slight problem was that the tool hasn't been updated to [[JDK]]8 language constructs (e.g. '''default''' and '''static''' methods in interfaces). However, as [[NetBeans]] need to use the tool as well, I got a great help from Tomáš Zezula. He is currently working on switching the [[NetBeans]] codebase to [[JDK]]8 and he updated the [[netbeans:APITest|APITest]] to deal properly with [[JDK]]8 features (see | + | Slight problem was that the tool hasn't been updated to [[JDK]]8 language constructs (e.g. '''default''' and '''static''' methods in interfaces). However, as [[NetBeans]] need to use the tool as well, I got a great help from Tomáš Zezula. He is currently working on switching the [[NetBeans]] codebase to [[JDK]]8 and he updated the [[netbeans:APITest|APITest]] to deal properly with [[JDK]]8 features (see [http://hg.netbeans.org/apitest/rev/33e52387e536 here] and [http://hg.netbeans.org/apitest/rev/1d8a2a522dab here]). It is always [[good]] to build on shoulders of giants - e.g. use a tool that a mature project like [[NetBeans]] maintains. |
Revision as of 17:33, 20 November 2015
API signature tests are part of Truffle project workflow since today! Let me describe what I have done, as similar changes are likely needed in any Java project that wants to use SignatureTests to keep backward compatibility of its APIs.
The Right Tool
First and foremost one needs to select a signature testing tool. As my background is related to NetBeans, my choice was almost guaranteed. I decided to use NetBeans APITest.
Slight problem was that the tool hasn't been updated to JDK8 language constructs (e.g. default and static methods in interfaces). However, as NetBeans need to use the tool as well, I got a great help from Tomáš Zezula. He is currently working on switching the NetBeans codebase to JDK8 and he updated the APITest to deal properly with JDK8 features (see here and here). It is always good to build on shoulders of giants - e.g. use a tool that a mature project like NetBeans maintains.
Follow
