Update: I found a classpath entry that does use Gradle, and the GWT Compile runs when I remove that Gradle-related entry. Now that I've isolated the source of the problem, I'm trying (with no success yet) to work around it. It looks like this is the main bug report:
-- https://github.com/eclipse/buildship/issues/936
On Tuesday, January 28, 2020 at 9:25:55 AM UTC-8, Jim Douglas wrote:
On Tuesday, January 28, 2020 at 9:25:55 AM UTC-8, Jim Douglas wrote:
Still feeling my way around this. It seems clear that there was a bug introduced in Eclipse 2019-09 that still exists in Eclipse 2019-12. This Eclipse bug report shows the same basic error from a different context:The challenge here is that the package in question doesn't use Gradle at all.
On Monday, January 27, 2020 at 10:39:54 AM UTC-8, Jim Douglas wrote:Gradle is used in another package in this project, but not in the package where I'm trying to do a GWT Compile; this package doesn't use gradle at all.I do see reports of this same internal gradle exception in recent Eclipse distributions:
On Saturday, January 25, 2020 at 9:51:32 AM UTC-8, Jens wrote:Looks like Eclipse wants to resolve classpath entries using Gradle (through Eclipse Buildship Plugin bundled with Eclipse to support project configuration based on Gradle).Maybe Gradle is enabled in your project for any reason, even though you are using Maven?-- J.
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/30c500e9-51a0-48f8-994a-251722ab6446%40googlegroups.com.
No comments:
Post a Comment