Closed jreed-cartago closed 1 year ago
Please don't open new issues when there are other open issues and pull requests that would be appropriate to reply to instead.
The downside of a large, long-lived project is that sometimes we need to do more work reviewing and testing rather than just skipping ahead to shipping.
It is unfortunate that this plugin has languished for so long, but we expect to have a new release out this week. Note that the old marketplace entry is gone, and we've replaced all existing owners and maintainers of this repository, and have a new update site where we'll push changes once we're relative certain that we have a maintainable approach to take going forward.
We strongly advise using a build tool (maven, gradle) in addition to IDE integration, so that you are not dependent on the IDE, and can build from CI or command line. I can at least speak for the maven integration in eclipse being good enough that a maven project can be imported and the GWT plugin will be able to assist once project setup is managed.
Thank you for your advice and we do use the Maven tools to run GWT for the most part, but when you have the need to run two GWT instances the maven project isn't enough and we then rely on this plugin to perform the debugging for the second GWT instance.
We are looking forward to your upcoming release.
Even though there is a pull request #409 to correct the problem of #407 there has been no Merge into deployment and it is hindering those of us using newer versions of Eclipse.
Are there any plans to merge this fix, or do I need to find another solution for debugging my GWT applications via the maven plugins themselves?