id
int64 0
5.38k
| issuekey
stringlengths 4
16
| created
stringlengths 19
19
| title
stringlengths 5
252
| description
stringlengths 1
1.39M
| storypoint
float64 0
100
|
|---|---|---|---|---|---|
190 | CLOV-1403 | 01/02/2014 20:57:00 | Cloverage view layout is crappy with the Coverage Summary panel | 1. Not all buttons are visible by default. 2. Width/height proportion which triggers a change between horizontal/vertical layout is not set correctly. As a result we've got a crappy behavior as on the following screen shot: !cloverage_view_layout.png! | 2 |
191 | CLOV-1404 | 01/02/2014 21:20:56 | Source highlighting label is cropped in the settings dialog | Project Settings > Clover > View "Out of date" labels are cropped [^project_settings_clover.png] | 2 |
192 | CLOV-1406 | 01/11/2014 11:36:15 | URISyntaxException from Clover IDEA plugin under IDEA13 on Mac OS X | {noformat} java.net.URISyntaxException: Illegal character in path at index 37: file:/Users/grant/Library/Application Support/IntelliJIdea13/clover-idea-3.2.1.jar: java.net.URISyntaxException: Illegal character in path at index 37: file:/Users/grant/Library/Application Support/IntelliJIdea13/clover-idea-3.2.1.jar java.lang.RuntimeException: java.net.URISyntaxException: Illegal character in path at index 37: file:/Users/grant/Library/Application Support/IntelliJIdea13/clover-idea-3.2.1.jar at com.cenqua.clover.idea.LibrarySupport.getCloverClassBase(LibrarySupport.java:150) at com.cenqua.clover.idea.build.CloverCompiler$RefreshCloverGlobalLibraryTask.execute(CloverCompiler.java:282) at com.intellij.compiler.impl.CompileDriver.a(CompileDriver.java:2375) at com.intellij.compiler.impl.CompileDriver.access$900(CompileDriver.java:122) at com.intellij.compiler.impl.CompileDriver$8.run(CompileDriver.java:706) at com.intellij.compiler.progress.CompilerTask.run(CompilerTask.java:167) at com.intellij.openapi.progress.impl.ProgressManagerImpl$TaskRunnable.run(ProgressManagerImpl.java:464) at com.intellij.openapi.progress.impl.ProgressManagerImpl$2.run(ProgressManagerImpl.java:178) at com.intellij.openapi.progress.ProgressManager.executeProcessUnderProgress(ProgressManager.java:209) at com.intellij.openapi.progress.impl.ProgressManagerImpl.executeProcessUnderProgress(ProgressManagerImpl.java:212) at com.intellij.openapi.progress.impl.ProgressManagerImpl.runProcess(ProgressManagerImpl.java:171) at com.intellij.openapi.progress.impl.ProgressManagerImpl$8.run(ProgressManagerImpl.java:373) at com.intellij.openapi.application.impl.ApplicationImpl$8.run(ApplicationImpl.java:436) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) at java.lang.Thread.run(Thread.java:695) at com.intellij.openapi.application.impl.ApplicationImpl$1$1.run(ApplicationImpl.java:153) Caused by: java.net.URISyntaxException: Illegal character in path at index 37: file:/Users/grant/Library/Application Support/IntelliJIdea13/clover-idea-3.2.1.jar at java.net.URI$Parser.fail(URI.java:2810) at java.net.URI$Parser.checkChars(URI.java:2983) at java.net.URI$Parser.parseHierarchical(URI.java:3067) at java.net.URI$Parser.parse(URI.java:3015) at java.net.URI.<init>(URI.java:577) at com.cenqua.clover.idea.LibrarySupport.getCloverClassBase(LibrarySupport.java:121) ... 19 more java.net.URISyntaxException: Illegal character in path at index 37: file:/Users/grant/Library/Application Support/IntelliJIdea13/clover-idea-3.2.1.jar: java.net.URISyntaxException: Illegal character in path at index 37: file:/Users/grant/Library/Application Support/IntelliJIdea13/clover-idea-3.2.1.jar java.lang.RuntimeException: java.net.URISyntaxException: Illegal character in path at index 37: file:/Users/grant/Library/Application Support/IntelliJIdea13/clover-idea-3.2.1.jar at com.cenqua.clover.idea.LibrarySupport.getCloverClassBase(LibrarySupport.java:150) {noformat} | 2 |
193 | CLOV-1408 | 01/13/2014 11:27:04 | As a developer I'd like to see JUnit Parameterized tests in the report | Similarly to the Spock framework (CLOV-1256) I'd like to see runtime test names from the JUnit4 parameterized tests. Example: {code:java} import org.junit.*; import org.junit.runner.*; import org.junit.runners.*; import java.util.*; import static org.junit.Assert.*; import static org.junit.runners.Parameterized.*; @RunWith(Parameterized.class) public class FibonacciTest { @Parameters public static Collection<Object[]> data() { return Arrays.asList(new Object[][] { { 0, 0 }, { 1, 1 }, { 2, 1 }, { 3, 2 }, { 4, 3 }, { 5, 5 },{ 6, 8 } }); } private int fInput; private int fExpected; public FibonacciTest(int input, int expected) { fInput= input; fExpected= expected; } @Test public void test() { assertEquals(fExpected, Fibonacci.compute(fInput)); } } class Fibonacci { static int compute(int a) { return a; } } {code} | 5 |
194 | CLOV-1409 | 01/13/2014 11:32:37 | Split velocity templates to 2 sets: adg and classic | make a copy of original templates extend HtmlReporter and add option to choose one of them, e.g.: HtmlReporter -style classic/adg ADG is the default one | 2 |
195 | CLOV-1410 | 01/13/2014 11:34:15 | Add report style=adg/classic options for Ant, Maven, Grails | scope: ant, maven, grails plugins new toggle, default adg, pass to HtmlReporter | 2 |
196 | CLOV-1411 | 01/13/2014 11:36:29 | Add radio button style=adg/classic in eclipse and idea IDEs | optional: add radio button in reports wizards alternatively: use the default one (ADG) | 1 |
197 | CLOV-1412 | 01/13/2014 13:40:43 | Use ADG-compliant colour set for widgets | Replace existing colours by those recommended by ADG: * https://developer.atlassian.com/design/latest/colors.html Scope: (/) tree map (/) cloud view (/) coverage bars (dashboard, package/class/file summary) (/) test results bars (dashboard, test results pages) (/) coverage markers on the page margin (/) class coverage distribution / class complexity diagrams (use "Blue" from ADG) (/) colours of hyperlinks | 1 |
198 | CLOV-1413 | 01/13/2014 14:13:48 | as a developer I expect that Clover will automatically configure IntelliJ IDEA compiler settings | Since IDEA12 a new external build feature has been introduced. It has also an option to perform parallel build (Settings > Compile > Build independent modules in parallel toggle), however Clover does not support parallel instrumentation (see CLOV-1284). Clover should automatically disable the parallel build toggle whenever compilation starts (it can notify about this fact by a baloon), otherwise it will throw various runtime exceptions during compilation. | 1 |
199 | CLOV-1415 | 01/15/2014 06:16:45 | The clover2:clover goal does not pass the sourcepath property to underlying <clover-report> task | *Original problem from the cloned issue:* {quote} Clover database contains FileInfo objects for every source file. One of FileInfo fields is an absolute path to given file. When database is written, it uses current platform file separator for file name ('\' for windows, '/' for Linux/MacOS). However, when database is read it interprets file name using again current platform file separator. As a consequence, when database is generated on Windows and report generated on Linux, it cannot resolve file name properly - it takes whole path as a single path segment, resulting in paths like: /path/from/report/generation/sourcepath/D:/path/from/instrumented/build/file.java As a consequence report generation does create html file containing source code with highlighted coverage. {quote} *Problem with the clover2:clover goal:* The clover2:clover call <clover-report> using a default report descriptor (which is located in the maven-clover2-plugin-X.X.X.jar/default-clover-report.xml). This report descriptor has a reporting defined like: {code:xml} <current outfile="${output}" summary="${summary}" charset="${charset}" title="${title}" titleAnchor="${titleAnchor}" span="${span}" alwaysReport="${alwaysReport}" showInnerFunctions="${showInnerFunctions}" showLambdaFunctions="${showLambdaFunctions}"> <format refid="clover.format"/> <testsources refid="test.sources"/> <columns refid="clover.columns"/> </current> {code} i.e. there is no <sourcepath> property. Possible fix #1: * add the <sourcepath> property * set it's value to a list of standard source roots, similarly as it's done for <testsources> tag _excerpt from the CloverReportMojo:_ {code:java} antProject.setProperty("testPattern", "**/src/test/**"); {code} _excerpt from the default-clover-report.xml:_ {code:xml} <fileset id="test.sources" dir="${projectDir}"> <include name="${testPattern}"/> </fileset> ... <testsources refid="test.sources"/> {code} so it could be like this: {code:java} antProject.setProperty("sourceRootsPattern", "**/src/test/*;**/src/main/*"); ... {code} (!) potential problem: build may have source roots different than src/test/xxx and src/main/xxx; in such case sources would not be found; it means that settings this <sourcepath> property should be optional; it could be done via boolean flag Possible fix #2: * add the <sourcepath> property to the clover2:clover goal * if it's not null then pass it's value to the <sourcepath> property in the <clover-report> goal in the report descriptor (!) potential problem: how developers could easily find all source roots in all modules in their maven project in order to pass it as the property? | 2 |
200 | CLOV-1419 | 01/15/2014 12:33:41 | change project/package statistics to the boxed component | Change this: !package_summary.png! Move it under a horizontal navigation (on overview tab for instance). Keep it as a boxed component (div grid). | 2 |
201 | CLOV-1420 | 01/15/2014 12:38:02 | change package and class list tables into TablesSortable | Change this (project summary, package summary): !package_and_class_list.png! into a sortable table like this: https://docs.atlassian.com/aui/latest/sandbox/# | 2 |
202 | CLOV-1423 | 01/15/2014 12:53:11 | change contributing tests table to TablesSortable etc | Change a table with contributing tests: !contributing_tests.png! To do: * table into TableSortable * "Show/hide tests" label into expander * "Select all/deselect all" labels into single master toggle * remember about highlighting of lines of code and class' methods in a table | 5 |
203 | CLOV-1424 | 01/15/2014 12:56:56 | change small class histogram into container | similarly as for coverage statistics put into a box: https://developer.atlassian.com/design/1.2/containers.html this: !small_histogram.png! | 1 |
204 | CLOV-1425 | 01/15/2014 12:59:44 | change dashboard boxes look | This: [^dashboard_boxes.png] should look like this: https://developer.atlassian.com/design/1.2/containers.html | 1 |
205 | CLOV-1426 | 01/15/2014 13:02:52 | change page footer look | This: [^page_footer.png] should look like this: https://developer.atlassian.com/design/1.2/page-footer.html | 1 |
206 | CLOV-1427 | 01/15/2014 13:08:54 | change cloud tabs | The "Package risks" and "Quick Wins" tabs: !cloud_tabs.png! should have an ADG tabs look: https://developer.atlassian.com/design/1.2/tabs.html | 1 |
207 | CLOV-1428 | 01/15/2014 13:18:27 | change classes/tests/results bottom left frame | Change this: !classes_tests_results.png! Scope: * add a title: https://developer.atlassian.com/design/1.2/typography.html * use tabs: https://developer.atlassian.com/design/1.2/tabs.html * use sortable table: https://developer.atlassian.com/design/1.2/tables.html | 2 |
208 | CLOV-1429 | 01/15/2014 13:20:57 | chage test result labels to lozenges | "pass" / "fail" / "error" test statuses shall be changed to Subtle lozenges: https://developer.atlassian.com/design/1.2/lozenges.html | 1 |
209 | CLOV-1431 | 01/17/2014 10:02:53 | JDK8 sources fail to compile when instrumented by Clover | See the attached comparison of original and instrumented code: [^unicode_decoding_error.png] A problem is as follows: * Clover has a UnicodeDecodingReader class which translates 6-letter character sequences "\uNNNN" into a single UTF16 character * this is used to correctly tokenize code identifiers (IDENT) written in non-ascii characters (a variable with German umlaut for instance) In this specific example, some "\uNNNN" sequences were translated inside comments, and some characters were "swallowed". So for instance a fragment: {noformat} {@code \u} {noformat} ends with "java: illegal unicode escape". Related issues: * CLOV-1305 - syntax highlighting problem * CLOV-1131 - Eclipse/IDEA editors get out of sync | 3 |
210 | CLOV-1432 | 01/20/2014 21:13:26 | Integration tests are not being instrumented in Grails 2.3 | Clover does not instrument integration tests in Grails 2.3. Caused by: * new GrailsIntegrationTestCompiler wrapper introduced in Grails 2.3.0 is not being recognized by Clover as a Groovy compiler * GrailsTestRunner calls Groovy compiler internally and this compiler does not have grover.jar on a classpath, thus Clover AST transformer is not called Todo: * check how to recognize/pass inclusion/exclusion patterns to the internal compiler of GrailsTestRunner Workaround: * not available | 3 |
211 | CLOV-1434 | 01/23/2014 14:49:46 | Transitive dependency resolution fails in Grails 2.3 during installation of the Clover plugin | Since Grails 2.3 sth has changed in the dependency resolution mechanism. As a consequence, when the Clover plugin is being installed for a first time, the transitive dependency to com.cenqua.clover:clover is not resolved and this jar is not available on class path. As a consequence build fails when it tries to import "cloverlib.xml". Workaround: define a dependency to com.cenqua.clover:clover in BuildConfig.groovy (or in pom.xml) - in the very same way as it was made in Clover-for-Grails 3.1.12 or older under the Grails 2.2. Fix: 1) reconfigure dependencies.groovy / pom.xml ? 2) roll back to a previous approach - i.e. merge clover-grails1 branch into default, produce one plugin version, rollback documentation | 1 |
212 | CLOV-1438 | 01/28/2014 07:30:42 | Create an API for plugging custom I/O handler | Currently Clover uses a standard Java IO/NIO libraries to read from and write to: a coverage database, coverage recording files (global and per-test), test optimization snapshots. This is not sufficient when user want to run an application on a custom file system, such as Apache HDFS. Provide an API which would allow to provide a custom IO handler. Scope: * writing coverage files (global and per-test) * reading/writing database (optional - we deal a lot with file channels which might be a problem; a growable coverage recorder can be used at runtime instead of this) * writing optimization snapshot (optional - not everyone uses test optimization) References: * https://answers.atlassian.com/questions/255286/does-clover-support-to-read-and-write-clover-db-and-coverage-recording-files-from-hdfs * https://answers.atlassian.com/questions/48360/how-can-i-get-functional-test-code-coverage-reports-for-mapreduce-program | 8 |
213 | CLOV-1441 | 01/30/2014 08:49:09 | Clover plugin doesn't load on IDEA 13 Startup | {noformat} null java.lang.NullPointerException at com.cenqua.clover.idea.LibrarySupport.getValidatedCloverLibrary(LibrarySupport.java:81) at com.cenqua.clover.idea.build.CloverLibraryInjector$1.run(CloverLibraryInjector.java:44) at com.intellij.openapi.application.impl.ApplicationImpl.runWriteAction(ApplicationImpl.java:997) at com.cenqua.clover.idea.build.CloverLibraryInjector.addCloverLibrary(CloverLibraryInjector.java:61) at com.cenqua.clover.idea.build.CloverLibraryInjector.updateModulesDependencies(CloverLibraryInjector.java:35) at com.cenqua.clover.idea.ProjectPlugin.projectPostStartup(ProjectPlugin.java:116) at com.cenqua.clover.idea.ProjectPlugin$1.run(ProjectPlugin.java:86) at com.intellij.ide.startup.impl.StartupManagerImpl$7.run(StartupManagerImpl.java:286) at com.intellij.ide.startup.impl.StartupManagerImpl.a(StartupManagerImpl.java:259) at com.intellij.ide.startup.impl.StartupManagerImpl.access$100(StartupManagerImpl.java:52) at com.intellij.ide.startup.impl.StartupManagerImpl$4.run(StartupManagerImpl.java:184) at com.intellij.openapi.project.DumbServiceImpl.a(DumbServiceImpl.java:238) at com.intellij.openapi.project.DumbServiceImpl.access$500(DumbServiceImpl.java:53) at com.intellij.openapi.project.DumbServiceImpl$IndexUpdateRunnable$1$3.run(DumbServiceImpl.java:420) at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:251) at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:733) at java.awt.EventQueue.access$200(EventQueue.java:103) at java.awt.EventQueue$3.run(EventQueue.java:694) at java.awt.EventQueue$3.run(EventQueue.java:692) at java.security.AccessController.doPrivileged(Native Method) at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:76) at java.awt.EventQueue.dispatchEvent(EventQueue.java:703) at com.intellij.ide.IdeEventQueue.e(IdeEventQueue.java:696) at com.intellij.ide.IdeEventQueue._dispatchEvent(IdeEventQueue.java:524) at com.intellij.ide.IdeEventQueue.dispatchEvent(IdeEventQueue.java:335) at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:242) at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:161) at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:150) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:146) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:138) at java.awt.EventDispatchThread.run(EventDispatchThread.java:91) {noformat} | 2 |
214 | CLOV-1442 | 01/30/2014 12:58:42 | Use more unique property names in clover.xml | The clover.xml contains the following properties: {code:xml} <property name="project.name" value="${ant.project.name}"/> <!-- By default, use the ant project name. --> <property name="project.title" value="${project.name}"/> <!-- If no title is set, use the project.name. --> <property name="test.target" value="test"/> <!-- The name of the target which runs the tests. --> {code} Their names are not very unique so there's some chance that developer could actually use similar ones in his project. This may lead to clash an Ant properties are not read-only once set. Use more distinct names, e.g. "clover.project.name". Update documentation on CAC accordingly. | 2 |
215 | CLOV-1443 | 01/31/2014 09:40:15 | Clover Grails Plugin fails when tests are launched from IDEA | Steps to reproduce: * import Grails-based project into IntelliJ IDEA * add Clover Grails plugin to the project * run *forked* tests from IDEA Build fails with an error like: {noformat} | Error Error running forked test-app: No such property: testNames for class: _Events (Use --stacktrace to see the full trace) | Error Forked Grails VM exited with error {noformat} Workaround: * disable forked test execution in IDEA Probable cause: IDEA does not call "grails test-app" but executes the GrailsScriptRunner, e.g.: {noformat} java -cp ... org.codehaus.groovy.grails.cli.support.GrailsStarter --main org.codehaus.groovy.grails.cli.GrailsScriptRunner {noformat} The most probably this runner does not import the _GrailsTest.groovy, which contains a definition of the testNames property. | 2 |
216 | CLOV-1446 | 02/07/2014 10:26:41 | Tree map report has an empty line in context menu | Open TreeMap report in IDEA, right click on a class, a context menu is opened which has an empty first line: !jump_to_source.png! | 2 |
217 | CLOV-1447 | 02/10/2014 08:30:10 | Add possibility to configure <profiles> in Eclipse and IDEA IDEs | The <clover-setup> and <clover-instr> tasks allow to define <profiles> section, where we can select coverage recorder type etc. There's no possibility to configure it in Clover-for-Eclipse and Clover-for-IDEA plugins. | 5 |
218 | CLOV-1448 | 02/10/2014 09:10:04 | Test spock under gradle | We don't support Gradle. However, it's worth checking how our Spock works (or not :-) ) with open-source gradle clover plugins available. To do: * prepare a sample app with a build.gradle script * integrate Clover into it using the https://github.com/bmuschko/gradle-clover-plugin * check if spock instrumentation works here * publish results on CAC as a developer guide | 3 |
219 | CLOV-1449 | 02/10/2014 09:15:26 | Test spock with XML importing | Test how the <clover-report> can be used together with: * Spock Spec classes with @Unroll * test results imported from an external XML file Purpose of test: * check if runtime test names recorded by Clover matches test names reported by Spock Outcome: * document whether it works (and how) or not | 2 |
220 | CLOV-1451 | 02/10/2014 09:38:11 | Fix uncheched warnings for code instrumented by Clover | Follow up of CLOV-1399: {quote} I tried it with 3.2.2 same issue for every instrumented class. [WARNING] /Users/kasperni/workspace/cake-container/cake-container/cake-container-api/target/clover/src-instrumented/org/cakeframework/container/RuntimeContainerException.java:[24,758] unchecked cast required: I found: java.lang.Object It is this generated line that generates the warning: return (I) java.lang.reflect.Proxy.newProxyInstance(l.getClass().getClassLoader(), l.getClass() .getInterfaces(), h); It can be solved by adding a @SuppressWarnings("unchecked") to the instrumented file: @SuppressWarnings("unchecked") public static <I, T extends I> I lambdaInc(final int i, final T l, final int si) {........} {quote} | 2 |
221 | CLOV-1455 | 02/17/2014 11:22:07 | ///Clover:OFF does not work with lambdas | The following piece of code fails to be instrumented {code:java} public class Foo { // /CLOVER:OFF public static void main(String[] args) { new ConcurrentHashMap<>().computeIfAbsent("foo", e -> null); } // /CLOVER:ON } {code} Results in [ERROR] /Users/kasperni/workspace/cake-container/cake-container/cake-container-impl/target/clover/src-instrumented/org/cakeframework/internal/container/handler/Foo.java:[28,58] cannot find symbol symbol: variable __CLR3_2_2133133hrrnhz2t location: class org.cakeframework.internal.container.handler.Foo | 2 |
222 | CLOV-1457 | 02/21/2014 18:56:58 | clover-for-grails plugin is not working with grails.project.fork | Hello, When I run the grails test-app command in grails 2.3.5. I get the following error: {noformat} Error running forked test-app: No such property: testNames for class: _Events groovy.lang.MissingPropertyException: No such property: testNames for class: _Ev ents at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptByteco deAdapter.java:50) at org.codehaus.groovy.runtime.callsite.PogoGetPropertySite.getProperty( PogoGetPropertySite.java:49) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callGroovyObjec tGetProperty(AbstractCallSite.java:231) at _Events$_run_closure3.doCall(_Events.groovy:75) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.springsource.loaded.ri.ReflectiveInterceptor.jlrMethodInvoke(Refl ectiveInterceptor.java:1254) at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java: 90) at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:233) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1086) at groovy.lang.ExpandoMetaClass.invokeMethod(ExpandoMetaClass.java:1110) {noformat} | 2 |
223 | CLOV-1459 | 02/27/2014 21:46:00 | native2ascii error converting i18n bundles for plugin | When running with -clover.on in our CI environment (TeamCity), we are getting a weird error: Error native2ascii error converting i18n bundles for plugin [xxxx] java.lang.reflect.InvocationTargetException It's not constrained to a single plugin, typically it lists different plugins. The full stack trace is: {code} [15:28:49][Step 4/8] | Error native2ascii error converting i18n bundles for plugin [spring-security-core-1.2.7.3] java.lang.reflect.InvocationTargetException [15:28:49][Step 4/8] | Error Error executing script TestApp: : java.lang.reflect.InvocationTargetException (NOTE: Stack trace has been filtered. Use --verbose to see entire trace.) [15:28:49][Step 4/8] : java.lang.reflect.InvocationTargetException [15:28:49][Step 4/8] at org.codehaus.gant.GantBuilder.invokeMethod(GantBuilder.java:99) [15:28:49][Step 4/8] at _GrailsTest_groovy$_run_closure1.doCall(_GrailsTest_groovy:102) [15:28:49][Step 4/8] at org.codehaus.gant.GantMetaClass.invokeMethod(GantMetaClass.java:133) [15:28:49][Step 4/8] at org.codehaus.gant.GantBinding$_initializeGantBinding_closure5_closure16_closure18.doCall(GantBinding.groovy:185) [15:28:49][Step 4/8] at org.codehaus.gant.GantBinding$_initializeGantBinding_closure5_closure16_closure18.doCall(GantBinding.groovy) [15:28:49][Step 4/8] at org.codehaus.gant.GantBinding.withTargetEvent(GantBinding.groovy:90) [15:28:49][Step 4/8] at org.codehaus.gant.GantBinding.this$4$withTargetEvent(GantBinding.groovy) [15:28:49][Step 4/8] at org.codehaus.gant.GantBinding$_initializeGantBinding_closure5_closure16.doCall(GantBinding.groovy:185) [15:28:49][Step 4/8] at org.codehaus.gant.GantBinding$_initializeGantBinding_closure5_closure16.doCall(GantBinding.groovy) [15:28:49][Step 4/8] at org.codehaus.gant.GantMetaClass.invokeMethod(GantMetaClass.java:133) [15:28:49][Step 4/8] at TestApp$_run_closure1.doCall(TestApp:32) [15:28:49][Step 4/8] at org.codehaus.gant.GantMetaClass.invokeMethod(GantMetaClass.java:133) [15:28:49][Step 4/8] at org.codehaus.gant.GantBinding$_initializeGantBinding_closure5_closure16_closure18.doCall(GantBinding.groovy:185) [15:28:49][Step 4/8] at org.codehaus.gant.GantBinding$_initializeGantBinding_closure5_closure16_closure18.doCall(GantBinding.groovy) [15:28:49][Step 4/8] at org.codehaus.gant.GantBinding.withTargetEvent(GantBinding.groovy:90) [15:28:49][Step 4/8] at org.codehaus.gant.GantBinding.this$4$withTargetEvent(GantBinding.groovy) [15:28:49][Step 4/8] at org.codehaus.gant.GantBinding$_initializeGantBinding_closure5_closure16.doCall(GantBinding.groovy:185) [15:28:49][Step 4/8] at org.codehaus.gant.GantBinding$_initializeGantBinding_closure5_closure16.doCall(GantBinding.groovy) [15:28:49][Step 4/8] at gant.Gant$_dispatch_closure5.doCall(Gant.groovy:381) [15:28:49][Step 4/8] at gant.Gant$_dispatch_closure7.doCall(Gant.groovy:415) [15:28:49][Step 4/8] at gant.Gant$_dispatch_closure7.doCall(Gant.groovy) [15:28:49][Step 4/8] at gant.Gant.withBuildListeners(Gant.groovy:427) [15:28:49][Step 4/8] at gant.Gant.this$2$withBuildListeners(Gant.groovy) [15:28:49][Step 4/8] at gant.Gant$this$2$withBuildListeners$0.callCurrent(Unknown Source) [15:28:49][Step 4/8] at gant.Gant.dispatch(Gant.groovy:415) [15:28:49][Step 4/8] at gant.Gant.this$2$dispatch(Gant.groovy) [15:28:49][Step 4/8] at gant.Gant.invokeMethod(Gant.groovy) [15:28:49][Step 4/8] at gant.Gant.executeTargets(Gant.groovy:591) [15:28:49][Step 4/8] at gant.Gant.executeTargets(Gant.groovy:590) [15:28:49][Step 4/8] at org.grails.wrapper.GrailsWrapper.main(GrailsWrapper.java:93) [15:28:49][Step 4/8] Caused by: java.lang.reflect.InvocationTargetException [15:28:49][Step 4/8] ... 30 more [15:28:49][Step 4/8] Caused by: java.util.ConcurrentModificationException [15:28:49][Step 4/8] at com.atlassian.clover.ant.groovy.GroovycSupport.logGroovycTasks(GroovycSupport.java:102) [15:28:49][Step 4/8] at com.atlassian.clover.ant.groovy.GroovycSupport.taskStarted(GroovycSupport.java:123) [15:28:49][Step 4/8] at org.apache.tools.ant.Project.fireTaskStarted(Project.java:2184) [15:28:49][Step 4/8] ... 30 more [15:28:49][Step 4/8] | Error Error executing script TestApp: : java.lang.reflect.InvocationTargetException [15:28:50][Step 4/8] Process exited with code 1 {code} Running without "-clover.on" removes this problem. | 2 |
224 | CLOV-1462 | 03/12/2014 20:20:22 | ClassNotFoundException when running tests in IDEA 13.1 RC with Clover enabled | Install IDEA 13.1 RC and Clover 3.2.2. Load Java project. Create a run configuration for JUnit, select "Test kind: All in package", select "Before launch: Make". Run tests with Clover disabled - all tests are executed. Run tests with Clover enabled - all tests are executed, but after second and next runs - ClassNotFoundException on a test class occurs. | 2 |
225 | CLOV-1466 | 03/21/2014 00:29:26 | Several tests fail with Cannot cast object ... to class 'com_cenqua_clover.CoverageRecorder' | See here for a travis build exhibiting this problem: https://travis-ci.org/thehyve/transmart-core-db/jobs/21220075 19 tests there fail because of this problem. The culprit seems to be this line: https://github.com/thehyve/transmart-core-db/blob/5e8f0400b9ddce75e1d3d2adccf747e42bff3ee6/src/groovy/org/transmartproject/db/dataquery/clinical/TerminalConceptVariablesTabularResult.groovy#L39 | 3 |
226 | CLOV-1467 | 03/26/2014 10:45:00 | Rename com.cenqua to com.atlassian | Rename all references to "Cenqua" to "Atlassian". It affects: * java packages - com.cenqua.* and com_cenqua_clover (/) * Clover-for-Eclipse plugins and features (/) * com.cenqua.clover:clover artifact (clover core) (/) Optional: Rename also Clover-for-Maven plugin from 'maven-clover2-plugin' to 'clover-maven-plugin'. (x) The maven plugin will not be renamed. Reason? Typing 'mvn clover:setup' in a project where clover-maven-plugin is not explicitly defined in pom.xml causes that Maven resolves the 'clover:setup' as 'com.atlassian.maven.plugins:maven-clover-plugin:maven-plugin:3.7' which is wrong. So it will be very confusing for customers. | 3 |
227 | CLOV-1469 | 03/27/2014 10:03:03 | Maven plugin sholud handle target/generated-test-sources | The AbstractInstrumenter recognizes only the target/generated-sources path: {code:java} private boolean isGeneratedSourcesDirectory(final String sourceRoot) { String generatedSrcDirDefaultLifecycle = File.separator + "target" + File.separator + "generated-sources"; String generatedSrcDirCloverLifecycle = File.separator + "target" + File.separator + "clover" + File.separator + "generated-sources"; return sourceRoot.indexOf(generatedSrcDirDefaultLifecycle) != -1 || sourceRoot.indexOf(generatedSrcDirCloverLifecycle) != -1; } {code} It shall also detect the target/generated-test-sources. | 1 |
228 | CLOV-1470 | 03/27/2014 22:59:00 | Maven clover2:setup ignores generated sources | We have several maven projects that contain only generated sources (target/generated-sources/...). The default source directory does not exist for those projects. clover2:setup does not work properly for those projects: the generated sources do not get compiled. We currently work around the issue by creating a marker file in the default source directory. | 1 |
229 | CLOV-1471 | 03/27/2014 23:02:11 | Maven clover2:setup triggers duplicate class exception | We have several maven projects that have more than one source directory. The non-default directories are added using the build-helper plugin. The clover2:setup goal instruments all source folders, but then sets all non-generated directories as source folders on the maven project. That results in compile errors, since source files are both present in the clover instrumented sources and original location. Example: java/src << 1. default source folder java/src-build << 2. additional source folder target/generate-sources/jaxb << 3. generated source folder Case (2) is causing problems. | 3 |
230 | CLOV-1478 | 03/31/2014 10:42:08 | Double instrumentation error when running 'mvn site' on JDK8 | Run 'mvn clean site' on the src/it/setTestFailureIgnore project using the JDK8 and Maven 2.2.1. It fails with an error: {noformat} [INFO] Processing files at 1.8 source level. [INFO] Instrumentation error com.atlassian.clover.api.CloverException: Double instrumentation detected: f:\Work\release\release-maven-clover2-plugin-hg\src\it\setTestFailureIgnore\target\clover\src-instrumented\com\atlassian\maven\plugin\clover\samples\setTestFailureIgnore\Simple.java appears to have already been instrumented by Clover. at com.atlassian.clover.instr.java.CloverTokenStreamFilter.guardAgainstDoubleInstrumentation(CloverTokenStreamFilter.java:66) ... {noformat} The same site goal works correctly under JDK7. | 1 |
231 | CLOV-1481 | 04/10/2014 13:30:51 | Invalid instrumentation code for test methods inside anonymous inline classes | Clover generates incorrect reference to the static field __CLR3_2_2_TEST_NAME_SNIFFER in case when a test method is declared inside an inner (static or non-static) or inside an anonymous inline class, which are located inside a non-test top-level class. In such case, the top-level class doesn't have the __CLR3_2_2_TEST_NAME_SNIFFER field (as it's not a test class), but inner/inline classes (which are test ones) are trying to access this field. {noformat} [clover] 2 test methods detected. [javac] ---------- [javac] 1. ERROR in ... [javac] public boolean test() {__CLR3_2_262c962c9htee2hlb.R.globalSliceStart(getClass().getName(),284284);int $CLV_p$=0;java.lang.Throwable $CLV_t$=null;try {boolean $CLV_r$=__CLR3_2_2qua64563cs();$CLV_p$=1;return $CLV_r$;} catch(java.lang.Throwable $CLV_t2$){if($CLV_p$==0&&$CLV_t$==null){$CLV_t$=$CLV_t2$;}_CLR3_2_262c962c9htee2hlb.R.rethrow($CLV_t2$);return false;}finally{CLR3_2_262c962c9htee2hlb.R.globalSliceEnd(getClass().getName(),"com.xyz.RuntimeDebugger.SaveTestCaseAction.getDefaultAvailablePredicate.test",CLR3_2_2_TEST_NAME_SNIFFER.getTestName(),284284,$CLV_p$,$CLV_t$);}}private boolean __CLR3_2_2qua64563cs(){_CLR3_2_262c962c9htee2hlb.R.inc(284284); [javac] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [javac] __CLR3_2_2_TEST_NAME_SNIFFER cannot be resolved [javac] ---------- [javac] 1 problem (1 error) {noformat} Code example: {code:java} public class SnifferInInnerAndInline { interface TestAction { boolean test(); } static class InnerStaticTest { public void testInnerStatic() { // FAILS HERE } } class InnerTest { public void testInnerNonStatic() { // FAILS HERE } } TestAction testWithInline() { return new TestAction() { public boolean test() { // FAILS HERE (assuming that we have a custom test pattern which matches it) return true; } }; } public static void main(String[] args) { new SnifferInInnerAndInline.InnerStaticTest().testInnerStatic(); new SnifferInInnerAndInline().new InnerTest().testInnerNonStatic(); new SnifferInInnerAndInline().testWithInline().test(); } } {code} | 2 |
232 | CLOV-1486 | 04/14/2014 13:34:18 | change historical report | scope: header, footer, tables with "added" and "movers", optionally, put charts in some boxes | 1 |
233 | CLOV-1490 | 04/18/2014 19:30:45 | Clover safeEval method is imcompatible with Groovy's @CompileStatic annotation | When trying to use Clover on a Groovy class that is marked @CompileStatic and it contains a null-safe operator (e.g. Bar bar = foo?.bar), then the groovyc compilation fails with the error: No such property: bar for class: java.lang.Object The error is that the generated {code}$CLV_safeEval${code} method returns an Object instead of the type of the property. This then causes Groovy compiler to fail later. I've created a sample project that exhibits the problem at https://github.com/johnrengelman/clover-grooyv-compilestatic Simply run {code}./gradlew test{code} | 3 |
234 | CLOV-1492 | 04/30/2014 21:45:56 | Grails' controller methods are not shown as entered | Hello, For some reason the method in a controller is marked as not entered even though the content inside is shown to be executed. Please can you help me rationalize/ understand this? Please refer to me screenshots: index_method_not_executed.png: to see that the index() method is not executed even though its contents are. test_for_index_method.png: the test that is run to get the method to run. | 3 |
235 | CLOV-1496 | 05/15/2014 11:29:08 | reduce html report size | As a developer I'd like to have small HTML report size in order to reduce disk space consumption, especially in case of builds on CI server. Possible ways to reduce report size: 1) extract list of packages to separate JSON file and load it dynamically using JS function (instead of embedding it on virtually every page) (/) DONE 2) use some html compression utility (which would strip all whitespace etc) https://code.google.com/p/htmlcompressor/#Compressing_selective_content_in_Velocity_templates (x) performance of the HtmlCompressor is unacceptable (+340% time) 3) remove whitespace from most frequent loops from velocity templates (/) DONE | 3 |
236 | CLOV-1497 | 05/27/2014 08:49:19 | improve report accessiblity | http://www.w3.org/TR/wai-aria-practices/#TreeView | 3 |
237 | CLOV-1498 | 05/28/2014 22:27:42 | improve navigation between report entities | We can navigate vertically and horizontally, but on a file level we've got a break: {noformat} project - dashboard | app | test | results | clouds | treemap v package - app | test | results | clouds | +--------------------------------------------------+ v v file - classes | contr tests | methods test class v test {noformat} fix it so that we can jump from test file to test results for a file fix it so that we have one "source" tab for a file -> put 'classes and methods' and 'contributing tests' into expandable tables, dialogs etc | 3 |
238 | CLOV-1500 | 06/09/2014 10:50:15 | implement global search in the html report - backend | Implement search box in a blue app header. Generate JSON data: * packages, files, classes, methods, tests Split into several indexes (for smaller file size) as theoretical size is up to 40MB (200'000 objects per 200 chars). Add "automatic" option (up to 10'000 elements). (/) Add options for: <clover report>/<current>/<format>/<globalSearch scope="package,file,class,method,test|auto" limit="10000"/> (/) Add option for HtmlReporter: --globalSearchScope=package,file,class,method,test|auto --globalSearchLimit=10000 to choose which elements shall be searchable. | 3 |
239 | CLOV-1502 | 06/10/2014 10:57:03 | tree view is not compacted properly when only 1 package is present | !tree_view_bug.png! We have com.cenqua + samples.money instead of exactly one (root) node named "com.cenqua.samples.money". | 1 |
240 | CLOV-1503 | 06/11/2014 12:49:08 | provide explanation when number of files is greater than number of classes for a package | There might be a case that number of files > number of classes listed: !more_files_than_classes.png! This is normal behaviour, because by default Clover hides entities having no executable code, such as: empty classes, enums (with no methods), interfaces (with no virtual extension methods). However, this may be confusing for end user. How we could improve this: 1) Set the showEmpty to true by default. Benefit: 'classes >= files' in all cases. Drawback: report will contain unnecessary noise. 2) Add [(?) Help] button above the table. Example: !package_help.png! 3) Add tooltip for 'Files' (TotalElements.getHelp()) 4) Add small text below the class table. For example: "3 classes are not listed because they contain no executable code." | 1 |
241 | CLOV-1505 | 06/16/2014 15:16:11 | replace a vertical navigation component by a sidebar | Instead of the aui-vertical-nav use the aui-sidebar component. | 3 |
242 | CLOV-1508 | 06/25/2014 14:57:58 | Upgrade HTML report to ADG 2.2+ / AUI 5.9+ | Upgrade AUI library to the latest version. We may need to make some corrections of CSS to be compatible (probably: colors, shadows, notification messages). | 2 |
243 | CLOV-1509 | 06/25/2014 21:50:49 | as a developer I'd like to have nanosecond precision for test duration | In reports lots of tests have duration = 0. This is because unit tests are fast and the System.currentTimeMillis() is used to record start and end time of a test. Which is not precise by design. We could increase precision to nanoseconds using System.nanoTime(). Note: we'd still need to call System.currentTimeMillis() to record datetime when test was run. | 3 |
244 | CLOV-1510 | 07/01/2014 13:20:30 | Remove "See more" links from the report dashboard | for: * Most complex packages * Most complex classes * Least tested methods * Class Coverage Distribution * Class Complexity | 0.5 |
245 | CLOV-1511 | 07/01/2014 13:24:41 | "Show contributing test" change to ... | "<a>Select tests</a> to highlight the code coverage" or something similar | 0.5 |
246 | CLOV-1512 | 07/09/2014 09:56:33 | The "Show methods" link does not open the modal dialog | This happens for inner classes (i.e. when a class name contains ".") May be caused by a way how Modal Dialog handles element id. | 1 |
247 | CLOV-1514 | 07/10/2014 10:56:18 | tool tips in dashboard widgets shall not be displayed on the right | Tool tips are by default placed on the right, so they don't fit in the 'Clover Dashboard' view: !screenshot-1.png! | 1 |
248 | CLOV-1515 | 07/11/2014 08:59:51 | use ADG fonts and colours in Cloud View in IDEA | The ADG HTML report in Clover 4 uses new colour set (shades of red instead of blue-red) for tag clouds. The Clover-for-Eclipse has this theme: [^cloud_view_eclipse.png] but the Clover-for-IDEA still uses the old colour set: [^cloud_view_idea.png] | 1 |
249 | CLOV-1517 | 07/18/2014 08:14:04 | AntIntegrator adds unnecessary double quotes for -Dparam=value JVM options | Class com.atlassian.clover.ci.AntIntegrator puts values of the following properties: -Dclover.historydir and -Dclover.license.cert, -Dclover.license.path in double quotes. On Windows platform it causes problems when a value contains space character - parameters are being split. See BAM-10740. Add a check if OS is Windows and don't add double quotes in such case. | 1 |
250 | CLOV-1518 | 07/21/2014 11:01:54 | implement global search in the html report - frontend | Implement search box in blue app header. Generate JSON data: * packages, files, classes, methods, tests Split into several indexes (for smaller file size) as theoretical size is up to 40MB (200'000 objects per 200 chars). Add "automatic" option (up to 10'000 elements). Add options for <clover report> <index scope="package, file, ..., method | auto"> to choose which elements shall be searchable. | 5 |
251 | CLOV-1526 | 07/28/2014 09:54:35 | View latest Clover information (BAM-14428) | See BAM-14428. | 5 |
252 | CLOV-1527 | 07/28/2014 09:56:10 | Clover tab with an HTML report generated by Clover 4 shall have a vertical scroll bar (BAM-14777) | See BAM-14777. | 1 |
253 | CLOV-1534 | 08/11/2014 09:45:08 | Move CloverCompilerAdapter out from org.apache.tools.ant.taskdefs package | The org.apache.tools.ant.taskdefs.CloverCompilerAdapter may cause conflicts with Apache Ant packaged as OSGI bundle which exports the same package. Possible fix: (x) The Javac.getFileList() is a getter for compileList. Try using it - we must ensure that compileList and replacementCompileSet have the same size or (/) Use reflections to access the package-protected field. Thanks to this we could move CloverCompilerAdapter to com.atlassian.clover package. | 1 |
254 | CLOV-1538 | 08/13/2014 13:37:01 | Instrumenting assignment of method reference to field results in reference to undefined symbol. | Instrumenting the following snippet results in the compilation error [ERROR] clover/src-instrumented/Test.java:[2,18] cannot find symbol [ERROR] symbol: variable __CLR3_3_000hysmxbbd [ERROR] location: class Test Source: public class Test { Runnable r = System::currentTimeMillis; } Instrumented code: /* $$ This file has been instrumented by Clover 3.3.0#2014033113020816 $$ */public class Test { Runnable r = __CLR3_3_000hysmxbbd.lambdaInc(0,System::currentTimeMillis,1); } | 2 |
255 | CLOV-1546 | 08/21/2014 09:30:19 | Resolve path to clover.jar when packed as OSGI bundle | ClassPathUtil.getCloverJarPath() searches for a JAR in case when URL returned by class loader is like: {noformat} jar:file:!/path/to/clover.jar/com/atlassian/clover/util/ClassPathUtil.class {noformat} or {noformat} file:/path/to/classes/directory/com/atlassian/clover/util/ClassPathUtil.class {noformat} However, it does not handle a case for OSGI bundles, which have an URI like: {noformat} bundle://28.0:2/com/atlassian/clover/util/ClassPathUtil.class {noformat} Fix: use getClass().getProtectionDomain().getCodeSource().getLocation().toURI() | 1 |
256 | CLOV-1547 | 08/21/2014 19:57:52 | The Grails' @Transactional annotation conflicts with Clover's AST transformations | The @Transactional annotation is the new Grails-y way of controlling transactional behavior in a service. It uses an AST transformation to essentially wrap public methods (if added to the class) in a GrailsTransactionTemplate. So you get code that looks like this: {code:java} public void reject(Invoice invoice) { Reference invoice = new Reference(invoice); CallSite[] arrayOfCallSite = $getCallSiteArray(); GrailsTransactionAttribute $transactionAttribute = (GrailsTransactionAttribute)ScriptBytecodeAdapter.castToType(arrayOfCallSite[9].callConstructor(GrailsTransactionAttribute.class), GrailsTransactionAttribute.class); GrailsTransactionTemplate $transactionTemplate = (GrailsTransactionTemplate)ScriptBytecodeAdapter.castToType(arrayOfCallSite[10].callConstructor(GrailsTransactionTemplate.class, this.transactionManager, $transactionAttribute), GrailsTransactionTemplate.class); $transactionTemplate.execute(new _reject_closure5(this, invoice)); } {code} The real body of the method is in the reject_closure5, which ends up calling a method named "$tt_reject(...)". Clover doesn't realize that the code originally under the reject method has essentially been relocated to the $tt__reject method. Given that @Transactional is a core part of Grails (starting in 2.3, I believe) and the recommended way to control transactions going forward, this is probably something that should be addressed in Clover core. | 3 |
257 | CLOV-1552 | 09/15/2014 09:55:47 | Upgrade FastUtil library to version 6.5.2 or later | API was changed since version 4.4.3, some methods used by Clover are missing and there's no direct replacement for them. Migrate Clover's code. | 3 |
258 | CLOV-1553 | 09/15/2014 10:02:16 | Upgrade Atlassian Extras to 3.2.x | API has changed in Atlassian Extras 3.x vs 2.5. There's no LicenseManagerFactory.getLicenseManager() We can compose our own license manager and decoder using: Version1LicenseDecoder + Version2LicenseDecoder + DelegatingLicenseDecoder + CloverProductLicenseFactory + DefaultLicenseManager However, there are problems with decoding the "Clover Desktop" license = the CloverLicenseTest.testDesktopLicense fails. Investigate: * maybe Clover Desktop license format has changed? * or maybe overlooked by atlassian-extras developers? * or ... ? | 3 |
259 | CLOV-1554 | 09/15/2014 11:26:16 | Replace iText library | Replace current iText 2.0.1 library by: * a commercial version of iText 5.x or * a PDFBox (http://pdfbox.apache.org) or other tool based on a good open-source license (Apache 2.0, MIT, BSD, PD). | 5 |
260 | CLOV-1559 | 10/01/2014 12:02:11 | Create Bitbucket Connect Clover Plugin | Bitbucket - Dan Bennett (Team Lead) - Investigate the creation of a Connect plugin to expose Clover functionality in Bitbucket diff & file viewer (same as Stash functionality) | 40 |
261 | CLOV-1561 | 10/07/2014 11:19:20 | Distributed Coverage does not work due to java.rmi.UnmarshalException | {noformat} Received result: Remote_Stub[UnicastRef2 [liveRef: [endpoint:[192.168.157.181:11 98,clover.gnu.cajo.invoke.Remote$RCSF@732e103d](remote),objID:[-26c3f6bf:148ea10 98a9:-7ffb, -3801964032288496245]]]] Started proxy: Thread-9 cutOff(java.rmi.UnmarshalException: error unmarshalling return; nested exception is: java.io.WriteAbortedException: writing aborted; java.io.NotSerializableE xception: com.atlassian.clover.ErrorInfo); from: localhost:1198. Attempting to r econnect. {noformat} | 1 |
262 | CLOV-1567 | 10/09/2014 11:53:15 | Test optimization in IDEA 14 shows wrong number of classes | There are 2 test classes in the 'Moneybags' tutorial project. Running test optimization in IDEA 14 (EAP build 138.2458.8) shows "3 test classes". !idea14_clover_test_optimization.png! | 2 |
263 | CLOV-1568 | 10/13/2014 09:41:20 | An orphaned lozenge when there are no search results | !html_adg_orphaned_lozenge.png! | 1 |
264 | CLOV-1569 | 10/13/2014 09:48:15 | A wrong caption in a search box in an HTML ADG report | !search_box_wrong_caption.png! | 1 |
265 | CLOV-1570 | 10/13/2014 09:50:02 | A historical report contains link to an XML report | !wrong_links_in_a_historical_report.png! | 1 |
266 | CLOV-1571 | 10/13/2014 11:28:16 | Upgrade third party libraries used by Clover - 2nd phase | Upgrade third party libraries to their latest versions: * Antlr 4.0, including java.g syntax file (x) tracked in CLOV-1329, CLOV-1331 and CLOV-1332 * atlassian-extras 3.2 (x) tracked in CLOV-1553 * cajo 1.175 * commons-lang3 3.3.2 (x) * fastutil 6.5.2 (x) tracked in CLOV-1552 * GSON 2.2.2 * JDOM 2.0.4 * JSON - replace by com.google.code.gson:gson Upgrade feasibility to be verified: * theJIT * KTreeMap/JTreeMap Get rid of: * Overlibvms (x) not until we drop Classic reports (Clover 4.1) * Utils.js (x) not until we drop Classic reports (Clover 4.1) * iText (x) tracked in CLOV-1554 To be considered: * upgrade Log4j to or 2.0.x | 8 |
267 | CLOV-1584 | 11/15/2014 11:53:31 | Add additional logging for <clover-setup>/<files> element | Currently, when <clover-setup> contains a <fileset> element, Clover prints information about included/excluded files (on a verbose logging level). In <clover-setup> we can also use a similar <files> element - but there's no logging for it. Add logging on a verbose level. | 1 |
268 | CLOV-1588 | 11/27/2014 10:47:57 | Integrate Clover with JUnitParams | The JUnitParams (https://github.com/Pragmatists/junitparams) is much more convenient way to parameterize tests instead of using JUnit's 4.10 @Parameterized annotation. | 5 |
269 | CLOV-1595 | 12/27/2014 12:20:56 | Clover does not work with Grails 2.4.4 | When developers use "./grailsw run-app" it gives the following error. {noformat} Running Grails application Error Error loading event script from file [/opt/stanson/target/work/plugins/clover-4.0.2/scripts/_Events.groovy] startup failed: /opt/stanson/target/work/plugins/clover-4.0.2/scripts/_Events.groovy: 4: unable to resolve class org.codehaus.groovy.grails.test.GrailsTestTargetPattern @ line 4, column 1. import org.codehaus.groovy.grails.test.GrailsTestTargetPattern ^ 1 error (Use --stacktrace to see the full trace) {noformat} | 3 |
270 | CLOV-1596 | 12/27/2014 13:07:04 | Use heuristics to solve JDK8 Stream compilation errors | Spike in which a problem with Java8 streams will be attacked as it seems that using stream() is very popular and the most probably it causes the majority of compilation problems with Clover's lambdaInc(). Scope: focus on streams only. Out of scope: attacking a generic problem of method signatures with a mixture of functional and non-functional arguments. | 13 |
271 | CLOV-1597 | 12/27/2014 13:10:04 | Set instrumentLambda=none as a default value for instrumentation | This is a temporary workaround thanks to which java8 code will always compile, at the cost that lambdas are not measured. User will be still able to enable lambda instrumentation, but this will be a conscious decision, so seeing compilation errors should be less surprising. Scope: CloverInstr, ant, maven, idea, eclipse, grails plugins. | 1 |
272 | CLOV-1603 | 01/07/2015 03:32:39 | CloverOptimizedTestNGSelector does not add "clover-optimized" group to TestNG @Before and @After annotations | In order for Clover to optimize a TestNG test suite, we have to use the {{CloverOptimizedTestNGSelector}} listener, and restrict TestNG to only run the "clover-optimized" group, as in: {code:xml|title=build.xml snippet} <testng groups="clover-optimized" listeners="com.atlassian.clover.ant.tasks.testng.CloverOptimizedTestNGSelector" > <!-- ... --> </testng> {code} The problem with this is that TestNG's {{@Before}} and {{@After}} annotations ({{@BeforeMethod}}, {{@AfterClass}}, etc) will not be run, because they are not part of the "clover-optimized" group. I have a workaround, which is to qualify all such annotations with {{alwaysRun=true}}, but this is pretty ugly. A possible solution is for {{CloverOptimizedTestNGSelector}} to implement {{IAnnotationTransformer2}} and override [transform( IConfigurationAnnotation, Class, Constructor, Method )|http://testng.org/javadoc/org/testng/IAnnotationTransformer2.html#transform%28org.testng.annotations.IConfigurationAnnotation,%20java.lang.Class,%20java.lang.reflect.Constructor,%20java.lang.reflect.Method%29], automatically adding the "clover-optimized" group to all non-tests. | 1 |
273 | CLOV-1605 | 01/09/2015 11:15:27 | Replace clover.licenseLocation by maven.clover.licenseLocation | While it's perfectly fine to have a declaration like this: {code:xml} <properties> <clover.licenseLocation>clover.license</clover.licenseLocation> </properties> {code} and next refer it in maven-clover2-plugin's configuration like this: {code:xml} <configuration> <licenseLocation>${clover.licenseLocation}</licenseLocation> </configuration> {code} it's misleading for users, because in case they would like to pass it via -D parameter or declare in settings.xml without having the <licenseLocation> in maven-clover2-plugin section, it will not work, because the correct property name is 'maven.clover.licenseLocation'. See: https://docs.atlassian.com/maven-clover2-plugin/latest/setup-mojo.html#licenseLocation Correct all references in documentation on confluence.atlassian.com, answers.atlassian.com, maven-clover2-plugin source code, tutorial source code. | 1 |
274 | CLOV-1606 | 01/09/2015 12:03:45 | Java8: method reference to a non-static method fails to compile | {quote} *NOT REPRODUCIBLE* {quote} In this code sample: {code:java} return map.entrySet().stream() .collect(Collectors.toMap( Map.Entry::getKey, e -> e.getValue().getAverage() )); {code} the Collectors.toMap() takes a "Map.Entry::getKey" method reference as input argument. However, the getKey method is not static. Wrapping it by Clover's lambdaInc() method leads to a compilation error like this: {noformat} [javac] symbol: method lambdaInc(int,Map.Entry::getKey,int) [javac] location: class __CLR4_0_22ci2cii4lxhoaj [javac] Foo.java:33: error: invalid method reference [javac] __CLR4_0_22ci2cii4lxhoaj.lambdaInc(3045,Map.Entry::getKey,3046), [javac] ^ [javac] non-static method getKey() cannot be referenced from a static context [javac] where K is a type-variable: [javac] K extends Object declared in interface Entry {noformat} *Possible workarounds ??* 1) Disable instrumentation of expression-like lambda functions (method references are treated as expression-like lambda) - use instrumentLambda="block" or "none". 2) Wrap such method reference with ///CLOVER:OFF and ///CLOVER:ON keywords, e.g.: {code:java} return map.entrySet().stream() .collect(Collectors.toMap( ///CLOVER:OFF Map.Entry::getKey, ///CLOVER:ON e -> e.getValue().getAverage() )); {code} 3) Use a variable with a non-static method reference or change to a lambda expression. {code:java} return map.entrySet().stream() .collect(Collectors.toMap( e -> e.getKey(), // unfortunately IDEA suggests to change it back e -> e.getValue().getAverage() )); {code} | 3 |
275 | CLOV-1607 | 01/14/2015 10:20:40 | Java8: don't instrument lambda functions when source < 1.8 | No matter what "-source" value is set, Clover instruments both expression-like and block-like lambdas. It's a behaviour slightly different from the one we have for e.g.: * -source 1.3 (it handles 'assert' as not a keyword) or * -source 1.4 (no 'enums'). Ways to improve it: 1) change Java grammar so that handling lambda functions is optional - only for source >= 1.8; otherwise Clover should throw a parse error 2) or parse lambdas also for source < 1.8 (no parse errors would be thrown, only javac will raise a compilation error), but do not add Clover's instrumentation to it {code:java} private LambdaBlockEntryEmitter instrEnterLambdaBlock(MethodSignature lambdaSignature, CloverToken leftCurly) { if (cfg.getInstrumentLambda() == LambdaInstrumentation.ALL || cfg.getInstrumentLambda() == LambdaInstrumentation.BLOCK /* add source level check*/ ) { ... {code} | 1 |
276 | CLOV-1608 | 01/17/2015 13:13:37 | New colour scheme for a tag cloud and a coverage treemap in the HTML report | Customers reported that using a single, red color gradient in a coverage tree map and in tag clouds has two drawbacks: * it's harder to find which code areas require improvement * seeing always a red color is discouraging :-) | 2 |
277 | CLOV-1612 | 01/27/2015 12:53:14 | Clover fails to generate HTML report for more than one project in Eclipse | {noformat} Clover Version 4.0.3, built on January 27 2015 (build-dev) Loaded from: D:\Soft\Eclipse\eclipse-4.4-luna\plugins\com.atlassian.clover.eclipse.core_4.0.3.v20150127120908-dev.jar Clover: Developer License registered to Atlassian. [C:/Users/Marek/.workspace-eclipse-4.4/Moneybags/.clover/coverage.db, 0 seconds"C:/Users/Marek/.workspace-eclipse-4.4/javasyntax18/.clover/coverage.db, 0 seconds--report, --testsIncludePattern, C:/Users/Marek/.workspace-eclipse-4.4/Moneybags/**/*Test.java, C:/Users/Marek/.workspace-eclipse-4.4/Moneybags/**/Test*.java, C:/Users/Marek/.workspace-eclipse-4.4/javasyntax18/**/*Test.java, C:/Users/Marek/.workspace-eclipse-4.4/javasyntax18/**/Test*.java--testsExcludePattern, C:/Users/Marek/.workspace-eclipse-4.4/Moneybags/, C:/Users/Marek/.workspace-eclipse-4.4/javasyntax18/, -a, -i, C:\Users\Marek\AppData\Local\Temp\clover3525180172645953949merge, -o, C:\Users\Marek\Desktop, -t, Coverage Report, -tc, 0, -f, , -s, 0 days] Error generating report: java.lang.NumberFormatException java.lang.NumberFormatException at java.math.BigDecimal.<init>(BigDecimal.java:459) at java.math.BigDecimal.<init>(BigDecimal.java:728) at com.atlassian.clover.cfg.Interval.initialise(Interval.java:183) at com.atlassian.clover.cfg.Interval.<init>(Interval.java:121) at com.atlassian.clover.eclipse.core.reports.MergeReportJob$MergeAndReport.run(MergeReportJob.java:140) at com.atlassian.clover.eclipse.core.reports.ForkingReporter.main(ForkingReporter.java:25) {noformat} | 1 |
278 | CLOV-1613 | 01/27/2015 13:38:02 | Unable to open generated reports in Eclipse 4.4 | Steps to reproduce: Open "Coverage Exploer", click "Run new report ..." and create any report. Next click "View report" and select it on a list. Nothing happens in the UI and the "Error log" view shows "Unhandled event exception" entry with a stack trace as follows: {noformat} java.lang.NoClassDefFoundError: Could not initialize class com.atlassian.clover.eclipse.core.reports.OpenReportOperation at com.atlassian.clover.eclipse.core.views.actions.GenerateReportAction$2.widgetSelected(GenerateReportAction.java:151) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4353) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1061) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4172) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603) at org.eclipse.equinox.launcher.Main.run(Main.java:1465) {noformat} | 1 |
279 | CLOV-1614 | 01/29/2015 10:54:24 | Error when closing Cloud Editor in Eclipse | Closing the "Cloud Editor" in Eclipse causes that sometimes an exception is thrown and reported in the Error Log: {noformat} Error disposing widget for : org.eclipse.e4.ui.model.application.ui.basic.impl.PartImpl Clover Coverage Cloud Report java.lang.NullPointerException at org.eclipse.swt.custom.CTabFolderLayout.computeSize(CTabFolderLayout.java:39) at org.eclipse.swt.widgets.Composite.computeSize(Composite.java:234) at org.eclipse.swt.layout.GridData.computeSize(GridData.java:491) at org.eclipse.swt.layout.GridLayout.layout(GridLayout.java:221) at org.eclipse.swt.layout.GridLayout.layout(GridLayout.java:197) at org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:1290) at org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:1297) at org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:1297) at org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:1297) at org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:1276) at org.eclipse.swt.widgets.Composite.layout(Composite.java:665) at org.eclipse.swt.custom.CTabFolder.runUpdate(CTabFolder.java:3755) at org.eclipse.swt.custom.CTabItem.getBounds(CTabItem.java:149) at org.eclipse.swt.custom.CTabFolder.onPaint(CTabFolder.java:1993) at org.eclipse.swt.custom.CTabFolder$1.handleEvent(CTabFolder.java:289) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4353) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1061) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1085) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1070) at org.eclipse.swt.widgets.Composite.WM_PAINT(Composite.java:1491) at org.eclipse.swt.widgets.Control.windowProc(Control.java:4667) at org.eclipse.swt.widgets.Display.windowProc(Display.java:5036) at org.eclipse.swt.internal.win32.OS.VtblCall(Native Method) at org.eclipse.swt.internal.ole.win32.IOleInPlaceObject.InPlaceDeactivate(IOleInPlaceObject.java:21) {noformat} and {noformat} Unhandled event loop exception java.lang.NullPointerException at org.eclipse.swt.custom.CTabFolderLayout.computeSize(CTabFolderLayout.java:39) at org.eclipse.swt.widgets.Composite.computeSize(Composite.java:234) at org.eclipse.swt.layout.GridData.computeSize(GridData.java:491) at org.eclipse.swt.layout.GridLayout.layout(GridLayout.java:221) at org.eclipse.swt.layout.GridLayout.layout(GridLayout.java:197) at org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:1290) at org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:1297) at org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:1297) at org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:1297) at org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:1297) at org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:1297) at org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:1297) at org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:1297) at org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:1297) at org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:1297) at org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:1297) at org.eclipse.swt.widgets.Composite.updateLayout(Composite.java:1276) at org.eclipse.swt.widgets.Composite.setLayoutDeferred(Composite.java:1087) at org.eclipse.swt.widgets.Display.runDeferredLayouts(Display.java:4196) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3754) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636) {noformat} Apparently, it fails in the CTabFolderLayout.computeSize() method: {code:java} protected Point computeSize(Composite composite, int wHint, int hHint, boolean flushCache) { CTabFolder folder = (CTabFolder)composite; CTabFolderRenderer renderer = folder.renderer; ... tabW = Math.max(tabW, renderer.computeSize(width, 2, gc, -1, -1).x); {code} the 'renderer' is null. This renderer is being set in CTabFolder.init() method and set to null in the CTabFolder.onDispose() method. It *may* be related with the: CloudEditor.dispose() which calls removeCoverageChangeListener after the super.dispose() so a refresh event may come in the meantinme or CloudEditor.createPages() which "hacks" the container layout by changing it from FillLayout to GridLayout. | 3 |
280 | CLOV-1617 | 02/09/2015 14:02:26 | Automatic Clover integration does not work for <groovyc> task | *Problem:* Automatic Clover integration in Bamboo does now work for Ant Tasks containing the <groovyc> task. *Root cause:* When automatic Clover integration is enabled in Bamboo, it uses Clover's AntIntegrationListener: {noformat} ant ... -lib clover.jar -listener com.atlassian.clover.ci.AntIntegrationListener {noformat} This listener listens to Ant's build events and intercepts Ant tasks such as: <javac>, <java>, <javadoc>, <junit> However, it does not intercept the <groovyc> one. Integration with <groovyc> task is performed by the <clover-setup> task, which calls: {code:java} GroovycSupport.ensureAddedTo(antProject); {code} Note that GroovycSupport implements Ant's BuildListener. However, it cannot be passed via command line, like this: {noformat} ant ... -lib clover.jar -listener com.atlassian.clover.ant.groovy.GroovycSupport {noformat} because the GroovycSupport does not have a default constructor. *Workaround:* Call the <clover-setup> from an Ant script. For example, add the following target: {code:xml} <target name="instrument" if="with.clover"> <!-- we assume that automatic integration is enabled, which adds the '-lib clover.jar' --> <taskdef name="clover-setup" classname="com.atlassian.clover.ant.tasks.CloverSetupTask"/> <!-- from the clover.jar --> <!-- call clover-setup to intercept <groovyc> task --> <clover-setup/> <!-- This fake compilation is to cheat the automatic Clover integration, so that it won't display the "Clover reports not being generated. No Clover instrumentation was done." error message. We instrument java sources, but through the <groovyc> task; and we need to trick Clover so that it generates an HTML report at the end. --> <mkdir dir="${target.classes}"/> <javac failonerror="false" srcdir="${src.java}" excludes="**/*" destdir="${target.classes}"/> </target> <target name="compile" depends="instrument"> <groovyc destdir="${target.classes}" classpathref="build.classpath" fork="yes"> <javac source="1.7" target="1.7" debug="on" encoding="UTF8"> </javac> <src path="${src.java}"/> <src path="${src.groovy}"/> </groovyc> </target> {code} Clover's initialization will occur only if '-Dwith.clover=true' is set. Therefore, modify the Ant Task in Bamboo, for instance: {noformat} clean test -Dwith.clover=true {noformat} *Possible fixes:* 1) Add default constructor for GroovycSupport. Pass it as a second '-listener' to ant command in Bamboo. 2) Change the AntIntegrationListener so that it will intercept all <groovyc> tasks as well. | 5 |
281 | CLOV-1632 | 02/10/2015 14:33:38 | Protect against deployment of instrumented code | If user calls "mvn clover2:setup install" or "mvn clover2:setup deploy", code instrumented by Clover will be installed to ~/.m2 or deployed to a repository. This may be not a desired behavior, especially if developer is not aware of it (for instance if someone switches on the automatic Clover integration in Bamboo). Furthermore, installation may occur not only for "install" or "deploy" phases expressed explicitly in the command line, but it can also happen when a plug-in runs such life cycle (mvn release:perform for instance). Implement a protection against it - in the clover2:setup check the reactor which phases are about to run and refuse code instrumentation if 'install' or 'deploy' will be called. This protection shall not be enabled by default, because there may be actually a need to install instrumented code (for instance - multiple build plans using the same local m2 cache or repository to fetch compiled artifacts and we want to measure coverage for all modules). Enable protection by a flag. e.g. {code:xml} <configuration> <repositoryPollutionProtection>true</repositoryPollutionProtection> </configuration> {code} mvn -Dmaven.clover.repositoryPollutionProtection=true Expected behavior: fail a build if repositoryPollutionProtection=true and build lifecycle contains 'install' or 'deploy' phases. *Extra:* Fail also if artifact contains a custom classifier and clover2:instrument is used (as Maven cannot handle an artifact with two classifiers). | 3 |
282 | CLOV-1654 | 02/28/2015 15:08:08 | as a plugin developer I'd like to have annotations for a package in a Clover database | Currently, annotations are available for classes and methods only: * ClassInfo.getModifiers().getAnnotations() * MethodInfo.getSignature().getAnnotations() There's nothing like PackageInfo.getAnnotations(). The reason to have this is that _package-info.java_ files may contain annotations (but no executable code). While having this adds no value for Clover instrumentation itself, it could be useful for plugin developers, who would like to read Clover database directly. For instance, this information could be used to filter classes based on the information stored on a package level. See: https://answers.atlassian.com/questions/12781852/how-to-read-package-annotations-from-clover-db | 5 |
283 | CLOV-1657 | 03/03/2015 10:57:57 | Compiling Groovy code with Clover throws NPE | Clover fails to integrate with Groovyc task and throws NPE: {noformat} Clover failed to integrate with <groovyc/> java.lang.NullPointerException at com.atlassian.clover.ant.groovy.GroovycSupport.buildTestDetector(GroovycSupport.java:242) at com.atlassian.clover.ant.groovy.GroovycSupport.taskStarted(GroovycSupport.java:141) at org.apache.tools.ant.Project.fireTaskStarted(Project.java:2184) at org.apache.tools.ant.Task.perform(Task.java:344) at org.apache.tools.ant.Target.execute(Target.java:392) at org.apache.tools.ant.Target.performTasks(Target.java:413) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399) ... {noformat} *Cause:* NPE is thrown when Clover cannot find it's AntInstrumentationConfig in project references in an Ant-based build. This can happen when a build calls <ant> or <antcall> tasks without {{inheritrefs=true}} - lack of this property causes that AntInstrumentationConfig is not passed to these calls. *Workaround:* Ensure that {{inheritrefs=true}} is used. | 1 |
284 | CLOV-1658 | 03/13/2015 11:34:58 | Publish Clover-for-Scala prototype | Tasks: * request releasing it as open source * publish plugin's source code on BitBucket, * prepare and publish documentation on CAC/Clover-for-Scala. * prepare plug-in developer documentation | 5 |
285 | CLOV-1659 | 03/13/2015 11:43:12 | as a user I want to use Clover with maven-scala-plugin | Integration of Clover-for-Scala with the maven-scala-plugin. Tasks: * clover2:setup shall "connect" to the maven-scala-plugin; t.b.d. how - META-INF/services? a plugin point? some properties? * clover2:clover shall include also *.scala sources Checks: * is it possible to have joint Scala-Java compilation (like with joint Groovy-Java)? Out of scope: * clover2:instr is out of scope as integration is performed using AST, not source code * clover2:optimize as test optimization is in another task | 13 |
286 | CLOV-1660 | 03/13/2015 11:45:39 | as a user I want to use Clover with scalac | Integration of Clover-for-Scala with scalac command line tool. Tasks: * shall be easy - plugging via META-INF/services Checks: * is it possible to have joint Scala-Java compilation? if yes, then how it works and how to intercept both compilers? | 5 |
287 | CLOV-1661 | 03/13/2015 11:49:07 | as a user I want to use Clover with SBT | Integration of Clover-for-Scala with SBT. Tasks: * write build plugin for SBT - equivalent of clover2:setup, shall intercept any scalac calls; shall add clover.jar (clover-scala.jar?) to class paths for compilation and runtime * write build plugin for SBT - equivalent of clover2:clover, shall generate reports; we may call Clover-for-Ant under the hood | 20 |
288 | CLOV-1662 | 03/13/2015 11:55:58 | as a user I want to see nested functions in reports | Scala allows to nest functions inside other functions. Enhance existing HTML / XML / JSON reports in such way that we could see such nesting as well. Some of the required functionality has already been done during implementation of lambda functions for Java 8 (Clover 3.2). Review if all possible nesting combinations are implemented in Velocity templates (method-in-method, class-in-method etc). Affects: table with list of methods for a class, calculation of metrics etc. | 5 |
289 | CLOV-1664 | 03/13/2015 12:38:32 | as a user I want to use Clover-for-Scala in IntelliJ IDEA | Tasks: * integrate with Scala complier in IDEA (using external build process) * show Scala classes in Cloverage view * show coverage highlighting in Scala editors (!) Challenge: simultaneous update of clover.db by Javac and Scalac (similar problem as for Groovy in IDE) Out of scope: * test optimization for Scala | 40 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.