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:
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:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=550966
The challenge here is that
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:
https://github.com/eclipse/buildship/issues/943
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
What does the Eclipse error log show? Sounds like an Eclipse / some plugin
issue and the error log should show some stack trace.
-- 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
Any suggestions?
On Wednesday, September 18, 2019 at 11:26:57 AM UTC-7, Jim Douglas wrote:
>
> (That should have said " after updating to Eclipse 2019-09 today.")
>
> On Wednesday, September 18, 2019 at 11:22:07 AM UTC-7, Jim Douglas wrote:
>>
>> I was able to get a Java 11 / Eclipse 2019-06
(That should have said " after updating to Eclipse 2019-09 today.")
On Wednesday, September 18, 2019 at 11:22:07 AM UTC-7, Jim Douglas wrote:
>
> I was able to get a Java 11 / Eclipse 2019-06 development environment
> building my GWT project with Maven Plugin for GWT
>
