>
> But it also takes some time to write release notes for every release.
> So again, mostly a problem of time to spend.
>
I think if we take care on good commit messages and bug tracking we could
automate releases including good enough release notes on Github using their
API.
-- J.
--
You r
On Saturday, July 2, 2016 at 4:22:28 PM UTC+2, Jens wrote:
>
>
> As said above, Google doesn't really care about "releases", except for
>> that they care enough about the community "outside" who, they know, do care
>> about releases.
>>
>
> @Thomas: And thats exactly why I think GWT will have a
On Saturday, July 2, 2016 at 5:36:58 PM UTC+2, Gilberto wrote:
>
> Guys, threads asking if GWT is dead/dying shouldn't appear as often as it
> does. Actually they shouldn't appear at all. But they do. Something is
> definitely wrong. As community we should do something.
>
Glad you're using "we
Hi,
+1 on the regular releases. I am perfectly aware that this is an open
source project so nobody is entitled in asking anything. However with long
standing releases it is getting difficult to justify use of GWT in my
organization. It is much easier to carry custom patches or skip a buggy
release
> As community we should do something. In my opinion the communication is
> pretty poor and should be improved. GWT is "too blackbox" in my opinion,
> because of the reasons I stated before.
>
Its as open as any other open source project.
But if the communication is fine, it's just a matt
See
https://groups.google.com/forum/m/?fromgroups#!topic/google-web-toolkit/fkbowz5-5do
it's old but maybe ir is still useful for your needs
El sáb., jul. 2, 2016 7:52, Gilberto escribió:
> Not the answer you would like to hear, but...
>
> In my humble opinion, the elegant solution would be not
Guys, threads asking if GWT is dead/dying shouldn't appear as often as it
does. Actually they shouldn't appear at all. But they do. Something is
definitely wrong. As community we should do something. In my opinion the
communication is pretty poor and should be improved. GWT is "too blackbox"
in
> As said above, Google doesn't really care about "releases", except for
> that they care enough about the community "outside" who, they know, do care
> about releases.
>
@Thomas: And thats exactly why I think GWT will have a better life if we
would do fixed, automated monthly / quarterly rel
On Saturday, July 2, 2016 at 12:29:32 PM UTC+2, Gilberto wrote:
>
> ... and that's a problem, at least the way it is developed now.
>
> GWT is a more-or-less open-source project. While it is indeed open-source
> (you can look at the code), the process of developing it depends heavily on
> close
Not the answer you would like to hear, but...
In my humble opinion, the elegant solution would be not using GWT RPC at
all. Go RESTful.
For the annotation problem, I don't know if there's a way to escape...
maybe you could try code generation (which usually also relies on
annotations... so...)
Hi Pierre!
Welcome to GWT and GWT Material =)
If you want a faster, direct communication with the developers from GWT
Material, join us at the Gitter chat:
https://gitter.im/GwtMaterialDesign/gwt-material
Also, I advise you to really try to use Maven. I know it's hard and
sometimes frustratin
... and that's a problem, at least the way it is developed now.
GWT is a more-or-less open-source project. While it is indeed open-source
(you can look at the code), the process of developing it depends heavily on
closed-source, blackbox projects made by Google, that nobody really knows
about o
12 matches
Mail list logo
