You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@netbeans.apache.org by Alessandro <al...@gmail.com> on 2019/10/01 13:54:56 UTC
NetBeans 11.2-beta1: broken pom.xml files editing
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
Re: NetBeans 11.2-beta1: broken pom.xml files editing
Posted by Alessandro <al...@gmail.com>.
Hi Laszlo,
thank you very much for suggesting this method. Will try later today.
Greets,
Alex
Il giorno mer 2 ott 2019 alle ore 19:32 Laszlo Kishalmi <
laszlo.kishalmi@gmail.com> ha scritto:
>
> You can remove the ergonomic cluster from etc/netbeans.clusters, that
> make the other clusters activated by default.
>
> On 10/2/19 2:19 AM, Alessandro wrote:
> > 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 <
> alex.falappa@gmail.com>
> > 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 <
> >> geertjan@apache.org> ha scritto:
> >>
> >>> Can you reproduce the issue with fresh userdir and cachedir?
> >>>
> >>> Gj
> >>>
> >>> On Tue, 1 Oct 2019 at 15:55, Alessandro <al...@gmail.com>
> 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
> >>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: dev-help@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>
Re: NetBeans 11.2-beta1: broken pom.xml files editing
Posted by Laszlo Kishalmi <la...@gmail.com>.
You can remove the ergonomic cluster from etc/netbeans.clusters, that
make the other clusters activated by default.
On 10/2/19 2:19 AM, Alessandro wrote:
> 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 <al...@gmail.com>
> 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 <
>> geertjan@apache.org> ha scritto:
>>
>>> Can you reproduce the issue with fresh userdir and cachedir?
>>>
>>> Gj
>>>
>>> On Tue, 1 Oct 2019 at 15:55, Alessandro <al...@gmail.com> 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
>>>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: NetBeans 11.2-beta1: broken pom.xml files editing
Posted by Alessandro <al...@gmail.com>.
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 <al...@gmail.com>
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 <
> geertjan@apache.org> ha scritto:
>
>> Can you reproduce the issue with fresh userdir and cachedir?
>>
>> Gj
>>
>> On Tue, 1 Oct 2019 at 15:55, Alessandro <al...@gmail.com> 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
>> >
>>
>
Re: NetBeans 11.2-beta1: broken pom.xml files editing
Posted by Alessandro <al...@gmail.com>.
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 <
geertjan@apache.org> ha scritto:
> Can you reproduce the issue with fresh userdir and cachedir?
>
> Gj
>
> On Tue, 1 Oct 2019 at 15:55, Alessandro <al...@gmail.com> 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
> >
>
Re: NetBeans 11.2-beta1: broken pom.xml files editing
Posted by Geertjan Wielenga <ge...@apache.org>.
Can you reproduce the issue with fresh userdir and cachedir?
Gj
On Tue, 1 Oct 2019 at 15:55, Alessandro <al...@gmail.com> 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
>