summaryrefslogtreecommitdiffstats
path: root/README.md
diff options
context:
space:
mode:
authorOlli Tietäväinen <ollit@vaadin.com>2017-11-10 15:59:13 +0200
committerPéter Török <31210544+torok-peter@users.noreply.github.com>2017-11-10 15:59:13 +0200
commitfe2b4d941fdfe06fbb79d3e9168618592136c337 (patch)
tree0f3f03cab8453fea579c2571d0d5a01e76d66a38 /README.md
parent8e14349e53c73e75c380ccd8405bb2c2ef9d51e6 (diff)
downloadvaadin-framework-fe2b4d941fdfe06fbb79d3e9168618592136c337.tar.gz
vaadin-framework-fe2b4d941fdfe06fbb79d3e9168618592136c337.zip
Update README.md (#10302)
Diffstat (limited to 'README.md')
-rw-r--r--README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/README.md b/README.md
index 9dac32941f..5d3aa500cf 100644
--- a/README.md
+++ b/README.md
@@ -23,7 +23,7 @@ If using Windows, you might want to add these Git settings: `core.autocrlf=false
Note that the first compilation takes a while to finish as maven downloads dependencies used in the projects.
1. 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.
1. Import the project into Eclipse as a maven project. Use *File* -> *Import* -> *Maven* -> *Existing Maven Projects*.
-1. Select the *vaadin* folder (where you cloned the project)
+1. Select the *framework* folder (where you cloned the project)
1. Click “Finish” to complete the import of Vaadin Framework
Now the project should compile without further configuration.