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 2018/09/18 04:11:53 UTC
Jakarta EE and Apache NetBeans 10
Hi all,
Some (e.g., Josh) have argued we should include the enterprise cluster in
the upcoming release to support Jakarta EE.
One point to realize here is that no development has been done in this area
and the functionality in GitHub right now is identical to that provided by
8.2 plugins.
However, the challenges we’re going to run into probably with
licensing-related issues, plus the simple fact that the enterprise cluster
is large and will add time in reviewing the release, might argue against
including it, and instead support Jakarta EE by including the 8.2 update
center registration in the release to simplify finding and installing the
related plugins.
Plus maybe we could rename the too general name ‘enterprise’ with ‘jakarta’
or ‘jakartaee’ as the name of the cluster, to make it clearer what it
contains, and to explicitly support Jakarta EE.
Gj
Re: Jakarta EE and Apache NetBeans 10
Posted by Geertjan Wielenga <ge...@googlemail.com.INVALID>.
Nice.
If those working on Java EE manage to get everything done this week, we
could include that cluster in the first voting candidate for Apache
NetBeans 10 -- and then if there turn out to be serious problems, we could
then decide to exclude that cluster in the next voting candidate.
But only if you are really confident that everything has been done and that
there's no area where we're going to encounter problems.
Gj
On Tue, Sep 25, 2018 at 1:07 PM, Josh Juneau <ju...@gmail.com> wrote:
> Hi Geertjan,
>
> Yes, I've not made it through the licensing for the Java EE modules as
> quickly as I had hoped to. There are a couple of particularly messy
> modules that I've been working with...but I will try to get through more
> this week.
>
> Thanks for following up...I appreciate it!
>
> On Tue, Sep 25, 2018 at 1:41 AM Geertjan Wielenga
> <ge...@googlemail.com.invalid> wrote:
>
> > I see a lot of items still open in the 'enterprise' cluster when I look
> at
> > the Rat report:
> >
> >
> > https://builds.apache.org/job/incubator-netbeans-linux/826/
> artifact/nbbuild/build/rat-report.txt
> >
> > Gj
> >
> > On Tue, Sep 18, 2018 at 1:35 PM, Josh Juneau <ju...@gmail.com>
> wrote:
> >
> > > Hi All,
> > >
> > > I've been trying to get through the licensing for the Java EE-related
> > > modules. Some of them are tough...no doubt. I've found some modules
> > that
> > > have dozens of files that need to be licensed (mostly test souces...but
> > not
> > > in Rat), and others include a few external dependencies that require
> > > special attention. I'll try to focus on getting through these
> licensing
> > > issues over the next week.
> > >
> > > Thanks
> > >
> > > On Tue, Sep 18, 2018 at 3:51 AM Geertjan Wielenga
> > > <ge...@googlemail.com.invalid> wrote:
> > >
> > > > Right now, it seems we're comfortable with JDK 11 and PHP, though
> we'd
> > be
> > > > very happy for Jakarta EE, Groovy, and JavaScript to be included --
> > > > assuming people step up for real beyond sending e-mails about this.
> > I.e.,
> > > > Junichi has clearly taken the leadership in terms of PHP and we're
> in a
> > > > good state here, if the same can be done for other clusters and soon,
> > > then
> > > > let's include those too for the November release, otherwise focus on
> > > those
> > > > for the next quarter, i.e., February 2019.
> > > >
> > > > That said, here's the starting point for the Wiki for Apache NetBeans
> > 10:
> > > >
> > > >
> > https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+10
> > > >
> > > > Please populate the above (e.g., put anything in the Miscellaneous
> page
> > > > that's not directly applicable to PHP and JDK 11) with your
> > enhancements,
> > > > features, and significant bug fixes.
> > > >
> > > > Thanks,
> > > >
> > > > Gj
> > > >
> > > >
> > > > On Tue, Sep 18, 2018 at 10:00 AM, Geertjan Wielenga <
> > > > geertjan.wielenga@googlemail.com> wrote:
> > > >
> > > > > Well, cool, and sorry for forgetting about that, Emmanuel.
> > > > >
> > > > > Could you put together everything you have done in this area?
> > > > >
> > > > > Have you put everything you've done as pull requests into the
> Apache
> > > > > NetBeans GitHub repo?
> > > > >
> > > > > How far off are we from having Java EE 8 support right now, i.e.,
> > what
> > > > > would that entail?
> > > > >
> > > > > Sure, if we can take a swing at it and have clear direction and the
> > > time
> > > > > to do it for the November release, let's do it.
> > > > >
> > > > > Gj
> > > > >
> > > > > On Tue, Sep 18, 2018 at 9:09 AM, ehsavoie <
> > emmanuel.hugonnet@gmail.com
> > > >
> > > > > wrote:
> > > > >
> > > > >> Hi,
> > > > >> I'm almost sure that i wrote some changes since 8.2 and I have
> more
> > > for
> > > > >> WildFly that have been resting in my local repo for a year.
> > > > >> Also we don't have support for javaEE8 so no Jakarta EE :(
> > > > >> We really should take a swing at this because this is coming back
> to
> > > me
> > > > a
> > > > >> lot this lack of 'native' support for JavaEE in NetBeans
> > > > >> ----------
> > > > >> Emmanuel Hugonnet
> > > > >> http://www.ehsavoie.com
> > > > >> http://twitter.com/ehsavoie
> > > > >>
> > > > >>
> > > > >> On Tue, Sep 18, 2018 at 6:11 AM Geertjan Wielenga
> > > > >> <ge...@googlemail.com.invalid> wrote:
> > > > >>
> > > > >> > Hi all,
> > > > >> >
> > > > >> > Some (e.g., Josh) have argued we should include the enterprise
> > > cluster
> > > > >> in
> > > > >> > the upcoming release to support Jakarta EE.
> > > > >> >
> > > > >> > One point to realize here is that no development has been done
> in
> > > this
> > > > >> area
> > > > >> > and the functionality in GitHub right now is identical to that
> > > > provided
> > > > >> by
> > > > >> > 8.2 plugins.
> > > > >> >
> > > > >> > However, the challenges we’re going to run into probably with
> > > > >> > licensing-related issues, plus the simple fact that the
> enterprise
> > > > >> cluster
> > > > >> > is large and will add time in reviewing the release, might argue
> > > > against
> > > > >> > including it, and instead support Jakarta EE by including the
> 8.2
> > > > update
> > > > >> > center registration in the release to simplify finding and
> > > installing
> > > > >> the
> > > > >> > related plugins.
> > > > >> >
> > > > >> > Plus maybe we could rename the too general name ‘enterprise’
> with
> > > > >> ‘jakarta’
> > > > >> > or ‘jakartaee’ as the name of the cluster, to make it clearer
> what
> > > it
> > > > >> > contains, and to explicitly support Jakarta EE.
> > > > >> >
> > > > >> > Gj
> > > > >> >
> > > > >>
> > > > >
> > > > >
> > > >
> > > --
> > > Josh Juneau
> > > juneau001@gmail.com
> > > http://jj-blogger.blogspot.com
> > > https://www.apress.com/index.php/author/author/view/id/1866
> > >
> >
> --
> Josh Juneau
> juneau001@gmail.com
> http://jj-blogger.blogspot.com
> https://www.apress.com/index.php/author/author/view/id/1866
>
Re: Jakarta EE and Apache NetBeans 10
Posted by Josh Juneau <ju...@gmail.com>.
Hi Geertjan,
Yes, I've not made it through the licensing for the Java EE modules as
quickly as I had hoped to. There are a couple of particularly messy
modules that I've been working with...but I will try to get through more
this week.
Thanks for following up...I appreciate it!
On Tue, Sep 25, 2018 at 1:41 AM Geertjan Wielenga
<ge...@googlemail.com.invalid> wrote:
> I see a lot of items still open in the 'enterprise' cluster when I look at
> the Rat report:
>
>
> https://builds.apache.org/job/incubator-netbeans-linux/826/artifact/nbbuild/build/rat-report.txt
>
> Gj
>
> On Tue, Sep 18, 2018 at 1:35 PM, Josh Juneau <ju...@gmail.com> wrote:
>
> > Hi All,
> >
> > I've been trying to get through the licensing for the Java EE-related
> > modules. Some of them are tough...no doubt. I've found some modules
> that
> > have dozens of files that need to be licensed (mostly test souces...but
> not
> > in Rat), and others include a few external dependencies that require
> > special attention. I'll try to focus on getting through these licensing
> > issues over the next week.
> >
> > Thanks
> >
> > On Tue, Sep 18, 2018 at 3:51 AM Geertjan Wielenga
> > <ge...@googlemail.com.invalid> wrote:
> >
> > > Right now, it seems we're comfortable with JDK 11 and PHP, though we'd
> be
> > > very happy for Jakarta EE, Groovy, and JavaScript to be included --
> > > assuming people step up for real beyond sending e-mails about this.
> I.e.,
> > > Junichi has clearly taken the leadership in terms of PHP and we're in a
> > > good state here, if the same can be done for other clusters and soon,
> > then
> > > let's include those too for the November release, otherwise focus on
> > those
> > > for the next quarter, i.e., February 2019.
> > >
> > > That said, here's the starting point for the Wiki for Apache NetBeans
> 10:
> > >
> > >
> https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+10
> > >
> > > Please populate the above (e.g., put anything in the Miscellaneous page
> > > that's not directly applicable to PHP and JDK 11) with your
> enhancements,
> > > features, and significant bug fixes.
> > >
> > > Thanks,
> > >
> > > Gj
> > >
> > >
> > > On Tue, Sep 18, 2018 at 10:00 AM, Geertjan Wielenga <
> > > geertjan.wielenga@googlemail.com> wrote:
> > >
> > > > Well, cool, and sorry for forgetting about that, Emmanuel.
> > > >
> > > > Could you put together everything you have done in this area?
> > > >
> > > > Have you put everything you've done as pull requests into the Apache
> > > > NetBeans GitHub repo?
> > > >
> > > > How far off are we from having Java EE 8 support right now, i.e.,
> what
> > > > would that entail?
> > > >
> > > > Sure, if we can take a swing at it and have clear direction and the
> > time
> > > > to do it for the November release, let's do it.
> > > >
> > > > Gj
> > > >
> > > > On Tue, Sep 18, 2018 at 9:09 AM, ehsavoie <
> emmanuel.hugonnet@gmail.com
> > >
> > > > wrote:
> > > >
> > > >> Hi,
> > > >> I'm almost sure that i wrote some changes since 8.2 and I have more
> > for
> > > >> WildFly that have been resting in my local repo for a year.
> > > >> Also we don't have support for javaEE8 so no Jakarta EE :(
> > > >> We really should take a swing at this because this is coming back to
> > me
> > > a
> > > >> lot this lack of 'native' support for JavaEE in NetBeans
> > > >> ----------
> > > >> Emmanuel Hugonnet
> > > >> http://www.ehsavoie.com
> > > >> http://twitter.com/ehsavoie
> > > >>
> > > >>
> > > >> On Tue, Sep 18, 2018 at 6:11 AM Geertjan Wielenga
> > > >> <ge...@googlemail.com.invalid> wrote:
> > > >>
> > > >> > Hi all,
> > > >> >
> > > >> > Some (e.g., Josh) have argued we should include the enterprise
> > cluster
> > > >> in
> > > >> > the upcoming release to support Jakarta EE.
> > > >> >
> > > >> > One point to realize here is that no development has been done in
> > this
> > > >> area
> > > >> > and the functionality in GitHub right now is identical to that
> > > provided
> > > >> by
> > > >> > 8.2 plugins.
> > > >> >
> > > >> > However, the challenges we’re going to run into probably with
> > > >> > licensing-related issues, plus the simple fact that the enterprise
> > > >> cluster
> > > >> > is large and will add time in reviewing the release, might argue
> > > against
> > > >> > including it, and instead support Jakarta EE by including the 8.2
> > > update
> > > >> > center registration in the release to simplify finding and
> > installing
> > > >> the
> > > >> > related plugins.
> > > >> >
> > > >> > Plus maybe we could rename the too general name ‘enterprise’ with
> > > >> ‘jakarta’
> > > >> > or ‘jakartaee’ as the name of the cluster, to make it clearer what
> > it
> > > >> > contains, and to explicitly support Jakarta EE.
> > > >> >
> > > >> > Gj
> > > >> >
> > > >>
> > > >
> > > >
> > >
> > --
> > Josh Juneau
> > juneau001@gmail.com
> > http://jj-blogger.blogspot.com
> > https://www.apress.com/index.php/author/author/view/id/1866
> >
>
--
Josh Juneau
juneau001@gmail.com
http://jj-blogger.blogspot.com
https://www.apress.com/index.php/author/author/view/id/1866
Re: Jakarta EE and Apache NetBeans 10
Posted by Geertjan Wielenga <ge...@googlemail.com.INVALID>.
I see a lot of items still open in the 'enterprise' cluster when I look at
the Rat report:
https://builds.apache.org/job/incubator-netbeans-linux/826/artifact/nbbuild/build/rat-report.txt
Gj
On Tue, Sep 18, 2018 at 1:35 PM, Josh Juneau <ju...@gmail.com> wrote:
> Hi All,
>
> I've been trying to get through the licensing for the Java EE-related
> modules. Some of them are tough...no doubt. I've found some modules that
> have dozens of files that need to be licensed (mostly test souces...but not
> in Rat), and others include a few external dependencies that require
> special attention. I'll try to focus on getting through these licensing
> issues over the next week.
>
> Thanks
>
> On Tue, Sep 18, 2018 at 3:51 AM Geertjan Wielenga
> <ge...@googlemail.com.invalid> wrote:
>
> > Right now, it seems we're comfortable with JDK 11 and PHP, though we'd be
> > very happy for Jakarta EE, Groovy, and JavaScript to be included --
> > assuming people step up for real beyond sending e-mails about this. I.e.,
> > Junichi has clearly taken the leadership in terms of PHP and we're in a
> > good state here, if the same can be done for other clusters and soon,
> then
> > let's include those too for the November release, otherwise focus on
> those
> > for the next quarter, i.e., February 2019.
> >
> > That said, here's the starting point for the Wiki for Apache NetBeans 10:
> >
> > https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+10
> >
> > Please populate the above (e.g., put anything in the Miscellaneous page
> > that's not directly applicable to PHP and JDK 11) with your enhancements,
> > features, and significant bug fixes.
> >
> > Thanks,
> >
> > Gj
> >
> >
> > On Tue, Sep 18, 2018 at 10:00 AM, Geertjan Wielenga <
> > geertjan.wielenga@googlemail.com> wrote:
> >
> > > Well, cool, and sorry for forgetting about that, Emmanuel.
> > >
> > > Could you put together everything you have done in this area?
> > >
> > > Have you put everything you've done as pull requests into the Apache
> > > NetBeans GitHub repo?
> > >
> > > How far off are we from having Java EE 8 support right now, i.e., what
> > > would that entail?
> > >
> > > Sure, if we can take a swing at it and have clear direction and the
> time
> > > to do it for the November release, let's do it.
> > >
> > > Gj
> > >
> > > On Tue, Sep 18, 2018 at 9:09 AM, ehsavoie <emmanuel.hugonnet@gmail.com
> >
> > > wrote:
> > >
> > >> Hi,
> > >> I'm almost sure that i wrote some changes since 8.2 and I have more
> for
> > >> WildFly that have been resting in my local repo for a year.
> > >> Also we don't have support for javaEE8 so no Jakarta EE :(
> > >> We really should take a swing at this because this is coming back to
> me
> > a
> > >> lot this lack of 'native' support for JavaEE in NetBeans
> > >> ----------
> > >> Emmanuel Hugonnet
> > >> http://www.ehsavoie.com
> > >> http://twitter.com/ehsavoie
> > >>
> > >>
> > >> On Tue, Sep 18, 2018 at 6:11 AM Geertjan Wielenga
> > >> <ge...@googlemail.com.invalid> wrote:
> > >>
> > >> > Hi all,
> > >> >
> > >> > Some (e.g., Josh) have argued we should include the enterprise
> cluster
> > >> in
> > >> > the upcoming release to support Jakarta EE.
> > >> >
> > >> > One point to realize here is that no development has been done in
> this
> > >> area
> > >> > and the functionality in GitHub right now is identical to that
> > provided
> > >> by
> > >> > 8.2 plugins.
> > >> >
> > >> > However, the challenges we’re going to run into probably with
> > >> > licensing-related issues, plus the simple fact that the enterprise
> > >> cluster
> > >> > is large and will add time in reviewing the release, might argue
> > against
> > >> > including it, and instead support Jakarta EE by including the 8.2
> > update
> > >> > center registration in the release to simplify finding and
> installing
> > >> the
> > >> > related plugins.
> > >> >
> > >> > Plus maybe we could rename the too general name ‘enterprise’ with
> > >> ‘jakarta’
> > >> > or ‘jakartaee’ as the name of the cluster, to make it clearer what
> it
> > >> > contains, and to explicitly support Jakarta EE.
> > >> >
> > >> > Gj
> > >> >
> > >>
> > >
> > >
> >
> --
> Josh Juneau
> juneau001@gmail.com
> http://jj-blogger.blogspot.com
> https://www.apress.com/index.php/author/author/view/id/1866
>
Re: Jakarta EE and Apache NetBeans 10
Posted by Josh Juneau <ju...@gmail.com>.
Hi All,
I've been trying to get through the licensing for the Java EE-related
modules. Some of them are tough...no doubt. I've found some modules that
have dozens of files that need to be licensed (mostly test souces...but not
in Rat), and others include a few external dependencies that require
special attention. I'll try to focus on getting through these licensing
issues over the next week.
Thanks
On Tue, Sep 18, 2018 at 3:51 AM Geertjan Wielenga
<ge...@googlemail.com.invalid> wrote:
> Right now, it seems we're comfortable with JDK 11 and PHP, though we'd be
> very happy for Jakarta EE, Groovy, and JavaScript to be included --
> assuming people step up for real beyond sending e-mails about this. I.e.,
> Junichi has clearly taken the leadership in terms of PHP and we're in a
> good state here, if the same can be done for other clusters and soon, then
> let's include those too for the November release, otherwise focus on those
> for the next quarter, i.e., February 2019.
>
> That said, here's the starting point for the Wiki for Apache NetBeans 10:
>
> https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+10
>
> Please populate the above (e.g., put anything in the Miscellaneous page
> that's not directly applicable to PHP and JDK 11) with your enhancements,
> features, and significant bug fixes.
>
> Thanks,
>
> Gj
>
>
> On Tue, Sep 18, 2018 at 10:00 AM, Geertjan Wielenga <
> geertjan.wielenga@googlemail.com> wrote:
>
> > Well, cool, and sorry for forgetting about that, Emmanuel.
> >
> > Could you put together everything you have done in this area?
> >
> > Have you put everything you've done as pull requests into the Apache
> > NetBeans GitHub repo?
> >
> > How far off are we from having Java EE 8 support right now, i.e., what
> > would that entail?
> >
> > Sure, if we can take a swing at it and have clear direction and the time
> > to do it for the November release, let's do it.
> >
> > Gj
> >
> > On Tue, Sep 18, 2018 at 9:09 AM, ehsavoie <em...@gmail.com>
> > wrote:
> >
> >> Hi,
> >> I'm almost sure that i wrote some changes since 8.2 and I have more for
> >> WildFly that have been resting in my local repo for a year.
> >> Also we don't have support for javaEE8 so no Jakarta EE :(
> >> We really should take a swing at this because this is coming back to me
> a
> >> lot this lack of 'native' support for JavaEE in NetBeans
> >> ----------
> >> Emmanuel Hugonnet
> >> http://www.ehsavoie.com
> >> http://twitter.com/ehsavoie
> >>
> >>
> >> On Tue, Sep 18, 2018 at 6:11 AM Geertjan Wielenga
> >> <ge...@googlemail.com.invalid> wrote:
> >>
> >> > Hi all,
> >> >
> >> > Some (e.g., Josh) have argued we should include the enterprise cluster
> >> in
> >> > the upcoming release to support Jakarta EE.
> >> >
> >> > One point to realize here is that no development has been done in this
> >> area
> >> > and the functionality in GitHub right now is identical to that
> provided
> >> by
> >> > 8.2 plugins.
> >> >
> >> > However, the challenges we’re going to run into probably with
> >> > licensing-related issues, plus the simple fact that the enterprise
> >> cluster
> >> > is large and will add time in reviewing the release, might argue
> against
> >> > including it, and instead support Jakarta EE by including the 8.2
> update
> >> > center registration in the release to simplify finding and installing
> >> the
> >> > related plugins.
> >> >
> >> > Plus maybe we could rename the too general name ‘enterprise’ with
> >> ‘jakarta’
> >> > or ‘jakartaee’ as the name of the cluster, to make it clearer what it
> >> > contains, and to explicitly support Jakarta EE.
> >> >
> >> > Gj
> >> >
> >>
> >
> >
>
--
Josh Juneau
juneau001@gmail.com
http://jj-blogger.blogspot.com
https://www.apress.com/index.php/author/author/view/id/1866
Re: Jakarta EE and Apache NetBeans 10
Posted by Geertjan Wielenga <ge...@googlemail.com.INVALID>.
Right now, it seems we're comfortable with JDK 11 and PHP, though we'd be
very happy for Jakarta EE, Groovy, and JavaScript to be included --
assuming people step up for real beyond sending e-mails about this. I.e.,
Junichi has clearly taken the leadership in terms of PHP and we're in a
good state here, if the same can be done for other clusters and soon, then
let's include those too for the November release, otherwise focus on those
for the next quarter, i.e., February 2019.
That said, here's the starting point for the Wiki for Apache NetBeans 10:
https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+10
Please populate the above (e.g., put anything in the Miscellaneous page
that's not directly applicable to PHP and JDK 11) with your enhancements,
features, and significant bug fixes.
Thanks,
Gj
On Tue, Sep 18, 2018 at 10:00 AM, Geertjan Wielenga <
geertjan.wielenga@googlemail.com> wrote:
> Well, cool, and sorry for forgetting about that, Emmanuel.
>
> Could you put together everything you have done in this area?
>
> Have you put everything you've done as pull requests into the Apache
> NetBeans GitHub repo?
>
> How far off are we from having Java EE 8 support right now, i.e., what
> would that entail?
>
> Sure, if we can take a swing at it and have clear direction and the time
> to do it for the November release, let's do it.
>
> Gj
>
> On Tue, Sep 18, 2018 at 9:09 AM, ehsavoie <em...@gmail.com>
> wrote:
>
>> Hi,
>> I'm almost sure that i wrote some changes since 8.2 and I have more for
>> WildFly that have been resting in my local repo for a year.
>> Also we don't have support for javaEE8 so no Jakarta EE :(
>> We really should take a swing at this because this is coming back to me a
>> lot this lack of 'native' support for JavaEE in NetBeans
>> ----------
>> Emmanuel Hugonnet
>> http://www.ehsavoie.com
>> http://twitter.com/ehsavoie
>>
>>
>> On Tue, Sep 18, 2018 at 6:11 AM Geertjan Wielenga
>> <ge...@googlemail.com.invalid> wrote:
>>
>> > Hi all,
>> >
>> > Some (e.g., Josh) have argued we should include the enterprise cluster
>> in
>> > the upcoming release to support Jakarta EE.
>> >
>> > One point to realize here is that no development has been done in this
>> area
>> > and the functionality in GitHub right now is identical to that provided
>> by
>> > 8.2 plugins.
>> >
>> > However, the challenges we’re going to run into probably with
>> > licensing-related issues, plus the simple fact that the enterprise
>> cluster
>> > is large and will add time in reviewing the release, might argue against
>> > including it, and instead support Jakarta EE by including the 8.2 update
>> > center registration in the release to simplify finding and installing
>> the
>> > related plugins.
>> >
>> > Plus maybe we could rename the too general name ‘enterprise’ with
>> ‘jakarta’
>> > or ‘jakartaee’ as the name of the cluster, to make it clearer what it
>> > contains, and to explicitly support Jakarta EE.
>> >
>> > Gj
>> >
>>
>
>
Re: Jakarta EE and Apache NetBeans 10
Posted by Geertjan Wielenga <ge...@googlemail.com.INVALID>.
Well, cool, and sorry for forgetting about that, Emmanuel.
Could you put together everything you have done in this area?
Have you put everything you've done as pull requests into the Apache
NetBeans GitHub repo?
How far off are we from having Java EE 8 support right now, i.e., what
would that entail?
Sure, if we can take a swing at it and have clear direction and the time to
do it for the November release, let's do it.
Gj
On Tue, Sep 18, 2018 at 9:09 AM, ehsavoie <em...@gmail.com>
wrote:
> Hi,
> I'm almost sure that i wrote some changes since 8.2 and I have more for
> WildFly that have been resting in my local repo for a year.
> Also we don't have support for javaEE8 so no Jakarta EE :(
> We really should take a swing at this because this is coming back to me a
> lot this lack of 'native' support for JavaEE in NetBeans
> ----------
> Emmanuel Hugonnet
> http://www.ehsavoie.com
> http://twitter.com/ehsavoie
>
>
> On Tue, Sep 18, 2018 at 6:11 AM Geertjan Wielenga
> <ge...@googlemail.com.invalid> wrote:
>
> > Hi all,
> >
> > Some (e.g., Josh) have argued we should include the enterprise cluster in
> > the upcoming release to support Jakarta EE.
> >
> > One point to realize here is that no development has been done in this
> area
> > and the functionality in GitHub right now is identical to that provided
> by
> > 8.2 plugins.
> >
> > However, the challenges we’re going to run into probably with
> > licensing-related issues, plus the simple fact that the enterprise
> cluster
> > is large and will add time in reviewing the release, might argue against
> > including it, and instead support Jakarta EE by including the 8.2 update
> > center registration in the release to simplify finding and installing the
> > related plugins.
> >
> > Plus maybe we could rename the too general name ‘enterprise’ with
> ‘jakarta’
> > or ‘jakartaee’ as the name of the cluster, to make it clearer what it
> > contains, and to explicitly support Jakarta EE.
> >
> > Gj
> >
>
Re: Jakarta EE and Apache NetBeans 10
Posted by ehsavoie <em...@gmail.com>.
Hi,
I'm almost sure that i wrote some changes since 8.2 and I have more for
WildFly that have been resting in my local repo for a year.
Also we don't have support for javaEE8 so no Jakarta EE :(
We really should take a swing at this because this is coming back to me a
lot this lack of 'native' support for JavaEE in NetBeans
----------
Emmanuel Hugonnet
http://www.ehsavoie.com
http://twitter.com/ehsavoie
On Tue, Sep 18, 2018 at 6:11 AM Geertjan Wielenga
<ge...@googlemail.com.invalid> wrote:
> Hi all,
>
> Some (e.g., Josh) have argued we should include the enterprise cluster in
> the upcoming release to support Jakarta EE.
>
> One point to realize here is that no development has been done in this area
> and the functionality in GitHub right now is identical to that provided by
> 8.2 plugins.
>
> However, the challenges we’re going to run into probably with
> licensing-related issues, plus the simple fact that the enterprise cluster
> is large and will add time in reviewing the release, might argue against
> including it, and instead support Jakarta EE by including the 8.2 update
> center registration in the release to simplify finding and installing the
> related plugins.
>
> Plus maybe we could rename the too general name ‘enterprise’ with ‘jakarta’
> or ‘jakartaee’ as the name of the cluster, to make it clearer what it
> contains, and to explicitly support Jakarta EE.
>
> Gj
>