plugin throws exception #386
Comments
|
I would expect another error in the logs because looking at the sources, the only thing I can imagine is that ModelClassPathDef.excludePaths thrown an error. Though this is the first time I would hear that. Can you check the IDE logs for another error? |
|
In particular, I would expected ClassLoaderUtils.findClassPathOfClassNonCanonical to fail though I have no idea why that could happen. |
|
Do you happen to have a "!" in your path to NB's user directory (which is in your user home) because if that is the case then that is probably the bug? |
|
Just in case I have fixed the possible "!" problem, so if that was you issue, it should work now. Try building the plugin from the sources, it should build out-of-the-box but if you want to be very meticulous, you could follow the Development wiki page. |
|
Hi Thanks for quick response! And this is what we can see when we open project PS I cannot see any exclamation marks here. PPS I replaced company name with "truncated" |
|
UPDATE |
|
That explains it. The File object does not support paths like \\filestore.XYZ.com\profilesFR$\.... I will review all such usages. However, Gradle also provides the dependencies as File objects, so I would guess that you have to set Gradle's cache (which is in the home directory by default) to somewhere else too. |
kelemen
added a commit
that referenced
this issue
Jun 1, 2018
|
I have added some fix, though I'm a little worried if this will fix every issue because I'm unsure how Gradle will treat these URLs. Can you check by building the plugin from the sources (master branch, I have not yead merged the changes into the nb9 branch)? At the very least, I would expect a better exception report. |
|
Hi, Sorry for delay, this is what I've got from one of our devs: Steps: |
|
I don't see any errors in the log file and I don't even see that the Gradle plugin attempted to load anything. Is this the complete log file and was there an actual issue during this NB session? The only exception there comes from the Ant integration of NB but it is logged at INFO level, so I assume that is not a problem (it probably realizes that it can't do anything with a non-ant project. |
|
after project reloading we can see following in the logs: |
|
It seems like a Gradle bug (you might want to try a newer version), although given the stack trace it might be that the Gradle bug just fails to show the original error. By the way, I assume trying to build the plugin from the command line works. Also, can you try if building (or executing any Gradle tasks) works from NB (even if it failed to load the project)? |
|
Hi, |
|
I would need to know what exactly Gradle's problem with the path. I guess that its dynamic-model-init-script.gradle. If you don't get better exception log from newer versions of Gradle, then can you try replacing |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
Developers in my team, who use windows experienced problems with gradle plugin.
After installation of gradle plugin netbeans reports following exception:
Their setup is:
OS: windows 7
Netbeans: various versions of netbeans. We tried upgrading to 8.2 and installing 8.2 from scratch - result is the same.
Java: 1.8_171
Additional info:
On mac and linux - we can't see such problem.
I've tried it in virtualbox(windows 7 + java 1.8_171 + netbeans 8.2) and I couldnt reproduce the problem.
Netbeans throws this error even if you work on non-gradle projects.
What could be the reason for such behaviour?
Thanks
The text was updated successfully, but these errors were encountered: