Skip to content
This repository
Browse code

remove extra logging & Update README

  • Loading branch information...
commit b2c1404d6e0ea1e7afe5377a0c9eb95d3dc3f137 1 parent 0414916
Mostafa Eweda mostafaeweda authored
73 plugins-client/ext.javalanguage/README.md
Source Rendered
@@ -2,83 +2,58 @@
2 2
3 3 ## Installation
4 4
5   -1- Install sun java 1.6 on your machine
  5 +1- Install sun-java6-jdk on your machine and ant to build from source code.
6 6
7   -2- install ant to build dependency projects from java source code
8   -
9   -3- Build the java debug project:
  7 +2- Build the java debug project:
10 8
11 9 $ cd node_modules/lib-javadebug && npm install && ant
12 10
13   -You may want to change the log file location in bin/log4j.properties instead of log/cloud9-java-debug.log to somewhere else
14   -
15   -4- Run the java debug daemon
  11 +3- Run the java debug daemon
16 12
17 13 $ java -cp bin/:lib/commons-logging-1.1.1.jar:lib/log4j-1.2.16.jar:lib/tools.jar com.cloud9ide.debug.daemon.Cloud9Daemon
18 14
19 15 The debug is now ready for cloud9 debug connections
20 16
21   -5- Build the jvm-run sub projects:
  17 +4- Build the jvm-run sub projects:
22 18
23 19 $ cd node_modules/jvm-run && && ant
24 20
25   -5- Download eclipse hellios sr2 for your platform and extract it somewhere
26   -
27   -6-
28   -
29   - $ cd node_modules/jvm_features && npm install
30   -
31   -7- Initial build and run for the eclipse plugin:
  21 +5- Download eclipse hellios sr2 - j2ee version - for your platform and extract it somewhere.
32 22
33   -a- Start eclipse into any workspace
  23 +6- Set C9_PATH and ECLIPSE_PATH environment variables to the location of your cloud9 folder and the location of your eclipse installation folder respectively.
34 24
35   -b- select File -> Import -> Existing project into workspace
  25 +In linux you can do
  26 + $ echo "export C9_PATH=/Users/eweda
  27 + export ECLIPSE_PATH=/Users/eweda/workspace/eclipse-hellios" >> ~/.bashrc && source ~/.bashrc
36 28
37   -c- Select the project: cloud9/node_modules/jvm_features
  29 +On MacOSX, you can do
  30 + $ echo "export C9_PATH=/Users/eweda
  31 + export ECLIPSE_PATH=/Users/eweda/workspace/eclipse-hellios" >> ~/.profile && source ~/.profile
38 32
39   -d- Wait few seconds for eclipse to import the project (no compile errors should be found)
  33 +7- Build the plugin
40 34
41   -e- Click Run as -> Eclipse application
  35 + $ cd node_modules/jvm_features
  36 + $ java -jar $ECLIPSE_PATH/plugins/org.eclipse.equinox.launcher_1.1.1.R36x_v20101122_1400.jar -application org.eclipse.ant.core.antRunner
42 37
43   -f- you should see:
44   -
45   - >>> STARTED
  38 +Ref: [Eclipse plugin headless build](http://eclipse.dzone.com/articles/headless-build-beginners-part)
46 39
47   -8- Open the init config file is: cloud9/node_modules/jvm_features/js/lib/eclipse/config.js and change paths according to your eclipse installation
  40 +b-
  41 + $ rm -f $ECLIPSE_PATH/plugins/CodeCompletePlugin*
  42 + $ cp CodeCompletePlugin* $ECLIPSE_PATH/plugins
48 43
49   -a- Change the path of the equinox launcher jar to your eclipse installation equivalent:
50   -${eclipse-installation-path}\plugins\org.eclipse.equinox.launcher_${version}${qualifier}.jar
  44 +c- test it with:
51 45
52   -b- Change the -configuration and -dev attributes according to your last (in or outside eclipse) values
  46 + $ java -Dosgi.requiredJavaVersion=1.5 -XX:MaxPermSize=256m -Xms40m -Xmx512m -cp $ECLIPSE_HOME/plugins/org.eclipse.equinox.launcher_1.1.1.R36x_v20101122_1400.jar org.eclipse.equinox.launcher.Main -application CodeCompletePlugin.Cloud9Eclipse -data ~/jvm_workspace -consoleLog
53 47
54   ---> for me from inside eclipse, it was:
  48 +8- Open the init config file in: cloud9/node_modules/jvm_features/js/lib/eclipse/config.js
55 49
56   --configuration file:/Users/eweda/workspace/eclipse-workspace/.metadata/.plugins/org.eclipse.pde.core/CodeCompletePlugin.Cloud9Eclipse/ -dev file:/Users/eweda/workspace/eclipse-workspace/.metadata/.plugins/org.eclipse.pde.core/CodeCompletePlugin.Cloud9Eclipse/dev.properties
  50 +* Remove the -configuration and -dev attributes
57 51
58 52 Now, the full java stack SHOULD BE ready for testing :)
59 53
60   -## Totally headless installaton (production environment) (NOT WORKING YET)
61   -
62   -Replace step 7 with
63   -
64   -7-
65   -
66   -a- build the plugin jar file
67   -
68   - $ java -jar ${eclipse-installation-path}\plugins\org.eclipse.equinox.launcher_${version}${qualifier}.jar -application org.eclipse.ant.core.antRunner -buildfile ${cloud9 absolute path}/node_modules/jvm_features/build.xml
69   -
70   -For me it was:
71   -
72   - $ java -jar /media/DATA/COLLEGE/IDEs/eclipse-linux-jee-helios-SR2/plugins/org.eclipse.equinox.launcher_1.1.1.R36x_v20101122_1400.jar -application org.eclipse.ant.core.antRunner -buildfile /home/eweda/cloud9/node_modules/jvm_features/build.xml
73   -
74   -Ref: [Eclipse plugin headless build](http://eclipse.dzone.com/articles/headless-build-beginners-part)
75   -
76   -b- Copy CodeComplePlugin...jar to ${eclipse-path}/plugins/
77   -
78   -
79 54 ## More files to care about
80 55 * cloud9/node_modules/jvm-run/build-tools/templates/j2ee-template/build.xml --> absoulte jetty location
81   -* cloud9/node_modules/jvm_features/js/lib/eclipse/config.js --> init command tweaking
  56 +* cloud9/node_modules/jvm_features/js/lib/eclipse/config.js --> init command
82 57
83 58 ## TODOs
84 59
1  plugins-server/cloud9.process-manager/process_manager.js
@@ -132,7 +132,6 @@ var ProcessManager = module.exports = function(runners, eventEmitter) {
132 132 };
133 133
134 134 this.debug = function(pid, debugMessage, callback) {
135   - console.log('\r\nPM debug: ', pid);
136 135 var child = this.processes[pid];
137 136 if (!child || !child.pid)
138 137 return callback("Process is not running: " + pid);

0 comments on commit b2c1404

Please sign in to comment.
Something went wrong with that request. Please try again.