[kune-commits] r1740 - trunk

Tue Mar 6 14:25:45 CET 2012

Author: vjrj_
Date: 2012-03-06 14:25:45 +0100 (Tue, 06 Mar 2012)
New Revision: 1740

Modified:
   trunk/DEV-GUIDE
   trunk/INSTALL
Log:
More doc

Modified: trunk/DEV-GUIDE
===================================================================

--- trunk/DEV-GUIDE	2012-03-05 21:11:54 UTC (rev 1739)
+++ trunk/DEV-GUIDE	2012-03-06 13:25:45 UTC (rev 1740)
@@ -72,6 +72,18 @@
 
 (*) Note: We actually use script/mvn-eclipse.sh instead of a simple 'mvn eclipse:eclipse' to hack a little bit the .classpath, because "mvn eclipse:eclipse" removes the GWT_CONTAINER line a the end of the .classpath. You can fix it from eclipse (anytime that we change the dependencies and you have to do a 'mvn eclipse:eclipse'), but we prefer to do it that way from the command line.
 
+====Configure Google GWT Plugin===
+
+For now we are using GWT 2.1.1 (not necessary match the one from the eclipse GWT plugin) so probably you have to download the SDK from:
+http://code.google.com/p/google-web-toolkit/downloads/list
+unzip, and add that SDK in Eclipse (Windows > Preferences > Google > Web Toolkit > Add). 
+
+Don't use other upper GWT SDK versions because our code (and dependencies) are not compatible with upper versions and we should do a coordinated migration.
+
+After that, right click Kune project in the PackageExplorer > Google > WebApplication > WAR directory: set to src/main/webapp and Uncheck the "Launch and deploy from this directory".
+
+Also in Kune project properties > Google > Web Toolkit > Check that you are using the 2.1.1 SDK. 
+
 ===UTF 8===
 
 The charset used in Kune is UTF8. In Eclipse, check the text-file enconding in Package Explorer > Preferences > Resource > Text file encoding.
@@ -124,13 +136,10 @@
 In /script directory exist two (mainly) launch configurations:
 - kune server via mvn.launch
 - kune client  -no-server.launch
-these configurations are eclipse run configurations that are normally imported by eclipse when you import the project (in GNU/Linux at least). See the Run and the Run External icon in the Eclipse toolbar to find these launchs. If is not there, try to import it: 
-http://help.eclipse.org/helios/topic/org.eclipse.jdt.doc.user/reference/wizards/ref-import_launch_configs.htm
+these configurations are eclipse run configurations that are normally imported by eclipse when you import the project (in GNU/Linux at least). See the Run and the Run External icon and menu options in the Eclipse toolbar to find these launchs. If is not there, try to import it (in Eclipse: File > Import > Launch Configurations > select the launchs from script directory). Also try to fix the path for the mvn command (especially Windows users). Other option is to create a new one launch to run a external "mvn exec:java" because the previous launch were created in GNU/Linux systems.
 
-Lauch the first to start the kune server (the first time that starts, will initialize the database). After that, launch the second to start kune in hosted mode and connect to the previous server, so you can make code modifications, and refresh the browser to see the changes. 
+Run it! Launch the first (it's equivalent to mvn exec:java) to start the kune server. After that, launch the second to start kune in hosted mode and connect to the previous server, so you can make code modifications, and refresh the browser to see the changes.
 
-Window users should create a kune server run external configuration to run "mvn exec:java" because the previous launch runs in GNU/Linux systems.
-
 ==== Optionally ==== 
 
 You can run the server via script/server.sh (also you can run server in debug mode, see TROUBLESHOOT or -h for help). This is quite useful to put breakpoints in the server code.

Modified: trunk/INSTALL
===================================================================
--- trunk/INSTALL	2012-03-05 21:11:54 UTC (rev 1739)
+++ trunk/INSTALL	2012-03-06 13:25:45 UTC (rev 1740)
@@ -93,7 +93,7 @@
 
 You can use other location (see kune.properties).
 
-Configurate hibernate-search (GNU/Linux instructions, look persistence.xml if you want to change indexes destination):
+Configurate hibernate/lucene indexes directories (these are GNU/Linux instructions, Windows developers: look and tune "hibernate.search.default.indexBase" variables in persistence.xml if you want to change indexes destination to other place):
  # yourUser is the user you are using to develop/run the application
  sudo mkdir -p /var/lib/kune/lucene/kune_dev/indexes
  sudo mkdir -p /var/lib/kune/lucene/kune_test/indexes


