JavaParser alternatives and similar libraries
Based on the "Development" category.
Alternatively, view JavaParser alternatives based on common mentions on social networks and blogs.
9.6 10.0 L2 JavaParser VS JHipsterJHipster is a development platform to quickly generate, develop, & deploy modern web applications & microservice architectures.
7.8 2.4 L1 JavaParser VS Spring LoadedJava agent that enables class reloading in a running JVM
7.6 7.4 L2 JavaParser VS ImmutablesAnnotation processor to create immutable objects and builders. Feels like Guava's immutable collections but for regular value objects. JSON, Jackson, Gson, JAX-RS integrations included
7.0 4.6 L1 JavaParser VS HotswapAgentJava unlimited redefinition of classes at runtime.
:octocat: ⭕️ CircleMenu is a simple, elegant UI menu with a circular layout and material design animations. Android UI library made by @Ramotion
2.0 0.0 JavaParser VS Better Error PagesRails like error pages for Spring Boot applications that are only active in development.
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of JavaParser or a related project?
Note that edits to this readme should be done via
Modifying this file directly within the root directory risks it being overwritten.
This project contains a set of libraries implementing a Java 1.0 - Java 15 Parser with advanced analysis functionalities. This includes preview features to Java 13, with Java 14 preview features work-in-progress.
Our main site is at JavaParser.org
The project binaries are available in Maven Central.
We strongly advise users to adopt Maven, Gradle or another build system for their projects. If you are not familiar with them we suggest taking a look at the maven quickstart projects (javaparser-maven-sample, javasymbolsolver-maven-sample).
Just add the following to your maven configuration or tailor to your own dependency management system.
<dependency> <groupId>com.github.javaparser</groupId> <artifactId>javaparser-symbol-solver-core</artifactId> <version>3.23.1</version> </dependency>
Since Version 3.5.10, the JavaParser project includes the JavaSymbolSolver. While JavaParser generates an Abstract Syntax Tree, JavaSymbolSolver analyzes that AST and is able to find the relation between an element and its declaration (e.g. for a variable name it could be a parameter of a method, providing information about its type, position in the AST, ect).
Using the dependency above will add both JavaParser and JavaSymbolSolver to your project. If you only need the core functionality of parsing Java source code in order to traverse and manipulate the generated AST, you can reduce your projects boilerplate by only including JavaParser to your project:
<dependency> <groupId>com.github.javaparser</groupId> <artifactId>javaparser-core</artifactId> <version>3.23.1</version> </dependency>
Since version 3.6.17 the AST can be serialized to JSON. There is a separate module for this:
<dependency> <groupId>com.github.javaparser</groupId> <artifactId>javaparser-core-serialization</artifactId> <version>3.23.1</version> </dependency>
How To Compile Sources
If you checked out the project from GitHub you can build the project with maven using:
mvn clean install
If you checkout the sources and want to view the project in an IDE, it is best to first generate some of the source files; otherwise you will get many compilation complaints in the IDE. (mvn clean install already does this for you.)
If you modify the code of the AST nodes, specifically if you add or remove fields or node classes,
the code generators will update a lot of code for you.
run_metamodel_generator.sh script will rebuild the metamodel,
which is used by the code generators which are run by
Make sure that
javaparser-core at least compiles before you run these.
Note: for Eclipse IDE follow the steps described in the wiki: https://github.com/javaparser/javaparser/wiki/Eclipse-Project-Setup-Guide
JavaParser.org is the main information site.
JavaParser is available either under the terms of the LGPL License or the Apache License. You as the user are entitled to choose the terms under which adopt JavaParser.
For details about the LGPL License please refer to [LICENSE.LGPL](ttps://github.com/javaparser/javaparser/blob/master/LICENSE.LGPL).
For details about the Apache License please refer to [LICENSE.APACHE](ttps://github.com/javaparser/javaparser/blob/master/LICENSE.APACHE).
*Note that all licence references and agreements mentioned in the JavaParser README section above are relevant to that project's source code only.