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
wrote:
> Hi Alessandro,
>
> I see, I mentioned SpringBoot as just a hypothetical example. in fact I
> think that Netbeans should
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
Hi Ondro,
Il giorno mer 30 gen 2019 alle ore 10:08 Ondro Mihályi <
ondrej.miha...@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
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
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
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
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"
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
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
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 It’s always a sensitive topic whenever considering to
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
>
> 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.
>
>
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
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
Sent: January 28, 2019 3:13 PM
To: dev@netbeans.incubator.apache.org
Subject: Re: What to do with
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
>
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
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
+1 to keep. I am using it on my current project.
On Mon, Jan 28, 2019, 20:54 Gary Bello +1 for ejb/ear support
>
> On Mon, Jan 28, 2019 at 11:52 AM Andreas Ernst 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
+1 for ejb/ear support
On Mon, Jan 28, 2019 at 11:52 AM Andreas Ernst 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 wrote:
> >
> >> Hi,
> >>
> >>
+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 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
+1 to keep the EAR and EJB support.
On Tue, 29 Jan 2019 at 1:07 AM, Antonio 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
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
22 matches
Mail list logo
