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, G
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 P
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 Smi
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,
>
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?
T
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:
> Thi
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
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 a
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.
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?
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,
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 v
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 W
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 We
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.
O
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".
Doe
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)
- A
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
18 matches
Mail list logo
