redhat-developer / redhat-developer/vscode-java
<file> s not on its project's build path
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.3k
- Forks
- 546
- Avg merge
- 20h 1m
- Merged PRs (30d)
- 11
Description
I get the following log output:
tomcat/work/Catalina/localhost/_/org/apache/jsp/tag/web/shared/googleTagManager/dataLayerInc [in platform] is not on its project's build path
Java Model Exception: Java Model Status [tomcat/work/Catalina/localhost/_/org/apache/jsp/tag/web/shared/googleTagManager/dataLayerInc [in platform] is not on its project's build path]
at org.eclipse.jdt.internal.core.JavaElement.newJavaModelException(JavaElement.java:580)
at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:253)
at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:527)
at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:247)
The tomcat folder should not be on the build path, so this error is not really an error!
Unfortunately the SAP Hybris Eclipse projects are pretty messed up (not fixable by me).
Environment
- Operating System: macOS 10.12.6 (16G1314)
- JDK version: java version "1.8.0_144"
- Visual Studio Code version: 1.24.1 (1.24.1)
- Java extension version: 0.27.0
Steps To Reproduce
Build the SAP Hybris platform project.
Current Result
Exception is thrown.
Expected Result
Don't throw an exception in that case, because it is not an exception, just ignore the file.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the problem by building the SAP Hybris platform project in the Java extension. Trace the handling of the Java Model Exception for tomcat/work paths that are outside the project's build path, then verify that the build completes without reporting this path as an exception.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, vscode
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100