Re: Java EE 8 Support Repairs - Enhancements to repair [NETBEANS-2800]

2019-07-12 Thread Neil C Smith
Hi,

Copied from PR ...

On Thu, 11 Jul 2019 at 22:35, Josh Juneau  wrote:
> Thanks Neil!  I’ll submit the PR tonight.  I appreciate it.

Unfortunately this PR is broken.  I've tried manually creating a patch
based on your last commit and it also fails to build with the same
error as in Travis

```
... netbeans/enterprise/j2ee.dd/build.xml:341: Replace: source file
...netbeans/enterprise/j2ee.dd/src/org/netbeans/modules/j2ee/dd/impl/web/model_4_0_frag/WebFragment.java
doesn't exist
```

It looks like the .gitignore file at
https://github.com/apache/netbeans/blob/master/enterprise/j2ee.dd/.gitignore
needs updating for the newly generated files too.

I think you're going to have to reset your fork (or delete and create
a new fork), keep master clean and in sync, apply these changes in a
PR-specific branch, check it builds, and resubmit the PR.

Let me know if that's feasible today and I'll hold off beta4 build.  Thanks!

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists





Re: Java EE 8 Support Repairs - Enhancements to repair [NETBEANS-2800]

2019-07-11 Thread Josh Juneau
Thanks Neil!  I’ll submit the PR tonight.  I appreciate it.  


Josh Juneau
http://jj-blogger.blogspot.com
https://www.apress.com/index.php/author/author/view/id/1866


> On Jul 11, 2019, at 3:04 PM, Neil C Smith  wrote:
> 
>> On Thu, 11 Jul 2019, 20:05 Josh Juneau,  wrote:
>> 
>> 
>> I have not yet created the PR, but I will do so.  One question though, when
>> I compare files on the PR within my project on GitHub, it shows all of the
>> commit history for the Java EE 8 commits...so there are 13 commits showing
>> up in the PR.  This is similar to the last PR I submitted that showed 12
>> commits...I believe you probably remember this.  Should I just go ahead and
>> proceed to submit the PR, or is there something I need to do with my fork
>> before submitting?
>> 
> 
> It's because your commits were squashed and merged in the original PR so
> don't exist in the upstream history. Ideally keep your fork's master branch
> in sync with upstream and create a separate branch off it for each PR.
> 
> I should be able to squash and merge the new PR to get it to work though,
> as I did with your last fixes, if you can't do above in time.
> 
> Thanks and best wishes,
> 
> Neil
> 
>> 


Re: Java EE 8 Support Repairs - Enhancements to repair [NETBEANS-2800]

2019-07-11 Thread Neil C Smith
On Thu, 11 Jul 2019, 20:05 Josh Juneau,  wrote:

>
> I have not yet created the PR, but I will do so.  One question though, when
> I compare files on the PR within my project on GitHub, it shows all of the
> commit history for the Java EE 8 commits...so there are 13 commits showing
> up in the PR.  This is similar to the last PR I submitted that showed 12
> commits...I believe you probably remember this.  Should I just go ahead and
> proceed to submit the PR, or is there something I need to do with my fork
> before submitting?
>

It's because your commits were squashed and merged in the original PR so
don't exist in the upstream history. Ideally keep your fork's master branch
in sync with upstream and create a separate branch off it for each PR.

I should be able to squash and merge the new PR to get it to work though,
as I did with your last fixes, if you can't do above in time.

Thanks and best wishes,

Neil

>


Re: Java EE 8 Support Repairs - Enhancements to repair [NETBEANS-2800]

2019-07-11 Thread Josh Juneau
Hi Neil,

I have not yet created the PR, but I will do so.  One question though, when
I compare files on the PR within my project on GitHub, it shows all of the
commit history for the Java EE 8 commits...so there are 13 commits showing
up in the PR.  This is similar to the last PR I submitted that showed 12
commits...I believe you probably remember this.  Should I just go ahead and
proceed to submit the PR, or is there something I need to do with my fork
before submitting?

Thanks

On Thu, Jul 11, 2019 at 1:45 PM Neil C Smith  wrote:

> Hi Josh,
>
> On Thu, 11 Jul 2019 at 04:05, Josh Juneau  wrote:
> > At this point, I would like to request that we create a vc2 to include
> > these new enhancements.  That way, the Java EE 8 support should be much
> > more stable, as the web.xml 4.0 would now being recognized correctly by
> the
> > IDE.
>
> Looks like you might be in luck! :-\  The Payara Micro bug seems like
> it's going to force a second VC.
>
> Is there a PR for this fix yet?  If not, could you create one?
>
> Given time pressures, I might not be able to roll another VC until
> early next week.  But, if we can get relevant fixes in tomorrow I
> might use that to our advantage and look at a beta4 to test with for a
> few days before then.
>
> Thanks,
>
> Neil
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
> For additional commands, e-mail: dev-h...@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
> --
Josh Juneau
juneau...@gmail.com
http://jj-blogger.blogspot.com
https://www.apress.com/us/search?query=Juneau



Re: Java EE 8 Support Repairs - Enhancements to repair [NETBEANS-2800]

2019-07-11 Thread Neil C Smith
Hi Josh,

On Thu, 11 Jul 2019 at 04:05, Josh Juneau  wrote:
> At this point, I would like to request that we create a vc2 to include
> these new enhancements.  That way, the Java EE 8 support should be much
> more stable, as the web.xml 4.0 would now being recognized correctly by the
> IDE.

Looks like you might be in luck! :-\  The Payara Micro bug seems like
it's going to force a second VC.

Is there a PR for this fix yet?  If not, could you create one?

Given time pressures, I might not be able to roll another VC until
early next week.  But, if we can get relevant fixes in tomorrow I
might use that to our advantage and look at a beta4 to test with for a
few days before then.

Thanks,

Neil

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists





Re: Java EE 8 Support Repairs - Enhancements to repair [NETBEANS-2800]

2019-07-11 Thread Geertjan Wielenga
That's great to hear, thanks Josh.

Gj

On Thu, Jul 11, 2019 at 2:17 PM Josh Juneau  wrote:

> Hi Neil/Geertjan,
>
> I think that we should list the "Known Issues" on the wiki page, but we
> should leave the "Preview" text off.  There are workarounds that will
> enable full functionality for the Java EE 8 projects.  In my opinion, I
> don't think it is a preview...it is just an initial release.
>
> I will write up some issues and workarounds and add them to the wiki.
>
> Thanks again
>
> Josh Juneau
> juneau...@gmail.com
> http://jj-blogger.blogspot.com
> https://www.apress.com/us/search?query=Juneau
> 
>
>
>
> On Thu, Jul 11, 2019 at 7:12 AM Geertjan Wielenga 
> wrote:
>
> > But, then again, calling the whole release a preview release would cause
> > confusion and send out the wrong message.
> >
> > So, I agree with Neil and disagree with my own counter proposal. :-)
> >
> > Gj
> >
> > On Thu, Jul 11, 2019 at 2:05 PM Geertjan Wielenga 
> > wrote:
> >
> > > Makes sense to me. The other approach is to consider all non-LTS
> releases
> > > as preview releases by default, i.e., preview release for the next LTS
> > > release.
> > >
> > > Gj
> > >
> > > On Thu, Jul 11, 2019 at 2:04 PM Neil C Smith 
> > > wrote:
> > >
> > >> On Thu, 11 Jul 2019 at 12:51, Josh Juneau 
> wrote:
> > >> >
> > >> > Thanks Geertjan...I will provide some details of the Java EE 8
> support
> > >> in
> > >> > 11.1 on the wiki page.
> > >> >
> > >>
> > >> Could you also add a known issues and workarounds section?  That would
> > >> be useful to add on the website.
> > >>
> > >> I wonder if we should also use (preview) on the website against new
> > >> features we know have a few issues?
> > >>
> > >> eg.
> > >>
> > >> JavaEE 8 (preview)
> > >> Inline editor hints (preview)
> > >>
> > >> non-LTS releases of Apache NetBeans may include preview features that
> > >> while mostly complete might have minor usability issues or require
> > >> occasional workarounds (see notes)
> > >>
> > >> Best wishes,
> > >>
> > >> Neil
> > >>
> > >> -
> > >> To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
> > >> For additional commands, e-mail: dev-h...@netbeans.apache.org
> > >>
> > >> For further information about the NetBeans mailing lists, visit:
> > >> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> > >>
> > >>
> > >>
> > >>
> >
>


Re: Java EE 8 Support Repairs - Enhancements to repair [NETBEANS-2800]

2019-07-11 Thread Geertjan Wielenga
Agreed.

Gj

On Thu, Jul 11, 2019 at 2:14 PM Neil C Smith  wrote:

> On Thu, 11 Jul 2019 at 13:06, Geertjan Wielenga 
> wrote:
> >
> > Makes sense to me. The other approach is to consider all non-LTS releases
> > as preview releases by default, i.e., preview release for the next LTS
> > release.
>
> Yes, that was definitely my thoughts on the schedule and making use of
> quarterly releases / NetCAT.  I just think that highlighting which new
> features are considered to be in that state and not is also useful for
> end users though.  Everything else should *hopefully* be just as
> stable as NB 11.0! :-)
>
> Neil
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
> For additional commands, e-mail: dev-h...@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>


Re: Java EE 8 Support Repairs - Enhancements to repair [NETBEANS-2800]

2019-07-11 Thread Neil C Smith
On Thu, 11 Jul 2019 at 13:06, Geertjan Wielenga  wrote:
>
> Makes sense to me. The other approach is to consider all non-LTS releases
> as preview releases by default, i.e., preview release for the next LTS
> release.

Yes, that was definitely my thoughts on the schedule and making use of
quarterly releases / NetCAT.  I just think that highlighting which new
features are considered to be in that state and not is also useful for
end users though.  Everything else should *hopefully* be just as
stable as NB 11.0! :-)

Neil

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists





Re: Java EE 8 Support Repairs - Enhancements to repair [NETBEANS-2800]

2019-07-11 Thread Neil C Smith
On Thu, 11 Jul 2019 at 12:51, Josh Juneau  wrote:
>
> Thanks Geertjan...I will provide some details of the Java EE 8 support in
> 11.1 on the wiki page.
>

Could you also add a known issues and workarounds section?  That would
be useful to add on the website.

I wonder if we should also use (preview) on the website against new
features we know have a few issues?

eg.

JavaEE 8 (preview)
Inline editor hints (preview)

non-LTS releases of Apache NetBeans may include preview features that
while mostly complete might have minor usability issues or require
occasional workarounds (see notes)

Best wishes,

Neil

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists





Re: Java EE 8 Support Repairs - Enhancements to repair [NETBEANS-2800]

2019-07-11 Thread Josh Juneau
Thanks Geertjan...I will provide some details of the Java EE 8 support in
11.1 on the wiki page.

Josh Juneau
juneau...@gmail.com
http://jj-blogger.blogspot.com
https://www.apress.com/us/search?query=Juneau




On Thu, Jul 11, 2019 at 6:42 AM Geertjan Wielenga 
wrote:

> Great to hear we're on the same page.
>
> I confess I do not know exactly what the Java EE 8 work you have done for
> 11.1 consists of, exactly. The more details you can provide on this page,
> as the basis for the official one to be published on netbeans.apache.org,
> even if simply a bulleted list, would help a lot:
>
> https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+11.1
>
> Gj
>
> On Thu, Jul 11, 2019 at 1:12 PM Josh Juneau  wrote:
>
> > Thanks Geertjan and Neil, I agree with your assessment.  Let's deliver
> 11.1
> > with the Java EE 8 support, as-is, and we'll continue to improve it for
> > future releases.  It is true that I now understand much more of the Java
> EE
> > support code in NetBeans...so making these enhancements for future
> releases
> > should be a bit easier.
> >
> > Just as a side note, I appreciate the feedback on the initial Java EE 8
> > support, Geertjan.  These changes in the upcoming PR will repair the
> wizard
> > issues.  It is all due to the web.xml not being a recognized version at
> > 4.0.
> >
> > I'll +1 this release so we can move onward...thanks again.
> >
> > On Thu, Jul 11, 2019 at 5:44 AM Geertjan Wielenga 
> > wrote:
> >
> > > Absolutely agree.
> > >
> > > Gj
> > >
> > > On Thu, Jul 11, 2019 at 12:43 PM Neil C Smith 
> > > wrote:
> > >
> > > > On Thu, 11 Jul 2019 at 10:24, Geertjan Wielenga  >
> > > > wrote:
> > > > >
> > > > > The other thing to bear in mind is that Josh is now really in the
> > > groove,
> > > > > or whatever the term is, in terms of his Java EE 8 / NetBeans
> > > development
> > > > > skills -- this is excellent news. It's all good from here, since
> > > > everything
> > > > > he does will just accumulate from one release to the next. We
> should
> > > see
> > > > > this as the first step in the direction of Java EE 8 and use 11.1
> to
> > > kick
> > > > > the tires for 11.2 etc so that when we get to 12, we'll have a
> really
> > > > solid
> > > > > product around Java EE 8. I haven't yet managed to get the large
> code
> > > > > generation wizards, e.g., from database to REST endpoints, etc, to
> > work
> > > > in
> > > > > Java EE 8, and these kinds of things should be the focus next -- as
> > > well
> > > > as
> > > > > getting more people on board to work with Josh, and Gaurav from
> > Payara,
> > > > on
> > > > > these kinds of enhancements.
> > > > >
> > > >
> > > > Agreed!  Given particularly these things came in after feature
> freeze,
> > > > we should expect there might be a few rough edges still.  That's not
> > > > only fine, IMO, it's also the main reason for having non-LTS.  The
> key
> > > > thing is to tidy up the rough edges by NB 12.0.  And obviously
> > > > presenting that clearly to end users via the website.
> > > >
> > > > And we have an AUC.  If we can find a better way to use it, we can
> > > > cherry pick and push select updates via the release branch if we
> > > > really want/need to.
> > > >
> > > > Neil
> > > >
> > > > -
> > > > To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
> > > > For additional commands, e-mail: dev-h...@netbeans.apache.org
> > > >
> > > > For further information about the NetBeans mailing lists, visit:
> > > > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> > > >
> > > >
> > > >
> > > >
> > >
> > --
> > Josh Juneau
> > juneau...@gmail.com
> > http://jj-blogger.blogspot.com
> > https://www.apress.com/us/search?query=Juneau
> > 
> >
>


Re: Java EE 8 Support Repairs - Enhancements to repair [NETBEANS-2800]

2019-07-11 Thread Geertjan Wielenga
Great to hear we're on the same page.

I confess I do not know exactly what the Java EE 8 work you have done for
11.1 consists of, exactly. The more details you can provide on this page,
as the basis for the official one to be published on netbeans.apache.org,
even if simply a bulleted list, would help a lot:

https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+11.1

Gj

On Thu, Jul 11, 2019 at 1:12 PM Josh Juneau  wrote:

> Thanks Geertjan and Neil, I agree with your assessment.  Let's deliver 11.1
> with the Java EE 8 support, as-is, and we'll continue to improve it for
> future releases.  It is true that I now understand much more of the Java EE
> support code in NetBeans...so making these enhancements for future releases
> should be a bit easier.
>
> Just as a side note, I appreciate the feedback on the initial Java EE 8
> support, Geertjan.  These changes in the upcoming PR will repair the wizard
> issues.  It is all due to the web.xml not being a recognized version at
> 4.0.
>
> I'll +1 this release so we can move onward...thanks again.
>
> On Thu, Jul 11, 2019 at 5:44 AM Geertjan Wielenga 
> wrote:
>
> > Absolutely agree.
> >
> > Gj
> >
> > On Thu, Jul 11, 2019 at 12:43 PM Neil C Smith 
> > wrote:
> >
> > > On Thu, 11 Jul 2019 at 10:24, Geertjan Wielenga 
> > > wrote:
> > > >
> > > > The other thing to bear in mind is that Josh is now really in the
> > groove,
> > > > or whatever the term is, in terms of his Java EE 8 / NetBeans
> > development
> > > > skills -- this is excellent news. It's all good from here, since
> > > everything
> > > > he does will just accumulate from one release to the next. We should
> > see
> > > > this as the first step in the direction of Java EE 8 and use 11.1 to
> > kick
> > > > the tires for 11.2 etc so that when we get to 12, we'll have a really
> > > solid
> > > > product around Java EE 8. I haven't yet managed to get the large code
> > > > generation wizards, e.g., from database to REST endpoints, etc, to
> work
> > > in
> > > > Java EE 8, and these kinds of things should be the focus next -- as
> > well
> > > as
> > > > getting more people on board to work with Josh, and Gaurav from
> Payara,
> > > on
> > > > these kinds of enhancements.
> > > >
> > >
> > > Agreed!  Given particularly these things came in after feature freeze,
> > > we should expect there might be a few rough edges still.  That's not
> > > only fine, IMO, it's also the main reason for having non-LTS.  The key
> > > thing is to tidy up the rough edges by NB 12.0.  And obviously
> > > presenting that clearly to end users via the website.
> > >
> > > And we have an AUC.  If we can find a better way to use it, we can
> > > cherry pick and push select updates via the release branch if we
> > > really want/need to.
> > >
> > > Neil
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
> > > For additional commands, e-mail: dev-h...@netbeans.apache.org
> > >
> > > For further information about the NetBeans mailing lists, visit:
> > > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> > >
> > >
> > >
> > >
> >
> --
> Josh Juneau
> juneau...@gmail.com
> http://jj-blogger.blogspot.com
> https://www.apress.com/us/search?query=Juneau
> 
>


Re: Java EE 8 Support Repairs - Enhancements to repair [NETBEANS-2800]

2019-07-11 Thread Josh Juneau
Thanks Geertjan and Neil, I agree with your assessment.  Let's deliver 11.1
with the Java EE 8 support, as-is, and we'll continue to improve it for
future releases.  It is true that I now understand much more of the Java EE
support code in NetBeans...so making these enhancements for future releases
should be a bit easier.

Just as a side note, I appreciate the feedback on the initial Java EE 8
support, Geertjan.  These changes in the upcoming PR will repair the wizard
issues.  It is all due to the web.xml not being a recognized version at 4.0.

I'll +1 this release so we can move onward...thanks again.

On Thu, Jul 11, 2019 at 5:44 AM Geertjan Wielenga 
wrote:

> Absolutely agree.
>
> Gj
>
> On Thu, Jul 11, 2019 at 12:43 PM Neil C Smith 
> wrote:
>
> > On Thu, 11 Jul 2019 at 10:24, Geertjan Wielenga 
> > wrote:
> > >
> > > The other thing to bear in mind is that Josh is now really in the
> groove,
> > > or whatever the term is, in terms of his Java EE 8 / NetBeans
> development
> > > skills -- this is excellent news. It's all good from here, since
> > everything
> > > he does will just accumulate from one release to the next. We should
> see
> > > this as the first step in the direction of Java EE 8 and use 11.1 to
> kick
> > > the tires for 11.2 etc so that when we get to 12, we'll have a really
> > solid
> > > product around Java EE 8. I haven't yet managed to get the large code
> > > generation wizards, e.g., from database to REST endpoints, etc, to work
> > in
> > > Java EE 8, and these kinds of things should be the focus next -- as
> well
> > as
> > > getting more people on board to work with Josh, and Gaurav from Payara,
> > on
> > > these kinds of enhancements.
> > >
> >
> > Agreed!  Given particularly these things came in after feature freeze,
> > we should expect there might be a few rough edges still.  That's not
> > only fine, IMO, it's also the main reason for having non-LTS.  The key
> > thing is to tidy up the rough edges by NB 12.0.  And obviously
> > presenting that clearly to end users via the website.
> >
> > And we have an AUC.  If we can find a better way to use it, we can
> > cherry pick and push select updates via the release branch if we
> > really want/need to.
> >
> > Neil
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
> > For additional commands, e-mail: dev-h...@netbeans.apache.org
> >
> > For further information about the NetBeans mailing lists, visit:
> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >
> >
> >
> >
>
-- 
Josh Juneau
juneau...@gmail.com
http://jj-blogger.blogspot.com
https://www.apress.com/us/search?query=Juneau



Re: Java EE 8 Support Repairs - Enhancements to repair [NETBEANS-2800]

2019-07-11 Thread Geertjan Wielenga
Absolutely agree.

Gj

On Thu, Jul 11, 2019 at 12:43 PM Neil C Smith  wrote:

> On Thu, 11 Jul 2019 at 10:24, Geertjan Wielenga 
> wrote:
> >
> > The other thing to bear in mind is that Josh is now really in the groove,
> > or whatever the term is, in terms of his Java EE 8 / NetBeans development
> > skills -- this is excellent news. It's all good from here, since
> everything
> > he does will just accumulate from one release to the next. We should see
> > this as the first step in the direction of Java EE 8 and use 11.1 to kick
> > the tires for 11.2 etc so that when we get to 12, we'll have a really
> solid
> > product around Java EE 8. I haven't yet managed to get the large code
> > generation wizards, e.g., from database to REST endpoints, etc, to work
> in
> > Java EE 8, and these kinds of things should be the focus next -- as well
> as
> > getting more people on board to work with Josh, and Gaurav from Payara,
> on
> > these kinds of enhancements.
> >
>
> Agreed!  Given particularly these things came in after feature freeze,
> we should expect there might be a few rough edges still.  That's not
> only fine, IMO, it's also the main reason for having non-LTS.  The key
> thing is to tidy up the rough edges by NB 12.0.  And obviously
> presenting that clearly to end users via the website.
>
> And we have an AUC.  If we can find a better way to use it, we can
> cherry pick and push select updates via the release branch if we
> really want/need to.
>
> Neil
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
> For additional commands, e-mail: dev-h...@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>


Re: Java EE 8 Support Repairs - Enhancements to repair [NETBEANS-2800]

2019-07-11 Thread Neil C Smith
On Thu, 11 Jul 2019 at 10:24, Geertjan Wielenga  wrote:
>
> The other thing to bear in mind is that Josh is now really in the groove,
> or whatever the term is, in terms of his Java EE 8 / NetBeans development
> skills -- this is excellent news. It's all good from here, since everything
> he does will just accumulate from one release to the next. We should see
> this as the first step in the direction of Java EE 8 and use 11.1 to kick
> the tires for 11.2 etc so that when we get to 12, we'll have a really solid
> product around Java EE 8. I haven't yet managed to get the large code
> generation wizards, e.g., from database to REST endpoints, etc, to work in
> Java EE 8, and these kinds of things should be the focus next -- as well as
> getting more people on board to work with Josh, and Gaurav from Payara, on
> these kinds of enhancements.
>

Agreed!  Given particularly these things came in after feature freeze,
we should expect there might be a few rough edges still.  That's not
only fine, IMO, it's also the main reason for having non-LTS.  The key
thing is to tidy up the rough edges by NB 12.0.  And obviously
presenting that clearly to end users via the website.

And we have an AUC.  If we can find a better way to use it, we can
cherry pick and push select updates via the release branch if we
really want/need to.

Neil

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists





Re: Java EE 8 Support Repairs - Enhancements to repair [NETBEANS-2800]

2019-07-11 Thread Geertjan Wielenga
The other thing to bear in mind is that Josh is now really in the groove,
or whatever the term is, in terms of his Java EE 8 / NetBeans development
skills -- this is excellent news. It's all good from here, since everything
he does will just accumulate from one release to the next. We should see
this as the first step in the direction of Java EE 8 and use 11.1 to kick
the tires for 11.2 etc so that when we get to 12, we'll have a really solid
product around Java EE 8. I haven't yet managed to get the large code
generation wizards, e.g., from database to REST endpoints, etc, to work in
Java EE 8, and these kinds of things should be the focus next -- as well as
getting more people on board to work with Josh, and Gaurav from Payara, on
these kinds of enhancements.

Gj


On Thu, Jul 11, 2019 at 11:14 AM Neil C Smith  wrote:

> On Thu, 11 Jul 2019 at 09:18, Geertjan Wielenga 
> wrote:
> > We should just document the various features that aren’t quite right yet
> > and create issues for them. If we don’t, this is potentially the start
> of a
> > very significant slip that we can’t afford.
>
> Agreed, particularly now I can get into JIRA and see mention of the
> workaround.  It's also not been marked with 11.1(!). and only classed
> as major (which seems accurate per
>
> https://cwiki.apache.org/confluence/display/NETBEANS/Bug+Priority+Guidelines
> )
>
> Creating the voting candidates (affectively the releases) is
> significantly more time consuming than the betas.  More so when you're
> still learning and have to rewrite half the docs because we're out of
> incubation. :-)
>
> Of course, if I've screwed something up in that process and we need a
> second VC anyway then we should consider this.
>
> But, in general, we're going to have a month of betas (two for LTS)
> before releases, and that's the time we should be picking up
> functionality issues.  And a voting candidate for release won't be
> made if there are blocker or critical issues assigned to the release.
> Ideally we'll only need one actual voting thread per release, unless a
> critical or blocker crops up during the vote (particularly around
> checking Apache release requirements).
>
> None of this precludes your right to -1 but given also Geertjan's
> point above my intention is to keep the vote thread live for the full
> 72hrs unless a blocking or critical is found in the meantime.
>
> Best wishes,
>
> Neil
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
> For additional commands, e-mail: dev-h...@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>


Re: Java EE 8 Support Repairs - Enhancements to repair [NETBEANS-2800]

2019-07-11 Thread Neil C Smith
On Thu, 11 Jul 2019 at 09:18, Geertjan Wielenga  wrote:
> We should just document the various features that aren’t quite right yet
> and create issues for them. If we don’t, this is potentially the start of a
> very significant slip that we can’t afford.

Agreed, particularly now I can get into JIRA and see mention of the
workaround.  It's also not been marked with 11.1(!). and only classed
as major (which seems accurate per
https://cwiki.apache.org/confluence/display/NETBEANS/Bug+Priority+Guidelines
)

Creating the voting candidates (affectively the releases) is
significantly more time consuming than the betas.  More so when you're
still learning and have to rewrite half the docs because we're out of
incubation. :-)

Of course, if I've screwed something up in that process and we need a
second VC anyway then we should consider this.

But, in general, we're going to have a month of betas (two for LTS)
before releases, and that's the time we should be picking up
functionality issues.  And a voting candidate for release won't be
made if there are blocker or critical issues assigned to the release.
Ideally we'll only need one actual voting thread per release, unless a
critical or blocker crops up during the vote (particularly around
checking Apache release requirements).

None of this precludes your right to -1 but given also Geertjan's
point above my intention is to keep the vote thread live for the full
72hrs unless a blocking or critical is found in the meantime.

Best wishes,

Neil

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists





Re: Java EE 8 Support Repairs - Enhancements to repair [NETBEANS-2800]

2019-07-11 Thread Neil C Smith
On Thu, 11 Jul 2019, 04:05 Josh Juneau,  wrote:

> At this point, I would like to request that we create a vc2 to include
> these new enhancements.  That way, the Java EE 8 support should be much
> more stable, as the web.xml 4.0 would now being recognized correctly by the
> IDE.
>

How major is this (JIRA down)? Specifically, according to our bug
guidelines, is this critical or a blocker? What if any workarounds are
there?

I'm not averse to rolling another vc for this if there's agreement even if
it's not a blocker, but realistically it'll probably be beginning of next
week before I can find time to now, so it'll knock the release back up to a
week.

Best wishes,

Neil

>