Exactly. That was it. Indexing was disabled.
When I cleared this checkbox and after 1/2hour of indexing it started working.
Thanks to everybody for your help.
Gary Greenberg
Staff Software Engineer
Data Product Development, BI-A
E: ggree...@visa.com
M: 650-269-7902
[EmailSig-TaglineVersion]
From
Have you checked this? Tools>Options>Java>Maven>Index: "Completely
disable indexing".
The Visa security may have turned this on.
Brad.
On 31/8/20 11:28 am, HRH wrote:
The Maven dependency search failure on your system might be the
concomitant of that security update by Visa, which has sever
The Maven dependency search failure on your system might be the concomitant of
that security update by Visa, which has severely impacted your environment.
Have you considered to reinstall Netbeans, perhaps the latest stable version
that comes with Maven 3.6.3 (i.e. Netbeans 12.0)?
On Monda
On 8/30/2020 6:59 PM, Greenberg, Gary wrote:
I have deleted .m2 and also installed new version of Maven (3.5.4 ->
3.6.3)
Did you inform NetBeans about it? Tools>Options>Java>Maven>Execution.
And some of the other Maven Categories might have some bearing on the
problem, like "Index".
-erni
I have deleted .m2 and also installed new version of Maven (3.5.4 -> 3.6.3)
Still search for dependencies doesn’t work.
Doesn’t look like it is searching for anything.
In a fraction of a second it pops-up “No matching items” window.
Gary Greenberg
Staff Software Engineer
Data Product Development,
You must have an .m2 folder somewhere, delete it. NetBeans might not be
using the latest Maven version, best to use the latest Maven version.
At this point I cannot help you further. I simply suggest setting up Maven
from scratch.
Gj
On Sun, 30 Aug 2020 at 23:47, Greenberg, Gary
wrote:
>
>
>
>
What do you mean from scratch?
I was using Maven built-in into Netbeans.
Do you suggest to install maven outside of NB?
Gary Greenberg
Staff Software Engineer
Data Product Development, BI-A
E: ggree...@visa.com
M: 650-269-7902
[EmailSig-TaglineVersion]
From: Geertjan Wielenga
Sent: Sunday, Augu
Well, sounds like something is wrong with your Maven installation. I
recommend you uninstall, remove the .m2 folder, and set up Maven again
completely from scratch.
Gj
On Sun, Aug 30, 2020 at 11:05 PM Greenberg, Gary
wrote:
> I found out what was wrong with it.
> Apparently security update remo
I found out what was wrong with it.
Apparently security update removed almost half of jars in JDK1.8 (my project is
using this platform).
Why did it do so, I do not know.
Anyway, I reinstalled Java 8 JDK (and upgraded from build 251 to 265 along the
way).
Hanging and problems with opening files d
