Re: TikiOne JaCoCoverage plugin
On 14.01.2021 19:58, Joe Kasprzyk wrote: I've downloaded the project and attempted to build. The plugin is a suite of four modules - for each module, the source level was updated to 11. When "clean and build"ing each of the four modules, three (JaCoCo Library, TikiOne JaCoCo Reporting Library, TikiOne JaCoCoverage Libraries) seem to build cleanly - TikiOne JaCoCoverage generates the following: I'm using TikiOne cloned from https://github.com/operez-ddgi/tikione-jacocoverage. It looked more current than the original one. I get some warnings when I build the suite, but in the end the build is successful and I can install and use the nbm / plugin. Christoph - To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org For additional commands, e-mail: users-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: TikiOne JaCoCoverage plugin
Look in the Maven POMs for “compat8” and delete that Maven dependency wherever you find it, you most likely don’t need it, then do the build again. Gj On Thu, 14 Jan 2021 at 19:58, Joe Kasprzyk wrote: > I've downloaded the project and attempted to build. The plugin is a suite > of four modules - for each module, the source level was updated to 11. When > "clean and build"ing each of the four modules, three (JaCoCo Library, > TikiOne JaCoCo Reporting Library, TikiOne JaCoCoverage Libraries) seem to > build cleanly - TikiOne JaCoCoverage generates the following: > > Running NetBeans on JDK 11.0.8 > > ant -f > D:\\NetBeans\\NetBeans-12.2-Zip\\PluginDownloads\\TikiOne-SourceCode\\tikione-jacocoverage-master\\tikione-jacocoverage-plugin > -Dcontinue.after.failing.tests=true -Ddo.not.clean.module.config.xml=true > clean build > taskdefs: > common-init: > projectized-common.basic-init: > basic-init: > files-init: > testuserdir-delete: > clean: > taskdefs: > common-init: > projectized-common.basic-init: > basic-init: > files-init: > nbm-license-init: > build-init: > Scanning for modules in > D:\NetBeans\NetBeans-12.2-Zip\NetBeans12.2\apisupport > Scanning for modules in D:\NetBeans\NetBeans-12.2-Zip\NetBeans12.2\extide > Scanning for modules in D:\NetBeans\NetBeans-12.2-Zip\NetBeans12.2\harness > Scanning for modules in D:\NetBeans\NetBeans-12.2-Zip\NetBeans12.2\ide > Scanning for modules in D:\NetBeans\NetBeans-12.2-Zip\NetBeans12.2\java > Scanning for modules in D:\NetBeans\NetBeans-12.2-Zip\NetBeans12.2\nb > Scanning for modules in D:\NetBeans\NetBeans-12.2-Zip\NetBeans12.2\platform > Scanning for modules in D:\NetBeans\NetBeans-12.2-Zip\NetBeans12.2\profiler > Scanning for modules in > D:\NetBeans\NetBeans-12.2-Zip\NetBeans12.2\websvccommon > Scanning for modules in suite > D:\NetBeans\NetBeans-12.2-Zip\PluginDownloads\TikiOne-SourceCode\tikione-jacocoverage-master > warning: had to upgrade dependencies for module > fr.tikione.jacocoverage.plugin: added = [module > org.netbeans.modules.project.ant.ui/1 > 1.62, module > org.netbeans.api.progress.compat8 > 1.40, module org.netbeans.api.templates > > 1.0, module org.openide.execution.compat8 > 9.0, module > org.netbeans.modules.java.source.base > 1.1, module > org.netbeans.modules.projectuiapi.base/1 > 1.78.0, module > org.openide.filesystems.nb, module org.netbeans.modules.java.source.compat8 > > 9.0, module org.openide.filesystems.compat8, module > org.netbeans.modules.project.ant.compat8/1 > 1.62] removed = []; details: > [Removal of FileSystemCapability, Separate project.ant into desktop and > NetBeans independent and dependent parts, Separate projectuiapi into > desktop and NetBeans independent and dependent parts, Separation of desktop > and cleanup, Swing dependencies split away, Templates API has been > separated into its own module., The old editor settings and completion APIs > have been deprecated, see http://wiki.netbeans.org/EditorSettingsUpgrade > and update your module.] > Distilling > D:\NetBeans\NetBeans-12.2-Zip\PluginDownloads\TikiOne-SourceCode\tikione-jacocoverage-master\build\public-package-jars\fr-tikione-jacocoexec-analyzer.jar > from > [D:\NetBeans\NetBeans-12.2-Zip\PluginDownloads\TikiOne-SourceCode\tikione-jacocoverage-master\build\cluster\modules\fr-tikione-jacocoexec-analyzer.jar] > D:\NetBeans\NetBeans-12.2-Zip\NetBeans12.2\harness\build.xml:150: No > dependent module org.netbeans.modules.java.source.compat8 > BUILD FAILED (total time: 0 seconds) > > Running NetBeans on 1.8.0_u251 yields the same results. > > I'm unfamiliar with maven... > > On Thu, Jan 14, 2021 at 12:09 PM Geertjan Wielenga > wrote: > >> Right. And whoever needs it, can download the code, build it in 12.2, >> probably there won't be any problems, and then install it and/or provide >> NBMs at that stage. >> >> Gj >> >> On Thu, Jan 14, 2021 at 6:07 PM Laszlo Kishalmi < >> laszlo.kisha...@gmail.com> wrote: >> >>> That one is here: >>> https://github.com/jonathanlermitage/tikione-jacocoverage >>> >>> On the other hand if you need the coverage now, you can switch the build >>> System from Ant to Gradle or Maven where we provide that support out of the >>> box. >>> On 1/14/21 8:45 AM, Geertjan Wielenga wrote: >>> >>> If you can point to the sources, hopefully on GitHub, we could compile >>> them against 12.2 to update it, that's probably all that's needed. >>> >>> Gj >>> >>> On Thu, Jan 14, 2021 at 5:39 PM Joe Kasprzyk >>> wrote: >>> >>>> I've been using the TikiOne JaCoCoverage
Re: TikiOne JaCoCoverage plugin
I've downloaded the project and attempted to build. The plugin is a suite of four modules - for each module, the source level was updated to 11. When "clean and build"ing each of the four modules, three (JaCoCo Library, TikiOne JaCoCo Reporting Library, TikiOne JaCoCoverage Libraries) seem to build cleanly - TikiOne JaCoCoverage generates the following: Running NetBeans on JDK 11.0.8 ant -f D:\\NetBeans\\NetBeans-12.2-Zip\\PluginDownloads\\TikiOne-SourceCode\\tikione-jacocoverage-master\\tikione-jacocoverage-plugin -Dcontinue.after.failing.tests=true -Ddo.not.clean.module.config.xml=true clean build taskdefs: common-init: projectized-common.basic-init: basic-init: files-init: testuserdir-delete: clean: taskdefs: common-init: projectized-common.basic-init: basic-init: files-init: nbm-license-init: build-init: Scanning for modules in D:\NetBeans\NetBeans-12.2-Zip\NetBeans12.2\apisupport Scanning for modules in D:\NetBeans\NetBeans-12.2-Zip\NetBeans12.2\extide Scanning for modules in D:\NetBeans\NetBeans-12.2-Zip\NetBeans12.2\harness Scanning for modules in D:\NetBeans\NetBeans-12.2-Zip\NetBeans12.2\ide Scanning for modules in D:\NetBeans\NetBeans-12.2-Zip\NetBeans12.2\java Scanning for modules in D:\NetBeans\NetBeans-12.2-Zip\NetBeans12.2\nb Scanning for modules in D:\NetBeans\NetBeans-12.2-Zip\NetBeans12.2\platform Scanning for modules in D:\NetBeans\NetBeans-12.2-Zip\NetBeans12.2\profiler Scanning for modules in D:\NetBeans\NetBeans-12.2-Zip\NetBeans12.2\websvccommon Scanning for modules in suite D:\NetBeans\NetBeans-12.2-Zip\PluginDownloads\TikiOne-SourceCode\tikione-jacocoverage-master warning: had to upgrade dependencies for module fr.tikione.jacocoverage.plugin: added = [module org.netbeans.modules.project.ant.ui/1 > 1.62, module org.netbeans.api.progress.compat8 > 1.40, module org.netbeans.api.templates > 1.0, module org.openide.execution.compat8 > 9.0, module org.netbeans.modules.java.source.base > 1.1, module org.netbeans.modules.projectuiapi.base/1 > 1.78.0, module org.openide.filesystems.nb, module org.netbeans.modules.java.source.compat8 > 9.0, module org.openide.filesystems.compat8, module org.netbeans.modules.project.ant.compat8/1 > 1.62] removed = []; details: [Removal of FileSystemCapability, Separate project.ant into desktop and NetBeans independent and dependent parts, Separate projectuiapi into desktop and NetBeans independent and dependent parts, Separation of desktop and cleanup, Swing dependencies split away, Templates API has been separated into its own module., The old editor settings and completion APIs have been deprecated, see http://wiki.netbeans.org/EditorSettingsUpgrade and update your module.] Distilling D:\NetBeans\NetBeans-12.2-Zip\PluginDownloads\TikiOne-SourceCode\tikione-jacocoverage-master\build\public-package-jars\fr-tikione-jacocoexec-analyzer.jar from [D:\NetBeans\NetBeans-12.2-Zip\PluginDownloads\TikiOne-SourceCode\tikione-jacocoverage-master\build\cluster\modules\fr-tikione-jacocoexec-analyzer.jar] D:\NetBeans\NetBeans-12.2-Zip\NetBeans12.2\harness\build.xml:150: No dependent module org.netbeans.modules.java.source.compat8 BUILD FAILED (total time: 0 seconds) Running NetBeans on 1.8.0_u251 yields the same results. I'm unfamiliar with maven... On Thu, Jan 14, 2021 at 12:09 PM Geertjan Wielenga wrote: > Right. And whoever needs it, can download the code, build it in 12.2, > probably there won't be any problems, and then install it and/or provide > NBMs at that stage. > > Gj > > On Thu, Jan 14, 2021 at 6:07 PM Laszlo Kishalmi > wrote: > >> That one is here: >> https://github.com/jonathanlermitage/tikione-jacocoverage >> >> On the other hand if you need the coverage now, you can switch the build >> System from Ant to Gradle or Maven where we provide that support out of the >> box. >> On 1/14/21 8:45 AM, Geertjan Wielenga wrote: >> >> If you can point to the sources, hopefully on GitHub, we could compile >> them against 12.2 to update it, that's probably all that's needed. >> >> Gj >> >> On Thu, Jan 14, 2021 at 5:39 PM Joe Kasprzyk >> wrote: >> >>> I've been using the TikiOne JaCoCoverage plugin for years now, up to >>> NetBeans 8.2 . I've been migrating to NetBeans 12.2 and am trying to >>> install this plugin (development marked closed on the author's project >>> site). I set the default JDK to 1.8 and am running NetBeans on 1.8. When I >>> install, I get >>> >>> [image: image.png] >>> >>> Anyone know where I can find the org.openide.execution.deprecated plugin >>> (and/or if it is compatible with 12.2)? Thanks! >>> >>> NetBean 12.2 "about": >>> >>> *Product Version:* Apache NetBeans IDE 12.2 >>> >>> *Updates:
Re: TikiOne JaCoCoverage plugin
Right. And whoever needs it, can download the code, build it in 12.2, probably there won't be any problems, and then install it and/or provide NBMs at that stage. Gj On Thu, Jan 14, 2021 at 6:07 PM Laszlo Kishalmi wrote: > That one is here: > https://github.com/jonathanlermitage/tikione-jacocoverage > > On the other hand if you need the coverage now, you can switch the build > System from Ant to Gradle or Maven where we provide that support out of the > box. > On 1/14/21 8:45 AM, Geertjan Wielenga wrote: > > If you can point to the sources, hopefully on GitHub, we could compile > them against 12.2 to update it, that's probably all that's needed. > > Gj > > On Thu, Jan 14, 2021 at 5:39 PM Joe Kasprzyk > wrote: > >> I've been using the TikiOne JaCoCoverage plugin for years now, up to >> NetBeans 8.2 . I've been migrating to NetBeans 12.2 and am trying to >> install this plugin (development marked closed on the author's project >> site). I set the default JDK to 1.8 and am running NetBeans on 1.8. When I >> install, I get >> >> [image: image.png] >> >> Anyone know where I can find the org.openide.execution.deprecated plugin >> (and/or if it is compatible with 12.2)? Thanks! >> >> NetBean 12.2 "about": >> >> *Product Version:* Apache NetBeans IDE 12.2 >> >> *Updates:* NetBeans IDE is updated to version NetBeans 8.2 Patch 2 >> <http://wiki.netbeans.org/NetBeans8.2PatchesInfo> >> >> *Java:* 1.8.0_271; Java HotSpot(TM) 64-Bit Server VM 25.271-b09 >> >> *Runtime:* Java(TM) SE Runtime Environment 1.8.0_271-b09 >> >> *System:* Windows 10 version 10.0 running on amd64; Cp1252; en_US (nb) >> >> *User directory:* D:\NetBeans\NetBeans-12.2-Zip-JDK8\NBUserSettings\12.2 >> >> *Cache directory:* >> D:\NetBeans\NetBeans-12.2-Zip-JDK8\NBUserSettings\12.2\var\cache >> >> Joe >> >
Re: TikiOne JaCoCoverage plugin
That one is here: https://github.com/jonathanlermitage/tikione-jacocoverage On the other hand if you need the coverage now, you can switch the build System from Ant to Gradle or Maven where we provide that support out of the box. On 1/14/21 8:45 AM, Geertjan Wielenga wrote: If you can point to the sources, hopefully on GitHub, we could compile them against 12.2 to update it, that's probably all that's needed. Gj On Thu, Jan 14, 2021 at 5:39 PM Joe Kasprzyk <mailto:jkasprzyk1...@gmail.com>> wrote: I've been using the TikiOne JaCoCoverage plugin for years now, up to NetBeans 8.2 . I've been migrating to NetBeans 12.2 and am trying to install this plugin (development marked closed on the author's project site). I set the default JDK to 1.8 and am running NetBeans on 1.8. When I install, I get image.png Anyone know where I can find the org.openide.execution.deprecated plugin (and/or if it is compatible with 12.2)? Thanks! NetBean 12.2 "about": *Product Version:* Apache NetBeans IDE 12.2 *Updates:* NetBeans IDE is updated to version NetBeans 8.2 Patch 2 <http://wiki.netbeans.org/NetBeans8.2PatchesInfo> *Java:* 1.8.0_271; Java HotSpot(TM) 64-Bit Server VM 25.271-b09 *Runtime:* Java(TM) SE Runtime Environment 1.8.0_271-b09 *System:* Windows 10 version 10.0 running on amd64; Cp1252; en_US (nb) *User directory:* D:\NetBeans\NetBeans-12.2-Zip-JDK8\NBUserSettings\12.2 *Cache directory:* D:\NetBeans\NetBeans-12.2-Zip-JDK8\NBUserSettings\12.2\var\cache Joe
Re: TikiOne JaCoCoverage plugin
If you can point to the sources, hopefully on GitHub, we could compile them against 12.2 to update it, that's probably all that's needed. Gj On Thu, Jan 14, 2021 at 5:39 PM Joe Kasprzyk wrote: > I've been using the TikiOne JaCoCoverage plugin for years now, up to > NetBeans 8.2 . I've been migrating to NetBeans 12.2 and am trying to > install this plugin (development marked closed on the author's project > site). I set the default JDK to 1.8 and am running NetBeans on 1.8. When I > install, I get > > [image: image.png] > > Anyone know where I can find the org.openide.execution.deprecated plugin > (and/or if it is compatible with 12.2)? Thanks! > > NetBean 12.2 "about": > > *Product Version:* Apache NetBeans IDE 12.2 > > *Updates:* NetBeans IDE is updated to version NetBeans 8.2 Patch 2 > <http://wiki.netbeans.org/NetBeans8.2PatchesInfo> > > *Java:* 1.8.0_271; Java HotSpot(TM) 64-Bit Server VM 25.271-b09 > > *Runtime:* Java(TM) SE Runtime Environment 1.8.0_271-b09 > > *System:* Windows 10 version 10.0 running on amd64; Cp1252; en_US (nb) > > *User directory:* D:\NetBeans\NetBeans-12.2-Zip-JDK8\NBUserSettings\12.2 > > *Cache directory:* > D:\NetBeans\NetBeans-12.2-Zip-JDK8\NBUserSettings\12.2\var\cache > > Joe >
TikiOne JaCoCoverage plugin
I've been using the TikiOne JaCoCoverage plugin for years now, up to NetBeans 8.2 . I've been migrating to NetBeans 12.2 and am trying to install this plugin (development marked closed on the author's project site). I set the default JDK to 1.8 and am running NetBeans on 1.8. When I install, I get [image: image.png] Anyone know where I can find the org.openide.execution.deprecated plugin (and/or if it is compatible with 12.2)? Thanks! NetBean 12.2 "about": *Product Version:* Apache NetBeans IDE 12.2 *Updates:* NetBeans IDE is updated to version NetBeans 8.2 Patch 2 <http://wiki.netbeans.org/NetBeans8.2PatchesInfo> *Java:* 1.8.0_271; Java HotSpot(TM) 64-Bit Server VM 25.271-b09 *Runtime:* Java(TM) SE Runtime Environment 1.8.0_271-b09 *System:* Windows 10 version 10.0 running on amd64; Cp1252; en_US (nb) *User directory:* D:\NetBeans\NetBeans-12.2-Zip-JDK8\NBUserSettings\12.2 *Cache directory:* D:\NetBeans\NetBeans-12.2-Zip-JDK8\NBUserSettings\12.2\var\cache Joe
Re: JaCoCoverage plugin
+1 to using Maven in the classroom. Way to go, I think. This is a standard de facto in industry, I think. Cheers, Antonio El 27/5/19 a las 20:01, Pieter van den Hombergh escribió: Hi Eduardo, I was in similar situation, but then followed Geertjan Wielenga’s advice to consider maven over ant based projects. If used properly, maven does all the rights things and better. So I have made the switch, and are happy with it. Supplying the students with a proper parent-Pom takes a lot of the scary things of maven away, because in there you can provide things like coverage (== Jacoco ) as a maven dependency, so that students only have the libraries their projects actually need. I will switch over to maven projects for our initial java course too in September. To find some examples, have a look at github sebivenlo, where you find such parent-pom, called sebipom and a few projects that use that parent. Navigate to https://github.com/sebivenlo/sebipom And it sibling projects on github to see what I provide. If you want some example exercises, let me know and I will send them using a private channel. On Sat, 25 May 2019 at 00:54, Eduardo Mosqueira Rey mailto:eduardo.mosque...@udc.es>> wrote: Hi all, __ __ I used in classroom the JaCoCoverage plugin with NetBeans 8.2 for the students to check the coverage of their tests. It had an easy and straightforward installation and was very simple to use, ideal for newbies. __ __ Nevertheless, the plugin is no longer maintained at it doesn’t work with NetBeans 11.0. This year I want to migrate the classroom installation to Apache NetBeans but the lack of a coverage tool is an inconvenient. __ __ Is there an easy way to install a Coverage tool (whatever) in NetBeans 11.0? **easy to install** is an important requirement. __ __ Any suggestion would be appreciated. __ __ Many thanks, -- Eduardo __ __ -- Pieter Van den Hombergh. No software documentation is complete with out it's source code. - To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org For additional commands, e-mail: users-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
RE: JaCoCoverage plugin
Thank you Pieter. I am also considering that the best option is to switch to Maven projects in the next course. I have to prepare some brief introduction to Maven to the students, but if we maintain things simple I thing that there should be no problems. De: Pieter van den Hombergh Enviado: lunes, 27 de mayo de 2019 20:01 Para: Eduardo Mosqueira Rey Cc: users@netbeans.apache.org Asunto: Re: JaCoCoverage plugin Hi Eduardo, I was in similar situation, but then followed Geertjan Wielenga’s advice to consider maven over ant based projects. If used properly, maven does all the rights things and better. So I have made the switch, and are happy with it. Supplying the students with a proper parent-Pom takes a lot of the scary things of maven away, because in there you can provide things like coverage (== Jacoco ) as a maven dependency, so that students only have the libraries their projects actually need. I will switch over to maven projects for our initial java course too in September. To find some examples, have a look at github sebivenlo, where you find such parent-pom, called sebipom and a few projects that use that parent. Navigate to https://github.com/sebivenlo/sebipom And it sibling projects on github to see what I provide. If you want some example exercises, let me know and I will send them using a private channel. On Sat, 25 May 2019 at 00:54, Eduardo Mosqueira Rey mailto:eduardo.mosque...@udc.es>> wrote: Hi all, I used in classroom the JaCoCoverage plugin with NetBeans 8.2 for the students to check the coverage of their tests. It had an easy and straightforward installation and was very simple to use, ideal for newbies. Nevertheless, the plugin is no longer maintained at it doesn’t work with NetBeans 11.0. This year I want to migrate the classroom installation to Apache NetBeans but the lack of a coverage tool is an inconvenient. Is there an easy way to install a Coverage tool (whatever) in NetBeans 11.0? *easy to install* is an important requirement. Any suggestion would be appreciated. Many thanks, -- Eduardo -- Pieter Van den Hombergh. No software documentation is complete with out it's source code.
Re: JaCoCoverage plugin
Hi Eduardo, I was in similar situation, but then followed Geertjan Wielenga’s advice to consider maven over ant based projects. If used properly, maven does all the rights things and better. So I have made the switch, and are happy with it. Supplying the students with a proper parent-Pom takes a lot of the scary things of maven away, because in there you can provide things like coverage (== Jacoco ) as a maven dependency, so that students only have the libraries their projects actually need. I will switch over to maven projects for our initial java course too in September. To find some examples, have a look at github sebivenlo, where you find such parent-pom, called sebipom and a few projects that use that parent. Navigate to https://github.com/sebivenlo/sebipom And it sibling projects on github to see what I provide. If you want some example exercises, let me know and I will send them using a private channel. On Sat, 25 May 2019 at 00:54, Eduardo Mosqueira Rey < eduardo.mosque...@udc.es> wrote: > Hi all, > > > > I used in classroom the JaCoCoverage plugin with NetBeans 8.2 for the > students to check the coverage of their tests. > > It had an easy and straightforward installation and was very simple to > use, ideal for newbies. > > > > Nevertheless, the plugin is no longer maintained at it doesn’t work with > NetBeans 11.0. > > This year I want to migrate the classroom installation to Apache NetBeans > but the lack of a coverage tool is an inconvenient. > > > > Is there an easy way to install a Coverage tool (whatever) in NetBeans > 11.0? > > **easy to install** is an important requirement. > > > > Any suggestion would be appreciated. > > > > Many thanks, > > -- Eduardo > > > -- Pieter Van den Hombergh. No software documentation is complete with out it's source code.
Re: JaCoCoverage plugin
You might be hitting this with Gradle: https://github.com/vaskoz/core-java9-impatient/issues Also are you trying to use Java modular projects? That's not working with the current plugin. On 5/25/19 2:04 AM, Eduardo Mosqueira Rey wrote: With Maven I managed to get the coverage data adding this plugin to the pom: org.jacoco jacoco-maven-plugin 0.8.2 prepare-agent report test report The problem is that it forces the students to look under the hood in the project structure. Also I missed the branch coverage information. It seems to be counting only line coverage, as far as I know. With Gradle I cannot even run the tests. I am not a Gradle user so maybe I missed something. Here it is the output: JAVA_HOME="C:\Program Files\Java\jdk-11.0.2" cd C:\Users\Eduardo\Documents\NetBeansProjects\gradleproject1; C:\Users\Eduardo\.gradle\wrapper\dists\gradle-4.10.2-bin\cghg6c4gf4vkiutgsab8yrnwv\gradle-4.10.2\bin\gradle --configure-on-demand --rerun-tasks -x check test Configuration on demand is an incubating feature. > Task :compileJava > Task :processResources NO-SOURCE > Task :classes > Task :compileTestJava > Task :processTestResources NO-SOURCE > Task :testClasses Could not write standard input to Gradle Test Executor 1. java.io.IOException: Se est cerrando la canalizacin at java.base/java.io.FileOutputStream.writeBytes(Native Method) at java.base/java.io.FileOutputStream.write(FileOutputStream.java:354) at java.base/java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:81) at java.base/java.io.BufferedOutputStream.flush(BufferedOutputStream.java:142) at org.gradle.process.internal.streams.ExecOutputHandleRunner.forwardContent(ExecOutputHandleRunner.java:66) at org.gradle.process.internal.streams.ExecOutputHandleRunner.run(ExecOutputHandleRunner.java:51) at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63) at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:55) at java.base/java.lang.Thread.run(Thread.java:834) > Task :test FAILED Exception in thread "main" java.lang.reflect.InvocationTargetException at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at java.instrument/sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:513) at java.instrument/sun.instrument.InstrumentationImpl.loadClassAndCallPremain(InstrumentationImpl.java:525) Caused by: java.lang.RuntimeException: Class java/lang/UnknownError could not be instrumented.FATAL ERROR in native method: processing of -javaagent failed at org.jacoco.agent.rt.internal_c13123e.core.runtime.ModifiedSystemClassRuntime.createFor(ModifiedSystemClassRuntime.java:140) at org.jacoco.agent.rt.internal_c13123e.core.runtime.ModifiedSystemClassRuntime.createFor(ModifiedSystemClassRuntime.java:101) at org.jacoco.agent.rt.internal_c13123e.PreMain.createRuntime(PreMain.java:55) at org.jacoco.agent.rt.internal_c13123e.PreMain.premain(PreMain.java:47) ... 6 more Caused by: java.lang.NoSuchFieldException: $jacocoAccess at java.base/java.lang.Class.getField(Class.java:2000) at org.jacoco.agent.rt.internal_c13123e.core.runtime.ModifiedSystemClassRuntime.createFor(ModifiedSystemClassRuntime.java:138) ... 9 more *De:* Laszlo Kishalmi *Enviado:* sábado, 25 de mayo de 2019 1:49 *Para:* users@netbeans.apache.org *Asunto:* Re: JaCoCoverage plugin Hi! Actually JaCoCo support is out-of-the box in NetBeans, the additional plugin was required for Ant Based projects and it is not maintained right now (AFAIK it still has to be contributed by Oracle to Apache) So JaCoCo with Maven project do work though it require some configuration in the pom.xml. I'd say the easiest way is to achieve it if you just create a new Gradle Project from the IDE: File > New Project > Java with Gradle > Java Application | Java Class Library The new project wi
Re: JaCoCoverage plugin
Bos días, Eduardo, all, You're using JDK11 or JDK12, right? It seems you'll have to upgrade the jacoco version in your pom.xml, as JBoss is doing in [1]. This looks very similar to the error you're getting. They've upgraded to 0.8.2 [2]. AFAIK jacoco 0.8.0 has only _experimental_ support for JDK11 and JDK12. Unha aperta, Antonio [1] https://issues.jboss.org/browse/JBIDE-26336?_sscc=t [2] https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml#L893 El 25/5/19 a las 11:26, Eduardo Mosqueira Rey escribió: Just for clarify the branch coverage is in the full report at "\target\site\jacoco\index.html" what I missed was that information in the NetBeans GUI. *De:* Eduardo Mosqueira Rey *Enviado:* sábado, 25 de mayo de 2019 11:04 *Para:* Laszlo Kishalmi; users@netbeans.apache.org *Asunto:* RE: JaCoCoverage plugin With Maven I managed to get the coverage data adding this plugin to the pom: org.jacoco jacoco-maven-plugin 0.8.2 prepare-agent report test report The problem is that it forces the students to look under the hood in the project structure. Also I missed the branch coverage information. It seems to be counting only line coverage, as far as I know. With Gradle I cannot even run the tests. I am not a Gradle user so maybe I missed something. Here it is the output: JAVA_HOME="C:\Program Files\Java\jdk-11.0.2" cd C:\Users\Eduardo\Documents\NetBeansProjects\gradleproject1; C:\Users\Eduardo\.gradle\wrapper\dists\gradle-4.10.2-bin\cghg6c4gf4vkiutgsab8yrnwv\gradle-4.10.2\bin\gradle --configure-on-demand --rerun-tasks -x check test Configuration on demand is an incubating feature. > Task :compileJava > Task :processResources NO-SOURCE > Task :classes > Task :compileTestJava > Task :processTestResources NO-SOURCE > Task :testClasses Could not write standard input to Gradle Test Executor 1. java.io.IOException: Se est cerrando la canalizacin at java.base/java.io.FileOutputStream.writeBytes(Native Method) at java.base/java.io.FileOutputStream.write(FileOutputStream.java:354) at java.base/java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:81) at java.base/java.io.BufferedOutputStream.flush(BufferedOutputStream.java:142) at org.gradle.process.internal.streams.ExecOutputHandleRunner.forwardContent(ExecOutputHandleRunner.java:66) at org.gradle.process.internal.streams.ExecOutputHandleRunner.run(ExecOutputHandleRunner.java:51) at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63) at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:55) at java.base/java.lang.Thread.run(Thread.java:834) > Task :test FAILED Exception in thread "main" java.lang.reflect.InvocationTargetException at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at java.instrument/sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:513) at java.instrument/sun.instrument.InstrumentationImpl.loadClassAndCallPremain(InstrumentationImpl.java:525) Caused by: java.lang.RuntimeException: Class java/lang/UnknownError could not be instrumented.FATAL ERROR in native method: processing of -javaagent failed at org.jacoco.agent.rt.internal_c13123e.core.runtime.ModifiedSystemClassRuntime.createFor(ModifiedSystemClassRuntime.java:140) at org.jacoco.agent.rt.internal_c13123e.core.runtime.ModifiedSystemClassRuntime.createFor(ModifiedSystemClassRuntime.java:101) at org.jacoco.agent.rt.internal_c13123e.PreMain.createRuntime(PreMain.java:55) at org.jacoco.agent.rt.internal_c13123e.PreMain.premain(PreMain.java:47) ... 6 more Caused by: java.lang.NoSuchFieldException: $jacocoAccess at java.base/java.lang.Class.getField(Class.java:2000) at org.jacoco.agent.rt.internal_c13123e.core.runtime.ModifiedSystem
RE: JaCoCoverage plugin
Just for clarify the branch coverage is in the full report at "\target\site\jacoco\index.html" what I missed was that information in the NetBeans GUI. De: Eduardo Mosqueira Rey Enviado: sábado, 25 de mayo de 2019 11:04 Para: Laszlo Kishalmi; users@netbeans.apache.org Asunto: RE: JaCoCoverage plugin With Maven I managed to get the coverage data adding this plugin to the pom: org.jacoco jacoco-maven-plugin 0.8.2 prepare-agent report test report The problem is that it forces the students to look under the hood in the project structure. Also I missed the branch coverage information. It seems to be counting only line coverage, as far as I know. With Gradle I cannot even run the tests. I am not a Gradle user so maybe I missed something. Here it is the output: JAVA_HOME="C:\Program Files\Java\jdk-11.0.2" cd C:\Users\Eduardo\Documents\NetBeansProjects\gradleproject1; C:\Users\Eduardo\.gradle\wrapper\dists\gradle-4.10.2-bin\cghg6c4gf4vkiutgsab8yrnwv\gradle-4.10.2\bin\gradle --configure-on-demand --rerun-tasks -x check test Configuration on demand is an incubating feature. > Task :compileJava > Task :processResources NO-SOURCE > Task :classes > Task :compileTestJava > Task :processTestResources NO-SOURCE > Task :testClasses Could not write standard input to Gradle Test Executor 1. java.io.IOException: Se est cerrando la canalizacin at java.base/java.io.FileOutputStream.writeBytes(Native Method) at java.base/java.io.FileOutputStream.write(FileOutputStream.java:354) at java.base/java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:81) at java.base/java.io.BufferedOutputStream.flush(BufferedOutputStream.java:142) at org.gradle.process.internal.streams.ExecOutputHandleRunner.forwardContent(ExecOutputHandleRunner.java:66) at org.gradle.process.internal.streams.ExecOutputHandleRunner.run(ExecOutputHandleRunner.java:51) at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63) at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:55) at java.base/java.lang.Thread.run(Thread.java:834) > Task :test FAILED Exception in thread "main" java.lang.reflect.InvocationTargetException at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at java.instrument/sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:513) at java.instrument/sun.instrument.InstrumentationImpl.loadClassAndCallPremain(InstrumentationImpl.java:525) Caused by: java.lang.RuntimeException: Class java/lang/UnknownError could not be instrumented.FATAL ERROR in native method: processing of -javaagent failed at org.jacoco.agent.rt.internal_c13123e.core.runtime.ModifiedSystemClassRuntime.createFor(ModifiedSystemClassRuntime.java:140) at org.jacoco.agent.rt.internal_c13123e.core.runtime.ModifiedSystemClassRuntime.createFor(ModifiedSystemClassRuntime.java:101) at org.jacoco.agent.rt.internal_c13123e.PreMain.createRuntime(PreMain.java:55) at org.jacoco.agent.rt.internal_c13123e.PreMain.premain(PreMain.java:47) ... 6 more Caused by: java.lang.NoSuchFieldException: $jacocoAccess at java.base/java.lang.Class.getField(Class.java:2000) at org.jacoco.agent.rt.internal_c13123e.core.runtime.ModifiedSystemClassRuntime.createFor(ModifiedSystemClassRuntime.java:138) ... 9 more De: Laszlo Kishalmi Enviado: sábado, 25 de mayo de 2019 1:49 Para: users@netbeans.apache.org Asunto: Re: JaCoCoverage plugin Hi! Actually JaCoCo support is out-of-the box in NetBeans, the additional plugin was required for Ant Based projects and it is not maintained right now (AFAIK it still has to be contributed by Oracle to Apache) So JaCoCo with Maven project do work though it require some configuration in the pom.xml. I'd say the easiest way is to achieve it if you just create a new Gradle Project from the IDE: File > New Project >
RE: JaCoCoverage plugin
With Maven I managed to get the coverage data adding this plugin to the pom: org.jacoco jacoco-maven-plugin 0.8.2 prepare-agent report test report The problem is that it forces the students to look under the hood in the project structure. Also I missed the branch coverage information. It seems to be counting only line coverage, as far as I know. With Gradle I cannot even run the tests. I am not a Gradle user so maybe I missed something. Here it is the output: JAVA_HOME="C:\Program Files\Java\jdk-11.0.2" cd C:\Users\Eduardo\Documents\NetBeansProjects\gradleproject1; C:\Users\Eduardo\.gradle\wrapper\dists\gradle-4.10.2-bin\cghg6c4gf4vkiutgsab8yrnwv\gradle-4.10.2\bin\gradle --configure-on-demand --rerun-tasks -x check test Configuration on demand is an incubating feature. > Task :compileJava > Task :processResources NO-SOURCE > Task :classes > Task :compileTestJava > Task :processTestResources NO-SOURCE > Task :testClasses Could not write standard input to Gradle Test Executor 1. java.io.IOException: Se est cerrando la canalizacin at java.base/java.io.FileOutputStream.writeBytes(Native Method) at java.base/java.io.FileOutputStream.write(FileOutputStream.java:354) at java.base/java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:81) at java.base/java.io.BufferedOutputStream.flush(BufferedOutputStream.java:142) at org.gradle.process.internal.streams.ExecOutputHandleRunner.forwardContent(ExecOutputHandleRunner.java:66) at org.gradle.process.internal.streams.ExecOutputHandleRunner.run(ExecOutputHandleRunner.java:51) at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63) at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:55) at java.base/java.lang.Thread.run(Thread.java:834) > Task :test FAILED Exception in thread "main" java.lang.reflect.InvocationTargetException at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at java.instrument/sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:513) at java.instrument/sun.instrument.InstrumentationImpl.loadClassAndCallPremain(InstrumentationImpl.java:525) Caused by: java.lang.RuntimeException: Class java/lang/UnknownError could not be instrumented.FATAL ERROR in native method: processing of -javaagent failed at org.jacoco.agent.rt.internal_c13123e.core.runtime.ModifiedSystemClassRuntime.createFor(ModifiedSystemClassRuntime.java:140) at org.jacoco.agent.rt.internal_c13123e.core.runtime.ModifiedSystemClassRuntime.createFor(ModifiedSystemClassRuntime.java:101) at org.jacoco.agent.rt.internal_c13123e.PreMain.createRuntime(PreMain.java:55) at org.jacoco.agent.rt.internal_c13123e.PreMain.premain(PreMain.java:47) ... 6 more Caused by: java.lang.NoSuchFieldException: $jacocoAccess at java.base/java.lang.Class.getField(Class.java:2000) at org.jacoco.agent.rt.internal_c13123e.core.runtime.ModifiedSystemClassRuntime.createFor(ModifiedSystemClassRuntime.java:138) ... 9 more De: Laszlo Kishalmi Enviado: sábado, 25 de mayo de 2019 1:49 Para: users@netbeans.apache.org Asunto: Re: JaCoCoverage plugin Hi! Actually JaCoCo support is out-of-the box in NetBeans, the additional plugin was required for Ant Based projects and it is not maintained right now (AFAIK it still has to be contributed by Oracle to Apache) So JaCoCo with Maven project do work though it require some configuration in the pom.xml. I'd say the easiest way is to achieve it if you just create a new Gradle Project from the IDE: File > New Project > Java with Gradle > Java Application | Java Class Library The new project will be created with Gradle's Jacoco plugin applied. NetBeans recognize that, so right clicking the project there will be a Code Coverage menu where you can enable the collection of the coverage results. From that point whenever some unit tests were executed the
Re: JaCoCoverage plugin
I opened this issue about this: https://issues.apache.org/jira/browse/NETBEANS-1997 On Fri, May 24, 2019 at 7:59 PM Laszlo Kishalmi wrote: > Hi! > > Actually JaCoCo support is out-of-the box in NetBeans, the additional > plugin was required for Ant Based projects and it is not maintained right > now (AFAIK it still has to be contributed by Oracle to Apache) > > So JaCoCo with Maven project do work though it require some configuration > in the pom.xml. > > I'd say the easiest way is to achieve it if you just create a new Gradle > Project from the IDE: File > New Project > Java with Gradle > Java > Application | Java Class Library > > The new project will be created with Gradle's Jacoco plugin applied. > NetBeans recognize that, so right clicking the project there will be a Code > Coverage menu where you can enable the collection of the coverage results. > From that point whenever some unit tests were executed the code coverage > results would be updated. > > on 5/24/19 3:54 PM, Eduardo Mosqueira Rey wrote: > > Hi all, > > > > I used in classroom the JaCoCoverage plugin with NetBeans 8.2 for the > students to check the coverage of their tests. > > It had an easy and straightforward installation and was very simple to > use, ideal for newbies. > > > > Nevertheless, the plugin is no longer maintained at it doesn’t work with > NetBeans 11.0. > > This year I want to migrate the classroom installation to Apache NetBeans > but the lack of a coverage tool is an inconvenient. > > > > Is there an easy way to install a Coverage tool (whatever) in NetBeans > 11.0? > > **easy to install** is an important requirement. > > > > Any suggestion would be appreciated. > > > > Many thanks, > > -- Eduardo > > > >
Re: JaCoCoverage plugin
Hi! Actually JaCoCo support is out-of-the box in NetBeans, the additional plugin was required for Ant Based projects and it is not maintained right now (AFAIK it still has to be contributed by Oracle to Apache) So JaCoCo with Maven project do work though it require some configuration in the pom.xml. I'd say the easiest way is to achieve it if you just create a new Gradle Project from the IDE: File > New Project > Java with Gradle > Java Application | Java Class Library The new project will be created with Gradle's Jacoco plugin applied. NetBeans recognize that, so right clicking the project there will be a Code Coverage menu where you can enable the collection of the coverage results. From that point whenever some unit tests were executed the code coverage results would be updated. on 5/24/19 3:54 PM, Eduardo Mosqueira Rey wrote: Hi all, I used in classroom the JaCoCoverage plugin with NetBeans 8.2 for the students to check the coverage of their tests. It had an easy and straightforward installation and was very simple to use, ideal for newbies. Nevertheless, the plugin is no longer maintained at it doesn’t work with NetBeans 11.0. This year I want to migrate the classroom installation to Apache NetBeans but the lack of a coverage tool is an inconvenient. Is there an easy way to install a Coverage tool (whatever) in NetBeans 11.0? **easy to install** is an important requirement. Any suggestion would be appreciated. Many thanks, -- Eduardo
JaCoCoverage plugin
Hi all, I used in classroom the JaCoCoverage plugin with NetBeans 8.2 for the students to check the coverage of their tests. It had an easy and straightforward installation and was very simple to use, ideal for newbies. Nevertheless, the plugin is no longer maintained at it doesn’t work with NetBeans 11.0. This year I want to migrate the classroom installation to Apache NetBeans but the lack of a coverage tool is an inconvenient. Is there an easy way to install a Coverage tool (whatever) in NetBeans 11.0? *easy to install* is an important requirement. Any suggestion would be appreciated. Many thanks, -- Eduardo
