[sikuli] 25/385: Update README.md

[Gilles Filippini]

This is an automated email from the git hooks/post-receive script.

pini pushed a commit to tag upstream/1.1.0_beta1
in repository sikuli.

commit fca694c611fe2eeff0fd2825264faa122016fcb6
Author: Raimund Hocke <rmhdevelop at me.com>
Date:   Thu Dec 26 10:07:02 2013 +0100

    Update README.md
---
 README.md | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/README.md b/README.md
index 39fbd18..02b94ca 100644
--- a/README.md
+++ b/README.md
@@ -63,7 +63,7 @@ Each folder (module) in this repo is a Maven project by itself with its own POM,
 Usage - basic information
 -------------------------
 
-If you intend to compile and build the modules after having downloaded this repo, you need a valid Maven 3 installation and some IDE, that is enabled for working with Maven projects. <br />(I myself use NetBeans 7.4, which supports Maven by default)
+If you intend to compile and build the modules after having downloaded this repo, you need a valid Maven 3 installation and for editing, testing and integration some IDE, that is enabled for working with Maven projects. <br />(I myself use NetBeans 7.4, which supports Maven by default)
 
 **Take care** Even if you only want to work on one of the modules (e.g. API), the modules should not be moved around, but stay in the structure of the downloaded repo. Each module depends on the parent POM in the root and the ready-to-use-jar-production POMs additionally on the assembly descriptors plain.xml and complete.xml.
 
@@ -81,11 +81,12 @@ If you want jars containing the sources of the respective modules and/or contain
 
 **--- Basic compile/package/install for each module**
 
-You have 2 options, to selectively run the POM of a specific module alone:
+You have 3 options, to selectively run the POM of a specific module alone:
  1. in the root folder run<br />`mvn -pl<ModuleName> [clean] [compile|package|install]` <br />where `<ModuleName>` is the respective folder name
  2. in the module's folder run <br />`mvn [clean] [compile|package|install]`
+ 3. use the respective build steps in your IDE being in one of the module projects
 
-where you might additionally use the above mentioned profile switches
+You might additionally use the above mentioned profile switches.
 
 **--- How to produce the ready to use jars ...**
 

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-java/sikuli.git