Thanks +Goktug Gokdogan for response.
APT is very good option and java 8 support for GWT 3.0 would be a amazing
thing.
You have a planning for Elemental 2.0 or initial documentation to share, to
how you plan address the desing?
El miércoles, 20 de agosto de 2014 16:38:31 UTC-3, Goktug Gokdogan
Dear GWT lovers,
I'm trying to test the last GWT snapshot but I cannot configure maven to
use it.
I've added the following repo:
repositories
repository
idgwt-sonatype-snapshots/id
urlhttps://oss.sonatype.org/content/repositories/google/url
The repo structure is ok, your maven should download the metadata file [1]
which has a reference to the last snapshot index then it should continue
downloading the pom [2] and jar [3] files.
Maybe something wrong in your local repo cache, try to force updating
snapshots running:
mvn -U clean
indeed mvn clean install -U does the trick...
Thanks Manolo
On Thu, Aug 21, 2014 at 4:24 PM, Manuel Carrasco Moñino man...@apache.org
wrote:
The repo structure is ok, your maven should download the metadata file [1]
which has a reference to the last snapshot index then it should continue
For what its worth, we use a slightly different snapshot url:
https://oss.sonatype.org/content/repositories/google-snapshots/. This
appears to only contain snapshots instead of releases and snapshots.
The /google/ url for whatever reason has a newer md5 and sha1 for the
maven-metadata.xml file,
Right, both contain the same snapshot versions. Our jenkins CI server is
pushing to the google-snapshots folder, hence some process else should be
mirroring to the google one after a while, that is the reason for
differences in sha1/md5. I think the best choice is to point to the url you
suggest.
We should add a section on the website explaining how to install and use
the snapshot.
On Thu, Aug 21, 2014 at 4:45 PM, Manuel Carrasco Moñino man...@apache.org
wrote:
Right, both contain the same snapshot versions. Our jenkins CI server is
pushing to the google-snapshots folder, hence some
On Thu, Aug 21, 2014 at 5:29 AM, Cristian Rinaldi csrina...@gmail.com
wrote:
Thanks +Goktug Gokdogan for response.
APT is very good option and java 8 support for GWT 3.0 would be a amazing
thing.
You have a planning for Elemental 2.0 or initial documentation to share,
to how you plan
I think the IDL-DOM generation stuff will be the easy part since the API
is driven by the IDL. The more tricky (likely to bikeshed) stuff I think is
modeling all of the ES5 APIs that back everything. e.g. JsObject, JsArray,
etc.
I somewhat like the old Elemental interfaces (ArrayOf,
I'm eager to start using Java 8 too, but I think we should wait until we
have Java 8 committed (behind a flag) before having the discussion about
whether to require it for anything. As we've found with incremental
compile, sometimes we end up changing direction a bit to reach our goal, so
there's
10 matches
Mail list logo
