Hi, I am using JavaParser 3.24.7 to parse a few opensource projects and I got an exception during the creation of the compilation unit for the file "src\core\lombok\javac\handlers\HandleVal.java" from lombok release 1.18.16:
Exception in thread "main" com.github.javaparser.ParseProblemException: (line 107,col 64) "var" is not allowed here.

The error occurs in this part of code (second line of the block):

		if (localNode.shouldDeleteLombokAnnotations()) {
			JavacHandlerUtil.deleteImportFromCompilationUnit(localNode, val.class.getName());
			JavacHandlerUtil.deleteImportFromCompilationUnit(localNode, lombok.experimental.var.class.getName());
			JavacHandlerUtil.deleteImportFromCompilationUnit(localNode, var.class.getName());
		}

HandleVal.zip

Hello there,
I am trying to run the maven_sample project, namely, the LogicPositivizer.java file, but the error that I receive is as follows:

Error: Unable to initialize main class App
Caused by: java.lang.NoClassDefFoundError: com/github/javaparser/ast/visitor/GenericVisitor

The commands I run are:

mvn clean install java -cp target/<name-of-jar-file> com.yourorganization.maven_sample.LogicPositivizer

Does anybody know here this issue might use from? It happens both while using Intellij IDEA and in terminal.

SourceRoot can not use in gradle

[INFO] Including com.github.javaparser:javaparser-core:jar:3.15.21 in the shaded jar.
[WARNING] javaparser-core-3.15.21.jar, javaparser-maven-sample-1.0-SNAPSHOT.jar define 1 overlapping resources: 
[WARNING]   - META-INF/MANIFEST.MF
[WARNING] maven-shade-plugin has detected that some class files are
[WARNING] present in two or more JARs. When this happens, only one
[WARNING] single version of the class is copied to the uber jar.
[WARNING] Usually this is not harmful and you can skip these warnings,
[WARNING] otherwise try to manually exclude artifacts based on
[WARNING] mvn dependency:tree -Ddetail=true and the above output.
[WARNING] See http://maven.apache.org/plugins/maven-shade-plugin/
[INFO] Attaching shaded artifact.

This is probably because of an upgraded dependency? Be sure to manually test these projects after upgrading, because they have no tests.

JDK8 seems to be removed :-/

When saving the modified source, Javaparser also adds newlines, and moves comments from end of line to above the line.
This is harmless, but when ran agains a large code base it would produces a gigantic commit change, while only a small fraction of it is useful.

Hi,
I am not able to find a reference for Java parser, so that I can cite it. As I have used it in my work.
Please, provide me any pointer or information that I can use to cite it in a research article.

Thank you.

As a complete nooB at Maven and JavaParser, this sample project sounded perfect for me. However, I stumbled a lot trying to use it. I would like to make a few suggestions (highlighted in italics) to this README:

On line 4, please make two changes so the sentence reads:
This fully working sample Maven project parses and generates code with JavaParser
Reason: the existing line 4 is a sentence fragment. As a 30 yr tech writer/editor, I feel the overwhelming need to read/write complete sentences. Changing the first word and deleting the seventh word ("that") will make this a complete sentence with minimal impact to the original wording.

On line 6, please add the word "sample" between the first and second words so it reads:
This sample is targeted at people without Maven experience..
Reason: adding the word "sample" makes the word "this" a little more specific. Grammatically, the word "this" refers to the last noun written which is the word "code".

Between lines 10 and 11, please add instructions similar to:
If required, install git . If you haven't already done so, clone this sample repository with git clone https://github.com/javaparser/javaparser-maven-sample.git. Change to the root folder of where this sample project was installed (where the pom.xml file is located).
Reason: As a Maven nooB, I didn't know if I was supposed to manually clone this sample project or if Maven would somehow auto-magically figure out what repository dependency I had. I finally decided that because I needed the pom.xml file that I needed to git a clone of this sample myself and run mvn from inside the main/top/root folder of this sample. I know, I know, now it seems so obvious but I am a double nooB, both git and Maven.

Add to line 14:
This runs LogicPositivizer which reads, parses, and modifies the code in resources/Blabla.java and then writes the modified file to the output folder.
Reason: as a complete nooB, I had wildly wrong expectations about what this sample would do or produce. It was only after drilling down in the src tree and reading thru LogicPositivizer.java and Blabla.java that I appreciated what had happened. It sort of reminded me of a chemistry experiment where a material is added to the clear liquid in a test tube and the liquid remains clear and apparently unaffected afterwards, only to find out later that a clear odorless gas was output. I didn't understand and appreciate what had just happened. Maybe even at end of LogicPositivizer.java, insert a System.out.println("parsed Blabla.java and wrote modified file to output folder."); statement to tell user that something happened.

Somewhere after line 16, please add a line similar to:
Please refer to "JavaParser: Visited" for more information about what the code in LogicPositivizer.java does.
Reason: If someone jumps into this sample completely unaware of how powerful JavaParser is, they may be confused or mystified by the sample code.