Vaadin 7 beta 3 released

Vaadin 6 / 7 / 8
1


More flexible deployments

In beta1 we simplified the concepts of Application, ApplicationServlet and ApplicationContext. For beta3 we have worked on making the new concepts flexible enough for all use cases based on the feedback we have received. If you are making an application with more than one servlet, you should note that there is now one VaadinServiceSession per servlet (i.e. VaadinService) instead of one shared VaadinSession for all servlets.


Improved server support

Some issues with application servers, mainly with Websphere and Google App Engine, were found in the beta2 release. These have now been resolved while OSGi compatibility is still work in progress but should make it to next week’s release.


Themes still coming up

We were hoping to get the refactored, Sassy themes included in this release, but they just aren’t quite done yet. Next week we will have more on this topic.

For short examples on how to use the new features, check out the Vaadin 7 mini tutorials:
https://vaadin.com/wiki/-/wiki/Main/Vaadin+7

For information on how to migrate from Vaadin 6 to Vaadin 7, see
http://dev.vaadin.com/wiki/Vaadin7/MigrationGuide

This is an beta release so we expect there to be bugs. We will no longer be making large new features but finalization of the current features might still affect API in some places. All your comments on the new features are welcome. Please post all Vaadin 7 related comments in the Vaadin 7 category.

2

in the
download page
 I got this:

mvn archetype:generate -DarchetypeGroupId=com.vaadin -DarchetypeArtifactId=vaadin-archetype-application -DarchetypeVersion=7.0.0.beta3 -Dpackaging=war

but it is not working:

[INFO]
 Generating project in Interactive mode
[INFO]
 Archetype repository missing. Using the one from [com.vaadin:vaadin-archetype-application:7.0.0.beta2]
 found in catalog remote
Downloading: http://repo.maven.apache.org/maven2/com/vaadin/vaadin-archetype-application/7.0.0.beta3/vaadin-archetype-application-7.0.0.beta3.jar
[INFO]
 ------------------------------------------------------------------------
[INFO]
 BUILD FAILURE
[INFO]
 ------------------------------------------------------------------------
[INFO]
 Total time: 29.466s
[INFO]
 Finished at: Tue Oct 02 15:57:13 BRT 2012
[INFO]
 Final Memory: 9M/265M
[INFO]
 ------------------------------------------------------------------------
[ERROR]
 Failed to execute goal org.apache.maven.plugins:maven-archetype-plugin:2.2:generate (default-cli) on project standalone-pom: The desired archetype does not exist (com.vaadin:vaadin-archetype-application:7.0.0.beta3) -> [Help 1]
3

It always takes a while for the release to be replicated to the Maven central. You should retry the command today and it will work

4

Yeap, it works today.

Btw, it exists any published maven repository for snapshot buildings ?

thanks,

Cristiano

5

Our snapshot repository http://oss.sonatype.org/content/repositories/vaadin-snapshots/ is already configured in at least the more recent Vaadin archetypes.

6

Hello,

I have the same problem :

Unable to create project from archetype [com.vaadin:vaadin-archetype-application:7.0.0.beta3 -> ]

The desired archetype does not exist (com.vaadin:vaadin-archetype-application:7.0.0.beta3)

It should be available now?

7

In fact my problem was in Eclipse. After playing with the maven preferences and untick “Do not update automactically dependencies” it works. It’s good to know…

8

Hi guys, long time no see.

I too was trying to get the latest Vaadin 7 beta using maven. Correct me if I’m wrong, but isn’t the suggested vaadin-archetype-application just a dummy application without the actual vaadin7 jar files (or even dependencies to it)?

And after digging though all the archetypes, there was the vaadin library too, but the latest version was alpha 3 or something like that.

So, should I just download the full release zip and handle all the jar dependencies manually (quite more work than with s6’s jars)? Or should there be an archetype for the beta 9 library jar too?

9

No need to handle depencies manually. To get up and running with the latest beta 9, just follow the instructions on the
Download page
:

Or if using Eclipse and have the m2e plugin installed add the archetype via “New Maven project” → “Add Archetype”

Or if using Eclipse and have the m2e plugin installed using the “New Maven project” wizard:
Wait until the Updating indexes and archetypes progresses finish
Type filter vaadin-archetype-application
You thould be able to see com.vaadin vaadin-archetype-application 7.0.0.beta9 as the only option left
Hit next and finish the wizard

The actual jar files will be downloaded to your .m2/repository directory

10

That’s what I did, or at least thought I did. The only jar appearing under .m2/repository was vaadin-archetype-application-7.0.0.beta9.jar and that does not contain the library files, only the dummy application class. And it’s pom file has no dependencies either.

11

Have you built the project (e.g. with “mvn package”)?

Many of the dependencies are only loaded to the local repository at that point.

It is also conceivable, although unlikely, that your IDE uses a separate Maven cache directory.

12

Sorry guys.

Same old story: never trust IDEs and plugins, always use command line tools :wacko:

I still have no clue, why IDEA screwed up the maven stuff, but nevermind. Now I got the project and the libs as expected :slight_smile: It did quite a compilation: first time my 8 cores maxed out a full 100% load and made my background music jam B)