-
Notifications
You must be signed in to change notification settings - Fork 193
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Java Model Exception in error log #1041
Comments
Additional note: DCS-SHOP is neither a Java Project, nor a Groovy Project. This may be another candidate reason of the problem, perhaps. |
Let me see if I understand. Filesystem:
Eclipse workspace:
Is this right? |
I use SVN instead of Git, but the structure is right. |
ready to test |
I do not have Groovy sources in the master project, but I do have a Gradle build file (written in Groovy). I did not open that file explicitly but an open editor existed for it when this error occurred. I see that closing and reopening this editor produces that error in the error log. I'm going to try your latest fix to see if it disappears. |
I updated to 3.7.0.v202002262305-e1912, but I still get this exception when I open the editor on
|
ready to test |
No updates found when performing a "check for updates"... |
Can you try again? There were builds over the weekend. |
Retried with 3.7.0.v202003020145-e1912 and no exceptions in console now when I open the |
I don't know exactly when this happens, but today I found this in my log and I'm pretty sure I already saw this in the past other times.
I'm not 100% sure it's Greclipse responsibility, but I see that there's
GroovyCompilationUnit
in the stack trace.Context: I have an Eclipse project handled with Gradle/Buildship which is located in:
<checkout path>\master
The project is imported into the workspace without copying its contents. However, the project name is not "master", but rather it's set to DCS-SHOP in
.project
file (by Gradle).I suspect this mismatch between the folder name ("master") and the project name ("DCS-SHOP") is causing this problem in some way.
The text was updated successfully, but these errors were encountered: