Nelze vybrat více než 25 témat Téma musí začínat písmenem nebo číslem, může obsahovat pomlčky („-“) a může být dlouhé až 35 znaků.
Marko Grönroos 2bae222b0c Removed mention of an outdated formatting trick. Also some wording and formatting fixes, as well as cleanup. před 8 roky
.settings Disable automatic removal of trailing whitespace and reformatted using Luna před 9 roky
WebContent Grid sidebar menu design changed. See design document and comments at trac ticket. (#18325) před 8 roky
all Fix build scripts for BOM (#17025) před 9 roky
bom Build Maven BOM for Vaadin (#17025) před 9 roky
build Avoid on-the-fly compilation when running tests (#15135) před 9 roky
buildhelpers Fix release notes query url to use https. před 9 roky
checkstyle Ignore irrelevant header lines in checkstyle configuration před 10 roky
client Prevent scrolling when expanding a TreeTable item (#18247) před 8 roky
client-compiled Always include default widget set files in OSGi manifest (#16993) před 9 roky
client-compiler Replaced HashMaps with TreeMaps to keep the same order (#14736) před 8 roky
documentation Removed mention of an outdated formatting trick. Also some wording and formatting fixes, as well as cleanup. před 8 roky
eclipse Reserve enough memory so SDM can be run for more than one browser před 8 roky
gwt replaced all org.json.* usages with elemental.json.* (#8942) před 9 roky
liferay Added dummy checkstyle and test targets to liferay module před 10 roky
push Provide compressed vaadinPush.js (#18329) před 8 roky
scripts Basic tagging commands in staging report před 8 roky
server Use latest GAE SDK supporting Java 6 před 8 roky
shared Add @since for change 11526 ticket #17590 před 8 roky
tests/testbench/com/vaadin/tests/components Update copyright year to 2014 před 10 roky
themes Include compressed themes (#18332) před 8 roky
uitest Use latest GAE SDK supporting Java 6 před 8 roky
widgets Add missing ComputedStyle.java to vaadin-widgets (#18414) před 8 roky
.classpath Add widgets-module to Eclipse (#15544) před 9 roky
.gitignore Ignore .pyc files před 8 roky
.project Removed Javascript buider and nature to avoid Eclipse choking on validating widgetset files (#9998) před 11 roky
LICENSE Add LICENSE file according to GitHub conventions před 9 roky
README.md Add link to IDEA workspace instructions. před 9 roky
build.properties Update to GWT version 2.7.0.vaadin3. před 9 roky
build.xml Build Maven BOM for Vaadin (#17025) před 9 roky
common.xml Fix build scripts for BOM (#17025) před 9 roky
gwt-files.xml Don't include elemental in vaadin-server.jar (#15558) před 9 roky
ivy-taskdefs.xml Formatted XML files using defined rules (#11956) před 11 roky
ivysettings-publish.xml Unified xml files to end with new line před 10 roky
ivysettings.xml Build Maven BOM for Vaadin (#17025) před 9 roky
pom-template.xml Use vaadin-parent as parent in POMs (#17300) před 9 roky
publish.properties Publish to SFTP (#9299) před 11 roky
publish.xml Fix publishing of POM-only modules (#17025) před 9 roky

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