Re: One of the unit tests not executed. Why?

2020-12-20 Thread Jose Ch
Can you try the newest version of surefire plugin?
*org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5*



El dom, 20 dic 2020 a las 5:03, Greenberg, Gary ()
escribió:

> I sure did clean and build the project.
>
> During the build all unit tests are executed except this one.
> When I am trying to run the test on this very particular class, I was
> getting the previously mentioned error.
>
>
>
> I did try to run Maven test from the command line several times and it
> fails in some random unit test. The one that succeed in Netbeans.
>
> I tried to run maven with different JDKs and increased heap size to 2GB,
> but I am still getting something like the following:
>
> [INFO]
> 
>
> [INFO] BUILD FAILURE
>
> [INFO]
> 
>
> [INFO] Total time:  01:47 min
>
> [INFO] Finished at: 2020-12-19T20:51:16-08:00
>
> [INFO]
> 
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.22.2:test (default-test)
> on project universal-batch-processor: There are test failures.
>
> [ERROR]
>
> [ERROR] Please refer to C:\Users\ggreenbe\OneDrive - Visa
> Inc\Development\Projects\universal-batch-processor\target\surefire-reports
> for the individual test results.
>
> [ERROR] Please refer to dump files (if any exist) [date].dump,
> [date]-jvmRun[N].dump and [date].dumpstream.
>
> [ERROR] The forked VM terminated without properly saying goodbye. VM crash
> or System.exit called?
>
> [ERROR] Command was cmd.exe /X /C ""C:\Program
> Files\Java\jdk-14.0.2\bin\java" -jar
> C:\Users\ggreenbe\AppData\Local\Temp\surefire5797367098824429966\surefirebooter5235882171158911878.jar
> C:\Users\ggreenbe\AppData\Local\Temp\surefire5797367098824429966
> 2020-12-19T20-49-39_741-jvmRun1 surefire8349322470433008227tmp
> surefire_018344052671012744992tmp"
>
> [ERROR] Process Exit Code: 0
>
> [ERROR] Crashed tests:
>
> [ERROR] com.visa.dpd.batch.uni.proc.cfg.BatchConfigTest
>
> [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: The
> forked VM terminated without properly saying goodbye. VM crash or
> System.exit called?
>
> [ERROR] Command was cmd.exe /X /C ""C:\Program
> Files\Java\jdk-14.0.2\bin\java" -jar
> C:\Users\ggreenbe\AppData\Local\Temp\surefire5797367098824429966\surefirebooter5235882171158911878.jar
> C:\Users\ggreenbe\AppData\Local\Temp\surefire5797367098824429966
> 2020-12-19T20-49-39_741-jvmRun1 surefire8349322470433008227tmp
> surefire_018344052671012744992tmp"
>
> [ERROR] Process Exit Code: 0
>
> [ERROR] Crashed tests:
>
> [ERROR] com.visa.dpd.batch.uni.proc.cfg.BatchConfigTest
>
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:669)
>
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:282)
>
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:245)
>
> [ERROR] at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1183)
>
> [ERROR] at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:1011)
>
> [ERROR] at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:857)
>
> [ERROR] at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
>
> [ERROR] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)
>
> [ERROR] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)
>
> [ERROR] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
>
> [ERROR] at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
>
> [ERROR] at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
>
> [ERROR] at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
>
> [ERROR] at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
>
> [ERROR] at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
>
> [ERROR] at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
>
> [ERROR] at
> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)
>
> [ERROR] at org.apache.maven.cli.MavenCli.execute(MavenCli.java:957)
>
> [ERROR] at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:289)
>
> [ERROR] at org.apache.maven.cli.MavenCli.main(MavenCli.java:193)
>
> [ERROR] at
> 

Re: Wildfly in NetBeans 11.3

2020-03-11 Thread Jose Ch
I think this PR fix it.

https://github.com/apache/netbeans/pull/2000

Regards.
Jose Contreras

El mié., 11 mar. 2020 a las 10:06, Miguel Cardoso Martins (<
miguelcardosomart...@gmail.com>) escribió:

> Hello all
>
> I downloaded the wildfly plugin but after installing and restarting the
> plugin is
> still not installed.
> Looking at the IDE logs I found the line
>
> INFO [org.netbeans.core.startup.NbEvents]: Warning: the module
> //modules/org-netbeans-modules-javaee-wildfly.jar could not be found,
> ignoring...
>
> Anyone experienced this before? Any Tips?
>
> Thanks
>


Re: Netbeans 11.2 Spring Framework problem

2020-02-04 Thread Jose Ch
Hi Tom,

This PR fix that problem. I tested with both 3.x & 4.x versions of Spring.

https://github.com/apache/netbeans/pull/1908

Regards.

Jose


El jue., 30 ene. 2020 a las 9:39, Tom M () escribió:

> When I create a new Java web project with Maven and add Spring Framework
> support and try to build it I get an error message "Failure to find
> org.springframework:spring-framework-bom:jar:4.0.1.RELEASE"
>
> The same is true for the 3.x version of Spring Framework. All I did was
>
> New Project -> Java with Maven -> Web Application and put in my name and
> folder info for the project.
>
> Next I right click the project
> Properties -> Frameworks -> Add -> Spring MVC -> select 4.0.1 and include
> JSTL
>
> As soon as I do that I get a warning on the project. If I expand the list
> of dependencies all look fine except for
> spring-framework-bom-4.0.1.RELEASE.jar if I hover over it I see "Dependency
> not yet downloaded. Build project to correct errors." So I build and get
> the following error"
>
> Failed to execute goal on project REPhotoTours: Could not resolve
> dependencies for project com.mydomain:MyNetbeansProject:war:1.0-SNAPSHOT:
> Failure to find org.springframework:spring-framework-bom:jar:4.0.1.RELEASE
> in https://repo.maven.apache.org/maven2 was cached in the local
> repository, resolution will not be reattempted until the update interval of
> central has elapsed or updates are forced -> [Help 1]
>
> I found this solution online
> https://stackoverflow.com/questions/37625875/dependency-resolution-exception-in-
> netbeans
> -maven-web-application-for-spring-fra/38700407#38700407?newreg=1a731c3515884682a1efef40fe33c3b0
>
> Which suggested adding type and scope to the dependency in pom.xml.
>
> 
>   org.springframework
>   spring-framework-bom
>   4.0.1.RELEASE
>   pom
>   import
> 
>
> When I do that, it works. This is an old thread so it doesn't make sense
> that Netbeans would have an error in such a popular framework for a few
> years without it being fixed so I think there might be something wrong with
> my configuration.
>
> I'm not that familiar with Maven. Can someone explain what adding type and
> scope exactly does and why it fixes it? Should it work in Netbeans without
> that? What should I be looking for?
>
> I'm using JDK-13.0.2 on windows 10 64 bit.
>


Re: 11.2 and JUnit 5 "no tests executed"

2019-12-18 Thread Jose Ch
I think it was already fix with this PR:
https://github.com/apache/netbeans/pull/1632

Regards
Jose

El mié., 18 dic. 2019 a las 6:36, John Mc ()
escribió:

> Hi Michael,
>
> Can you create a JIRA ticket for this please?
>
> https://issues.apache.org/jira/projects/NETBEANS
>
> If I get some time over Christmas, I might look to fix it, if possible so
> we can help others out moving forward?
>
> Regards
>
> John
>
> On Wed, 18 Dec 2019 at 10:44, Michael Remijan  wrote:
>
>> I am using Maven 3.3.9 bundled with NetBeans.
>>
>> This version of Maven uses the 2.12.4 version of the surefire plugin. I
>> switched to the latest non-milestone version:
>>
>> 
>> 
>> 
>> maven-surefire-plugin
>> 2.22.2
>> 
>> 
>> 
>>
>> And now it works. Thanks for the help!
>>
>>
>> On Wednesday, December 18, 2019, 02:03:14 AM CST, John Mc <
>> mcdonnell.j...@gmail.com> wrote:
>>
>>
>> Hi
>>
>> What version of maven are you running?
>>
>> Include the maven surefire plugin but check the JUnit 5 documentation for
>> what is the minimum version supported. I think off the top of my head it's
>> something like 2.21 but double check on their site.
>>
>> I'd guess that when you include that plugin I to your pom, Maven will
>> start to execute your tests.
>>
>> Regards
>>
>> John
>>
>> On Wed, 18 Dec 2019, 03:19 Michael Remijan, 
>> wrote:
>>
>> I've started a brand new Maven project and had NetBeans take care of the
>> POM updates when I added a unit test. NetBean automatically put in the
>> dependencies for JUnit 5. So far so good. But I can't seem to get the test
>> to run. NetBeans is always saying: "No tests executed".  Below are the
>> details...can't get much more simple I think.
>>
>> C O M M A N DL I N E
>> Here is the command line to run the tests (Alt + F6):
>>
>> cd D:\Projects\thoth-email;
>> JAVA_HOME=D:\\Applications\\java\\zulu11.35.15-ca-jdk11.0.5-win_x64 cmd /c
>> "\"\"D:\\Applications\\netbeans\\netbeans-11.0\\java\\maven\\bin\\mvn.cmd\"
>> -Dmaven.ext.class.path=D:\\Applications\\netbeans\\netbeans-11.0\\java\\maven-nblib\\netbeans-eventspy.jar
>> -Dfile.encoding=UTF-8 test\""
>>
>> P O M
>> Here is the POM:
>>
>> 
>> http://maven.apache.org/POM/4.0.0; xmlns:xsi="
>> http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation="
>> http://maven.apache.org/POM/4.0.0
>> http://maven.apache.org/xsd/maven-4.0.0.xsd;>
>> 4.0.0
>> org.thoth
>> thoth-email
>> 1.0.0.0-SNAPSHOT
>> jar
>> 
>> UTF-8
>> 11
>> 11
>> 
>>
>> 
>> 
>> org.junit.jupiter
>> junit-jupiter-api
>> 5.3.1
>> test
>> 
>> 
>> org.junit.jupiter
>> junit-jupiter-params
>> 5.3.1
>> test
>> 
>> 
>> org.junit.jupiter
>> junit-jupiter-engine
>> 5.3.1
>> test
>> 
>> 
>> 
>>
>>
>> J U N I TT E S T
>> Here is the Unit test...
>>
>> package org.thoth.email.ssl;
>> import org.junit.jupiter.api.Assertions;
>> import org.junit.jupiter.api.BeforeEach;
>> import org.junit.jupiter.api.Test;
>> public class SSLTest {
>> public SSLTest() {
>> }
>> @BeforeEach
>> public void setUp() {
>> }
>> @Test
>> public void a_test() throws Exception
>> {
>> System.out.printf("Hello test!%n");
>> Assertions.assertEquals("A", "A");
>> }
>> }
>>
>>
>> Any thoughts?
>>
>>


Re: Static code analysis - FindBugs (SpotBugs) support

2019-11-27 Thread Jose Ch
When you try to install it:

"FindBugs Integration" module has not been downloaded.

It does not exist in the plugin portal.

El mié., 27 nov. 2019 a las 14:29, Emilian Bold ()
escribió:

> I think JaCoCo works. I wonder why FindBugs doesn't work anymore?
>
> --emi
>
> On Wed, Nov 27, 2019 at 9:04 PM Mark A. Claassen 
> wrote:
> >
> > Once upon a time there was a FindBugs module for Netbeans. Is there one
> that works with Netbeans 11.  (FindBugs or its descendant 'SpotBugs')
> >
> > Does Netbeans have support for any more complete tools for static
> analysis besides the included "hints"?
> >
> > Mark Claassen
> > Senior Software Engineer
> >
> > Donnell Systems, Inc.
> > 130 South Main Street
> > Leighton Plaza Suite 375
> > South Bend, IN  46601
> > E-mail: mailto:mclaas...@ocie.net
> > Voice: (574)232-3784
> > Fax: (574)232-4014
> >
> > Disclaimer:
> > The opinions provided herein do not necessarily state or reflect
> > those of Donnell Systems, Inc.(DSI). DSI makes no warranty for and
> > assumes no legal liability or responsibility for the posting.
> >
> >
> >
> > -
> > 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
> >
>
> -
> 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: ISO-8859-1

2019-10-29 Thread Jose Ch
You can use the default option in the netbeans.conf

-J-Dfile.encoding=UTF8 // change encoding

El mar., 29 oct. 2019 a las 11:44, Juan Algaba ()
escribió:

> I'd recommend downloading the excellent encoding support plugin
> http://plugins.netbeans.org/plugin/60487/encoding-support
>
> [image: image.png]
>
> Though every time you open a file you'd have to check in the corner if nb
> is assuming the right encoding and change it if necessary.
>
> When working without a project, Does anyone know if there's a default
> encoding or if Netbeans uses heuristics to guess the file's encoding?
>
> I tested by saving a file in ISO-8859-1 with characters that wouldn't have
> the same byte code in UTF-8 i.e. "áíó" and upon reopening it
> successfully detected it as ISO-8859-1 but I'm not sure if it detected it
> or if it "remembered" the last encoding I set.
>
> As a last resort, you could simply create a new "Project with existing
> sources" on an upper folder level and add your source directory as sources
> for such project, the project's only purpose would be to set the default
> encoding and nothing else.
>
>
> On Mon, Oct 28, 2019 at 1:42 PM Jack Woehr  wrote:
>
>> Hmm I see ...
>>
>> Doesn't actually seem to do much at all.
>>
>> On Mon, Oct 28, 2019 at 2:34 PM Jack Woehr  wrote:
>>
>>> I sorta gave up on plugins, even in NetBeans, and just do my own git
>>> stuff, so I hadn't noticed.
>>>
>>> What's short on jEdit's plugin?
>>>
>>>
>>> On Mon, Oct 28, 2019 at 1:25 PM Glenn Holmer 
>>> wrote:
>>>
 On 10/28/19 1:33 PM, Jack Woehr wrote:
 > Try jEdit

 I am :) We used to use it at work, back in prehistoric times before we
 were using NetBeans. Unfortunately, its git plugin leaves something to
 be desired.

>>>
>
> --
>
> -Juan Algaba
>


Re: Problem using NetBeans on Ubuntu

2019-09-20 Thread Jose Ch
This is the download page for Apache NetBeans:

https://netbeans.apache.org/download/index.html

Is it the same page that you used a few days ago?

El vie., 20 sept. 2019 a las 17:23, Walter Oney ()
escribió:

> From: Neil C Smith 
>
> >>  I installed NetBeans IDE 10.0, in which Netbeans is at 8.3 Patch
> 2,
>
> > What exactly does that mean? Try 11.1. NetBeans 10.0 is no longer
> supported. There is a Snap available for Ubuntu as well as the installers
> and zip.
>
> Somebody connected with Apache wrote the code that generated the About box
> in which 10.0 and 8.3 Patch 2 appear, so your guess is probably better than
> mine.
>
> Anyhow, what is a "Snap" and why did I get version 10.0 of the IDE just a
> few days ago when I tried to install the current stable release?
>
> --
> Walter C. Oney, Jr., Esq.
> 267 Pearl Hill Rd., Fitchburg, MA 01420
> Tel.: 978-343-3390
> http://www.oneylaw.com
>
>
>
>
> -
> 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: Fw: Problem in installing netbeans 11 on a computer with JDK 13

2019-09-19 Thread Jose Ch
Does the netbeans installation was with the exe or the zip archive? The
easy way is to specify the JDK in the netbeans.conf file located in
/netbeans/etc/netbeans.conf.
e.g.
netbeans_jdkhome="/opt/jvm/zulu-13"

El mié., 18 sept. 2019 a las 22:05, xog blog ()
escribió:

> The netbeans 11 install program keeps complaining that it can't find JDK
> 13 (both are the latest versions, downloaded and installed this morning).
> To be sure, the name on the JDK executable was
> "jdk-13_windows-x64_bin.exe", and it was downloaded from Oracle.
>
> I tried adding the JDK directory to my PATH variable from windows; I tried
> running JDK from the command line with the path specified (using
> --javahome).
>
> In all cases, the installer complains that the JDK was not found on this
> computer.
>
> Any suggestions for troubleshooting this problem would be welcome.
>
> Paul
>