-
Notifications
You must be signed in to change notification settings - Fork 34
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
.classpath needs manual fixes #46
Comments
Slight correction... I'd forgotten that we did fix problem 1 through gradle, by adding a destinationDirectory setting to the eclipse {} configuration, so really we are only left with problems 2 and 3, the lack of a proper classpath entry for GWT, and fixing the default output for src/main/java (which I presume can be done with sourceSets, but I just can't get it to work). |
The latest plugin code doesn’t include anything related to Eclipse any
more. So it will be all configurations in Gradle and Eclipse.
…On Wed, 16 Jun 2021 at 9:36 pm, Bob Lacatena ***@***.***> wrote:
Slight correction... I'd forgotten that we did fix problem 1 through
gradle, by adding a destinationDirectory setting to the eclipse {}
configuration, so really we are only left with problems 2 and 3, the lack
of a proper classpath entry for GWT, and fixing the default output for
src/main/java (which I presume can be done with sourceSets, but I just
can't get it to work).
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#46 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAECF5C25JTBHFD26PA6CP3TTCSE3ANCNFSM46ZLDO2Q>
.
|
I try to build a gradle-based GWT project from pure Eclipse project, have found this plugin, have similar problems the 2:I have to manually enable GWT for the Eclipse project in GWT settings after each "Refresh gradle project" 1 and 3 are resolved via eclipse plugin:
Then I have The base of this plugin (steffenschaefer.github.io/gwt-gradle-plugin) mentions
but doesn't explain how the web.xml gets into this /war path. |
We recently upgraded our environments to the latest Eclipse release (2021 03) and Gradle (7.1), and are using GWT 2.8.1 with the GWT plugin 3.0.
The end result has several errors that must be fixed manually in .classpath (using the Eclipse UI, but it could be done by editing .classpath) after any build (which is only done when we change any dependencies, otherwise we just code-and-test).
Our problems:
The default output is set to /bin/main, which generates an error on the project (presumably produced by the GWT plugin, the the source of the error is Unknown). The fix is to add a classpathentry with kind="output" and the GWT-desired path of war/WEB-INF/classes to the end of .classpath.
It complains that there is no GWT SDK. The fix is to add a classpathentry with kind="con" and path = the proper GWT version (com.gwtplugins.gwt.eclipse.core.GWT_CONTAINER/gwt-2.8.1). This by itself is not good enough in our application, as it is sensitive to the order of the class path entries. This entry must come after the classpathentry for the JRE but before that for the web container and buildship.
It sets the output for src/main/java to the standard default, bin/main, which results in all automatic build code going there instead of into war/WEB-INF/classes (which means that during active development, one must constantly run a build to get the latest code). We fix this by removing the output designation from src/main/java, allowing it to go to the default location for the project (which GWT required be set to war/WEB-INF/classes in step 1 above). I have tried using sourceSets to get gradle to do this properly within gradle, but none of my attempts have succeeded.
It is my presumption that we are doing something wrong, and that all of this would work properly otherwise, but days of research and trial and error has failed to resolve these problems. It has been very frustrating. It took a lot of trial and error to figure out the work arounds (we are a small shop, without "build engineers", so our contact with gradle is fleeting and "just as much as necessary", and so we lack a strong grasp of gradle (let alone gradle + GWT + eclipse plugins + gradle plugins), which makes managing this very difficult.
I can send along (privately, our code is proprietary) any source files you might need to look at to resolve this.
The text was updated successfully, but these errors were encountered: