Re: [Lazy Consensus] Feature freeze pass for Java EE and Payara PRs for NB 11.1

[Neil C Smith]

On Sat, 22 Jun 2019 at 17:32, Neil C Smith  wrote:
> My inclination is to squash and merge these unless anyone has a reason
> not to before then?

I've squashed and merged two.
https://github.com/apache/netbeans/pull/1290  now has a merge
conflict.  Seems a simple and obvious reason, but be good, Gaurav, if
you can have a quick check over.

Thanks and 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: Re: [Lazy Consensus] Feature freeze pass for Java EE and Payara PRs for NB 11.1

[Geertjan Wielenga]

I was talking about from a UI perspective.

Gj

On Sun, 23 Jun 2019 at 16:39, Eric Bresie  wrote:

> Are you talking about a “branch” or label of some type from a git
> perspective or from a version display in the UI perspective?
>
> Eric Bresie
> ebre...@gmail.com
> > On June 22, 2019 at 1:54:56 PM CDT, Geertjan Wielenga <
> geert...@apache.org> wrote:
> > Great, makes sense.
> >
> > Gj
> >
> > On Sat, 22 Jun 2019 at 19:10, Neil C Smith 
> wrote:
> >
> > > On Sat, 22 Jun 2019 at 17:41, Geertjan Wielenga 
> > > wrote:
> > > >
> > > > One thing — how can the betas and final release be distinguished from
> > > each
> > > > other? Right now we have beta-1, soon beta-2, eventually final
> release,
> > > but
> > > > one day when someone reports an issue how will we know which one
> they’re
> > > > using?
> > >
> > > The only current way I think is the IDE log itself, where the modules
> > > have the release number and build date?
> > >
> > > Ideally the version in the UI would have a -beta suffix, which I don't
> > > think we had with NB 11.0 either. I could (should) have added this in
> > > all the different places it's mentioned for each beta release. I'm
> > > putting some thoughts together for NB 11.2 so that the remaining
> > > changes required in the release branch (eg.
> > > https://github.com/apache/netbeans/pull/1304 ) can be set from one
> > > place in the build so that we can more easily update each time.
> > >
> > > Hopefully anyone outside of this community will only be using the
> > > voted on releases anyway! :-)
> > >
> > > 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: Re: [Lazy Consensus] Feature freeze pass for Java EE and Payara PRs for NB 11.1

[Eric Bresie]

Are you talking about a “branch” or label of some type from a git perspective 
or from a version display in the UI perspective?

Eric Bresie
ebre...@gmail.com
> On June 22, 2019 at 1:54:56 PM CDT, Geertjan Wielenga  
> wrote:
> Great, makes sense.
>
> Gj
>
> On Sat, 22 Jun 2019 at 19:10, Neil C Smith  wrote:
>
> > On Sat, 22 Jun 2019 at 17:41, Geertjan Wielenga 
> > wrote:
> > >
> > > One thing — how can the betas and final release be distinguished from
> > each
> > > other? Right now we have beta-1, soon beta-2, eventually final release,
> > but
> > > one day when someone reports an issue how will we know which one they’re
> > > using?
> >
> > The only current way I think is the IDE log itself, where the modules
> > have the release number and build date?
> >
> > Ideally the version in the UI would have a -beta suffix, which I don't
> > think we had with NB 11.0 either. I could (should) have added this in
> > all the different places it's mentioned for each beta release. I'm
> > putting some thoughts together for NB 11.2 so that the remaining
> > changes required in the release branch (eg.
> > https://github.com/apache/netbeans/pull/1304 ) can be set from one
> > place in the build so that we can more easily update each time.
> >
> > Hopefully anyone outside of this community will only be using the
> > voted on releases anyway! :-)
> >
> > 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: [Lazy Consensus] Feature freeze pass for Java EE and Payara PRs for NB 11.1

[Geertjan Wielenga]

Great, makes sense.

Gj

On Sat, 22 Jun 2019 at 19:10, Neil C Smith  wrote:

> On Sat, 22 Jun 2019 at 17:41, Geertjan Wielenga 
> wrote:
> >
> > One thing — how can the betas and final release be distinguished from
> each
> > other? Right now we have beta-1, soon beta-2, eventually final release,
> but
> > one day when someone reports an issue how will we know which one they’re
> > using?
>
> The only current way I think is the IDE log itself, where the modules
> have the release number and build date?
>
> Ideally the version in the UI would have a -beta suffix, which I don't
> think we had with NB 11.0 either.  I could (should) have added this in
> all the different places it's mentioned for each beta release.  I'm
> putting some thoughts together for NB 11.2 so that the remaining
> changes required in the release branch (eg.
> https://github.com/apache/netbeans/pull/1304 ) can be set from one
> place in the build so that we can more easily update each time.
>
> Hopefully anyone outside of this community will only be using the
> voted on releases anyway! :-)
>
> 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: [Lazy Consensus] Feature freeze pass for Java EE and Payara PRs for NB 11.1

[Neil C Smith]

On Sat, 22 Jun 2019 at 17:41, Geertjan Wielenga  wrote:
>
> One thing — how can the betas and final release be distinguished from each
> other? Right now we have beta-1, soon beta-2, eventually final release, but
> one day when someone reports an issue how will we know which one they’re
> using?

The only current way I think is the IDE log itself, where the modules
have the release number and build date?

Ideally the version in the UI would have a -beta suffix, which I don't
think we had with NB 11.0 either.  I could (should) have added this in
all the different places it's mentioned for each beta release.  I'm
putting some thoughts together for NB 11.2 so that the remaining
changes required in the release branch (eg.
https://github.com/apache/netbeans/pull/1304 ) can be set from one
place in the build so that we can more easily update each time.

Hopefully anyone outside of this community will only be using the
voted on releases anyway! :-)

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: [Lazy Consensus] Feature freeze pass for Java EE and Payara PRs for NB 11.1

[Geertjan Wielenga]

One thing — how can the betas and final release be distinguished from each
other? Right now we have beta-1, soon beta-2, eventually final release, but
one day when someone reports an issue how will we know which one they’re
using?

Gj


On Sat, 22 Jun 2019 at 18:38, Geertjan Wielenga  wrote:

> This is great!
>
> Gj
>
> On Sat, 22 Jun 2019 at 18:32, Neil C Smith  wrote:
>
>> Hi All,
>>
>> OK, looks like we have consensus on merging these then.
>>
>> I will merge to master on Monday, unless someone else does before, and
>> then sync everything across to release111 for our next beta.
>>
>> My inclination is to squash and merge these unless anyone has a reason
>> not to before then?
>>
>> Thanks and 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: [Lazy Consensus] Feature freeze pass for Java EE and Payara PRs for NB 11.1

[Geertjan Wielenga]

This is great!

Gj

On Sat, 22 Jun 2019 at 18:32, Neil C Smith  wrote:

> Hi All,
>
> OK, looks like we have consensus on merging these then.
>
> I will merge to master on Monday, unless someone else does before, and
> then sync everything across to release111 for our next beta.
>
> My inclination is to squash and merge these unless anyone has a reason
> not to before then?
>
> Thanks and 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: [Lazy Consensus] Feature freeze pass for Java EE and Payara PRs for NB 11.1

[Neil C Smith]

Hi All,

OK, looks like we have consensus on merging these then.

I will merge to master on Monday, unless someone else does before, and
then sync everything across to release111 for our next beta.

My inclination is to squash and merge these unless anyone has a reason
not to before then?

Thanks and 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: [Lazy Consensus] Feature freeze pass for Java EE and Payara PRs for NB 11.1

[Geertjan Wielenga]

That would be wonderful!

Gj

On Thu, Jun 20, 2019 at 6:05 AM Laszlo Kishalmi 
wrote:

> It won't magically happen on Gradle. The support needs to be patched for
> that. Hopefully not a big deal and might catch the release train...
>
> On 6/19/19 4:50 AM, Geertjan Wielenga wrote:
> > That is great.
> >
> > Is "Java EE 8 Web" correct as a label or should it have "Jakarta" there
> in
> > some way instead?
> >
> > Can you check if Ant-based Java Web projects and Gradle-based Java Web
> > projects (new in 11.1) don't somehow magically inherit this new feature?
> > Probably not, but worth checking.
> >
> > Gj
> >
> >
> > On Wed, Jun 19, 2019 at 1:44 PM Josh Juneau  wrote:
> >
> >> Hi Geertjan,
> >>
> >> You are correct.  The drop-down you've mentioned should now include
> "Java
> >> EE 8 Web" as an option.
> >>
> >> Additionally, if you right-click on an existing Maven Web Project using
> >> Java EE 7 or less, the Project Properties dialog "Run" panel now
> contains
> >> "Java EE 8 Web" as a Java EE Version.
> >>
> >> On Wed, Jun 19, 2019 at 6:36 AM Geertjan Wielenga 
> >> wrote:
> >>
> >>> Great, thanks Josh. Just to understand what this consists of -- when I
> go
> >>> to the New Project dialog and I choose "Java with Maven" and then "Web
> >>> Application" and click Next, and Next again, there is a "Java EE
> Version"
> >>> drop-down, which now has "Java EE 7 Web", "Java EE 6 Web", and "Java EE
> >> 5".
> >>> Does your PR add new content to that drop-down? That's my assumption,
> >>> please just confirm/deny that.
> >>>
> >>> Thanks,
> >>>
> >>> Gj
> >>>
> >>>
> >>> On Wed, Jun 19, 2019 at 1:32 PM Josh Juneau 
> wrote:
> >>>
>  Thanks Neil, for the information.  I created the PR for Java EE 8
>  integration, and those enhancements are specifically geared towards
> >> Maven
>  projects.  The PR includes the following functionality:
> 
>  - Ability to create a new Maven Web Project using Java EE 8 (utilizes
> a
>  Java EE 8 maven archetype)
>  - Ability to change an existing Maven Web Project to use the Java EE 8
>  Platform
>  - Support for GlassFish 5.0.1 and GlassFish 5.1 (enhanced by adding
>  separate identifiers in the sources for GlassFish 5 branch - gfv5ee8,
>  rather than gfv3ee6)
>  - IDE recognizes all Java EE 8 artifact versions, for example: JSF 2.3
>  faces-config, CDI beans.xml 2.0, web.xml 4.0
> 
>  +1 for merging the Payara server and micro tools integration as well.
> 
>  On Wed, Jun 19, 2019 at 3:53 AM Neil C Smith 
>  wrote:
> 
> > Hi All,
> >
> > This email follows some off-list discussion with various people
> > including Geertjan and the relevant contributors.  The release
> > schedule we agreed has an open question about allowing selective
> > feature freeze bypass based on mailing list agreement - hence ...
> >
> > I propose we allow the pending Java EE and Payara PRs to be merged to
> > master for the NB 11.1 release -
> >
> > * Incorporating new files and code modifications for adding Java EE 8
> > support. https://github.com/apache/netbeans/pull/1298
> > * NP-20 Payara Server tools integration in Apache NetBeans IDE.
> > https://github.com/apache/netbeans/pull/1290
> > * NP-20 Payara Micro tools integration in Apache NetBeans IDE.
> > https://github.com/apache/netbeans/pull/1297
> >
> > One of the reasons we discussed having quarterly and non-LTS releases
> > was to get things testing in the wild earlier.  These partly missed
> > the feature freeze because of Travis issues, seem ready to merge, and
> > (hopefully!) have minimal impact on existing features.
> >
> > This is a lazy consensus thread that will be open for 72hrs.  You do
> > not need to +1 (although you're welcome to), but do raise concerns or
> > -1 if need be.  Assuming this goes ahead, we can merge in time to
> >> sync
> > up and include in beta2 next Wednesday.
> >
> > My own lazy consent as release manager is also based on -
> >
> > * All tests are passing before merging (appears now to be the case)
> > * Merging is done before second beta (possibly a good criteria for
> > feature freeze bypass in general?)
> > * The respective contributors can commit to timely fixes in case of
> > issues so that this doesn't cause delay in the NB 11.1 release
> > schedule.
> >
> > Thanks and 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
> >
> >
> >
> > --
>  Josh Juneau
>  juneau...@gmail.com
>  

Re: [Lazy Consensus] Feature freeze pass for Java EE and Payara PRs for NB 11.1

[Laszlo Kishalmi]

It won't magically happen on Gradle. The support needs to be patched for 
that. Hopefully not a big deal and might catch the release train...


On 6/19/19 4:50 AM, Geertjan Wielenga wrote:

That is great.

Is "Java EE 8 Web" correct as a label or should it have "Jakarta" there in
some way instead?

Can you check if Ant-based Java Web projects and Gradle-based Java Web
projects (new in 11.1) don't somehow magically inherit this new feature?
Probably not, but worth checking.

Gj


On Wed, Jun 19, 2019 at 1:44 PM Josh Juneau  wrote:


Hi Geertjan,

You are correct.  The drop-down you've mentioned should now include "Java
EE 8 Web" as an option.

Additionally, if you right-click on an existing Maven Web Project using
Java EE 7 or less, the Project Properties dialog "Run" panel now contains
"Java EE 8 Web" as a Java EE Version.

On Wed, Jun 19, 2019 at 6:36 AM Geertjan Wielenga 
wrote:


Great, thanks Josh. Just to understand what this consists of -- when I go
to the New Project dialog and I choose "Java with Maven" and then "Web
Application" and click Next, and Next again, there is a "Java EE Version"
drop-down, which now has "Java EE 7 Web", "Java EE 6 Web", and "Java EE

5".

Does your PR add new content to that drop-down? That's my assumption,
please just confirm/deny that.

Thanks,

Gj


On Wed, Jun 19, 2019 at 1:32 PM Josh Juneau  wrote:


Thanks Neil, for the information.  I created the PR for Java EE 8
integration, and those enhancements are specifically geared towards

Maven

projects.  The PR includes the following functionality:

- Ability to create a new Maven Web Project using Java EE 8 (utilizes a
Java EE 8 maven archetype)
- Ability to change an existing Maven Web Project to use the Java EE 8
Platform
- Support for GlassFish 5.0.1 and GlassFish 5.1 (enhanced by adding
separate identifiers in the sources for GlassFish 5 branch - gfv5ee8,
rather than gfv3ee6)
- IDE recognizes all Java EE 8 artifact versions, for example: JSF 2.3
faces-config, CDI beans.xml 2.0, web.xml 4.0

+1 for merging the Payara server and micro tools integration as well.

On Wed, Jun 19, 2019 at 3:53 AM Neil C Smith 
wrote:


Hi All,

This email follows some off-list discussion with various people
including Geertjan and the relevant contributors.  The release
schedule we agreed has an open question about allowing selective
feature freeze bypass based on mailing list agreement - hence ...

I propose we allow the pending Java EE and Payara PRs to be merged to
master for the NB 11.1 release -

* Incorporating new files and code modifications for adding Java EE 8
support. https://github.com/apache/netbeans/pull/1298
* NP-20 Payara Server tools integration in Apache NetBeans IDE.
https://github.com/apache/netbeans/pull/1290
* NP-20 Payara Micro tools integration in Apache NetBeans IDE.
https://github.com/apache/netbeans/pull/1297

One of the reasons we discussed having quarterly and non-LTS releases
was to get things testing in the wild earlier.  These partly missed
the feature freeze because of Travis issues, seem ready to merge, and
(hopefully!) have minimal impact on existing features.

This is a lazy consensus thread that will be open for 72hrs.  You do
not need to +1 (although you're welcome to), but do raise concerns or
-1 if need be.  Assuming this goes ahead, we can merge in time to

sync

up and include in beta2 next Wednesday.

My own lazy consent as release manager is also based on -

* All tests are passing before merging (appears now to be the case)
* Merging is done before second beta (possibly a good criteria for
feature freeze bypass in general?)
* The respective contributors can commit to timely fixes in case of
issues so that this doesn't cause delay in the NB 11.1 release
schedule.

Thanks and 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



--

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



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




-
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: [Lazy Consensus] Feature freeze pass for Java EE and Payara PRs for NB 11.1

[Jose Ch]

Hi all,

I vote +1.

Regards,
Jose.

El mié., 19 jun. 2019 a las 7:52, Gaurav Gupta ()
escribió:

> Hi all,
>
> Payara Server integration is based on Apache NetBeans GlassFish modules
> which supports Payara Server v4.1.144 to v5.192 with additional features
> like payara-web.xml DD editor, JDK 11, and connection pool properties, etc.
>
> And Payara Micro integration supports Payara Micro v 4.1.2.174  to v5.192
> and
> enables to create Payara Micro maven application from IDE itself from the
> archetype  payara-micro-maven-archetype
> <
> https://mvnrepository.com/artifact/fish.payara.maven.archetypes/payara-micro-maven-archetype
> >.
> And a developer may start, stop and debug, etc the Payara Micro application
> with Hot reload support.
>
> Both tools are already used by many developers since last 2 years :
> http://plugins.netbeans.org/plugin/72263/payara-server
>
> Although If any issue arises, I will make sure to fix those on priority.
> And *+1* for including both Java EE 8 and Payara tools integration into
> NetBeans IDE 11.1.
>
> Thanks and kind regards,
> Gaurav Gupta
>
> On Wed, Jun 19, 2019 at 5:38 PM Josh Juneau  wrote:
>
> > Hi Geertjan,
> >
> > I think for this release "Java EE 8" is the correct label.  We do not yet
> > have a release of "Jakarta EE 8".  However, I will put in a PR once that
> > has occurred.
> >
> > I will test the Ant and Gradle based Java web projects to see how things
> > work with the Java EE 8 integration.
> >
> > Thanks
> >
> > On Wed, Jun 19, 2019 at 6:50 AM Geertjan Wielenga 
> > wrote:
> >
> > > That is great.
> > >
> > > Is "Java EE 8 Web" correct as a label or should it have "Jakarta" there
> > in
> > > some way instead?
> > >
> > > Can you check if Ant-based Java Web projects and Gradle-based Java Web
> > > projects (new in 11.1) don't somehow magically inherit this new
> feature?
> > > Probably not, but worth checking.
> > >
> > > Gj
> > >
> > >
> > > On Wed, Jun 19, 2019 at 1:44 PM Josh Juneau 
> wrote:
> > >
> > > > Hi Geertjan,
> > > >
> > > > You are correct.  The drop-down you've mentioned should now include
> > "Java
> > > > EE 8 Web" as an option.
> > > >
> > > > Additionally, if you right-click on an existing Maven Web Project
> using
> > > > Java EE 7 or less, the Project Properties dialog "Run" panel now
> > contains
> > > > "Java EE 8 Web" as a Java EE Version.
> > > >
> > > > On Wed, Jun 19, 2019 at 6:36 AM Geertjan Wielenga <
> geert...@apache.org
> > >
> > > > wrote:
> > > >
> > > > > Great, thanks Josh. Just to understand what this consists of --
> when
> > I
> > > go
> > > > > to the New Project dialog and I choose "Java with Maven" and then
> > "Web
> > > > > Application" and click Next, and Next again, there is a "Java EE
> > > Version"
> > > > > drop-down, which now has "Java EE 7 Web", "Java EE 6 Web", and
> "Java
> > EE
> > > > 5".
> > > > >
> > > > > Does your PR add new content to that drop-down? That's my
> assumption,
> > > > > please just confirm/deny that.
> > > > >
> > > > > Thanks,
> > > > >
> > > > > Gj
> > > > >
> > > > >
> > > > > On Wed, Jun 19, 2019 at 1:32 PM Josh Juneau 
> > > wrote:
> > > > >
> > > > > > Thanks Neil, for the information.  I created the PR for Java EE 8
> > > > > > integration, and those enhancements are specifically geared
> towards
> > > > Maven
> > > > > > projects.  The PR includes the following functionality:
> > > > > >
> > > > > > - Ability to create a new Maven Web Project using Java EE 8
> > > (utilizes a
> > > > > > Java EE 8 maven archetype)
> > > > > > - Ability to change an existing Maven Web Project to use the Java
> > EE
> > > 8
> > > > > > Platform
> > > > > > - Support for GlassFish 5.0.1 and GlassFish 5.1 (enhanced by
> adding
> > > > > > separate identifiers in the sources for GlassFish 5 branch -
> > gfv5ee8,
> > > > > > rather than gfv3ee6)
> > > > > > - IDE recognizes all Java EE 8 artifact versions, for example:
> JSF
> > > 2.3
> > > > > > faces-config, CDI beans.xml 2.0, web.xml 4.0
> > > > > >
> > > > > > +1 for merging the Payara server and micro tools integration as
> > well.
> > > > > >
> > > > > > On Wed, Jun 19, 2019 at 3:53 AM Neil C Smith <
> > neilcsm...@apache.org>
> > > > > > wrote:
> > > > > >
> > > > > > > Hi All,
> > > > > > >
> > > > > > > This email follows some off-list discussion with various people
> > > > > > > including Geertjan and the relevant contributors.  The release
> > > > > > > schedule we agreed has an open question about allowing
> selective
> > > > > > > feature freeze bypass based on mailing list agreement - hence
> ...
> > > > > > >
> > > > > > > I propose we allow the pending Java EE and Payara PRs to be
> > merged
> > > to
> > > > > > > master for the NB 11.1 release -
> > > > > > >
> > > > > > > * Incorporating new files and code modifications for adding
> Java
> > > EE 8
> > > > > > > support. https://github.com/apache/netbeans/pull/1298
> > > > > > > * NP-20 Payara Server tools integration in Apache NetBeans IDE.
> > > > > > > 

Re: [Lazy Consensus] Feature freeze pass for Java EE and Payara PRs for NB 11.1

[Gaurav Gupta]

Hi all,

Payara Server integration is based on Apache NetBeans GlassFish modules
which supports Payara Server v4.1.144 to v5.192 with additional features
like payara-web.xml DD editor, JDK 11, and connection pool properties, etc.

And Payara Micro integration supports Payara Micro v 4.1.2.174  to v5.192 and
enables to create Payara Micro maven application from IDE itself from the
archetype  payara-micro-maven-archetype
.
And a developer may start, stop and debug, etc the Payara Micro application
with Hot reload support.

Both tools are already used by many developers since last 2 years :
http://plugins.netbeans.org/plugin/72263/payara-server

Although If any issue arises, I will make sure to fix those on priority.
And *+1* for including both Java EE 8 and Payara tools integration into
NetBeans IDE 11.1.

Thanks and kind regards,
Gaurav Gupta

On Wed, Jun 19, 2019 at 5:38 PM Josh Juneau  wrote:

> Hi Geertjan,
>
> I think for this release "Java EE 8" is the correct label.  We do not yet
> have a release of "Jakarta EE 8".  However, I will put in a PR once that
> has occurred.
>
> I will test the Ant and Gradle based Java web projects to see how things
> work with the Java EE 8 integration.
>
> Thanks
>
> On Wed, Jun 19, 2019 at 6:50 AM Geertjan Wielenga 
> wrote:
>
> > That is great.
> >
> > Is "Java EE 8 Web" correct as a label or should it have "Jakarta" there
> in
> > some way instead?
> >
> > Can you check if Ant-based Java Web projects and Gradle-based Java Web
> > projects (new in 11.1) don't somehow magically inherit this new feature?
> > Probably not, but worth checking.
> >
> > Gj
> >
> >
> > On Wed, Jun 19, 2019 at 1:44 PM Josh Juneau  wrote:
> >
> > > Hi Geertjan,
> > >
> > > You are correct.  The drop-down you've mentioned should now include
> "Java
> > > EE 8 Web" as an option.
> > >
> > > Additionally, if you right-click on an existing Maven Web Project using
> > > Java EE 7 or less, the Project Properties dialog "Run" panel now
> contains
> > > "Java EE 8 Web" as a Java EE Version.
> > >
> > > On Wed, Jun 19, 2019 at 6:36 AM Geertjan Wielenga  >
> > > wrote:
> > >
> > > > Great, thanks Josh. Just to understand what this consists of -- when
> I
> > go
> > > > to the New Project dialog and I choose "Java with Maven" and then
> "Web
> > > > Application" and click Next, and Next again, there is a "Java EE
> > Version"
> > > > drop-down, which now has "Java EE 7 Web", "Java EE 6 Web", and "Java
> EE
> > > 5".
> > > >
> > > > Does your PR add new content to that drop-down? That's my assumption,
> > > > please just confirm/deny that.
> > > >
> > > > Thanks,
> > > >
> > > > Gj
> > > >
> > > >
> > > > On Wed, Jun 19, 2019 at 1:32 PM Josh Juneau 
> > wrote:
> > > >
> > > > > Thanks Neil, for the information.  I created the PR for Java EE 8
> > > > > integration, and those enhancements are specifically geared towards
> > > Maven
> > > > > projects.  The PR includes the following functionality:
> > > > >
> > > > > - Ability to create a new Maven Web Project using Java EE 8
> > (utilizes a
> > > > > Java EE 8 maven archetype)
> > > > > - Ability to change an existing Maven Web Project to use the Java
> EE
> > 8
> > > > > Platform
> > > > > - Support for GlassFish 5.0.1 and GlassFish 5.1 (enhanced by adding
> > > > > separate identifiers in the sources for GlassFish 5 branch -
> gfv5ee8,
> > > > > rather than gfv3ee6)
> > > > > - IDE recognizes all Java EE 8 artifact versions, for example: JSF
> > 2.3
> > > > > faces-config, CDI beans.xml 2.0, web.xml 4.0
> > > > >
> > > > > +1 for merging the Payara server and micro tools integration as
> well.
> > > > >
> > > > > On Wed, Jun 19, 2019 at 3:53 AM Neil C Smith <
> neilcsm...@apache.org>
> > > > > wrote:
> > > > >
> > > > > > Hi All,
> > > > > >
> > > > > > This email follows some off-list discussion with various people
> > > > > > including Geertjan and the relevant contributors.  The release
> > > > > > schedule we agreed has an open question about allowing selective
> > > > > > feature freeze bypass based on mailing list agreement - hence ...
> > > > > >
> > > > > > I propose we allow the pending Java EE and Payara PRs to be
> merged
> > to
> > > > > > master for the NB 11.1 release -
> > > > > >
> > > > > > * Incorporating new files and code modifications for adding Java
> > EE 8
> > > > > > support. https://github.com/apache/netbeans/pull/1298
> > > > > > * NP-20 Payara Server tools integration in Apache NetBeans IDE.
> > > > > > https://github.com/apache/netbeans/pull/1290
> > > > > > * NP-20 Payara Micro tools integration in Apache NetBeans IDE.
> > > > > > https://github.com/apache/netbeans/pull/1297
> > > > > >
> > > > > > One of the reasons we discussed having quarterly and non-LTS
> > releases
> > > > > > was to get things testing in the wild earlier.  These partly
> missed
> > > > > > the feature freeze because of Travis issues, seem ready to merge,
> > 

Re: [Lazy Consensus] Feature freeze pass for Java EE and Payara PRs for NB 11.1

[Josh Juneau]

Hi Geertjan,

I think for this release "Java EE 8" is the correct label.  We do not yet
have a release of "Jakarta EE 8".  However, I will put in a PR once that
has occurred.

I will test the Ant and Gradle based Java web projects to see how things
work with the Java EE 8 integration.

Thanks

On Wed, Jun 19, 2019 at 6:50 AM Geertjan Wielenga 
wrote:

> That is great.
>
> Is "Java EE 8 Web" correct as a label or should it have "Jakarta" there in
> some way instead?
>
> Can you check if Ant-based Java Web projects and Gradle-based Java Web
> projects (new in 11.1) don't somehow magically inherit this new feature?
> Probably not, but worth checking.
>
> Gj
>
>
> On Wed, Jun 19, 2019 at 1:44 PM Josh Juneau  wrote:
>
> > Hi Geertjan,
> >
> > You are correct.  The drop-down you've mentioned should now include "Java
> > EE 8 Web" as an option.
> >
> > Additionally, if you right-click on an existing Maven Web Project using
> > Java EE 7 or less, the Project Properties dialog "Run" panel now contains
> > "Java EE 8 Web" as a Java EE Version.
> >
> > On Wed, Jun 19, 2019 at 6:36 AM Geertjan Wielenga 
> > wrote:
> >
> > > Great, thanks Josh. Just to understand what this consists of -- when I
> go
> > > to the New Project dialog and I choose "Java with Maven" and then "Web
> > > Application" and click Next, and Next again, there is a "Java EE
> Version"
> > > drop-down, which now has "Java EE 7 Web", "Java EE 6 Web", and "Java EE
> > 5".
> > >
> > > Does your PR add new content to that drop-down? That's my assumption,
> > > please just confirm/deny that.
> > >
> > > Thanks,
> > >
> > > Gj
> > >
> > >
> > > On Wed, Jun 19, 2019 at 1:32 PM Josh Juneau 
> wrote:
> > >
> > > > Thanks Neil, for the information.  I created the PR for Java EE 8
> > > > integration, and those enhancements are specifically geared towards
> > Maven
> > > > projects.  The PR includes the following functionality:
> > > >
> > > > - Ability to create a new Maven Web Project using Java EE 8
> (utilizes a
> > > > Java EE 8 maven archetype)
> > > > - Ability to change an existing Maven Web Project to use the Java EE
> 8
> > > > Platform
> > > > - Support for GlassFish 5.0.1 and GlassFish 5.1 (enhanced by adding
> > > > separate identifiers in the sources for GlassFish 5 branch - gfv5ee8,
> > > > rather than gfv3ee6)
> > > > - IDE recognizes all Java EE 8 artifact versions, for example: JSF
> 2.3
> > > > faces-config, CDI beans.xml 2.0, web.xml 4.0
> > > >
> > > > +1 for merging the Payara server and micro tools integration as well.
> > > >
> > > > On Wed, Jun 19, 2019 at 3:53 AM Neil C Smith 
> > > > wrote:
> > > >
> > > > > Hi All,
> > > > >
> > > > > This email follows some off-list discussion with various people
> > > > > including Geertjan and the relevant contributors.  The release
> > > > > schedule we agreed has an open question about allowing selective
> > > > > feature freeze bypass based on mailing list agreement - hence ...
> > > > >
> > > > > I propose we allow the pending Java EE and Payara PRs to be merged
> to
> > > > > master for the NB 11.1 release -
> > > > >
> > > > > * Incorporating new files and code modifications for adding Java
> EE 8
> > > > > support. https://github.com/apache/netbeans/pull/1298
> > > > > * NP-20 Payara Server tools integration in Apache NetBeans IDE.
> > > > > https://github.com/apache/netbeans/pull/1290
> > > > > * NP-20 Payara Micro tools integration in Apache NetBeans IDE.
> > > > > https://github.com/apache/netbeans/pull/1297
> > > > >
> > > > > One of the reasons we discussed having quarterly and non-LTS
> releases
> > > > > was to get things testing in the wild earlier.  These partly missed
> > > > > the feature freeze because of Travis issues, seem ready to merge,
> and
> > > > > (hopefully!) have minimal impact on existing features.
> > > > >
> > > > > This is a lazy consensus thread that will be open for 72hrs.  You
> do
> > > > > not need to +1 (although you're welcome to), but do raise concerns
> or
> > > > > -1 if need be.  Assuming this goes ahead, we can merge in time to
> > sync
> > > > > up and include in beta2 next Wednesday.
> > > > >
> > > > > My own lazy consent as release manager is also based on -
> > > > >
> > > > > * All tests are passing before merging (appears now to be the case)
> > > > > * Merging is done before second beta (possibly a good criteria for
> > > > > feature freeze bypass in general?)
> > > > > * The respective contributors can commit to timely fixes in case of
> > > > > issues so that this doesn't cause delay in the NB 11.1 release
> > > > > schedule.
> > > > >
> > > > > Thanks and 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:
> > > > > 

Re: [Lazy Consensus] Feature freeze pass for Java EE and Payara PRs for NB 11.1

[Josh Juneau]

Hi Geertjan,

You are correct.  The drop-down you've mentioned should now include "Java
EE 8 Web" as an option.

Additionally, if you right-click on an existing Maven Web Project using
Java EE 7 or less, the Project Properties dialog "Run" panel now contains
"Java EE 8 Web" as a Java EE Version.

On Wed, Jun 19, 2019 at 6:36 AM Geertjan Wielenga 
wrote:

> Great, thanks Josh. Just to understand what this consists of -- when I go
> to the New Project dialog and I choose "Java with Maven" and then "Web
> Application" and click Next, and Next again, there is a "Java EE Version"
> drop-down, which now has "Java EE 7 Web", "Java EE 6 Web", and "Java EE 5".
>
> Does your PR add new content to that drop-down? That's my assumption,
> please just confirm/deny that.
>
> Thanks,
>
> Gj
>
>
> On Wed, Jun 19, 2019 at 1:32 PM Josh Juneau  wrote:
>
> > Thanks Neil, for the information.  I created the PR for Java EE 8
> > integration, and those enhancements are specifically geared towards Maven
> > projects.  The PR includes the following functionality:
> >
> > - Ability to create a new Maven Web Project using Java EE 8 (utilizes a
> > Java EE 8 maven archetype)
> > - Ability to change an existing Maven Web Project to use the Java EE 8
> > Platform
> > - Support for GlassFish 5.0.1 and GlassFish 5.1 (enhanced by adding
> > separate identifiers in the sources for GlassFish 5 branch - gfv5ee8,
> > rather than gfv3ee6)
> > - IDE recognizes all Java EE 8 artifact versions, for example: JSF 2.3
> > faces-config, CDI beans.xml 2.0, web.xml 4.0
> >
> > +1 for merging the Payara server and micro tools integration as well.
> >
> > On Wed, Jun 19, 2019 at 3:53 AM Neil C Smith 
> > wrote:
> >
> > > Hi All,
> > >
> > > This email follows some off-list discussion with various people
> > > including Geertjan and the relevant contributors.  The release
> > > schedule we agreed has an open question about allowing selective
> > > feature freeze bypass based on mailing list agreement - hence ...
> > >
> > > I propose we allow the pending Java EE and Payara PRs to be merged to
> > > master for the NB 11.1 release -
> > >
> > > * Incorporating new files and code modifications for adding Java EE 8
> > > support. https://github.com/apache/netbeans/pull/1298
> > > * NP-20 Payara Server tools integration in Apache NetBeans IDE.
> > > https://github.com/apache/netbeans/pull/1290
> > > * NP-20 Payara Micro tools integration in Apache NetBeans IDE.
> > > https://github.com/apache/netbeans/pull/1297
> > >
> > > One of the reasons we discussed having quarterly and non-LTS releases
> > > was to get things testing in the wild earlier.  These partly missed
> > > the feature freeze because of Travis issues, seem ready to merge, and
> > > (hopefully!) have minimal impact on existing features.
> > >
> > > This is a lazy consensus thread that will be open for 72hrs.  You do
> > > not need to +1 (although you're welcome to), but do raise concerns or
> > > -1 if need be.  Assuming this goes ahead, we can merge in time to sync
> > > up and include in beta2 next Wednesday.
> > >
> > > My own lazy consent as release manager is also based on -
> > >
> > > * All tests are passing before merging (appears now to be the case)
> > > * Merging is done before second beta (possibly a good criteria for
> > > feature freeze bypass in general?)
> > > * The respective contributors can commit to timely fixes in case of
> > > issues so that this doesn't cause delay in the NB 11.1 release
> > > schedule.
> > >
> > > Thanks and 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
> > >
> > >
> > >
> > > --
> > Josh Juneau
> > juneau...@gmail.com
> > http://jj-blogger.blogspot.com
> > https://www.apress.com/us/search?query=Juneau
> > 
> >
>
-- 
Josh Juneau
juneau...@gmail.com
http://jj-blogger.blogspot.com
https://www.apress.com/us/search?query=Juneau

Re: [Lazy Consensus] Feature freeze pass for Java EE and Payara PRs for NB 11.1

[Geertjan Wielenga]

Great, thanks Josh. Just to understand what this consists of -- when I go
to the New Project dialog and I choose "Java with Maven" and then "Web
Application" and click Next, and Next again, there is a "Java EE Version"
drop-down, which now has "Java EE 7 Web", "Java EE 6 Web", and "Java EE 5".

Does your PR add new content to that drop-down? That's my assumption,
please just confirm/deny that.

Thanks,

Gj


On Wed, Jun 19, 2019 at 1:32 PM Josh Juneau  wrote:

> Thanks Neil, for the information.  I created the PR for Java EE 8
> integration, and those enhancements are specifically geared towards Maven
> projects.  The PR includes the following functionality:
>
> - Ability to create a new Maven Web Project using Java EE 8 (utilizes a
> Java EE 8 maven archetype)
> - Ability to change an existing Maven Web Project to use the Java EE 8
> Platform
> - Support for GlassFish 5.0.1 and GlassFish 5.1 (enhanced by adding
> separate identifiers in the sources for GlassFish 5 branch - gfv5ee8,
> rather than gfv3ee6)
> - IDE recognizes all Java EE 8 artifact versions, for example: JSF 2.3
> faces-config, CDI beans.xml 2.0, web.xml 4.0
>
> +1 for merging the Payara server and micro tools integration as well.
>
> On Wed, Jun 19, 2019 at 3:53 AM Neil C Smith 
> wrote:
>
> > Hi All,
> >
> > This email follows some off-list discussion with various people
> > including Geertjan and the relevant contributors.  The release
> > schedule we agreed has an open question about allowing selective
> > feature freeze bypass based on mailing list agreement - hence ...
> >
> > I propose we allow the pending Java EE and Payara PRs to be merged to
> > master for the NB 11.1 release -
> >
> > * Incorporating new files and code modifications for adding Java EE 8
> > support. https://github.com/apache/netbeans/pull/1298
> > * NP-20 Payara Server tools integration in Apache NetBeans IDE.
> > https://github.com/apache/netbeans/pull/1290
> > * NP-20 Payara Micro tools integration in Apache NetBeans IDE.
> > https://github.com/apache/netbeans/pull/1297
> >
> > One of the reasons we discussed having quarterly and non-LTS releases
> > was to get things testing in the wild earlier.  These partly missed
> > the feature freeze because of Travis issues, seem ready to merge, and
> > (hopefully!) have minimal impact on existing features.
> >
> > This is a lazy consensus thread that will be open for 72hrs.  You do
> > not need to +1 (although you're welcome to), but do raise concerns or
> > -1 if need be.  Assuming this goes ahead, we can merge in time to sync
> > up and include in beta2 next Wednesday.
> >
> > My own lazy consent as release manager is also based on -
> >
> > * All tests are passing before merging (appears now to be the case)
> > * Merging is done before second beta (possibly a good criteria for
> > feature freeze bypass in general?)
> > * The respective contributors can commit to timely fixes in case of
> > issues so that this doesn't cause delay in the NB 11.1 release
> > schedule.
> >
> > Thanks and 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
> >
> >
> >
> > --
> Josh Juneau
> juneau...@gmail.com
> http://jj-blogger.blogspot.com
> https://www.apress.com/us/search?query=Juneau
> 
>

Re: [Lazy Consensus] Feature freeze pass for Java EE and Payara PRs for NB 11.1

[Josh Juneau]

Thanks Neil, for the information.  I created the PR for Java EE 8
integration, and those enhancements are specifically geared towards Maven
projects.  The PR includes the following functionality:

- Ability to create a new Maven Web Project using Java EE 8 (utilizes a
Java EE 8 maven archetype)
- Ability to change an existing Maven Web Project to use the Java EE 8
Platform
- Support for GlassFish 5.0.1 and GlassFish 5.1 (enhanced by adding
separate identifiers in the sources for GlassFish 5 branch - gfv5ee8,
rather than gfv3ee6)
- IDE recognizes all Java EE 8 artifact versions, for example: JSF 2.3
faces-config, CDI beans.xml 2.0, web.xml 4.0

+1 for merging the Payara server and micro tools integration as well.

On Wed, Jun 19, 2019 at 3:53 AM Neil C Smith  wrote:

> Hi All,
>
> This email follows some off-list discussion with various people
> including Geertjan and the relevant contributors.  The release
> schedule we agreed has an open question about allowing selective
> feature freeze bypass based on mailing list agreement - hence ...
>
> I propose we allow the pending Java EE and Payara PRs to be merged to
> master for the NB 11.1 release -
>
> * Incorporating new files and code modifications for adding Java EE 8
> support. https://github.com/apache/netbeans/pull/1298
> * NP-20 Payara Server tools integration in Apache NetBeans IDE.
> https://github.com/apache/netbeans/pull/1290
> * NP-20 Payara Micro tools integration in Apache NetBeans IDE.
> https://github.com/apache/netbeans/pull/1297
>
> One of the reasons we discussed having quarterly and non-LTS releases
> was to get things testing in the wild earlier.  These partly missed
> the feature freeze because of Travis issues, seem ready to merge, and
> (hopefully!) have minimal impact on existing features.
>
> This is a lazy consensus thread that will be open for 72hrs.  You do
> not need to +1 (although you're welcome to), but do raise concerns or
> -1 if need be.  Assuming this goes ahead, we can merge in time to sync
> up and include in beta2 next Wednesday.
>
> My own lazy consent as release manager is also based on -
>
> * All tests are passing before merging (appears now to be the case)
> * Merging is done before second beta (possibly a good criteria for
> feature freeze bypass in general?)
> * The respective contributors can commit to timely fixes in case of
> issues so that this doesn't cause delay in the NB 11.1 release
> schedule.
>
> Thanks and 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
>
>
>
> --
Josh Juneau
juneau...@gmail.com
http://jj-blogger.blogspot.com
https://www.apress.com/us/search?query=Juneau