Fixed (I think).
It turns out that it was a combination of poor Nexus configuration
(group repository set as releases rather than mixed) plus a settings.xml
file that referenced both the group proxy repository as well as
individual repositories.
Why this didn't trigger issues with a command
Hi,
Matthias, I apologize if I sounded like I was disparaging NetBeans. That
is not my intention, and I think that NetBeans is an awesome IDE.
I will try to construct a set of projects that will help facilitate
understanding the issue I'm having. I'm not quite sure how to do this,
as my
Hi,
Am Mittwoch, dem 15.06.2022 um 12:32 -0700 schrieb Mark Eggers:
> Every time I open a project with a parent pom (with or without
> ), NetBeans re-indexes my remote repository. This even
> happens on sub-projects within a Maven multi-module project (and the
> parent specified as the parent
Another addendum:
Every time I open a project with a parent pom (with or without
), NetBeans re-indexes my remote repository. This even
happens on sub-projects within a Maven multi-module project (and the
parent specified as the parent project).
The only time it does not seem to happen is
Addendum:
Even with removed from the node,
NetBeans insists on re-indexing the remote repository.
This happens after every clean or build as long as pom.xml is open in
the IDE.
If pom.xml is not open in the editor, then no re-index occurs.
This definitely feels like a bug.
. . . just
Folks,
First of all, I apologize for not testing for the last two rounds (my bad).
Second of all, is anyone else seeing this?
Environment:
Windows 10 Professional - latest updates
NetBeans 14 installed from zip file
Running under javac 17.0.3 (adoptium.net)
Maven 3.8.6
Maven projects (Java
