Maybe a better question is, what do you feel is missing to call it a
- Documentation is lacking. It's not something unique but we really need to do a bit more work on it.
- We don't ship any Maven artifacts. Therefore, even if technically it's possible to use Maven for building Scala+GWT projects then in practice it's not feasible yet.
- We still don't have continuous builds set up (meaning I don't want to have storm of pull request yet)
- Nobody apart from me knows how to build Eclipse plugin that supports Scala+GWT. Exact steps got a lot better due to work of Eclipse plugin team but still I need to document it.Apart from first bullet others are fairly straightforward to address. I don't say everything has to be perfect for 1.0 release but I'd like to get at least a few things addressed here. Help is always welcome.
Also, I'd like to release more often from now.
It's very easy to ship maven artifacts. We don't even need to host
them in common maven repository. People are used to adding additional
maven repositories to get the artifacts that they care about.
This guy hosts his maven artifacts on github:
It works like a charm.
P.S. If you wanted to host them in scala-tools, sonatype, or maven
central, it will be more difficult since we need to re-use groupId's
that belong to other teams (org.scala-lang, and com.google.gwt).
It Smseems like we have the right person to work on this? :-)
-- Sent from Android
I also have had good experience with http://travis-ci.org/ for
open-source continuous builds.
And yes, I'd be happy to do the setup for maven gwt. I'll start on it
as soon as you tag a release. =)