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.
Ilia Motornyi ef306c16f5 Revert "Better default for nullRepresentation (#13221, #12877)" hace 8 años
.settings Convert Eclipse project to Maven based hace 8 años
all Revert "Documentation fix for null representation (#13221)" hace 8 años
bom Move organization, license and SCM to parent POM hace 8 años
buildhelpers Move checkstyles plugin to actual modules hace 8 años
checkstyle Relax checkstyle rules hace 8 años
client Take body scrolling into account when deciding combobox popup position (#19162) hace 8 años
client-compiled Compile default widgetset with maven plugin, fix unit cache hace 8 años
client-compiler Move checkstyles plugin to actual modules hace 8 años
documentation added one missing "you" hace 8 años
eclipse Remove obsolete launch files hace 8 años
liferay Final working configuration for nexus staging plugin hace 8 años
push Move organization, license and SCM to parent POM hace 8 años
scripts Remove duplicate link, improve tag script variable ordering hace 8 años
server Revert "Better default for nullRepresentation (#13221, #12877)" hace 8 años
shared Move checkstyles plugin to actual modules hace 8 años
themes Restrict grid sidebar size to visible viewport (#19349) hace 8 años
uitest Revert "Better default for nullRepresentation (#13221, #12877)" hace 8 años
widgets Move checkstyles plugin to actual modules hace 8 años
.classpath Convert Eclipse project to Maven based hace 8 años
.gitignore Ignore files generated for checkstyles hace 8 años
.project Convert Eclipse project to Maven based hace 8 años
LICENSE Specify the license of the documentation in the LICENSE file. hace 8 años
README.md Fix README.md hace 8 años
build.properties Convert Eclipse project to Maven based hace 8 años
common.xml Run checkstyle with Maven hace 8 años
ivy-taskdefs.xml Use Maven to build vaadin-push hace 8 años
ivysettings.xml Use parameter for uitest Ivy repository hace 8 años
pom-template.xml Use vaadin-parent as parent in POMs (#17300) hace 9 años
pom.xml Move checkstyles plugin to actual modules hace 8 años

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 Contributing Code for general instructions and requirements for contributing code to the Vaadin framework.

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

Eclipse Quick Setup

  1. Run git clone https://github.com/vaadin/vaadin.git command or clone the repository your favorite Git tool. If using Windows, you might want to add these Git settings: core.autocrlf=false and core.fileMode=false.
  2. Run mvn install in the project root. Note that the first compilation takes a while to finish as maven downloads dependencies used in the projects.
  3. 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.
  4. Import the project into Eclipse as a maven project. Use File -> Import -> Maven -> Existing Maven Projects.
  5. Select the vaadin folder (where you cloned the project)
  6. Click “Finish” to complete the import of Vaadin Framework

Now the project should compile without further configuration.

Compiling the Default Widget Set and Themes

  • Compile the default widgetset by running install maven goal in vaadin-client-compiled module root. In Eclipse this is done by right clicking on vaadin-client-compiled project it and choosing Run As -> Maven Build….
  • Compile the default themes by running install maven goal in vaadin-themes module root. In Eclipse this is done by right clicking on vaadin-themes project it and choosing Run As -> Maven Build….

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

  1. In a Project Explorer right-click vaadin-uitest
  2. Open Run As -> Maven build…
  3. Type in jetty:run-exploded into Goals and click Run
  4. Open URL http://localhost:8080/run/

Building a package

The distribution files can be built by running maven goal

maven clean install
in the project root directory.

To use a specific version number, modify <version> tag in root pom.xml file. This goal runs all project tests TestBench tests, which require access to a a TestBench cluster, currently only available internally at Vaadin Ltd.

Setting up IntelliJ IDEA to Develop Vaadin 7

  1. Intall and run IDEA. Ultimate Edition is better but Community Edition should also work.
  2. Ensure if Git and Maven plugins are installed, properly configured and enabled.
  3. Clone the repository, using menu VCS -> Checkout from Version Control -> Git -> Git Repository URL -> https://github.com/vaadin/vaadin.git. When the repository is cloned, do NOT open it as a project.
  4. Open cloned repository as a maven object. Use File -> Open and choose root pom.xml file
  5. Have a coffee break while IDEA is loading dependencies and indexing the project
  6. Run Maven targets clean and install using Maven Projects tool window to compile the whole project

Running a UI test

  1. Open Maven Projects
  2. Open vaadin-uitest -> Plugins -> jetty -> jetty:run-exploded
  3. Open URL http://localhost:8080/run/