You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Leif Åstrand dc89e28f4d Trigger a checkstyle error if importing the wrong Element class (#13287) 10 years ago
.settings Do not add empty package javadoc for new classes 10 years ago
WebContent Integrate the Responsive add-on #12394 10 years ago
all Fixed nojavadoc parameter on "all" build. 10 years ago
build Revert "Theme Parser is deleted, build procedure now generates it (#13161)." 10 years ago
buildhelpers Remove dead code 10 years ago
checkstyle Trigger a checkstyle error if importing the wrong Element class (#13287) 10 years ago
client Use FQN instead of import for the bad Element class (#13287) 10 years ago
client-compiled Use more worker threads for widgetset compilation 10 years ago
client-compiler Avoid using toString method to access to SCSS serialized state (#9530). 10 years ago
eclipse Fixed broken launch configuration (#13053) 10 years ago
liferay Added dummy checkstyle and test targets to liferay module 10 years ago
push Update JQuery version for Atmosphere js 2.1.5.vaadin1 (#13374) 10 years ago
scripts Email author about merge failures 10 years ago
server Integrate the Responsive add-on #12394 10 years ago
shared Remove all unnecessary semicolons reported by Eclipse 10 years ago
tests/testbench/com/vaadin/tests/components Fix lost focus in Table when refreshing row cache (#12231) 10 years ago
theme-compiler Revert "Use Guava 16 which does not have compatibility issues" 10 years ago
themes Reduce Ivy resolver spam to a minimum (#12510) 10 years ago
uitest Use FQN instead of import for the bad Element class (#13287) 10 years ago
.classpath JUnit tests should be supported for shared (#13081) 10 years ago
.gitignore Revert "Theme Parser is deleted, build procedure now generates it (#13161)." 10 years ago
.project Removed Javascript buider and nature to avoid Eclipse choking on validating widgetset files (#9998) 11 years ago
README.md GWT requires max 1.6 compiler compliance level currently - #12345 10 years ago
build.properties Refactor OSGi manifest attribute handling to support import/export better (#9793) 11 years ago
build.xml Extracted integration-test target. 10 years ago
common.xml Trigger a checkstyle error if importing the wrong Element class (#13287) 10 years ago
gwt-files.xml Reformatted using Ant editor (#12040) 11 years ago
ivy-taskdefs.xml Formatted XML files using defined rules (#11956) 11 years ago
ivysettings-publish.xml Unified xml files to end with new line 10 years ago
ivysettings.xml Added liferay module for building liferay.zip #12748 10 years ago
pom-template.xml Unified xml files to end with new line 10 years ago
publish.properties Publish to SFTP (#9299) 11 years ago
publish.xml Merge branch '7.1' into testbench4 10 years ago

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

Install IvyDE

You’ll need the Apache Ivy plug-in for Eclipse to build the project later on, in “Compiling the Default Widget Set and Themes”.

  1. Go to Help -> Install New Software…
  2. Enter http://www.apache.org/dist/ant/ivyde/updatesite in the “Work with:” text field
  3. Select and install all items

If you have installed IvyDE via the Eclipse Marketplace previously, make sure that you also have Apache Ivy Ant Targets installed, which is not included in that IvyDE installation:

  1. Go to Help -> Install New Software…
  2. Click the hyperlink in the “What is already installed?” sentence near the bottom right-hand corner
  3. Verify that the list includes Apache Ivy Ant Tasks

If it isn’t included, follow the installation process above, but select only Apache Ivy library > Apache Ivy Ant Tasks

Set up the Workspace and define required variables for projects

  1. Open Window -> Preferences (Windows) or Eclipse -> Preferences (Mac)
  2. Go to General -> Workspace
    1. Set Text file encoding to UTF-8
    2. Set New text file line delimiter to Unix
  3. Go to General -> Workspace -> Linked Resources
  4. Add a new Path Variable GWT_ROOT referring to the gwt folder containing the gwt project GWT_ROOT
  5. Go to Java -> Build Path -> Classpath Variables
  6. 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
  7. Go to Java -> Compiler
    1. Check that the compliance level has been set to 1.6
  8. Go to XML -> XML Files -> Editor
    1. Ensure the settings are follows:
      Line width: 72
      Format comments: true
      Join lines: true
      Insert whitespace before closing empty end-tags: true
      Indent-using spaces: true
      Indentation size: 4
      

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.