You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@netbeans.apache.org by Geertjan Wielenga <ge...@googlemail.com.INVALID> on 2019/01/28 19:05:35 UTC
What to do with features for EARs and EJBs?
Hi all,
Especially to Java/Jakarta EE people out there, e.g., Ivar, Josh, David, at
least -- please advise what should be done with the EAR and EJB support, as
described here:
https://blogs.apache.org/netbeans/entry/enterprise-cluster-integrated-into-apache
And, hurray, thanks Matthias especially, and Vikas, Arunava, Sarvesh, and
Reema, for a lot of work on relicensing, for getting the enterprise cluster
integrated!
Gj
Re: What to do with features for EARs and EJBs?
Posted by Geertjan Wielenga <ge...@googlemail.com.INVALID>.
>
> before we decide about the color of the bike shed, it would be great if
> we _first_ make sure, that it is still safe to use and works as
> expected. The cluster was only partially integrated and the jboss,
> wsit, wsitext, weblogic, wildfly and metro integrations are currently
> disabled.
>
> After that I would see, that it survives the next heavy weather, as in:
> What happens when java 11 meets JavaEE 6/7? I get some bad vibes there.
>
Agree completely, by the way.
There's quite a lot of work to do and would be great if several would pitch
in and try out the current daily build, you'll find problems, errors, etc.
No need to panic, just file issues and make them blockers if they're
related to Java EE since we need to focus on these for this release.
Gj
On Mon, Jan 28, 2019 at 9:22 PM Matthias Bläsing <mb...@doppel-helix.eu>
wrote:
> Hi,
>
> Am Montag, den 28.01.2019, 21:06 +0100 schrieb Geertjan Wielenga:
> > OK, OK, let's assume everyone continues to say 'keep it', the question is
> > how do we call those categories, one is right now 'Java Web' and the
> other
> > 'Java EE', does that still make sense? In the referenced blog entry, I
> > suggest 'Modern Java EE' and 'Vintage Java EE', or should it be as it is,
> > or different, if so, how?
>
> before we decide about the color of the bike shed, it would be great if
> we _first_ make sure, that it is still safe to use and works as
> expected. The cluster was only partially integrated and the jboss,
> wsit, wsitext, weblogic, wildfly and metro integrations are currently
> disabled.
>
> After that I would see, that it survives the next heavy weather, as in:
> What happens when java 11 meets JavaEE 6/7? I get some bad vibes there.
>
> Greetings
>
> Matthias
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>
Re: What to do with features for EARs and EJBs?
Posted by Matthias Bläsing <mb...@doppel-helix.eu>.
Hi,
Am Montag, den 28.01.2019, 21:06 +0100 schrieb Geertjan Wielenga:
> OK, OK, let's assume everyone continues to say 'keep it', the question is
> how do we call those categories, one is right now 'Java Web' and the other
> 'Java EE', does that still make sense? In the referenced blog entry, I
> suggest 'Modern Java EE' and 'Vintage Java EE', or should it be as it is,
> or different, if so, how?
before we decide about the color of the bike shed, it would be great if
we _first_ make sure, that it is still safe to use and works as
expected. The cluster was only partially integrated and the jboss,
wsit, wsitext, weblogic, wildfly and metro integrations are currently
disabled.
After that I would see, that it survives the next heavy weather, as in:
What happens when java 11 meets JavaEE 6/7? I get some bad vibes there.
Greetings
Matthias
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: What to do with features for EARs and EJBs?
Posted by Geertjan Wielenga <ge...@googlemail.com.INVALID>.
Well, take a look at the blog entry -- if you were going to use Java EE,
you'd go to the Java EE category, and not find Java Web applications:
https://blogs.apache.org/netbeans/entry/enterprise-cluster-integrated-into-apache
But, since you use Maven, you'd go to the Maven category and not have this
problem.
Gj
On Mon, Jan 28, 2019 at 10:01 PM Kenneth Fogel <kf...@dawsoncollege.qc.ca>
wrote:
> Have I missed something? Have EJBs and EARs been deprecated? If not then
> why are we discussing whether or not to include them or what to call them.
>
> Ken
>
>
> -----Original Message-----
> From: Antonio <an...@vieiro.net>
> Sent: January 28, 2019 3:13 PM
> To: dev@netbeans.incubator.apache.org
> Subject: Re: What to do with features for EARs and EJBs?
>
> So I assume you can call it either "Vintage" or "Legacy".
>
> That's what people call me at home too... X-D
>
> El 28/1/19 a las 21:10, Antonio escribió:
> > Once upon a long time ago (when I was young) that was called... J2EE
> > :-)
> >
> > El 28/1/19 a las 21:06, Geertjan Wielenga escribió:
> >> OK, OK, let's assume everyone continues to say 'keep it', the
> >> question is how do we call those categories, one is right now 'Java
> >> Web' and the other 'Java EE', does that still make sense? In the
> >> referenced blog entry, I suggest 'Modern Java EE' and 'Vintage Java
> >> EE', or should it be as it is, or different, if so, how?
> >>
> >> Gj
> >>
> >> On Mon, Jan 28, 2019 at 8:59 PM Tomas Poledny <sa...@gmail.com>
> wrote:
> >>
> >>> +1 to keep. I am using it on my current project.
> >>>
> >>> On Mon, Jan 28, 2019, 20:54 Gary Bello <gary.bello@gmail.com wrote:
> >>>
> >>>> +1 for ejb/ear support
> >>>>
> >>>> On Mon, Jan 28, 2019 at 11:52 AM Andreas Ernst <ae...@ae-online.de>
> wrote:
> >>>>
> >>>>> +1 to keep the EAR and EJB support. YES, please.
> >>>>>
> >>>>> Am 28.01.19 um 20:42 schrieb Gaurav Gupta:
> >>>>>> +1 to keep the EAR and EJB support.
> >>>>>>
> >>>>>> On Tue, 29 Jan 2019 at 1:07 AM, Antonio <an...@vieiro.net> wrote:
> >>>>>>
> >>>>>>> Hi,
> >>>>>>>
> >>>>>>> Last year I had to help out a customer that was stuck in Java 6
> >>>>>>> / WebLogic 8. NetBeans was of great help for me.
> >>>>>>>
> >>>>>>> I'd try to keep the EAR/EJB functionality. Don't know if as a
> >>>>>>> plugin
> >>>> or
> >>>>>>> bundled in the IDE, though.
> >>>>>>>
> >>>>>>> Maybe it saves the day to somebody else in the future.
> >>>>>>>
> >>>>>>> Cheers,
> >>>>>>> Antonio
> >>>>>>>
> >>>>>>> El 28/1/19 a las 20:05, Geertjan Wielenga escribió:
> >>>>>>>> Hi all,
> >>>>>>>>
> >>>>>>>> Especially to Java/Jakarta EE people out there, e.g., Ivar,
> >>>>>>>> Josh,
> >>>>> David,
> >>>>>>> at
> >>>>>>>> least -- please advise what should be done with the EAR and EJB
> >>>>> support,
> >>>>>>> as
> >>>>>>>> described here:
> >>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>
> >>>>
> >>> https://blogs.apache.org/netbeans/entry/enterprise-cluster-integrate
> >>> d-into-apache
> >>>
> >>>>>>>>
> >>>>>>>> And, hurray, thanks Matthias especially, and Vikas, Arunava,
> >>> Sarvesh,
> >>>>> and
> >>>>>>>> Reema, for a lot of work on relicensing, for getting the
> >>>>>>>> enterprise
> >>>>>>> cluster
> >>>>>>>> integrated!
> >>>>>>>>
> >>>>>>>> Gj
> >>>>>>>>
> >>>>>>>
> >>>>>>>
> >>> --------------------------------------------------------------------
> >>> -
> >>>>>>> To unsubscribe, e-mail:
> >>> dev-unsubscribe@netbeans.incubator.apache.org
> >>>>>>> For additional commands, e-mail:
> >>>> dev-help@netbeans.incubator.apache.org
> >>>>>>>
> >>>>>>> For further information about the NetBeans mailing lists, visit:
> >>>>>>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lis
> >>>>>>> ts
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> --
> >>>>>> Thanks and kind regards,
> >>>>>> Gaurav Gupta
> >>>>>> <https://twitter.com/ImJeddict> <https://jeddict.github.io/>
> >>>>>> <https://www.youtube.com/JPAModeler>
> >>>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>> ae | Andreas Ernst | IT Spektrum
> >>>>> Postfach 5, 65612 Beselich
> >>>>> Schupbacher Str. 32, 65614 Beselich, Germany
> >>>>> Tel: +49-6484-91002 Fax: +49-6484-91003 ae@ae-online.de |
> >>>>> www.ae-online.de www.tachyon-online.de
> >>>>>
> >>>>> ------------------------------------------------------------------
> >>>>> --- To unsubscribe, e-mail:
> >>>>> dev-unsubscribe@netbeans.incubator.apache.org
> >>>>> For additional commands, e-mail:
> >>> dev-help@netbeans.incubator.apache.org
> >>>>>
> >>>>> For further information about the NetBeans mailing lists, visit:
> >>>>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>
> >>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>
RE: What to do with features for EARs and EJBs?
Posted by Kenneth Fogel <kf...@dawsoncollege.qc.ca>.
Have I missed something? Have EJBs and EARs been deprecated? If not then why are we discussing whether or not to include them or what to call them.
Ken
-----Original Message-----
From: Antonio <an...@vieiro.net>
Sent: January 28, 2019 3:13 PM
To: dev@netbeans.incubator.apache.org
Subject: Re: What to do with features for EARs and EJBs?
So I assume you can call it either "Vintage" or "Legacy".
That's what people call me at home too... X-D
El 28/1/19 a las 21:10, Antonio escribió:
> Once upon a long time ago (when I was young) that was called... J2EE
> :-)
>
> El 28/1/19 a las 21:06, Geertjan Wielenga escribió:
>> OK, OK, let's assume everyone continues to say 'keep it', the
>> question is how do we call those categories, one is right now 'Java
>> Web' and the other 'Java EE', does that still make sense? In the
>> referenced blog entry, I suggest 'Modern Java EE' and 'Vintage Java
>> EE', or should it be as it is, or different, if so, how?
>>
>> Gj
>>
>> On Mon, Jan 28, 2019 at 8:59 PM Tomas Poledny <sa...@gmail.com> wrote:
>>
>>> +1 to keep. I am using it on my current project.
>>>
>>> On Mon, Jan 28, 2019, 20:54 Gary Bello <gary.bello@gmail.com wrote:
>>>
>>>> +1 for ejb/ear support
>>>>
>>>> On Mon, Jan 28, 2019 at 11:52 AM Andreas Ernst <ae...@ae-online.de> wrote:
>>>>
>>>>> +1 to keep the EAR and EJB support. YES, please.
>>>>>
>>>>> Am 28.01.19 um 20:42 schrieb Gaurav Gupta:
>>>>>> +1 to keep the EAR and EJB support.
>>>>>>
>>>>>> On Tue, 29 Jan 2019 at 1:07 AM, Antonio <an...@vieiro.net> wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> Last year I had to help out a customer that was stuck in Java 6
>>>>>>> / WebLogic 8. NetBeans was of great help for me.
>>>>>>>
>>>>>>> I'd try to keep the EAR/EJB functionality. Don't know if as a
>>>>>>> plugin
>>>> or
>>>>>>> bundled in the IDE, though.
>>>>>>>
>>>>>>> Maybe it saves the day to somebody else in the future.
>>>>>>>
>>>>>>> Cheers,
>>>>>>> Antonio
>>>>>>>
>>>>>>> El 28/1/19 a las 20:05, Geertjan Wielenga escribió:
>>>>>>>> Hi all,
>>>>>>>>
>>>>>>>> Especially to Java/Jakarta EE people out there, e.g., Ivar,
>>>>>>>> Josh,
>>>>> David,
>>>>>>> at
>>>>>>>> least -- please advise what should be done with the EAR and EJB
>>>>> support,
>>>>>>> as
>>>>>>>> described here:
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>
>>>>
>>> https://blogs.apache.org/netbeans/entry/enterprise-cluster-integrate
>>> d-into-apache
>>>
>>>>>>>>
>>>>>>>> And, hurray, thanks Matthias especially, and Vikas, Arunava,
>>> Sarvesh,
>>>>> and
>>>>>>>> Reema, for a lot of work on relicensing, for getting the
>>>>>>>> enterprise
>>>>>>> cluster
>>>>>>>> integrated!
>>>>>>>>
>>>>>>>> Gj
>>>>>>>>
>>>>>>>
>>>>>>>
>>> --------------------------------------------------------------------
>>> -
>>>>>>> To unsubscribe, e-mail:
>>> dev-unsubscribe@netbeans.incubator.apache.org
>>>>>>> For additional commands, e-mail:
>>>> dev-help@netbeans.incubator.apache.org
>>>>>>>
>>>>>>> For further information about the NetBeans mailing lists, visit:
>>>>>>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lis
>>>>>>> ts
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>> Thanks and kind regards,
>>>>>> Gaurav Gupta
>>>>>> <https://twitter.com/ImJeddict> <https://jeddict.github.io/>
>>>>>> <https://www.youtube.com/JPAModeler>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> ae | Andreas Ernst | IT Spektrum
>>>>> Postfach 5, 65612 Beselich
>>>>> Schupbacher Str. 32, 65614 Beselich, Germany
>>>>> Tel: +49-6484-91002 Fax: +49-6484-91003 ae@ae-online.de |
>>>>> www.ae-online.de www.tachyon-online.de
>>>>>
>>>>> ------------------------------------------------------------------
>>>>> --- To unsubscribe, e-mail:
>>>>> dev-unsubscribe@netbeans.incubator.apache.org
>>>>> For additional commands, e-mail:
>>> dev-help@netbeans.incubator.apache.org
>>>>>
>>>>> For further information about the NetBeans mailing lists, visit:
>>>>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: What to do with features for EARs and EJBs?
Posted by Antonio <an...@vieiro.net>.
So I assume you can call it either "Vintage" or "Legacy".
That's what people call me at home too... X-D
El 28/1/19 a las 21:10, Antonio escribió:
> Once upon a long time ago (when I was young) that was called... J2EE :-)
>
> El 28/1/19 a las 21:06, Geertjan Wielenga escribió:
>> OK, OK, let's assume everyone continues to say 'keep it', the question is
>> how do we call those categories, one is right now 'Java Web' and the
>> other
>> 'Java EE', does that still make sense? In the referenced blog entry, I
>> suggest 'Modern Java EE' and 'Vintage Java EE', or should it be as it is,
>> or different, if so, how?
>>
>> Gj
>>
>> On Mon, Jan 28, 2019 at 8:59 PM Tomas Poledny <sa...@gmail.com> wrote:
>>
>>> +1 to keep. I am using it on my current project.
>>>
>>> On Mon, Jan 28, 2019, 20:54 Gary Bello <gary.bello@gmail.com wrote:
>>>
>>>> +1 for ejb/ear support
>>>>
>>>> On Mon, Jan 28, 2019 at 11:52 AM Andreas Ernst <ae...@ae-online.de> wrote:
>>>>
>>>>> +1 to keep the EAR and EJB support. YES, please.
>>>>>
>>>>> Am 28.01.19 um 20:42 schrieb Gaurav Gupta:
>>>>>> +1 to keep the EAR and EJB support.
>>>>>>
>>>>>> On Tue, 29 Jan 2019 at 1:07 AM, Antonio <an...@vieiro.net> wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> Last year I had to help out a customer that was stuck in Java 6 /
>>>>>>> WebLogic 8. NetBeans was of great help for me.
>>>>>>>
>>>>>>> I'd try to keep the EAR/EJB functionality. Don't know if as a plugin
>>>> or
>>>>>>> bundled in the IDE, though.
>>>>>>>
>>>>>>> Maybe it saves the day to somebody else in the future.
>>>>>>>
>>>>>>> Cheers,
>>>>>>> Antonio
>>>>>>>
>>>>>>> El 28/1/19 a las 20:05, Geertjan Wielenga escribió:
>>>>>>>> Hi all,
>>>>>>>>
>>>>>>>> Especially to Java/Jakarta EE people out there, e.g., Ivar, Josh,
>>>>> David,
>>>>>>> at
>>>>>>>> least -- please advise what should be done with the EAR and EJB
>>>>> support,
>>>>>>> as
>>>>>>>> described here:
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>
>>>>
>>> https://blogs.apache.org/netbeans/entry/enterprise-cluster-integrated-into-apache
>>>
>>>>>>>>
>>>>>>>> And, hurray, thanks Matthias especially, and Vikas, Arunava,
>>> Sarvesh,
>>>>> and
>>>>>>>> Reema, for a lot of work on relicensing, for getting the enterprise
>>>>>>> cluster
>>>>>>>> integrated!
>>>>>>>>
>>>>>>>> Gj
>>>>>>>>
>>>>>>>
>>>>>>>
>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail:
>>> dev-unsubscribe@netbeans.incubator.apache.org
>>>>>>> For additional commands, e-mail:
>>>> dev-help@netbeans.incubator.apache.org
>>>>>>>
>>>>>>> For further information about the NetBeans mailing lists, visit:
>>>>>>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>> Thanks and kind regards,
>>>>>> Gaurav Gupta
>>>>>> <https://twitter.com/ImJeddict> <https://jeddict.github.io/>
>>>>>> <https://www.youtube.com/JPAModeler>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> ae | Andreas Ernst | IT Spektrum
>>>>> Postfach 5, 65612 Beselich
>>>>> Schupbacher Str. 32, 65614 Beselich, Germany
>>>>> Tel: +49-6484-91002 Fax: +49-6484-91003
>>>>> ae@ae-online.de | www.ae-online.de
>>>>> www.tachyon-online.de
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
>>>>> For additional commands, e-mail:
>>> dev-help@netbeans.incubator.apache.org
>>>>>
>>>>> For further information about the NetBeans mailing lists, visit:
>>>>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: What to do with features for EARs and EJBs?
Posted by Antonio <an...@vieiro.net>.
Once upon a long time ago (when I was young) that was called... J2EE :-)
El 28/1/19 a las 21:06, Geertjan Wielenga escribió:
> OK, OK, let's assume everyone continues to say 'keep it', the question is
> how do we call those categories, one is right now 'Java Web' and the other
> 'Java EE', does that still make sense? In the referenced blog entry, I
> suggest 'Modern Java EE' and 'Vintage Java EE', or should it be as it is,
> or different, if so, how?
>
> Gj
>
> On Mon, Jan 28, 2019 at 8:59 PM Tomas Poledny <sa...@gmail.com> wrote:
>
>> +1 to keep. I am using it on my current project.
>>
>> On Mon, Jan 28, 2019, 20:54 Gary Bello <gary.bello@gmail.com wrote:
>>
>>> +1 for ejb/ear support
>>>
>>> On Mon, Jan 28, 2019 at 11:52 AM Andreas Ernst <ae...@ae-online.de> wrote:
>>>
>>>> +1 to keep the EAR and EJB support. YES, please.
>>>>
>>>> Am 28.01.19 um 20:42 schrieb Gaurav Gupta:
>>>>> +1 to keep the EAR and EJB support.
>>>>>
>>>>> On Tue, 29 Jan 2019 at 1:07 AM, Antonio <an...@vieiro.net> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> Last year I had to help out a customer that was stuck in Java 6 /
>>>>>> WebLogic 8. NetBeans was of great help for me.
>>>>>>
>>>>>> I'd try to keep the EAR/EJB functionality. Don't know if as a plugin
>>> or
>>>>>> bundled in the IDE, though.
>>>>>>
>>>>>> Maybe it saves the day to somebody else in the future.
>>>>>>
>>>>>> Cheers,
>>>>>> Antonio
>>>>>>
>>>>>> El 28/1/19 a las 20:05, Geertjan Wielenga escribió:
>>>>>>> Hi all,
>>>>>>>
>>>>>>> Especially to Java/Jakarta EE people out there, e.g., Ivar, Josh,
>>>> David,
>>>>>> at
>>>>>>> least -- please advise what should be done with the EAR and EJB
>>>> support,
>>>>>> as
>>>>>>> described here:
>>>>>>>
>>>>>>>
>>>>>>
>>>>
>>>
>> https://blogs.apache.org/netbeans/entry/enterprise-cluster-integrated-into-apache
>>>>>>>
>>>>>>> And, hurray, thanks Matthias especially, and Vikas, Arunava,
>> Sarvesh,
>>>> and
>>>>>>> Reema, for a lot of work on relicensing, for getting the enterprise
>>>>>> cluster
>>>>>>> integrated!
>>>>>>>
>>>>>>> Gj
>>>>>>>
>>>>>>
>>>>>>
>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail:
>> dev-unsubscribe@netbeans.incubator.apache.org
>>>>>> For additional commands, e-mail:
>>> dev-help@netbeans.incubator.apache.org
>>>>>>
>>>>>> For further information about the NetBeans mailing lists, visit:
>>>>>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>> Thanks and kind regards,
>>>>> Gaurav Gupta
>>>>> <https://twitter.com/ImJeddict> <https://jeddict.github.io/>
>>>>> <https://www.youtube.com/JPAModeler>
>>>>>
>>>>
>>>>
>>>> --
>>>> ae | Andreas Ernst | IT Spektrum
>>>> Postfach 5, 65612 Beselich
>>>> Schupbacher Str. 32, 65614 Beselich, Germany
>>>> Tel: +49-6484-91002 Fax: +49-6484-91003
>>>> ae@ae-online.de | www.ae-online.de
>>>> www.tachyon-online.de
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
>>>> For additional commands, e-mail:
>> dev-help@netbeans.incubator.apache.org
>>>>
>>>> For further information about the NetBeans mailing lists, visit:
>>>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>>>
>>>>
>>>>
>>>>
>>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: What to do with features for EARs and EJBs?
Posted by Geertjan Wielenga <ge...@googlemail.com.INVALID>.
OK, OK, let's assume everyone continues to say 'keep it', the question is
how do we call those categories, one is right now 'Java Web' and the other
'Java EE', does that still make sense? In the referenced blog entry, I
suggest 'Modern Java EE' and 'Vintage Java EE', or should it be as it is,
or different, if so, how?
Gj
On Mon, Jan 28, 2019 at 8:59 PM Tomas Poledny <sa...@gmail.com> wrote:
> +1 to keep. I am using it on my current project.
>
> On Mon, Jan 28, 2019, 20:54 Gary Bello <gary.bello@gmail.com wrote:
>
> > +1 for ejb/ear support
> >
> > On Mon, Jan 28, 2019 at 11:52 AM Andreas Ernst <ae...@ae-online.de> wrote:
> >
> > > +1 to keep the EAR and EJB support. YES, please.
> > >
> > > Am 28.01.19 um 20:42 schrieb Gaurav Gupta:
> > > > +1 to keep the EAR and EJB support.
> > > >
> > > > On Tue, 29 Jan 2019 at 1:07 AM, Antonio <an...@vieiro.net> wrote:
> > > >
> > > >> Hi,
> > > >>
> > > >> Last year I had to help out a customer that was stuck in Java 6 /
> > > >> WebLogic 8. NetBeans was of great help for me.
> > > >>
> > > >> I'd try to keep the EAR/EJB functionality. Don't know if as a plugin
> > or
> > > >> bundled in the IDE, though.
> > > >>
> > > >> Maybe it saves the day to somebody else in the future.
> > > >>
> > > >> Cheers,
> > > >> Antonio
> > > >>
> > > >> El 28/1/19 a las 20:05, Geertjan Wielenga escribió:
> > > >>> Hi all,
> > > >>>
> > > >>> Especially to Java/Jakarta EE people out there, e.g., Ivar, Josh,
> > > David,
> > > >> at
> > > >>> least -- please advise what should be done with the EAR and EJB
> > > support,
> > > >> as
> > > >>> described here:
> > > >>>
> > > >>>
> > > >>
> > >
> >
> https://blogs.apache.org/netbeans/entry/enterprise-cluster-integrated-into-apache
> > > >>>
> > > >>> And, hurray, thanks Matthias especially, and Vikas, Arunava,
> Sarvesh,
> > > and
> > > >>> Reema, for a lot of work on relicensing, for getting the enterprise
> > > >> cluster
> > > >>> integrated!
> > > >>>
> > > >>> Gj
> > > >>>
> > > >>
> > > >>
> ---------------------------------------------------------------------
> > > >> To unsubscribe, e-mail:
> dev-unsubscribe@netbeans.incubator.apache.org
> > > >> For additional commands, e-mail:
> > dev-help@netbeans.incubator.apache.org
> > > >>
> > > >> For further information about the NetBeans mailing lists, visit:
> > > >> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> > > >>
> > > >>
> > > >>
> > > >> --
> > > > Thanks and kind regards,
> > > > Gaurav Gupta
> > > > <https://twitter.com/ImJeddict> <https://jeddict.github.io/>
> > > > <https://www.youtube.com/JPAModeler>
> > > >
> > >
> > >
> > > --
> > > ae | Andreas Ernst | IT Spektrum
> > > Postfach 5, 65612 Beselich
> > > Schupbacher Str. 32, 65614 Beselich, Germany
> > > Tel: +49-6484-91002 Fax: +49-6484-91003
> > > ae@ae-online.de | www.ae-online.de
> > > www.tachyon-online.de
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> > > For additional commands, e-mail:
> dev-help@netbeans.incubator.apache.org
> > >
> > > For further information about the NetBeans mailing lists, visit:
> > > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> > >
> > >
> > >
> > >
> >
>
Re: What to do with features for EARs and EJBs?
Posted by Tomas Poledny <sa...@gmail.com>.
+1 to keep. I am using it on my current project.
On Mon, Jan 28, 2019, 20:54 Gary Bello <gary.bello@gmail.com wrote:
> +1 for ejb/ear support
>
> On Mon, Jan 28, 2019 at 11:52 AM Andreas Ernst <ae...@ae-online.de> wrote:
>
> > +1 to keep the EAR and EJB support. YES, please.
> >
> > Am 28.01.19 um 20:42 schrieb Gaurav Gupta:
> > > +1 to keep the EAR and EJB support.
> > >
> > > On Tue, 29 Jan 2019 at 1:07 AM, Antonio <an...@vieiro.net> wrote:
> > >
> > >> Hi,
> > >>
> > >> Last year I had to help out a customer that was stuck in Java 6 /
> > >> WebLogic 8. NetBeans was of great help for me.
> > >>
> > >> I'd try to keep the EAR/EJB functionality. Don't know if as a plugin
> or
> > >> bundled in the IDE, though.
> > >>
> > >> Maybe it saves the day to somebody else in the future.
> > >>
> > >> Cheers,
> > >> Antonio
> > >>
> > >> El 28/1/19 a las 20:05, Geertjan Wielenga escribió:
> > >>> Hi all,
> > >>>
> > >>> Especially to Java/Jakarta EE people out there, e.g., Ivar, Josh,
> > David,
> > >> at
> > >>> least -- please advise what should be done with the EAR and EJB
> > support,
> > >> as
> > >>> described here:
> > >>>
> > >>>
> > >>
> >
> https://blogs.apache.org/netbeans/entry/enterprise-cluster-integrated-into-apache
> > >>>
> > >>> And, hurray, thanks Matthias especially, and Vikas, Arunava, Sarvesh,
> > and
> > >>> Reema, for a lot of work on relicensing, for getting the enterprise
> > >> cluster
> > >>> integrated!
> > >>>
> > >>> Gj
> > >>>
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> > >> For additional commands, e-mail:
> dev-help@netbeans.incubator.apache.org
> > >>
> > >> For further information about the NetBeans mailing lists, visit:
> > >> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> > >>
> > >>
> > >>
> > >> --
> > > Thanks and kind regards,
> > > Gaurav Gupta
> > > <https://twitter.com/ImJeddict> <https://jeddict.github.io/>
> > > <https://www.youtube.com/JPAModeler>
> > >
> >
> >
> > --
> > ae | Andreas Ernst | IT Spektrum
> > Postfach 5, 65612 Beselich
> > Schupbacher Str. 32, 65614 Beselich, Germany
> > Tel: +49-6484-91002 Fax: +49-6484-91003
> > ae@ae-online.de | www.ae-online.de
> > www.tachyon-online.de
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> > For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
> >
> > For further information about the NetBeans mailing lists, visit:
> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >
> >
> >
> >
>
Re: What to do with features for EARs and EJBs?
Posted by Gary Bello <ga...@gmail.com>.
+1 for ejb/ear support
On Mon, Jan 28, 2019 at 11:52 AM Andreas Ernst <ae...@ae-online.de> wrote:
> +1 to keep the EAR and EJB support. YES, please.
>
> Am 28.01.19 um 20:42 schrieb Gaurav Gupta:
> > +1 to keep the EAR and EJB support.
> >
> > On Tue, 29 Jan 2019 at 1:07 AM, Antonio <an...@vieiro.net> wrote:
> >
> >> Hi,
> >>
> >> Last year I had to help out a customer that was stuck in Java 6 /
> >> WebLogic 8. NetBeans was of great help for me.
> >>
> >> I'd try to keep the EAR/EJB functionality. Don't know if as a plugin or
> >> bundled in the IDE, though.
> >>
> >> Maybe it saves the day to somebody else in the future.
> >>
> >> Cheers,
> >> Antonio
> >>
> >> El 28/1/19 a las 20:05, Geertjan Wielenga escribió:
> >>> Hi all,
> >>>
> >>> Especially to Java/Jakarta EE people out there, e.g., Ivar, Josh,
> David,
> >> at
> >>> least -- please advise what should be done with the EAR and EJB
> support,
> >> as
> >>> described here:
> >>>
> >>>
> >>
> https://blogs.apache.org/netbeans/entry/enterprise-cluster-integrated-into-apache
> >>>
> >>> And, hurray, thanks Matthias especially, and Vikas, Arunava, Sarvesh,
> and
> >>> Reema, for a lot of work on relicensing, for getting the enterprise
> >> cluster
> >>> integrated!
> >>>
> >>> Gj
> >>>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> >> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
> >>
> >> For further information about the NetBeans mailing lists, visit:
> >> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >>
> >>
> >>
> >> --
> > Thanks and kind regards,
> > Gaurav Gupta
> > <https://twitter.com/ImJeddict> <https://jeddict.github.io/>
> > <https://www.youtube.com/JPAModeler>
> >
>
>
> --
> ae | Andreas Ernst | IT Spektrum
> Postfach 5, 65612 Beselich
> Schupbacher Str. 32, 65614 Beselich, Germany
> Tel: +49-6484-91002 Fax: +49-6484-91003
> ae@ae-online.de | www.ae-online.de
> www.tachyon-online.de
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>
Re: What to do with features for EARs and EJBs?
Posted by Andreas Ernst <ae...@ae-online.de>.
+1 to keep the EAR and EJB support. YES, please.
Am 28.01.19 um 20:42 schrieb Gaurav Gupta:
> +1 to keep the EAR and EJB support.
>
> On Tue, 29 Jan 2019 at 1:07 AM, Antonio <an...@vieiro.net> wrote:
>
>> Hi,
>>
>> Last year I had to help out a customer that was stuck in Java 6 /
>> WebLogic 8. NetBeans was of great help for me.
>>
>> I'd try to keep the EAR/EJB functionality. Don't know if as a plugin or
>> bundled in the IDE, though.
>>
>> Maybe it saves the day to somebody else in the future.
>>
>> Cheers,
>> Antonio
>>
>> El 28/1/19 a las 20:05, Geertjan Wielenga escribió:
>>> Hi all,
>>>
>>> Especially to Java/Jakarta EE people out there, e.g., Ivar, Josh, David,
>> at
>>> least -- please advise what should be done with the EAR and EJB support,
>> as
>>> described here:
>>>
>>>
>> https://blogs.apache.org/netbeans/entry/enterprise-cluster-integrated-into-apache
>>>
>>> And, hurray, thanks Matthias especially, and Vikas, Arunava, Sarvesh, and
>>> Reema, for a lot of work on relicensing, for getting the enterprise
>> cluster
>>> integrated!
>>>
>>> Gj
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
>> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>>
>> For further information about the NetBeans mailing lists, visit:
>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>
>>
>>
>> --
> Thanks and kind regards,
> Gaurav Gupta
> <https://twitter.com/ImJeddict> <https://jeddict.github.io/>
> <https://www.youtube.com/JPAModeler>
>
--
ae | Andreas Ernst | IT Spektrum
Postfach 5, 65612 Beselich
Schupbacher Str. 32, 65614 Beselich, Germany
Tel: +49-6484-91002 Fax: +49-6484-91003
ae@ae-online.de | www.ae-online.de
www.tachyon-online.de
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: What to do with features for EARs and EJBs?
Posted by Gaurav Gupta <ga...@gmail.com>.
+1 to keep the EAR and EJB support.
On Tue, 29 Jan 2019 at 1:07 AM, Antonio <an...@vieiro.net> wrote:
> Hi,
>
> Last year I had to help out a customer that was stuck in Java 6 /
> WebLogic 8. NetBeans was of great help for me.
>
> I'd try to keep the EAR/EJB functionality. Don't know if as a plugin or
> bundled in the IDE, though.
>
> Maybe it saves the day to somebody else in the future.
>
> Cheers,
> Antonio
>
> El 28/1/19 a las 20:05, Geertjan Wielenga escribió:
> > Hi all,
> >
> > Especially to Java/Jakarta EE people out there, e.g., Ivar, Josh, David,
> at
> > least -- please advise what should be done with the EAR and EJB support,
> as
> > described here:
> >
> >
> https://blogs.apache.org/netbeans/entry/enterprise-cluster-integrated-into-apache
> >
> > And, hurray, thanks Matthias especially, and Vikas, Arunava, Sarvesh, and
> > Reema, for a lot of work on relicensing, for getting the enterprise
> cluster
> > integrated!
> >
> > Gj
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
> --
Thanks and kind regards,
Gaurav Gupta
<https://twitter.com/ImJeddict> <https://jeddict.github.io/>
<https://www.youtube.com/JPAModeler>
Re: What to do with features for EARs and EJBs?
Posted by Antonio <an...@vieiro.net>.
Hi,
Last year I had to help out a customer that was stuck in Java 6 /
WebLogic 8. NetBeans was of great help for me.
I'd try to keep the EAR/EJB functionality. Don't know if as a plugin or
bundled in the IDE, though.
Maybe it saves the day to somebody else in the future.
Cheers,
Antonio
El 28/1/19 a las 20:05, Geertjan Wielenga escribió:
> Hi all,
>
> Especially to Java/Jakarta EE people out there, e.g., Ivar, Josh, David, at
> least -- please advise what should be done with the EAR and EJB support, as
> described here:
>
> https://blogs.apache.org/netbeans/entry/enterprise-cluster-integrated-into-apache
>
> And, hurray, thanks Matthias especially, and Vikas, Arunava, Sarvesh, and
> Reema, for a lot of work on relicensing, for getting the enterprise cluster
> integrated!
>
> Gj
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: What to do with features for EARs and EJBs?
Posted by Geertjan Wielenga <ge...@googlemail.com.INVALID>.
Of course, no one is suggesting that Java EE be removed. Read the blog
entry:
https://blogs.apache.org/netbeans/entry/enterprise-cluster-integrated-into-apache
By the way, I have set up the Java EE 8 AirHacks CDI demo by Adam Bien
inside NetBeans a few minutes ago, works perfectly.
Thanks,
Gj
On Mon, Jan 28, 2019 at 10:33 PM Tomas Poledny <sa...@gmail.com> wrote:
> NetBeans had the best support of JEE from all IDE. Support for Spring is
> very poor. I think remove of support part of JEE is suicide for NetBeans.
> This is main reason why I am using NetBeans.
> Tomas
>
> On Mon, Jan 28, 2019, 22:24 Brett Ryan <brett.ryan@gmail.com wrote:
>
> > It’s always a sensitive topic whenever considering to remove something,
> > however; I am in favour for removing classic JavaEE support in favour of
> > concentrating on modern java web technologies such as spring and Jakarta.
> >
> > It becomes an enormous task to support everything. We can always provide
> > support in the form of a plugin though I feel that those using classic
> Java
> > EE may not benefit from the additions being added to NetBeans IDE and may
> > continue to use 8.2.
> >
> > > On 29 Jan 2019, at 06:05, Geertjan Wielenga
> > <ge...@googlemail.com.invalid> wrote:
> > >
> > > Hi all,
> > >
> > > Especially to Java/Jakarta EE people out there, e.g., Ivar, Josh,
> David,
> > at
> > > least -- please advise what should be done with the EAR and EJB
> support,
> > as
> > > described here:
> > >
> > >
> >
> https://blogs.apache.org/netbeans/entry/enterprise-cluster-integrated-into-apache
> > >
> > > And, hurray, thanks Matthias especially, and Vikas, Arunava, Sarvesh,
> and
> > > Reema, for a lot of work on relicensing, for getting the enterprise
> > cluster
> > > integrated!
> > >
> > > Gj
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> > For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
> >
> > For further information about the NetBeans mailing lists, visit:
> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >
> >
> >
> >
>
Re: Re: What to do with features for EARs and EJBs?
Posted by Geertjan Wielenga <ge...@googlemail.com.INVALID>.
Feel free to add thoughts on this topic in the related PR:
https://github.com/apache/incubator-netbeans/pull/1038
Gj
On Wed, Jan 30, 2019 at 4:01 PM Ondro Mihályi <on...@gmail.com>
wrote:
> Hi Alessandro,
>
> I see, I mentioned SpringBoot as just a hypothetical example. in fact I
> think that Netbeans should adopt maven and maybe also gradle as first-class
> citizens and stop putting maven and gradle projects into a separate
> category. For example, I'd like to go to New Project -> Java Web -> Web
> Application -> select build tool (one of Ant, Maven, Gradle) and create a
> project. It's very weird that most of the industry uses Maven and Gradle,
> but the default in Netbeans is Ant. Newcomers choose Ant projects in
> Netbeans most of the time, not knowing that most of the world out there
> already uses Maven or Gradle.
>
> If we had Maven and Gradle projects under the same categories as Ant
> projects, then a SpringBoot project could be under Java Web category.
> That's all what I meant in my previous email.
>
> All the best,
> Ondro
>
> st 30. 1. 2019 o 15:28 Alessandro <al...@gmail.com> napísal(a):
>
> > Hi Ondro,
> >
> > Il giorno mer 30 gen 2019 alle ore 10:08 Ondro Mihályi <
> > ondrej.mihalyi@gmail.com> ha scritto:
> >
> > > ...
> >
> > Although the project creation dialog refers to Java EE in one select box,
> >
> > it allows choosing Tomcat and only adds dependencies present in Tomcat.
> In
> > > addition, if there was a plugin for generating Ant-based Spring Boot
> > apps,
> > > it could also be in this category, as it would be a Java Web project,
> > > although a separate SpringBoot type packaged as JAR.
> > > ...
> > > - Ondro
> > >
> >
> > While creating an Ant project using Spring Boot is entirely possible it
> is
> > not recommended as Spring Boot heavily relies on a build tool with
> > dependency management capabilities (see
> >
> >
> https://docs.spring.io/spring-boot/docs/current/reference/html/using-boot-build-systems.html
> > ).
> >
> > The NB Spring Boot plugin I created intentionally adds items to the Maven
> > category for this reason. Now that Gradle support is in master it could
> be
> > worth having a look at supporting Spring Boot Gradle projects too.
> >
> > Greets,
> > Alessandro
> >
>
Re: Re: What to do with features for EARs and EJBs?
Posted by Ondro Mihályi <on...@gmail.com>.
Hi Alessandro,
I see, I mentioned SpringBoot as just a hypothetical example. in fact I
think that Netbeans should adopt maven and maybe also gradle as first-class
citizens and stop putting maven and gradle projects into a separate
category. For example, I'd like to go to New Project -> Java Web -> Web
Application -> select build tool (one of Ant, Maven, Gradle) and create a
project. It's very weird that most of the industry uses Maven and Gradle,
but the default in Netbeans is Ant. Newcomers choose Ant projects in
Netbeans most of the time, not knowing that most of the world out there
already uses Maven or Gradle.
If we had Maven and Gradle projects under the same categories as Ant
projects, then a SpringBoot project could be under Java Web category.
That's all what I meant in my previous email.
All the best,
Ondro
st 30. 1. 2019 o 15:28 Alessandro <al...@gmail.com> napísal(a):
> Hi Ondro,
>
> Il giorno mer 30 gen 2019 alle ore 10:08 Ondro Mihályi <
> ondrej.mihalyi@gmail.com> ha scritto:
>
> > ...
>
> Although the project creation dialog refers to Java EE in one select box,
>
> it allows choosing Tomcat and only adds dependencies present in Tomcat. In
> > addition, if there was a plugin for generating Ant-based Spring Boot
> apps,
> > it could also be in this category, as it would be a Java Web project,
> > although a separate SpringBoot type packaged as JAR.
> > ...
> > - Ondro
> >
>
> While creating an Ant project using Spring Boot is entirely possible it is
> not recommended as Spring Boot heavily relies on a build tool with
> dependency management capabilities (see
>
> https://docs.spring.io/spring-boot/docs/current/reference/html/using-boot-build-systems.html
> ).
>
> The NB Spring Boot plugin I created intentionally adds items to the Maven
> category for this reason. Now that Gradle support is in master it could be
> worth having a look at supporting Spring Boot Gradle projects too.
>
> Greets,
> Alessandro
>
Re: Re: What to do with features for EARs and EJBs?
Posted by Alessandro <al...@gmail.com>.
Hi Ondro,
Il giorno mer 30 gen 2019 alle ore 10:08 Ondro Mihályi <
ondrej.mihalyi@gmail.com> ha scritto:
> ...
Although the project creation dialog refers to Java EE in one select box,
it allows choosing Tomcat and only adds dependencies present in Tomcat. In
> addition, if there was a plugin for generating Ant-based Spring Boot apps,
> it could also be in this category, as it would be a Java Web project,
> although a separate SpringBoot type packaged as JAR.
> ...
> - Ondro
>
While creating an Ant project using Spring Boot is entirely possible it is
not recommended as Spring Boot heavily relies on a build tool with
dependency management capabilities (see
https://docs.spring.io/spring-boot/docs/current/reference/html/using-boot-build-systems.html
).
The NB Spring Boot plugin I created intentionally adds items to the Maven
category for this reason. Now that Gradle support is in master it could be
worth having a look at supporting Spring Boot Gradle projects too.
Greets,
Alessandro
Re: Re: What to do with features for EARs and EJBs?
Posted by David Heffelfinger <dh...@gmail.com>.
I agree that things get a bit confusing with the renaming of Java EE to
Jakarta EE. If this wasn't the case I wouldn't like any renaming at all. As
far as I can tell the current separation of "Java Web" and "Java EE" hasn't
caused any confusion among NetBeans users.
I'm not sure I like the words "Legacy" or "Vintage", as some may interpret
these as having negative connotations. There are still many projects out
there that use EAR files and EJBs. EJBs in particular suffer from the bad
rep EJB 2 had, where EJB 3 is a whole different beast, very easy and simple
to use. Moving EJBs to a "Legacy" or "Vintage" category may reinforce the
bad reputation from EJB 2. Additionally, I still see a fair amount of
projects using EAR Files (mostly maintenance of existing code).
I like Ondro's idea of using "Java Enterprise", which would cover both Java
EE and Jakarta EE.
On Wed, Jan 30, 2019 at 4:08 AM Ondro Mihályi <on...@gmail.com>
wrote:
> Hi,
>
> I agree with Eric. EJB and EAR is still part of Java EE, will be part of
> Jakarta EE and there are no plans to deprecate it. I heard some ideas to
> create a new "modern" profile in Jakarta EE but it's only ideas and we're
> far away from that happening. Therefore all this should be supported by
> Netbeans at least via a plugin if we already have that functionality. I
> know that a lot of companies still maintain their older applications that
> use EJB and EAR and they're not going to remove it even when using Docker
> or other modern technology.
>
> I propose (reasoning below):
>
> - leave "Jave Web" category as is
> - rename "Java EE" category to "Java Enterprise" category (which to many
> would sound like "legacy" anyway)
>
> Reasoning:
>
> I thought that the "Java Web" category is for web apps in general, for WAR
> projects, which can be also deployed to servlet containers like Tomcat.
> Although the project creation dialog refers to Java EE in one select box,
> it allows choosing Tomcat and only adds dependencies present in Tomcat. In
> addition, if there was a plugin for generating Ant-based Spring Boot apps,
> it could also be in this category, as it would be a Java Web project,
> although a separate SpringBoot type packaged as JAR.
>
> On the other hand, the "Java EE" category is for legacy enterprise
> constructs in Java EE, like EARs, EJBs and EJB clients. Here the name "Java
> EE" for the category is wrong, because Java EE is no longer used only in
> enterprise and with EARs. I would rename this category to "Enterprise
> Java".This could be extracted into a separate plugin and only installed if
> needed. Later if these constructs are deprecated in Jakarta EE we could
> just make the plugin deprecated too.
>
> A bonus is we wouldn't need to rename anything to Jakarta EE later.
>
> - Ondro
>
>
>
>
>
> st 30. 1. 2019 o 5:19 Eric Bresie <eb...@gmail.com> napísal(a):
>
> > I’m a little bit of an outsider looking in but give the older
> technologies
> > are still Java EE why confuse things with Vintage and Legacy and just
> leave
> > them there with the new Jakarta EE category when available.
> >
> > Then just make sure to have a Version attribute to configure the setup of
> > the project?
> >
> > I thought recent Java EE has different profiles ( Web Profiles, Full
> > Profiles,etc.). Would linking with these profiles work better? Or is the
> > Java Web not necessarily related to Java EE Web Profiles? Is the Java Web
> > more of a micro service?
> >
> > Would having an Enterprise category work better maybe and allowing
> > different flavors under that?
> >
> > Eric Bresie
> > Ebresie@gmail.com
> > > On January 28, 2019 at 11:50:02 PM CST, Josh Juneau <
> juneau001@gmail.com>
> > wrote:
> > > I certainly agree that we need to keep this functionality within the
> > IDE. Regarding naming and/or breaking it out into an extension: I would
> be
> > in favor of keeping this functionality under a "Vintage Java EE"
> category.
> > That is what it is, correct? I think we will need a "Jakarta EE" category
> > in the near future, and this new category will not contain older
> > functionality. I would prefer going straight to "Jakarta EE" as a
> category,
> > rather than use "Modern Java EE". Jakarta EE 8 is due out soon and it
> will
> > be in alignment with Java EE 8.
> > >
> > > Older (deprecated) functionality should go into the "Vintage Java EE"
> > category. As Ken had mentioned, these technologies have not been
> > deprecated, but these older EAR wizards would certainly be vintage in my
> > opinion. If the day comes where most of the necessary EJB functionality
> is
> > moved into other APIs, then maybe it can be broken off as an add-on
> > extension...but not until then.
> > >
> > > Hope this makes sense. Thanks for all of the work that has gone into
> > moving the IDE forward.
> > >
> > > Josh Juneau
> > > juneau001@gmail.com
> > > http://jj-blogger.blogspot.com
> > > https://www.apress.com/index.php/author/author/view/id/1866
> > >
> > > > On Jan 28, 2019, at 3:41 PM, Brett Ryan <br...@gmail.com>
> wrote:
> > > >
> > > > Geertjan’s article is not about removing EE support it’s what to do
> > about the old Java EE which is deprecated in favour of Jakarta EE in the
> > future being the modern EE variant.
> > > >
> > > > For those that do not know, yes; Java EE 8 is the last version of
> Java
> > EE, Jakarta EE while not being a replacement it is the new way forward
> for
> > enterprise web applications. Removing legacy support in favour of new
> > technologies is certainly not suicide it is moving with the times.
> > > >
> > > > Spring support has always been brilliant in NetBeans with bean
> > navigation suppirt and now a lot of bootstrap support, but that’s the
> > modern current focus.
> > > >
> > > > > On 29 Jan 2019, at 08:33, Tomas Poledny <sa...@gmail.com>
> wrote:
> > > > >
> > > > > NetBeans had the best support of JEE from all IDE. Support for
> > Spring is
> > > > > very poor. I think remove of support part of JEE is suicide for
> > NetBeans.
> > > > > This is main reason why I am using NetBeans.
> > > > > Tomas
> > > > >
> > > > > > On Mon, Jan 28, 2019, 22:24 Brett Ryan <brett.ryan@gmail.com
> > wrote:
> > > > > >
> > > > > > It’s always a sensitive topic whenever considering to remove
> > something,
> > > > > > however; I am in favour for removing classic JavaEE support in
> > favour of
> > > > > > concentrating on modern java web technologies such as spring and
> > Jakarta.
> > > > > >
> > > > > > It becomes an enormous task to support everything. We can always
> > provide
> > > > > > support in the form of a plugin though I feel that those using
> > classic Java
> > > > > > EE may not benefit from the additions being added to NetBeans IDE
> > and may
> > > > > > continue to use 8.2.
> > > > > >
> > > > > > > > On 29 Jan 2019, at 06:05, Geertjan Wielenga
> > > > > > > <ge...@googlemail.com.invalid> wrote:
> > > > > > >
> > > > > > > Hi all,
> > > > > > >
> > > > > > > Especially to Java/Jakarta EE people out there, e.g., Ivar,
> > Josh, David,
> > > > > > at
> > > > > > > least -- please advise what should be done with the EAR and EJB
> > support,
> > > > > > as
> > > > > > > described here:
> > > > > >
> >
> https://blogs.apache.org/netbeans/entry/enterprise-cluster-integrated-into-apache
> > > > > > >
> > > > > > > And, hurray, thanks Matthias especially, and Vikas, Arunava,
> > Sarvesh, and
> > > > > > > Reema, for a lot of work on relicensing, for getting the
> > enterprise
> > > > > > cluster
> > > > > > > integrated!
> > > > > > >
> > > > > > > Gj
> > > > > >
> > > > > >
> > ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail:
> > dev-unsubscribe@netbeans.incubator.apache.org
> > > > > > For additional commands, e-mail:
> > dev-help@netbeans.incubator.apache.org
> > > > > >
> > > > > > For further information about the NetBeans mailing lists, visit:
> > > > > >
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail:
> dev-unsubscribe@netbeans.incubator.apache.org
> > > > For additional commands, e-mail:
> > dev-help@netbeans.incubator.apache.org
> > > >
> > > > For further information about the NetBeans mailing lists, visit:
> > > > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> > > >
> > > >
> > > >
> >
>
--
http://ensode.net - A Guide to Java, Linux and Other Technology Topics
My Books: https://www.packtpub.com/books/info/authors/david-r-heffelfinger
<http://www.packtpub.com/authors/profiles/david-heffelfinger>
My Video Training:
http://www.packtpub.com/java-ee-development-with-netbeans-7/video
Follow me on Twitter: https://twitter.com/ensode
Re: Re: What to do with features for EARs and EJBs?
Posted by Ondro Mihályi <on...@gmail.com>.
Hi,
I agree with Eric. EJB and EAR is still part of Java EE, will be part of
Jakarta EE and there are no plans to deprecate it. I heard some ideas to
create a new "modern" profile in Jakarta EE but it's only ideas and we're
far away from that happening. Therefore all this should be supported by
Netbeans at least via a plugin if we already have that functionality. I
know that a lot of companies still maintain their older applications that
use EJB and EAR and they're not going to remove it even when using Docker
or other modern technology.
I propose (reasoning below):
- leave "Jave Web" category as is
- rename "Java EE" category to "Java Enterprise" category (which to many
would sound like "legacy" anyway)
Reasoning:
I thought that the "Java Web" category is for web apps in general, for WAR
projects, which can be also deployed to servlet containers like Tomcat.
Although the project creation dialog refers to Java EE in one select box,
it allows choosing Tomcat and only adds dependencies present in Tomcat. In
addition, if there was a plugin for generating Ant-based Spring Boot apps,
it could also be in this category, as it would be a Java Web project,
although a separate SpringBoot type packaged as JAR.
On the other hand, the "Java EE" category is for legacy enterprise
constructs in Java EE, like EARs, EJBs and EJB clients. Here the name "Java
EE" for the category is wrong, because Java EE is no longer used only in
enterprise and with EARs. I would rename this category to "Enterprise
Java".This could be extracted into a separate plugin and only installed if
needed. Later if these constructs are deprecated in Jakarta EE we could
just make the plugin deprecated too.
A bonus is we wouldn't need to rename anything to Jakarta EE later.
- Ondro
st 30. 1. 2019 o 5:19 Eric Bresie <eb...@gmail.com> napísal(a):
> I’m a little bit of an outsider looking in but give the older technologies
> are still Java EE why confuse things with Vintage and Legacy and just leave
> them there with the new Jakarta EE category when available.
>
> Then just make sure to have a Version attribute to configure the setup of
> the project?
>
> I thought recent Java EE has different profiles ( Web Profiles, Full
> Profiles,etc.). Would linking with these profiles work better? Or is the
> Java Web not necessarily related to Java EE Web Profiles? Is the Java Web
> more of a micro service?
>
> Would having an Enterprise category work better maybe and allowing
> different flavors under that?
>
> Eric Bresie
> Ebresie@gmail.com
> > On January 28, 2019 at 11:50:02 PM CST, Josh Juneau <ju...@gmail.com>
> wrote:
> > I certainly agree that we need to keep this functionality within the
> IDE. Regarding naming and/or breaking it out into an extension: I would be
> in favor of keeping this functionality under a "Vintage Java EE" category.
> That is what it is, correct? I think we will need a "Jakarta EE" category
> in the near future, and this new category will not contain older
> functionality. I would prefer going straight to "Jakarta EE" as a category,
> rather than use "Modern Java EE". Jakarta EE 8 is due out soon and it will
> be in alignment with Java EE 8.
> >
> > Older (deprecated) functionality should go into the "Vintage Java EE"
> category. As Ken had mentioned, these technologies have not been
> deprecated, but these older EAR wizards would certainly be vintage in my
> opinion. If the day comes where most of the necessary EJB functionality is
> moved into other APIs, then maybe it can be broken off as an add-on
> extension...but not until then.
> >
> > Hope this makes sense. Thanks for all of the work that has gone into
> moving the IDE forward.
> >
> > Josh Juneau
> > juneau001@gmail.com
> > http://jj-blogger.blogspot.com
> > https://www.apress.com/index.php/author/author/view/id/1866
> >
> > > On Jan 28, 2019, at 3:41 PM, Brett Ryan <br...@gmail.com> wrote:
> > >
> > > Geertjan’s article is not about removing EE support it’s what to do
> about the old Java EE which is deprecated in favour of Jakarta EE in the
> future being the modern EE variant.
> > >
> > > For those that do not know, yes; Java EE 8 is the last version of Java
> EE, Jakarta EE while not being a replacement it is the new way forward for
> enterprise web applications. Removing legacy support in favour of new
> technologies is certainly not suicide it is moving with the times.
> > >
> > > Spring support has always been brilliant in NetBeans with bean
> navigation suppirt and now a lot of bootstrap support, but that’s the
> modern current focus.
> > >
> > > > On 29 Jan 2019, at 08:33, Tomas Poledny <sa...@gmail.com> wrote:
> > > >
> > > > NetBeans had the best support of JEE from all IDE. Support for
> Spring is
> > > > very poor. I think remove of support part of JEE is suicide for
> NetBeans.
> > > > This is main reason why I am using NetBeans.
> > > > Tomas
> > > >
> > > > > On Mon, Jan 28, 2019, 22:24 Brett Ryan <brett.ryan@gmail.com
> wrote:
> > > > >
> > > > > It’s always a sensitive topic whenever considering to remove
> something,
> > > > > however; I am in favour for removing classic JavaEE support in
> favour of
> > > > > concentrating on modern java web technologies such as spring and
> Jakarta.
> > > > >
> > > > > It becomes an enormous task to support everything. We can always
> provide
> > > > > support in the form of a plugin though I feel that those using
> classic Java
> > > > > EE may not benefit from the additions being added to NetBeans IDE
> and may
> > > > > continue to use 8.2.
> > > > >
> > > > > > > On 29 Jan 2019, at 06:05, Geertjan Wielenga
> > > > > > <ge...@googlemail.com.invalid> wrote:
> > > > > >
> > > > > > Hi all,
> > > > > >
> > > > > > Especially to Java/Jakarta EE people out there, e.g., Ivar,
> Josh, David,
> > > > > at
> > > > > > least -- please advise what should be done with the EAR and EJB
> support,
> > > > > as
> > > > > > described here:
> > > > >
> https://blogs.apache.org/netbeans/entry/enterprise-cluster-integrated-into-apache
> > > > > >
> > > > > > And, hurray, thanks Matthias especially, and Vikas, Arunava,
> Sarvesh, and
> > > > > > Reema, for a lot of work on relicensing, for getting the
> enterprise
> > > > > cluster
> > > > > > integrated!
> > > > > >
> > > > > > Gj
> > > > >
> > > > >
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail:
> dev-unsubscribe@netbeans.incubator.apache.org
> > > > > For additional commands, e-mail:
> dev-help@netbeans.incubator.apache.org
> > > > >
> > > > > For further information about the NetBeans mailing lists, visit:
> > > > > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> > > For additional commands, e-mail:
> dev-help@netbeans.incubator.apache.org
> > >
> > > For further information about the NetBeans mailing lists, visit:
> > > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> > >
> > >
> > >
>
Re: Re: What to do with features for EARs and EJBs?
Posted by Eric Bresie <eb...@gmail.com>.
I’m a little bit of an outsider looking in but give the older technologies are still Java EE why confuse things with Vintage and Legacy and just leave them there with the new Jakarta EE category when available.
Then just make sure to have a Version attribute to configure the setup of the project?
I thought recent Java EE has different profiles ( Web Profiles, Full Profiles,etc.). Would linking with these profiles work better? Or is the Java Web not necessarily related to Java EE Web Profiles? Is the Java Web more of a micro service?
Would having an Enterprise category work better maybe and allowing different flavors under that?
Eric Bresie
Ebresie@gmail.com
> On January 28, 2019 at 11:50:02 PM CST, Josh Juneau <ju...@gmail.com> wrote:
> I certainly agree that we need to keep this functionality within the IDE. Regarding naming and/or breaking it out into an extension: I would be in favor of keeping this functionality under a "Vintage Java EE" category. That is what it is, correct? I think we will need a "Jakarta EE" category in the near future, and this new category will not contain older functionality. I would prefer going straight to "Jakarta EE" as a category, rather than use "Modern Java EE". Jakarta EE 8 is due out soon and it will be in alignment with Java EE 8.
>
> Older (deprecated) functionality should go into the "Vintage Java EE" category. As Ken had mentioned, these technologies have not been deprecated, but these older EAR wizards would certainly be vintage in my opinion. If the day comes where most of the necessary EJB functionality is moved into other APIs, then maybe it can be broken off as an add-on extension...but not until then.
>
> Hope this makes sense. Thanks for all of the work that has gone into moving the IDE forward.
>
> Josh Juneau
> juneau001@gmail.com
> http://jj-blogger.blogspot.com
> https://www.apress.com/index.php/author/author/view/id/1866
>
> > On Jan 28, 2019, at 3:41 PM, Brett Ryan <br...@gmail.com> wrote:
> >
> > Geertjan’s article is not about removing EE support it’s what to do about the old Java EE which is deprecated in favour of Jakarta EE in the future being the modern EE variant.
> >
> > For those that do not know, yes; Java EE 8 is the last version of Java EE, Jakarta EE while not being a replacement it is the new way forward for enterprise web applications. Removing legacy support in favour of new technologies is certainly not suicide it is moving with the times.
> >
> > Spring support has always been brilliant in NetBeans with bean navigation suppirt and now a lot of bootstrap support, but that’s the modern current focus.
> >
> > > On 29 Jan 2019, at 08:33, Tomas Poledny <sa...@gmail.com> wrote:
> > >
> > > NetBeans had the best support of JEE from all IDE. Support for Spring is
> > > very poor. I think remove of support part of JEE is suicide for NetBeans.
> > > This is main reason why I am using NetBeans.
> > > Tomas
> > >
> > > > On Mon, Jan 28, 2019, 22:24 Brett Ryan <brett.ryan@gmail.com wrote:
> > > >
> > > > It’s always a sensitive topic whenever considering to remove something,
> > > > however; I am in favour for removing classic JavaEE support in favour of
> > > > concentrating on modern java web technologies such as spring and Jakarta.
> > > >
> > > > It becomes an enormous task to support everything. We can always provide
> > > > support in the form of a plugin though I feel that those using classic Java
> > > > EE may not benefit from the additions being added to NetBeans IDE and may
> > > > continue to use 8.2.
> > > >
> > > > > > On 29 Jan 2019, at 06:05, Geertjan Wielenga
> > > > > <ge...@googlemail.com.invalid> wrote:
> > > > >
> > > > > Hi all,
> > > > >
> > > > > Especially to Java/Jakarta EE people out there, e.g., Ivar, Josh, David,
> > > > at
> > > > > least -- please advise what should be done with the EAR and EJB support,
> > > > as
> > > > > described here:
> > > > https://blogs.apache.org/netbeans/entry/enterprise-cluster-integrated-into-apache
> > > > >
> > > > > And, hurray, thanks Matthias especially, and Vikas, Arunava, Sarvesh, and
> > > > > Reema, for a lot of work on relicensing, for getting the enterprise
> > > > cluster
> > > > > integrated!
> > > > >
> > > > > Gj
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> > > > For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
> > > >
> > > > For further information about the NetBeans mailing lists, visit:
> > > > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> > For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
> >
> > For further information about the NetBeans mailing lists, visit:
> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >
> >
> >
Re: What to do with features for EARs and EJBs?
Posted by Josh Juneau <ju...@gmail.com>.
I certainly agree that we need to keep this functionality within the IDE. Regarding naming and/or breaking it out into an extension: I would be in favor of keeping this functionality under a "Vintage Java EE" category. That is what it is, correct? I think we will need a "Jakarta EE" category in the near future, and this new category will not contain older functionality. I would prefer going straight to "Jakarta EE" as a category, rather than use "Modern Java EE". Jakarta EE 8 is due out soon and it will be in alignment with Java EE 8.
Older (deprecated) functionality should go into the "Vintage Java EE" category. As Ken had mentioned, these technologies have not been deprecated, but these older EAR wizards would certainly be vintage in my opinion. If the day comes where most of the necessary EJB functionality is moved into other APIs, then maybe it can be broken off as an add-on extension...but not until then.
Hope this makes sense. Thanks for all of the work that has gone into moving the IDE forward.
Josh Juneau
juneau001@gmail.com
http://jj-blogger.blogspot.com
https://www.apress.com/index.php/author/author/view/id/1866
> On Jan 28, 2019, at 3:41 PM, Brett Ryan <br...@gmail.com> wrote:
>
> Geertjan’s article is not about removing EE support it’s what to do about the old Java EE which is deprecated in favour of Jakarta EE in the future being the modern EE variant.
>
> For those that do not know, yes; Java EE 8 is the last version of Java EE, Jakarta EE while not being a replacement it is the new way forward for enterprise web applications. Removing legacy support in favour of new technologies is certainly not suicide it is moving with the times.
>
> Spring support has always been brilliant in NetBeans with bean navigation suppirt and now a lot of bootstrap support, but that’s the modern current focus.
>
>> On 29 Jan 2019, at 08:33, Tomas Poledny <sa...@gmail.com> wrote:
>>
>> NetBeans had the best support of JEE from all IDE. Support for Spring is
>> very poor. I think remove of support part of JEE is suicide for NetBeans.
>> This is main reason why I am using NetBeans.
>> Tomas
>>
>>> On Mon, Jan 28, 2019, 22:24 Brett Ryan <brett.ryan@gmail.com wrote:
>>>
>>> It’s always a sensitive topic whenever considering to remove something,
>>> however; I am in favour for removing classic JavaEE support in favour of
>>> concentrating on modern java web technologies such as spring and Jakarta.
>>>
>>> It becomes an enormous task to support everything. We can always provide
>>> support in the form of a plugin though I feel that those using classic Java
>>> EE may not benefit from the additions being added to NetBeans IDE and may
>>> continue to use 8.2.
>>>
>>>>> On 29 Jan 2019, at 06:05, Geertjan Wielenga
>>>> <ge...@googlemail.com.invalid> wrote:
>>>>
>>>> Hi all,
>>>>
>>>> Especially to Java/Jakarta EE people out there, e.g., Ivar, Josh, David,
>>> at
>>>> least -- please advise what should be done with the EAR and EJB support,
>>> as
>>>> described here:
>>> https://blogs.apache.org/netbeans/entry/enterprise-cluster-integrated-into-apache
>>>>
>>>> And, hurray, thanks Matthias especially, and Vikas, Arunava, Sarvesh, and
>>>> Reema, for a lot of work on relicensing, for getting the enterprise
>>> cluster
>>>> integrated!
>>>>
>>>> Gj
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
>>> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>>>
>>> For further information about the NetBeans mailing lists, visit:
>>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
Re: What to do with features for EARs and EJBs?
Posted by Brett Ryan <br...@gmail.com>.
Geertjan’s article is not about removing EE support it’s what to do about the old Java EE which is deprecated in favour of Jakarta EE in the future being the modern EE variant.
For those that do not know, yes; Java EE 8 is the last version of Java EE, Jakarta EE while not being a replacement it is the new way forward for enterprise web applications. Removing legacy support in favour of new technologies is certainly not suicide it is moving with the times.
Spring support has always been brilliant in NetBeans with bean navigation suppirt and now a lot of bootstrap support, but that’s the modern current focus.
> On 29 Jan 2019, at 08:33, Tomas Poledny <sa...@gmail.com> wrote:
>
> NetBeans had the best support of JEE from all IDE. Support for Spring is
> very poor. I think remove of support part of JEE is suicide for NetBeans.
> This is main reason why I am using NetBeans.
> Tomas
>
>> On Mon, Jan 28, 2019, 22:24 Brett Ryan <brett.ryan@gmail.com wrote:
>>
>> It’s always a sensitive topic whenever considering to remove something,
>> however; I am in favour for removing classic JavaEE support in favour of
>> concentrating on modern java web technologies such as spring and Jakarta.
>>
>> It becomes an enormous task to support everything. We can always provide
>> support in the form of a plugin though I feel that those using classic Java
>> EE may not benefit from the additions being added to NetBeans IDE and may
>> continue to use 8.2.
>>
>>> On 29 Jan 2019, at 06:05, Geertjan Wielenga
>> <ge...@googlemail.com.invalid> wrote:
>>>
>>> Hi all,
>>>
>>> Especially to Java/Jakarta EE people out there, e.g., Ivar, Josh, David,
>> at
>>> least -- please advise what should be done with the EAR and EJB support,
>> as
>>> described here:
>>>
>>>
>> https://blogs.apache.org/netbeans/entry/enterprise-cluster-integrated-into-apache
>>>
>>> And, hurray, thanks Matthias especially, and Vikas, Arunava, Sarvesh, and
>>> Reema, for a lot of work on relicensing, for getting the enterprise
>> cluster
>>> integrated!
>>>
>>> Gj
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
>> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>>
>> For further information about the NetBeans mailing lists, visit:
>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>
>>
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: What to do with features for EARs and EJBs?
Posted by Tomas Poledny <sa...@gmail.com>.
NetBeans had the best support of JEE from all IDE. Support for Spring is
very poor. I think remove of support part of JEE is suicide for NetBeans.
This is main reason why I am using NetBeans.
Tomas
On Mon, Jan 28, 2019, 22:24 Brett Ryan <brett.ryan@gmail.com wrote:
> It’s always a sensitive topic whenever considering to remove something,
> however; I am in favour for removing classic JavaEE support in favour of
> concentrating on modern java web technologies such as spring and Jakarta.
>
> It becomes an enormous task to support everything. We can always provide
> support in the form of a plugin though I feel that those using classic Java
> EE may not benefit from the additions being added to NetBeans IDE and may
> continue to use 8.2.
>
> > On 29 Jan 2019, at 06:05, Geertjan Wielenga
> <ge...@googlemail.com.invalid> wrote:
> >
> > Hi all,
> >
> > Especially to Java/Jakarta EE people out there, e.g., Ivar, Josh, David,
> at
> > least -- please advise what should be done with the EAR and EJB support,
> as
> > described here:
> >
> >
> https://blogs.apache.org/netbeans/entry/enterprise-cluster-integrated-into-apache
> >
> > And, hurray, thanks Matthias especially, and Vikas, Arunava, Sarvesh, and
> > Reema, for a lot of work on relicensing, for getting the enterprise
> cluster
> > integrated!
> >
> > Gj
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>
Re: What to do with features for EARs and EJBs?
Posted by Brett Ryan <br...@gmail.com>.
It’s always a sensitive topic whenever considering to remove something, however; I am in favour for removing classic JavaEE support in favour of concentrating on modern java web technologies such as spring and Jakarta.
It becomes an enormous task to support everything. We can always provide support in the form of a plugin though I feel that those using classic Java EE may not benefit from the additions being added to NetBeans IDE and may continue to use 8.2.
> On 29 Jan 2019, at 06:05, Geertjan Wielenga <ge...@googlemail.com.invalid> wrote:
>
> Hi all,
>
> Especially to Java/Jakarta EE people out there, e.g., Ivar, Josh, David, at
> least -- please advise what should be done with the EAR and EJB support, as
> described here:
>
> https://blogs.apache.org/netbeans/entry/enterprise-cluster-integrated-into-apache
>
> And, hurray, thanks Matthias especially, and Vikas, Arunava, Sarvesh, and
> Reema, for a lot of work on relicensing, for getting the enterprise cluster
> integrated!
>
> Gj
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists