Wow, what a team!
Gj
On Sunday, March 3, 2019, Gaurav Gupta wrote:
> I fixed a similar issue in Payara plugin, I will check make the PR for
> GlassFish modules too.
>
> https://github.com/payara/ecosystem-netbeans-plugin/pull/17/files
>
> Thanks and kind regards,
> Gaurav Gupta
>
>
>
>
>
>
>
I fixed a similar issue in Payara plugin, I will check make the PR for
GlassFish modules too.
https://github.com/payara/ecosystem-netbeans-plugin/pull/17/files
Thanks and kind regards,
Gaurav Gupta
On Sun, Mar 3, 2019 at 8:17 AM Josh Juneau wrote:
> Nice work Pete! Thanks for confirming
Nice work Pete! Thanks for confirming and digging into the code looking for
the fix.
Let me know if you need me to try and help with anything.
Best
Josh Juneau
juneau...@gmail.com
http://jj-blogger.blogspot.com
https://www.apress.com/index.php/author/author/view/id/1866
> On Mar 2, 2019, at
I was able to replicate - but in my case, after starting GF from withing
NB, running netstat -tnlp at the console showed the GlassFish had started
listening on 8080 (and navigating to http://localhost:8080 proved it), but
NB wasn't opening the GF log window, or recognizing that it had started.
Sure thing Geertjan, I think your solution is perfect for this release.
Essentially, if you are developing Java EE applications then run NetBeans under
the same version of the JDK that you are using to run the server. At this
point it is JDK 8. Hopefully within the year we will see some
Also, a simple solution may be to explicitly tell users to run Apache
NetBeans 11 on JDK 8 if they want to make use of GlassFish, since GlassFish
itself runs on JDK 8 only and that if, as has been pointed out, code that
is explicit to JDK 9 or later is run on GlassFish, it will fail. So best to
Again, please, do this: fresh user dir, fresh everything, start GlassFish
from inside NetBeans, close NetBeans, restart NetBeans, refresh the
GlassFish node.
Just confirm the above works so that we can go from there -- i.e., don't
start GlassFish anywhere other than in NetBeans, then restart,
I've confirmed that the same issue occurs under vc1, unfortunately. I had not
fully tested vc1 under JDK 9/10/11/12, only used running under JDK 8.
Running NetBeans 11 vc1/vc2 Under JDK 9/10/11/12: If you start up GlassFish
and then open up the IDE, the controls for starting/stopping the
Try to start it, close the IDE, then refresh the node after restart.
Yes, not ideal, but please try to see if that works so we can figure it out
further from there and so we can confirm that it actually can start, though
after the above steps.
Gj
On Sat, Mar 2, 2019 at 7:46 PM Jose Ch wrote:
To be clear I used JDK 8 for the Platform option for Glassfish and Payara
and JDK 11/12/13 for Netbeans and never successfully started them. I will
try many combinations with different vendors (but always use JDK 8 for the
app servers) as soon as I get the chance this weekend.
José.
On Sat, Mar
GlassFish does not support anything beyond JDK 8.
Gj
On Saturday, March 2, 2019, Jose Ch wrote:
> The same happens to me in Fedora 29, but I never tried with JDK 8 always
> with JDK 11/12/13 and never successfully start payara or glassfish within
> the IDE.
>
> On Sat, Mar 2, 2019, 10:04
The same happens to me in Fedora 29, but I never tried with JDK 8 always
with JDK 11/12/13 and never successfully start payara or glassfish within
the IDE.
On Sat, Mar 2, 2019, 10:04 Geertjan Wielenga
wrote:
> I’ve started GlassFish v5 and v5.1 from the Servers node with Apache
> NetBeans 11
I’ve started GlassFish v5 and v5.1 from the Servers node with Apache
NetBeans 11 vc1 without a problem several times. To check whether this is
specific to vc2 or specific to you, can you try with vc1 (instead of vc2)?
Gj
On Saturday, March 2, 2019, Josh Juneau wrote:
> Thanks Pete, I will put
Thanks Pete, I will put something in the JIRA. Just wanted to confirm that
someone else was seeing the same issue first. I'm running on Mac OS X
10.13.6.
On Sat, Mar 2, 2019 at 9:46 AM Pete Whelpton wrote:
> Doh! I did notice whilst I was poking around in the GlassFish code that the
> base64
Doh! I did notice whilst I was poking around in the GlassFish code that the
base64 package that is removed from JDK10 onwards was being used somewhere
in authentication, so hopefully it is something as simple as that.
If not, it might be beyond my abilities, but if you create an issue in the
Hi Pete,
Thanks for the write-up. I have verified, and I already have JDK8
registered as an available platform. When I right-click on GlassFish ->
Properties, the JDK 8 platform is already selected under the Java tab.
I've verified on vc2 that JDK 10, JDK 11, and JDK 12 seem to be exhibiting
Hi Josh,
Apologies if this is stating the obvious and you have already tried it -
away from computer at the moment and can't test myself, but have you tried:
* Launching NB under JDK11
* Right click GlassFish instance -> Properties
* Java tab -> Manage platforms button
* Add JDK8
* Select JDK8
I have noticed that using vc2, and running NetBeans on JDK 11 or 12, my
registered GlassFish server will not start from within the IDE. I am unable to
manage GlassFish (or Payara) from within the IDE unless I start NetBeans under
JDK 8. If I start up NetBeans under JDK 8 things seem to work
18 matches
Mail list logo
