選択できるのは25トピックまでです。 トピックは、先頭が英数字で、英数字とダッシュ('-')を使用した35文字以内のものにしてください。
Tatu Lund 3b5d228c31
chore: Update dependencies (#12493)
2年前
.settings Convert Eclipse project to Maven based 8年前
all Cleaned out old references to removed buildhelpers module. (#12384) 2年前
bom deprecate vaadin-snapshot (v7) (#12407) 2年前
checkstyle Update copyright year (#12243) 3年前
client Applied save actions to Grid client-side classes. (#12388) 2年前
client-compiled Remove buildhelpers module and dependencies to it (#12280) 3年前
client-compiler Update links shown by license checker (#12403) 2年前
documentation Add a missing letter (#11677) 4年前
eclipse Remove obsolete launch files 8年前
liferay Format project pom files using correct settings (4 spaces) 7年前
push Format project pom files using correct settings (4 spaces) 7年前
scripts update the failed build checking (#12439) 2年前
server chore: Update dependencies (#12493) 2年前
shared Update copyright year (#12243) 3年前
test Small updates to servlet container test setup. (#12318) (#12447) 2年前
tests Fix validation build to work with new build agents (#11054) 5年前
themes Remove buildhelpers module and dependencies to it (#12280) 3年前
uitest Chrome 95 screenshot test fixes (#12495) 2年前
widgets Remove buildhelpers module and dependencies to it (#12280) 3年前
.classpath Convert Eclipse project to Maven based 8年前
.gitignore Cleaned out old references to removed buildhelpers module. (#12384) 2年前
.gitmodules Add screenshots as a Git submodule (#86) 7年前
.project Convert Eclipse project to Maven based 8年前
LICENSE Change license from Apache-2 to CVDLv4 (#12144) 3年前
README.md Run devserver under IDEA via maven target (#11152) 5年前
build.properties Upgrade GWT version 7年前
common.xml Run checkstyle with Maven 8年前
ivy-taskdefs.xml Use Maven to build vaadin-push 8年前
ivysettings.xml Cleaned out old references to removed buildhelpers module. (#12384) 2年前
pom-template.xml deprecate vaadin-snapshot (v7) (#12407) 2年前
pom.xml chore: Update dependencies (#12493) 2年前

README.md

Vaadin Framework

Vaadin Framework allows you to build modern web apps efficiently in plain Java, without touchking low level web technologies.

For instructions about using Vaadin to develop applications, please refer to Vaadin tutorial and other documentation.

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.

Building a package

The distribution files can be built by running the standard Maven goal mvn install in the project root.

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/

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 specific UI test

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

Running a Development Server

  1. Open Run menu and click Edit Configurations
  2. Click green + sign at top left corner, select Maven from popup
  3. In the run configuration page, set any name for the configuration, select vaadin-uitest project folder as Working directory
  4. Type exec:exec@run-development-server into Command line and save the configuration
  5. Run the configuration and open URL http://localhost:8888/run/<testUI>

Running a Development Server in a debug mode

  1. Type exec:exec@debug-development-server into Command line and save the configuration
  2. In the same dialog, create new “Remote” debug configuration, using localhost and Port 5005
  3. Start both configurations and open URL http://localhost:8888/run/<testUI>