If you are using the Vaadin Plugin for Eclipse,
the standard plugin does not yet support Vaadin 6.2 . You need the experimental plugin, which you can install to Eclipse with the URL [tt] http://vaadin.com/eclipse/experimental
[/tt]. After installing it, simply upgrade your project from project preferences to use the new version and the plugin will download the new Vaadin Jar for you.
Problem fixes and enhancements planned for upcoming releases can be found from the
Vaadin Roadmap in Vaadin Trac.
As always, when upgrading from an earlier version, you should recompile any custom widget sets and refresh your project in Eclipse. If you are upgrading from earlier than 6.1.0, notice that Vaadin 6.2 uses GWT 1.7 (included in the installation package). See the
General Upgrade Notes for more details on upgrading.
You might especially want to check out the new
Sampler , which has new examples and greatly enhanced icons for better clarity. Well, for a part of the examples for now.
I have some problems at least with getting the latest jar, I go into (from Eclipse 3.5.1) with right click from my project Properties, from there in the tree I select Vaadin and then click download to give me a list of the available versions, it shows 6.2.0 pre1 and a host of others but if you then select to then download by selecting and clicking OK it says failed to download.
However if I select on the download window the check box ‘show pre release versions and nightly…’ it gives me a much longer list (OK thats expected ) where I can then select 6.2.0 pre 1 but not the top one in the list but the one that is under 5.3.0 it then downloads and works ok.
Hope this helps if someone is having similar problems.
There was a problem caused by the download page that required the use of dash in the version name, as in “6.2.0-pre1”, but the version name is “6.2.0.pre1” (as required by OSGi), so I made a temporary workaround at the download site to get the website working, but the Vaadin Plugin for Eclipse could not cope with the workaround.
The website problem was fixed last friday (December 11th) and the workaround was removed. Please report if there are still any problems.
(Also the links in the announcement message above had gone sour on friday, they should work now.)
Great!