MIME-Version: 1.0
Message-ID: <61330f49-1447-48eb-9718-0dec84efd58f@u69g2000hse.googlegroups.com>
Date: Fri, 7 Mar 2008 04:57:30 -0800 (PST)
Received: by 10.86.70.8 with SMTP id s8mr13982fga.19.1204894650103; Fri, 07 
	Mar 2008 04:57:30 -0800 (PST)
In-Reply-To: <81b3ff2e-a48d-4724-99d1-833c2a956c6e@s13g2000prd.googlegroups.com>
X-IP: 82.192.90.214
References: <bb45dce50803061148p7c233866hefb1e03fb892b8d1@mail.gmail.com> 
	<81b3ff2e-a48d-4724-99d1-833c2a956c6e@s13g2000prd.googlegroups.com>
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.12) 
	Gecko/20080201 Firefox/2.0.0.12,gzip(gfe),gzip(gfe)
Subject: Re: GWT 1.5 Milestone 1 now available for download
From: Rockster <rjan...@gmail.com>
To: Google Web Toolkit <Google-Web-Toolkit@googlegroups.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Hi Bruce,

great work. A note though: You are only supporting JDK1.5.
We are busy making our production ready software using GWT
and since our customers can NOT upgrade tot 1.5 yet, is this
going to be an issue ?

I know that 1.4 is EOL at the end of this year, but we'll still have
customers
running the old VM (so <1.5). (Think about their AppServers, some of
the customer
are still running IBM Websphere 5.1 or 6.0, which are not JDK 1.5
platforms
yet and trust me, upgrading their VM's is a lot of work (for them)).

What would be the solution on this ? Can I use the GWT1.5 binaries
with a 1.4 VM (for example if I use RetroTranslator).

Hope to hear from you soon.

R.

On Mar 7, 7:39 am, NN <neh...@gmail.com> wrote:
> great..time for test drive
>
> On Mar 6, 11:48 am, "Bruce Johnson" <br...@google.com> wrote:
>
> > Hi everybody,
>
> > GWT 1.5 isn't finished yet, but it is starting to get close. I'm happy to
> > report that the first milestone build of GWT 1.5 is now available:
>
> >http://code.google.com/p/google-web-toolkit/downloads/list?can=4&q=ve...
>
> > (Note the odd version number of 0.0.2030 to help make it obvious that you
> > shouldn't use it for anything important.)
>
> > For milestone builds like this, please understand that there are still known
> > problems, and it is use-at-your-own-risk. It *definitely* isn't ready for
> > production use. For example, this milestone build is missing release notes,
> > and it doesn't include the developer guide documentation. So, you should
> > expect some trial and error getting everything to work.
>
> > Are your expectations low enough yet? Well, I also have some good news about
> > what's included in this milestone:
>
> >    - The Java 1.5 syntax is fully supported, including generics, enums,
> >    nice "for" loops, autoboxing, static imports, annotations, and so on
> >    - Support for generics in RPC (no more @gwt.typeArgs!)
> >    - The ability to subclass
> > JavaScriptObject<http://code.google.com/p/google-web-toolkit/wiki/JavaScriptObjectRede...>for
> > very straightforward JavaScript interop
> >    - Standards mode is now supported by the UI library (though there may
> >    be a few remaining bugs)
>
> > There are lots of other neat things in there if you dig a little. You can
> > see details<http://code.google.com/p/google-web-toolkit/issues/list?can=2&q=miles...>in
> > the issue tracker, or if you're really interested (or really bored),
> > you
> > can browse the commit
> > logs<http://code.google.com/p/google-web-toolkit/source/list>
> > .
>
> > Things to be aware of that may trip you up:
>
> >    - GWT 1.5 requires Java 5 or later
> >    - The compiler output now goes into a subdirectory (e.g. ".../std" or
> >    ".../xs", depending on your linker
> > settings<http://code.google.com/p/google-web-toolkit/wiki/LinkerDesign>
> >    )
> >    - To encourage people to start using annotations and generics instead
> >    of the javadoc metadata, you'll see warnings about uses of old-style
> >    metadata such as @gwt.typeArgs; it is intentionally annoying :-)
> >    - The benchmark classes have moved into a separate package; should be
> >    easily fixable using your IDE's auto-import fixup
> >    - As a performance improvement, widgets now often call DOM.sinkEvents()
> >    lazily, when listeners are actually added rather than in the constructor.
> >    Sometimes, widget subclasses implicitly depend on the set of events sunk in
> >    the superclass' constructor. Consequently, if you are overriding
> >    onBrowserEvent() in a widget subclass and certain events mysteriously stop
> >    firing, you should explicitly call DOM.sinkEvents() in your subclass
> >    constructor for the events you depend on (don't worry, sinking an event more
> >    than once has no effect). If the preceding sentences made no sense at all to
> >    you, then you shouldn't be affected.
>
> > We really hope you'll try it out, and we 're eager to see what you think so
> > far. Please report bugs in the issue
> > tracker<http://code.google.com/p/google-web-toolkit/issues/entry>,
> > and discuss it in the contributors
> > forum<http://groups.google.com/group/Google-Web-Toolkit-Contributors>
> > .
>
> > Enjoy!
>