Liberty Tools

Add this URL to your Eclipse Installation to reach this solution's update site.

2024-03 (4.31)

2023-12 (4.30)

2023-09 (4.29)

2023-06 (4.28)

2023-03 (4.27)

2022-12 (4.26), 2022-09 (4.25)

2022-09 (4.25)

2022-09 (4.25)

Learn more...
Solution Description

Liberty Tools for Eclipse IDE offers features for developing cloud-native Java applications with Open Liberty and WebSphere Liberty. Iterate fast with Liberty dev mode, code with assistance for MicroProfile and Jakarta EE APIs, and easily edit Liberty configuration files. For more information, see the project documentation in GitHub or check out a deep dive of Liberty Tools

Categories: Application Server, IDE, Tools

Additional Details

Eclipse Versions: 2024-03 (4.31), 2023-12 (4.30), 2023-09 (4.29), 2023-06 (4.28), 2023-03 (4.27), 2022-12 (4.26), 2022-09 (4.25)

Platform Support: Windows, Mac, Linux/GTK

Organization Name: IBM

Development Status: Production/Stable

Date Created: Tuesday, December 6, 2022 - 13:05

License: EPL 2.0

Date Updated: Friday, June 28, 2024 - 15:02

Submitted by: Adam Wisniewski

Date Ranking Installs Clickthroughs
July 2024 99/651 224 11
June 2024 108/681 278 21
May 2024 97/682 381 152
April 2024 91/687 417 19
March 2024 106/694 366 15
February 2024 89/687 387 12
January 2024 98/691 391 14
December 2023 107/671 318 24
November 2023 105/686 396 26
October 2023 80/673 528 21
September 2023 103/663 391 30
August 2023 104/673 353 26
View Data for all Listings

Marketplace Drag to Install Button

By adding the following code below to your website you will be able to add an install button for Liberty Tools.

HTML Code:

Markdown Syntax:


Drag to your running Eclipse* workspace. *Requires Eclipse Marketplace Client

Reviews Add new review

Cannot complete the install because one or more required items could not be found.
 Software being installed: Liberty Tools (
 Missing requirement: JDT Language Server - Core ( requires 'osgi.bundle; org.eclipse.lsp4j [,0.23.0)' but it could not be found
 Cannot satisfy dependency:
   From: Liberty Tools (
   To: org.eclipse.equinox.p2.iu; [,]
 Cannot satisfy dependency:
   From: Liberty Tools Support for Language Servers (
   To: osgi.bundle; 0.0.0

In reply to by Devanathan Vasu

Yes, you can still get some value from Liberty Tools Eclipse with a project using an Ant build.  You can get assistance with Liberty server config (server.xml,, server.env).   You can also get some assistance for the Jakarta EE 9 APIs via the language server (though you shouldn't expect this assistance to be Spring-"aware").

You would not, however, be able to use the Liberty Dashboard view in Liberty Tools to view and run your app, since these leverage the Liberty Maven/Gradle plugins.   


I'll also mention that we don't test for compatibility or coexistence with any Spring Eclipse tooling (e.g. STS), another thing you might be asking about.  

In reply to by chua chua

Good question.  

It's true that most of our tooling and documentation centers around a single application per server, and so, though we don't prevent you from using more than one app per server, the approach here isn't obvious.

So, it is possible to use the code assistance outside of a single, tooling-executable project.  E.g you can use the server.xml code assistance to get completions for adding elements/attributes and Jakarta API quick fixes even without the ability to use a tooling-integrated deployment and server execution.  True, this is less than a first-class experience but can still be helpful.


Another path you could take, assuming you're using Maven, requires a bit of setup work on your part.  

You could create a multi-module project with a 'pom' module which will hold your server.xml configuration (and integration tests) and declare dependencies on your other modules. See here,… for some more details.  

Please feel free to let us know your thoughts and feedback in this area.

Scott Kurz

Thank you for your updating plugin.

I am creating a dynamic web project which is going to use jakartaee v9
Set target runtime to "Liberty Runtime"
I want to specify 5.0 for "dynamic web module version",
But I cannot select anything higher than 4.0.

We guess that the cause is as follows.
There is no description of version 5.0 or higher in the following places.

  <extension point="org.eclipse.wst.common.project.facet.core.runtimes">
    <runtime-component-type id=""/>
    <runtime-component-version type="" version="4.0"/>
      <runtime-component id="" version="4.0"/>
      <facet id="jst.web" version="2.2,2.3,2.4,2.5,3.0,3.1,4.0"/>
      <facet id="jst.webfragment" version="3.0,3.1,4.0"/>

Is there a workaround for the above issue. Or is there an update planned?

In reply to by Nobuhiro Demura

There is not an update planned since you don't need one to use the (new) Liberty Tools IDE feature.   In Liberty Tools we take a different approach than the older Liberty/WebSphere Eclipse IDE tooling.   Rather than providing Liberty implementations for constructs like the Target runtime to support things like the Publish operation and management through the Servers view, as in the older Liberty/WebSphere Developer Tools features, we use a different approach.

For Liberty Tools, we assume the use of a Maven or Gradle project.   Compilation is performed against normal Maven/Gradle dependencies and the Liberty Maven and Gradle plugins manage installation of the Liberty runtime and deployment of your application to this runtime.  

So using a Jakarta EE 9-level feature like Jakarta Servlet 5.0 simply requires you to use a Maven/Gradle project with a recent version of the corresponding Liberty Maven/Gradle plugin, a valid dependency in your pom.xml/build.gradle, and the servlet-5.0 feature in your server.xml.



Based on the above comments that plugin is a next-generation version of IBM Liberty Developer Tools, I installed it to compare with the other. However, after doing so I am not able to see or create Liberty server profiles under the "Servers" view.

We don't integrate any Liberty dependencies (Maven/Gradle) or configuration in our application; we deploy our app to Liberty using the Servers pane in Eclipse. Is this be supported in this plugin?

In reply to by Ross Bender

Ross, thanks for your question.    Though Liberty Tools is indeed designed as a next-generation version of IBM Liberty Developer Tools, we do not provide the equivalent function in the same manner.  First and most importantly, with Liberty Tools we assume you're using a Maven or Gradle project configured with either the Liberty Maven or Gradle plugin.   Most Liberty projects are using Maven or Gradle these days, but if not, you would first need to convert your project to Maven or Gradle to make use of Liberty Tools.   With Liberty Tools there is no server under the Servers view; the Liberty server is "embedded" in the Liberty Maven or Gradle plugin.  Also there is no "Publish" operation; the Liberty Maven/Gradle plugin deploys the application to the plugin-managed Liberty server.

In reply to by Ross Bender

I believe it is.

In Liberty Tools for Eclipse plugin, when you select 'Servers' view and try to create a Liberty server, you should see 'WebSphere Application Server Liberty Extended Tools' under 'IBM'. After you installed it, you should see the same functionality like 'IBM Liberty Developer Tools' provides.

You don't really need Maven/Gradle at all, but I suggest everyone should try Maven/Gradle to let your development environment more friendly.

In reply to by Mark Su

Let me clarify, (I know the naming involved is confusing).  The Liberty-related entry in the 'Servers' view has nothing to do with the "Liberty Tools" feature supplied by this particular Eclipse Marketplace item.   It might though be something you are getting from the  <a href="">IBM Liberty Developer Tools</a> feature install. 

Like I mentioned in my own reply comment, the "Liberty Tools" feature does indeed assume the use of Maven/Gradle, (though the "Liberty Developer Tools" feature does not, which I think is what you noted).

While there could be some amount of value potentially in installing both "Liberty Tools" and "Liberty Developer Tools" in a single Eclipse installation (e.g. to get code assistance for Jakarta EE 9/10 APIs), we don't really document this.  The combination could get confusing because the underlying implementations are using different approaches and are not especially integrated.