Skip to content

Commit bfc31ae

Browse files
authored
Update issues-with-report.adoc
1 parent 06d7886 commit bfc31ae

File tree

1 file changed

+2
-12
lines changed

1 file changed

+2
-12
lines changed

docs/topics/issues-with-report.adoc

Lines changed: 2 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -8,15 +8,5 @@
88

99
Analysis precision is lower when the project cannot be built for whatever reasons. This lowering of precision can be caused by a number of factors;
1010

11-
* The lack of a proper build file, for example, a `pom.xml` or `build.gradle` file
12-
* Compilation errors of one form or another
13-
14-
.Running {ProductShortName} on a project with an inaccessible parent pom.xml file may not result in a full analysis
15-
16-
Running {ProductFullName} on a project with an inaccessible parent pom.xml file may not result in a full analysis. For example, this issue impacts the link:https://github.com/jboss-developer/jboss-eap-quickstarts/tree/EAP_7.4.0.GA[JBoss EAP Quickstarts], which demonstrate JBoss EAP, Jakarta EE 10, and other additional technologies. They provide small, specific, working examples that can be used as a reference for your project. However, these quickstarts specify a relative path to their parent POM file, which does not exist when the {ProductShortName} container is run.
17-
18-
Specifying an input path of link:https://github.com/jboss-developer/jboss-eap-quickstarts/tree/EAP_7.4.0.GA/kitchensink[`kitchensink`] mounts the `kitchensink` directory as a volume in the container, but that means that the JDT Language Server (jdtls) is unable to access the parent link:https://github.com/jboss-developer/jboss-eap-quickstarts/blob/EAP_7.4.0.GA/kitchensink/pom.xml[pom.xml] file.
19-
20-
This causes the jdtls to encounter a `Non-resolvable parent POM` project build error. This error creates a `.project` file, which is missing the `org.eclipse.jdt.core.javanature`, meaning that jdtls, and subsequently {ProductShortName}, is unable to access details about the Java files.
21-
22-
If you remove the parent pom.xml file and make the `kitchensink` project completely standalone, there are no issues.
11+
* The lack of a proper build file, such as, a `pom.xml` or `build.gradle` file. For example, running {ProductFullName} on a project with an inaccessible parent `pom.xml` file may not result in a full analysis.
12+
* Compilation errors of one form or another.

0 commit comments

Comments
 (0)