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.
Artur Signell 8d7783b4e9 API refactoring (#7749) пре 9 година
.settings Disable automatic removal of trailing whitespace and reformatted using Luna пре 9 година
WebContent Removed packages starting with a digit from export-package (#15105) пре 9 година
all Remove theme-compiler and replace with external vaadin-sass-compiler пре 10 година
build Update GWT to 2.7.0.beta1vaadin1. пре 9 година
buildhelpers Removed packages starting with a digit from export-package (#15105) пре 9 година
checkstyle Ignore irrelevant header lines in checkstyle configuration пре 10 година
client Delayed column layouting is visible (#15189) пре 9 година
client-compiled Disable closure compiler (#13778) пре 10 година
client-compiler Update GWT to 2.7.0.beta1vaadin1. пре 9 година
eclipse Update GWT to 2.7.0.beta1vaadin1. пре 9 година
gwt replaced all org.json.* usages with elemental.json.* (#8942) пре 9 година
liferay Added dummy checkstyle and test targets to liferay module пре 10 година
push Update atmosphere-runtime to 2.1.2.vaadin6. (#14674, #14861) пре 9 година
scripts Script for replacing all empty @since tags with a given version пре 9 година
server API refactoring (#7749) пре 9 година
shared VBrowserDetails fails to detect Android when using Firefox (#15183) пре 9 година
tests/testbench/com/vaadin/tests/components Update copyright year to 2014 пре 10 година
themes Fix themes build script not to overwrite all theme files on every iteration. (#14575) пре 9 година
uitest Some fixes to potus demo (#7749) пре 9 година
.classpath Fix super dev mode launch (#14443) пре 9 година
.gitignore Ignore compiled valo test themes пре 9 година
.project Removed Javascript buider and nature to avoid Eclipse choking on validating widgetset files (#9998) пре 11 година
LICENSE Add LICENSE file according to GitHub conventions пре 9 година
README.md Add link to IDEA workspace instructions. пре 9 година
build.properties Update to GWT 2.7.0 (#14522) пре 9 година
build.xml Extracted integration-test target. пре 10 година
common.xml Do not create default instances while reading designs (#7749) пре 9 година
gwt-files.xml Update to GWT 2.7.0 (#14522) пре 9 година
ivy-taskdefs.xml Formatted XML files using defined rules (#11956) пре 11 година
ivysettings-publish.xml Unified xml files to end with new line пре 10 година
ivysettings.xml Remove theme-compiler and replace with external vaadin-sass-compiler пре 10 година
pom-template.xml Change Sonatype URLs to https. пре 9 година
publish.properties Publish to SFTP (#9299) пре 11 година
publish.xml Merge branch '7.1' into testbench4 пре 10 година

README.md

Vaadin

Vaadin is a Java framework for building modern web applications that look great, perform well and make you and your users happy.

For instructions about using Vaadin to develop applications, please refer to https://vaadin.com/learn

To contribute, first refer to https://vaadin.com/wiki/-/wiki/Main/Contributing+Code for general instructions and requirements for contributing code to the Vaadin framework.

Instructions on how to set up a working environment for developing the Vaadin framework follow below.

Quick Setup

  1. git clone https://github.com/vaadin/vaadin.git
  2. Install IvyDE, including Ant Tasks, if needed (http://www.apache.org/dist/ant/ivyde/updatesite)
  3. Import the project into Eclipse
  4. Run build/ide.xml in Eclipse

For more details, see below

Cloning the project repositories

The Vaadin repository can be cloned using

git clone https://github.com/vaadin/vaadin.git

or using your favorite Git tool.

If using Windows, you might want to add these Git settings: core.autocrlf=false and core.fileMode=false.

Setting up Eclipse to Develop Vaadin 7

Start Eclipse

Start Eclipse with the workspace you would like to use. It is usually a good idea to use the parent folder of the Git repository as the workspace folder.

Install IvyDE

You’ll need the Apache Ivy plug-in for Eclipse to build the project:

  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 Tasks 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
  4. If it isn’t included, follow the installation process above, but select only Apache Ivy library > Apache Ivy Ant Tasks

Import the Project into the Workspace

  1. Do File -> Import -> General -> Existing Projects into Workspace ImportProject
  2. Select the vaadin folder (where you cloned the project)
  3. Ensure the vaadin project is checked
  4. Click “finish” to complete the import of Vaadin Framework

The project should compile without further configuration. If the project does not compile without errors, choose Ivy -> Resolve from the vaadin project popup menu to ensure all dependencies have been resolved.

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

Set up extra workspace preferences

The following preferences need to be set to keep the project consistent. You need to do this especially to be able to contribute changes to the project.

  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 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
      

Running a UI test

The vaadin project includes an embedded Jetty (com.vaadin.launcher.DevelopmentServerLauncher) which is used for running the UI tests. In Eclipse you can launch it using the included launch configuration: Right click on *eclipse/Development Server (vaadin).launch” and select Debug As -> Development Server (vaadin).

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 (Use ?restartApplication to ensure the correct UI is shown).

Running JUnit tests

The unit tests for the projects can be run using

ant test

Note that the included Vaadin TestBench (browser) tests require access to a TestBench cluster, currently only available internally at Vaadin Ltd.

Building a package

The distribution files can be built in two steps.

  1. Unpack required gwt jars into the project
    ant -f gwt-files.xml unpack.gwt
  2. Build the project by running
    ant
    in the project root directory (add -Dvaadin.version=1.2.3 to use a specific version number).

Setting up other IDEs to Develop Vaadin 7