Du kan inte välja fler än 25 ämnen Ämnen måste starta med en bokstav eller siffra, kan innehålla bindestreck ('-') och vara max 35 tecken långa.
Leif Åstrand dfe27b2deb Avoid excessive logging related to response handling locks (#11702) 11 år sedan
.settings Add default save actions to the project settings 11 år sedan
WebContent Added jQuery to license file (#11513) 11 år sedan
all Added push meta module (#11498) 11 år sedan
build Build a minified version of vaadinPush.js in vaadin-push.jar (#11630) 11 år sedan
buildhelpers Updated commons-io dependency to 2.2 (#11643) 11 år sedan
checkstyle Added check for carriage return (#9065) 11 år sedan
client Avoid excessive logging related to response handling locks (#11702) 11 år sedan
client-compiled Enabled closure compiler for default widget set (#9103) 11 år sedan
client-compiler Moved WidgetSetBuilder to server as ClassPathExplorer dependends on it (#11591) 11 år sedan
eclipse Launch configurations for dev server and dev mode (#11363) 11 år sedan
push Add patched AtmosphereFramework without support message (#11654) 11 år sedan
scripts Include commit id and message in merge commit message 11 år sedan
server Re-added Property.toString warning messages (#10916) 11 år sedan
shared Renamed loading indicator states to 'first','second','third' (#11668) 11 år sedan
theme-compiler Merge commit 'feb9a8c3510afc76c079fafcd9e507205bde139c' 11 år sedan
themes Renamed "tests" target to "test" and added "test-all" (#9998) 11 år sedan
uitest TestBench test for tree (#11612) 11 år sedan
.classpath Add patched AtmosphereFramework without support message (#11654) 11 år sedan
.gitignore Build a minified version of vaadinPush.js in vaadin-push.jar (#11630) 11 år sedan
.project Removed Javascript buider and nature to avoid Eclipse choking on validating widgetset files (#9998) 11 år sedan
README.md Clarified build documentation in README.md #11227 11 år sedan
build.properties Refactor OSGi manifest attribute handling to support import/export better (#9793) 11 år sedan
build.xml Renamed "tests" target to "test" and added "test-all" (#9998) 11 år sedan
common.xml Added push meta module (#11498) 11 år sedan
gwt-files.xml Made build process easier for Eclipse users (#9998) 11 år sedan
ivy-taskdefs.xml Checkstyle for Vaadin #9065 11 år sedan
ivysettings-publish.xml Snapshot deployment to Maven now works (#9299) 11 år sedan
ivysettings.xml Added push meta module (#11498) 11 år sedan
pom-template.xml Updated scm in pom template (#11204) 11 år sedan
publish.properties Publish to SFTP (#9299) 11 år sedan
publish.xml Avoid publishing 'all' zip to Maven (#9299) 11 år sedan

README.md

Cloning the project repositories

Vaadin 7 consists of three separate repositories

Start by cloning these repositories into the same folder:

git clone https://github.com/vaadin/vaadin.git
git clone https://github.com/vaadin/gwt.git
git clone https://github.com/vaadin/gwt-tools.git

The vaadin and gwt repositories contain project code. The gwt-tools project only contain dependency jars used by the other projects.

Do not rename the repositories as the rest of this document relies on using the standard naming.

Setting up Eclipse to Develop Vaadin 7

Assuming you have cloned the repositories as described in “Cloning the project repositories” above, you can import the vaadin and gwt projects into Eclipse as follows:

Start Eclipse

Start Eclipse and use the root checkout folder (the one containing the vaadin, gwt and gwt-tools folders) as the workspace folder

Define Required Variables for the GWT Eclipse Projects

To be able to find all files, the GWT project requires you to define a couple of variables:

  1. Open Window -> Preferences (Windows) or Eclipse -> Preferences (Mac)
  2. Go to General -> Workspace -> Linked Resources
  3. Add a new Path Variable GWT_ROOT referring to the gwt folder containing the gwt project GWT_ROOT
  4. Go to Java -> Build Path -> Classpath Variables
  5. Add two new variables
    1. GWT_TOOLS referring to the gwt-tools folder containing the dependency jars
    2. JDK_HOME referring to your jdk installation directory GWT_TOOLS
  6. Go to Java -> Compiler
    1. Check that the compliance level has been set to 1.6 (or higher)

Import the Projects into the Workspace

  1. Do File -> Import -> General -> Existing Projects into Workspace ImportProject
  2. Select the workspace folder as root directory
  3. Click “deselect all” and select
    1. gwt-dev
    2. gwt-user
  4. Click “finish” to complete the import of GWT
  5. Then repeat by doing File -> Import -> General -> Existing Projects into Workspace
  6. Select the workspace folder as root directory
  7. Click “deselect all” and select
    1. vaadin
  8. Click “finish” to complete the import of Vaadin Framework

FinishImportProject

You should now have three projects in your workspace. If the vaadin project does not compile without errors, choose Ivy -> Resolve from the vaadin project popup menu. Now all projects should compile without errors (there might be warnings).

Note that the first compilation takes a while to finish as Ivy downloads dependencies used in the projects.

Compiling the Default Widget Set and Themes

Compile the default widget set by executing the default target in build/ide.xml in the vaadin project. In Eclipse this is done by opening build/ide.xml, right clicking on it and choosing Run As -> Ant Build. CompileWidgetSet

Running a UI test

The vaadin project includes an embedded Jetty which is used for running the UI tests. It is a standard Java application: com.vaadin.launcher.DevelopmentServerLauncher. Launch it in debug mode in Eclipse by right clicking on it and selecting Debug As -> Java Application.

This launches a Jetty on port 8888 which allows you to run any UI class in the project by opening http://localhost:8888/run/<UI class name>?restartApplication in your browser, e.g. http://localhost:8888/run/com.vaadin.tests.components.label.LabelModes?restartApplication (Add ?restartApplication to ensure).

Running JUnit tests

The JUnit tests for the projects can be run using

ant test

Running this in the gwt directory will run the GWT JUnit tests. Running it in the vaadin directory will run the Vaadin JUnit tests.

Running the Vaadin TestBench tests currently requires access to a correctly configured TestBench 2 cluster, only available inside Vaadin.

Building a package

The distribution files can be built in a few steps. First build the gwt project by running

ant
in the gwt directory. The elemental package needs to be built separately:
ant elemental
Building the elemental package is not possible on Windows as it requires gcc.

Move to the vaadin project directory and unpack the previously built gwt jars

ant -f gwt-files.xml unpack.gwt
Then build the vaadin project by running
ant
in the vaadin directory.