Add this URL to your Eclipse Installation to reach this solution's update site.
For a long time Payara, a derivative of GlassFish, could be used in Eclipse using the Oracle GlassFish Tools. With the release of Payara 5, a few problems prevented the plug-in from recognizing Payara 5, meaning Payara 5 couldn’t really be used in Eclipse. A new set of tools again makes it possible to use Payara 5 with Eclipse, along with other improvements.
Unsuccessful Installs in the last 7 Days: 13
By adding the following code below to your website you will be able to add an install button for Payara Tools.HTML Code:
Submitted by Alex Popa-Tesileanu on Tue, 2020-01-14 03:32
First, great work!
I tried to use it with eclipse 2019-12, running on jdk11. Server is Payara 194. The problem is Eclipse cannot connect to the server. In fact it start the server but in Eclipse it gets stuck on 52% until timeout exceeded with the message: “Unable to start server on time. Timeout while waiting for Payara to start.”
After e few tries, I succeeded to start and connect to the the server running on jdk11, but only when I switched Eclipse to run on JDK 8.
Any idea why it doesn’t work with both Eclipse and Payara on JDK11?
Submitted by Michael Hutton on Thu, 2019-07-18 14:34
When trying to set up a new runtime environment with Payara 188.8.131.52 and JDK1.8.0_202, the dialog displays "Java 7 or higher is required" and refuses to continue. This happens with a number of Java 8 versions and for both JDK and JRE. The problem started with the latest refresh of the Payara tools.
This makes the tools useless for Payara 4 at this time. Does anyone know of a work around?
Submitted by Carl Bradwell on Thu, 2019-06-06 09:30
I've recently migrated to using JDK 11 rather than 1.8.
When I try to add a Payara Server in Eclipse, and give it the path to JDK 11, it displays error message "Java Development Kit (JDK) is required rather than a JRE"
Any idea how to get around this?
Submitted by Arjan Tijms on Tue, 2019-02-05 09:07
An alpha version of the plug-in is available at
This contains several fixes and new features, but is for use on ones own risk still (don't install on production systems)
Submitted by Thomas Kernstock on Thu, 2018-12-20 20:37
I tried to install Payara Tools with the marketplace install on a complete fresh installation og Photon 2018/12 and got this Errormessage:
Cannot complete the install because one or more required items could not be found.
Software being installed: Payara Tools 184.108.40.206804032346 (org.eclipse.payara.tools.feature.group 220.127.116.11804032346)
Missing requirement: Payara Tools 18.104.22.168804032346 (org.eclipse.payara.tools.feature.group 22.214.171.124804032346) requires 'org.eclipse.equinox.p2.iu; org.eclipse.sapphire.modeling.xml.feature.group [9.1.0,10.0.0)' but it could not be found
please advise or fix
Submitted by Thomas Kernstock on Thu, 2018-12-27 13:47
Solved. I manged to install the missing plugins manually.
Submitted by Stephen Ferjanec on Sat, 2019-01-05 17:56
How did you install the missing plugins manually? I have the exact same problem on Eclipse version 4.10.0. I tried adding the direct URL to the tools to the install new software section and that did not work at all.
Thanks for any help.
Submitted by Kenji HASUNUMA on Wed, 2019-01-09 10:06
The current version of Payara Tools depends on Eclipse Sapphire 9.x, however it's not included Eclipse 4.9 and 4.10. Add https://download.eclipse.org/sapphire/9.1.1/repository/ to the new software section and it would work.
Submitted by A Reed on Tue, 2018-12-18 11:58
I'm trying to install the eclipse Payara plugin in Eclipse 4.9 (sept 2018) and I get the following error:
Unable to read repository at https: //raw.githubusercontent.com/payara/Payara_PatchedProjects/eclipse/payaratools/oxygen/development/content.xml.
sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
Can somebody please adjust the path to the plugin?
Submitted by Marc Segond on Thu, 2019-04-25 13:43
Same here...any way to fix this?
Submitted by Marc Segond on Thu, 2019-04-25 13:42
Exactly the same problem here...is it a problem of the plugin, or something I am doing wrong? I have reinstalled Eclipse 2019-03 20 times, all fresh installs, and tried with Java 1.8.0_181, 1.8.0_212 and OpenJDK11...
Always this very same error...
Submitted by Arjan Tijms on Fri, 2019-04-26 11:46
>PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
This bizarre error message typicaly means that the keystore related to your JDK can't be found or that it doesn't contain the correct certifiate. In other words, it's an SSL handshake issue. The plug-in itself should be at the right path.
It's hard to say how to resolve this, but I'd check with the JDK on which Eclipse itself is being running, and look at the certificates of that store.
Submitted by Marc Segond on Thu, 2019-05-02 04:28
Is this normal than pasting this in a browser it gives a 404 error: h t t p s : / / raw.githubusercontent.com/payara/Payara_PatchedProjects/eclipse/payaratools/oxygen/development/content.xml ??
Submitted by Arjan Tijms on Fri, 2019-05-03 10:04
Yes, that's normal. There is no such file. See http s ://github. com/payara/Payara_PatchedProjects/tree/eclipse/payaratools/oxygen/development
Submitted by Marc Segond on Tue, 2019-05-07 03:52
That's my point ;) Then why is eclipse trying to read this non existing file to install the plugin?
Is it something that I do not understand?
Submitted by Marc Segond on Thu, 2019-05-02 04:15
I tried 2 Java versions: Java1.8.0_191, Java1.8.0_212 and OpenJDK11. The 3 give the same error. I really don't understand what happens. Where can I download the certificate to try to add it to the cacerts?
This happens on my professional laptop. The same installation of Eclipse works perfectly fine on my personal laptop...not sure about the difference. Both run Windows10.
A co-located event with KubeCon + CloudNativeCon EU on March 30, 2020