Solved, my mistake. The second NetBeans instance had unactivated features, once I activated the JavaSE feature all went to normal.
Is there a way to launch a NetBeans with some features pre-activated? Regards, Alex Il giorno mar 1 ott 2019 alle ore 16:08 Alessandro <[email protected]> ha scritto: > On further investigation this is less severe, it happens in a NetBeans > 11.2-beta1 instance launched from another NetBeans 11.2-beta1 instance from > a Maven NetBeans Module project. Maven projects open just fine in the > parent instance and pom.xml files are edited via the specialized editor in > it. > > It is however annoying as it impacts developing NetBeans plugins. > > Apologise for the alarming head-up. > > Regards, > Alex > > Il giorno mar 1 ott 2019 alle ore 15:56 Geertjan Wielenga < > [email protected]> ha scritto: > >> Can you reproduce the issue with fresh userdir and cachedir? >> >> Gj >> >> On Tue, 1 Oct 2019 at 15:55, Alessandro <[email protected]> wrote: >> >> > Hi all, >> > I have just realized that with NetBeans 11.2-beta1 pom.xml files are >> > opened in a vanilla XML editor instead of the specialized POM editor. >> > >> > This is a major regression in my opinion cause we loose code templates, >> > groupId/artifactId/version completion for dependencies, code generation, >> > effective POM inspection, POM dependency graph etc. >> > >> > Can anyone confirm? >> > >> > I also see a new "Open Advanced..." menu item in the context menu of a >> > pom.xml file in Project view that does nothing. >> > >> > Should I open an issue on JIRA? >> > >> > Regards, >> > Alex >> > >> >
