Skip to content

typetools/stubparser

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Stub Parser

This project contains a parser for the Checker Framework's stub files: https://checkerframework.org/manual/#stub . It is a fork of the JavaParser project.

Differences between the StubParser and JavaParser

These are the differences between JavaParser and StubParser:

  1. StubUnit class that represents the parsed stubfile.
  2. Changes to the java.jj file to parse the stub files.
  3. Methods for parsing the stub files in the JavaParser class.

To see the diffs between the forks, enter the root directory of the StubParser and perform the following commands:

git remote add upstream https://github.com/javaparser/javaparser
git fetch upstream
git diff upstream/master HEAD

Updating from upstream JavaParser

This section describes how to incorporate changes from JavaParser into StubParser. Only developers, not users, of StubParser need to do this.

Preparation

  1. Fork the StubParser project to your GitHub account.
  2. Clone the repository, using one of the following two commands:
git clone git@github.com:{user.name}/stubparser.git
git clone https://github.com/{user.name}/stubparser

Updating

  1. Update from StubParser.
cd stubparser
git pull --ff-only https://github.com/typetools/stubparser
  1. Find an appropriate tag name:
export TAG_NAME=javaparser-parent-3.24.7
  1. Create and checkout a new branch, via the below or gnb updating-${TAG_NAME}:
git checkout -b updating-${TAG_NAME}
  1. Pull the upstream of the JavaParser project.
git pull https://github.com/javaparser/javaparser ${TAG_NAME}
  1. Resolve conflicts if required and commit it (but don't push yet).
  2. Update the StubParser version to the JavaParser version to the version number in the <finalName> block of javaparser-core/pom.xml. (There should not be "-SNAPSHOT" there or in <version> in pom.xml.)
  3. Run Maven tests in the root directory:
./mvnw install test

If any tests fail, fix them before continuing.

  1. Deploy the snapshot. (This has been tested on tern.) Update the version block in javaparser-core/cfMavenCentral.xml to be the same as the JavaParser version plus -SNAPSHOT. Run the following in javaparser-core
export STUBPARSER=stubparser-3.25.5
export HOSTING_INFO_DIR=/projects/swlab1/checker-framework/hosting-info
mvn gpg:sign-and-deploy-file -Durl=https://oss.sonatype.org/content/repositories/snapshots/  \
   -DpomFile=cfMavenCentral.xml -Dfile=target/$STUBPARSER.jar\
   -Dgpg.keyname=checker-framework-dev@googlegroups.com \
   -Dgpg.passphrase="`cat $HOSTING_INFO_DIR/release-private.password`" \
   -DrepositoryId=sonatype-nexus-staging

(You must have a file at ~/.m2/settings.xml that lists a username and password for Sonatypes.)

  1. Update the stubparser version number in the Checker Framework. Create a branch with the same name as your StubParser branch. In checker-framework/build.gradle, update stubparserJar.
  2. Run Checker Framework tests (./gradlew build), using your StubParser branch. If any tests fail, fix them before continuing.
  3. Commit and push your changes to Checker Framework.
  4. Once the Azure tests pass, release the Stubparser:

Delete -SNAPSHOT from the version in javaparser-core/cfMavenCentral.xml.

mvn source:jar && \
mvn javadoc:javadoc && (cd target/site/apidocs && jar -c -f ../../$STUBPARSER-javadoc.jar com)
mvn gpg:sign-and-deploy-file -Durl=https://oss.sonatype.org/service/local/staging/deploy/maven2/  \
    -DpomFile=cfMavenCentral.xml -Dfile=target/$STUBPARSER.jar \
    -Dgpg.keyname=checker-framework-dev@googlegroups.com \
    -Dgpg.passphrase="`cat $HOSTING_INFO_DIR/release-private.password`" \
    -DrepositoryId=sonatype-nexus-staging

mvn gpg:sign-and-deploy-file -Durl=https://oss.sonatype.org/service/local/staging/deploy/maven2/  \
    -DpomFile=cfMavenCentral.xml \
    -Dgpg.keyname=checker-framework-dev@googlegroups.com \
    -Dgpg.passphrase="`cat $HOSTING_INFO_DIR/release-private.password`" \
    -DrepositoryId=sonatype-nexus-staging \
    -Dclassifier=javadoc -Dfile=target/$STUBPARSER-javadoc.jar

mvn gpg:sign-and-deploy-file -Durl=https://oss.sonatype.org/service/local/staging/deploy/maven2/  \
    -DpomFile=cfMavenCentral.xml \
    -Dgpg.keyname=checker-framework-dev@googlegroups.com \
    -Dgpg.passphrase="`cat $HOSTING_INFO_DIR/release-private.password`" \
    -DrepositoryId=sonatype-nexus-staging \
    -Dclassifier=sources -Dfile=target/$STUBPARSER-sources.jar

Complete the release at https://oss.sonatype.org/#stagingRepositories.

  1. In the Checker Framework, remove SNAPSHOT in the StubParser version numbers. Commit and push your changes to Checker Framework.

  2. Push commits to your fork of StubParser.

git push

GitHub Actions CI will not run for your branch.

  1. Create a pull request to typetools/stubparser. Give it a title like "Update to JavaParser 3.24.3". Do not squash-and-merge the pull request; you want to keep a history of what upstream commits were merged in.

  2. Create a pull request to typetools/checker-framework. Give it a title like "Update to StubParser 3.24.3".

  3. Merge both pull requests when both pass.

Changes to StubParser that break the Checker Framework

If you commit a change to the StubParser that breaks the Checker Framework, then change the StubParser version number. Do this only if necessary (probably not for minor bug fixes), because it breaks the mvn javadoc:javadoc command.

  • In javaparser-core/pom.xml, in the <finalName> block.
  • In the Checker Framework's top-level build.gradle file, on the stubparserJar = line.

Original JavaParser README

The remainder of this README file is the original JavaParser README.

JavaParser

Maven Central Build Status Coverage Status Join the chat at https://gitter.im/javaparser/javaparser License LGPL-3/Apache-2.0 DOI

This project contains a set of libraries implementing a Java 1.0 - Java 17 Parser with advanced analysis functionalities.

Our main site is at JavaParser.org

Setup

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.

Please refer to the Migration Guide when upgrading from 2.5.1 to 3.0.0+

Maven:

<dependency>
    <groupId>com.github.javaparser</groupId>
    <artifactId>javaparser-symbol-solver-core</artifactId>
    <version>3.25.6</version>
</dependency>

Gradle:

implementation 'com.github.javaparser:javaparser-symbol-solver-core:3.25.6'

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:

Maven:

<dependency>
    <groupId>com.github.javaparser</groupId>
    <artifactId>javaparser-core</artifactId>
    <version>3.25.6</version>
</dependency>

Gradle:

implementation 'com.github.javaparser:javaparser-core:3.25.6'

Since version 3.6.17 the AST can be serialized to JSON. There is a separate module for this:

Maven:

<dependency>
    <groupId>com.github.javaparser</groupId>
    <artifactId>javaparser-core-serialization</artifactId>
    <version>3.25.6</version>
</dependency>

Gradle:

implementation 'com.github.javaparser:javaparser-core-serialization:3.25.6'

How To Compile Sources

If you checked out the project's source code from GitHub, you can build the project with maven using:

mvnw clean install

If you want to generate the packaged jar files from the source files, you run the following maven command:

mvnw package

NOTE the jar files for the two modules can be found in:

  • javaparser/javaparser-core/target/javaparser-core-\<version\>.jar
  • javaparser-symbol-solver-core/target/javaparser-symbol-solver-core-\<version\>.jar

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. (mvnw clean install already does this for you.)

mvnw javacc:javacc

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. The run_metamodel_generator.sh script will rebuild the metamodel, which is used by the code generators which are run by run_core_generators.sh 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

More information

JavaParser.org is the main information site or see the wiki page https://github.com/javaparser/javaparser/wiki.

License

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.

For details about the Apache License please refer to LICENSE.APACHE.

Packages

No packages published

Languages

  • Java 99.3%
  • Other 0.7%