Thanks Alexander, Ill try to debug from my end too.
Regards Awanthika Awanthika Senarath Software Engineer, WSO2 Inc. Mobile: +94717681791 On Wed, Feb 3, 2016 at 12:47 PM, Alexander Garagatyi <agaraga...@codenvy.com > wrote: > Thank you. > About current failure you've got. I don't know where the problem is right > now. I need some time to investigate. > > On Wed, Feb 3, 2016 at 4:56 AM, Awanthika Senarath <awanth...@wso2.com> > wrote: > >> Hello Alexander, >> >> I have created the issues [1] [2] and [3] >> >> >> Regards >> Awanthika >> >> >> [1] https://github.com/codenvy/che/issues/260 >> >> [2] https://github.com/codenvy/che/issues/261 >> >> [3] https://github.com/codenvy/che/issues/262 >> <https://github.com/codenvy/che/issues/262> >> >> Awanthika Senarath >> Software Engineer, WSO2 Inc. >> Mobile: +94717681791 >> >> >> >> On Tue, Feb 2, 2016 at 6:54 PM, Awanthika Senarath <awanth...@wso2.com> >> wrote: >> >>> Still when I try to create a project it fails with the following >>> exception, >>> >>> Creating machine [ws = workspacec3uqzvrq98trmwr5: env = wksp-vo1e: >>> machine = ws-machine] >>> Exception in thread "WorkspaceManager-0" java.lang.RuntimeException: >>> java.lang.IllegalArgumentException: protocol = http host = null >>> at >>> sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1455) >>> at >>> sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1441) >>> at >>> sun.net.www.protocol.http.HttpURLConnection.getHeaderField(HttpURLConnection.java:2979) >>> at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:489) >>> at >>> org.eclipse.che.api.core.rest.DefaultHttpJsonRequest.doRequest(DefaultHttpJsonRequest.java:225) >>> at >>> org.eclipse.che.api.core.rest.DefaultHttpJsonRequest.request(DefaultHttpJsonRequest.java:136) >>> at >>> org.eclipse.che.api.machine.server.WsAgentLauncherImpl.pingWsAgent(WsAgentLauncherImpl.java:122) >>> at >>> org.eclipse.che.api.machine.server.WsAgentLauncherImpl.startWsAgent(WsAgentLauncherImpl.java:95) >>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >>> at >>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) >>> at >>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) >>> at java.lang.reflect.Method.invoke(Method.java:497) >>> at >>> com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:50) >>> at com.sun.proxy.$Proxy52.startWsAgent(Unknown Source) >>> at >>> org.eclipse.che.api.machine.server.MachineManager.createInstance(MachineManager.java:370) >>> at >>> org.eclipse.che.api.machine.server.MachineManager.createMachine(MachineManager.java:337) >>> at >>> org.eclipse.che.api.machine.server.MachineManager.createMachineSync(MachineManager.java:168) >>> at >>> org.eclipse.che.api.workspace.server.RuntimeWorkspaceRegistry.createMachine(RuntimeWorkspaceRegistry.java:451) >>> at >>> org.eclipse.che.api.workspace.server.RuntimeWorkspaceRegistry.startEnvironment(RuntimeWorkspaceRegistry.java:319) >>> at >>> org.eclipse.che.api.workspace.server.RuntimeWorkspaceRegistry.start(RuntimeWorkspaceRegistry.java:145) >>> at >>> org.eclipse.che.api.workspace.server.WorkspaceManager.performSyncStart(WorkspaceManager.java:642) >>> at >>> org.eclipse.che.api.workspace.server.WorkspaceManager.lambda$performAsyncStart$9(WorkspaceManager.java:613) >>> at >>> org.eclipse.che.commons.lang.concurrent.CopyThreadLocalRunnable.run(CopyThreadLocalRunnable.java:28) >>> at >>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) >>> at >>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) >>> at java.lang.Thread.run(Thread.java:745) >>> Caused by: java.lang.IllegalArgumentException: protocol = http host = >>> null >>> at sun.net.spi.DefaultProxySelector.select(DefaultProxySelector.java:176) >>> at >>> sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1099) >>> at >>> sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:999) >>> at >>> sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:933) >>> at >>> sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1513) >>> at >>> sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1441) >>> at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480) >>> ... 22 more >>> >>> >>> Awanthika Senarath >>> Software Engineer, WSO2 Inc. >>> Mobile: +94717681791 >>> >>> >>> >>> On Tue, Feb 2, 2016 at 6:52 PM, Awanthika Senarath <awanth...@wso2.com> >>> wrote: >>> >>>> thanks for the explanation Alexander, >>>> >>>> It worked after I exported the JAVA_HOME. JAVA_HOME was declared but >>>> not exported in the bashrc file. >>>> >>>> I will create the issues. >>>> >>>> Regards >>>> Awanthika >>>> >>>> Awanthika Senarath >>>> Software Engineer, WSO2 Inc. >>>> Mobile: +94717681791 >>>> >>>> >>>> >>>> On Tue, Feb 2, 2016 at 6:24 PM, Alexander Garagatyi < >>>> agaraga...@codenvy.com> wrote: >>>> >>>>> Would appreciate a clarification on this as your docs are a bit >>>>>> confusing :) >>>>> >>>>> Please create an issue on github. >>>>> >>>>> Is this correct? Do I need to create a docker image for Che to create >>>>>> the workspace in? >>>>>> >>>>> It is correct. You don't have to do anything else with docker. >>>>> >>>>> when we have the USE_DOCKER parameter false Che is not starting with >>>>>> docker? In that case is Che using the local file system of the machine? >>>>>> >>>>>> if not What is that parameter being used for? >>>>>> >>>>> when USE_DOCKER is false Che runs on localhost, but workspaces are >>>>> still in docker containers. >>>>> when USE_DOCKER is true Che runs in docker container, and workspaces >>>>> are in docker containers inside container where Che runs. It is called >>>>> dind >>>>> - docker in docker. >>>>> >>>>> Your script failed because it was not able to detect JAVA_HOME >>>>> variable. Please check that it is set and exported. e.g. >>>>> *export JAVA_HOME=/my/path/to/java/folder* >>>>> in ~/.bashrc file >>>>> >>>>> >>>>> On Tue, Feb 2, 2016 at 1:14 PM, Awanthika Senarath <awanth...@wso2.com >>>>> > wrote: >>>>> >>>>>> Hello Alexander, >>>>>> >>>>>> output is at [1]. >>>>>> >>>>>> Would appreciate a clarification on this as your docs are a bit >>>>>> confusing :) >>>>>> >>>>>> All I have done prior to running Che is installing docker. I did not >>>>>> install any images in docker or configure docker other than adding my >>>>>> user >>>>>> into docker user group. >>>>>> >>>>>> Is this correct? Do I need to create a docker image for Che to create >>>>>> the workspace in? >>>>>> >>>>>> If not how does Che create the workspace in docker when we start it >>>>>> with ./che.sh run ? >>>>>> >>>>>> when we have the USE_DOCKER parameter false Che is not starting with >>>>>> docker? In that case is Che using the local file system of the machine? >>>>>> >>>>>> if not What is that parameter being used for? >>>>>> >>>>>> >>>>>> thanks in advance! >>>>>> >>>>>> Regards >>>>>> Awanthika >>>>>> >>>>>> >>>>>> [1] >>>>>> >>>>>> Docker is natively installed and reachable... >>>>>> >>>>>> ############## HOW TO CONNECT YOUR CHE CLIENT ############### >>>>>> After Che server has booted, you can connect your clients by: >>>>>> 1. Open browser to http://localhost:8080, or: >>>>>> 2. Open native chromium app. >>>>>> ############################################################# >>>>>> >>>>>> >>>>>> JAVA_HOME is not set. Please set to directory of JVM or JRE. >>>>>> >>>>>> Looks like something went wrong. Possible issues: >>>>>> 1. (Win | Mac) VirtualBox not installed ==> Rerun Docker >>>>>> Toolbox installation >>>>>> 2. (Win | Mac) Docker Machine not installed ==> Rerun Docker >>>>>> Toolbox installation >>>>>> 3. (Win | Mac) Docker is not reachable ==> Docker VM >>>>>> failed to start >>>>>> 4. (Win | Mac) Docker ok, but docker ps fails ==> Docker >>>>>> environment variables not set properly >>>>>> 5. (Linux) Docker is not reachable ==> Install: wget >>>>>> -qO- https://get.docker.com/ | sh >>>>>> 6. (Linux) Permissions not properly set ==> Che must run >>>>>> as UID 1000 with user in docker group >>>>>> 7. Could not find the Che app server ==> Did /tomcat >>>>>> get moved away from CHE_HOME? >>>>>> 8. Wrong version of Java found ==> Che requires >>>>>> Java 1.8 >>>>>> 9. Did you use the right parameter syntax? ==> See usage >>>>>> >>>>>> We have seen issues with VirtualBox on Windows where your VM gets >>>>>> corrupted when your computer is >>>>>> suspended while the VM is still running. This will appear as SSH or >>>>>> ethernet connection issues. This is >>>>>> rare, but if encountered, current known solution is to uninstall >>>>>> VirtualBox and Docker Toolbox, and then >>>>>> reinstall. >>>>>> >>>>>> Che Environment Variables: >>>>>> (REQUIRED) JAVA_HOME ==> Location of >>>>>> Java runtime >>>>>> (REQUIRED: WIN|MAC) DOCKER_TOOLBOX_INSTALL_PATH ==> Location of >>>>>> Docker Toolbox >>>>>> (REQUIRED: WIN|MAC) VBOX_MSI_INSTALL_PATH ==> Location of >>>>>> VirtualBox >>>>>> (OPTIONAL) CHE_HOME ==> Directory >>>>>> where Che is installed >>>>>> (OPTIONAL) CHE_LOCAL_CONF_DIR ==> Directory with >>>>>> custom Che .properties files >>>>>> (OPTIONAL) CHE_LOGS_DIR ==> Directory for >>>>>> Che output logs >>>>>> (OPTIONAL) CHE_DOCKER_MACHINE_NAME ==> (Win | Mac) >>>>>> Name of VM created by docker-machine >>>>>> (OPTIONAL) DOCKER_MACHINE_HOST ==> (Linux) Docker >>>>>> host IP - set if browser clients remote >>>>>> >>>>>> Usage: >>>>>> che [OPTIONS] [run | start | stop] >>>>>> -i, --image Launches Che within a Docker container >>>>>> using latest image >>>>>> -i:tag, --image:tag Launches Che within a Docker container >>>>>> using specific image tag >>>>>> -p:port, --port:port Port that Che server will use for HTTP >>>>>> requests; default=8080 >>>>>> -r:ip, --remote:ip If Che clients are not localhost, set >>>>>> to IP address of Che server >>>>>> -g, --registry Launch Docker registry as a container >>>>>> (used for ws snapshots) >>>>>> -m:vm, --machine:vm For Win & Mac, sets the docker-machine >>>>>> VM name to vm; default=default >>>>>> -s:client, --skip:client Do not print browser client connection >>>>>> information >>>>>> -s:uid, --skip:uid Do not enforce UID=1000 for Docker >>>>>> -h, --help Show this help >>>>>> -d, --debug Use debug mode (prints command line >>>>>> options + app server debug) >>>>>> run Starts Che application server in current >>>>>> console >>>>>> start Starts Che application server in new >>>>>> console >>>>>> stop Stops Che application server >>>>>> >>>>>> The -r flag sets the DOCKER_MACHINE_HOST system environment variable. >>>>>> Set this to the IP address of the node >>>>>> that is running your Docker daemon. Only necessary to set this if on >>>>>> Linux and your browser clients are not >>>>>> localhost, ie they are remote. This property automatically set for >>>>>> Che on Windows and Mac. >>>>>> >>>>>> >>>>>> Awanthika Senarath >>>>>> Software Engineer, WSO2 Inc. >>>>>> Mobile: +94717681791 >>>>>> >>>>>> >>>>>> >>>>>> On Tue, Feb 2, 2016 at 4:14 PM, Awanthika Senarath < >>>>>> awanth...@wso2.com> wrote: >>>>>> >>>>>>> Hello Alexander, >>>>>>> >>>>>>> I tried with your command. It does not work either. >>>>>>> >>>>>>> Attached the script I used herewith. >>>>>>> >>>>>>> Regards >>>>>>> Awanthika >>>>>>> >>>>>>> Awanthika Senarath >>>>>>> Software Engineer, WSO2 Inc. >>>>>>> Mobile: +94717681791 >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Tue, Feb 2, 2016 at 4:02 PM, Alexander Garagatyi < >>>>>>> agaraga...@codenvy.com> wrote: >>>>>>> >>>>>>>> Sorry but I wrote you wrong command for disabling POSIX compliant >>>>>>>> mode. It should be "set +o posix" instead of "set -o posix". >>>>>>>> >>>>>>>> On Tue, Feb 2, 2016 at 11:52 AM, Susinda Perera <susi...@wso2.com> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Hi Alexander >>>>>>>>> >>>>>>>>> Could you also help me. I tried to run che with the "sh ./che.sh >>>>>>>>> run" command and its giving me following[1] error. Any idea what >>>>>>>>> might have >>>>>>>>> gone wrong? Note that i tried "start" and same issue. >>>>>>>>> >>>>>>>>> [1] >>>>>>>>> >>>>>>>>> ---------------------------------------------------------------------------------------------------------------- >>>>>>>>> GNU bash, version 4.3.11(1)-release (x86_64-pc-linux-gnu) >>>>>>>>> Copyright (C) 2013 Free Software Foundation, Inc. >>>>>>>>> License GPLv3+: GNU GPL version 3 or later < >>>>>>>>> http://gnu.org/licenses/gpl.html> >>>>>>>>> >>>>>>>>> This is free software; you are free to change and redistribute it. >>>>>>>>> There is NO WARRANTY, to the extent permitted by law. >>>>>>>>> 4231 pts/1 S+ 0:00 sh ./che.sh run >>>>>>>>> 4234 pts/1 S+ 0:00 grep che.sh >>>>>>>>> ./che.sh: 194: ./che.sh: [[: not found >>>>>>>>> ./che.sh: 197: ./che.sh: [[: not found >>>>>>>>> ./che.sh: 200: ./che.sh: [[: not found >>>>>>>>> ./che.sh: 203: ./che.sh: [[: not found >>>>>>>>> ./che.sh: 206: ./che.sh: [[: not found >>>>>>>>> ./che.sh: 209: ./che.sh: [[: not found >>>>>>>>> >>>>>>>>> We could not detect your operating system. Che is unlikely to work >>>>>>>>> properly. >>>>>>>>> >>>>>>>>> ----------------------------------------------------------------------------------------------------------------- >>>>>>>>> >>>>>>>>> On Fri, Jan 29, 2016 at 3:49 PM, Alexander Garagatyi < >>>>>>>>> agaraga...@codenvy.com> wrote: >>>>>>>>> >>>>>>>>>> Replace content of che.sh with >>>>>>>>>> https://gist.githubusercontent.com/garagatyi/5fe3f7abc0732a794391/raw/127bcf8ce3922721bac33ee8c214cce290859bc9/che.sh >>>>>>>>>> >>>>>>>>>> On Fri, Jan 29, 2016 at 11:39 AM, Awanthika Senarath < >>>>>>>>>> awanth...@wso2.com> wrote: >>>>>>>>>> >>>>>>>>>>> Could you please send me the script that you are working with? >>>>>>>>>>> the script that is available in the pack is somewhat different to >>>>>>>>>>> the >>>>>>>>>>> script in your git repo. >>>>>>>>>>> >>>>>>>>>>> It would be great if you could send me the exact script that I >>>>>>>>>>> need to start Che with. >>>>>>>>>>> >>>>>>>>>>> Regards >>>>>>>>>>> Awanthika >>>>>>>>>>> >>>>>>>>>>> Awanthika Senarath >>>>>>>>>>> Software Engineer, WSO2 Inc. >>>>>>>>>>> Mobile: +94717681791 >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Fri, Jan 29, 2016 at 3:05 PM, Alexander Garagatyi < >>>>>>>>>>> agaraga...@codenvy.com> wrote: >>>>>>>>>>> >>>>>>>>>>>> I'm working on ubuntu 14.04 and everything is ok. >>>>>>>>>>>> >>>>>>>>>>>> Please, try to update your version of Che. >>>>>>>>>>>> Provide output of *bash --version* >>>>>>>>>>>> Also comment these lines >>>>>>>>>>>> >>>>>>>>>>>> https://github.com/codenvy/che/blob/master/assembly-main/src/assembly/bin/che.sh#L14 >>>>>>>>>>>> >>>>>>>>>>>> https://github.com/codenvy/che/blob/master/assembly-main/src/assembly/bin/che.sh#L17 >>>>>>>>>>>> And add *ps ax | grep che.sh *on top of the script. Then send >>>>>>>>>>>> here output of this command and *bash --version* >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Fri, Jan 29, 2016 at 8:52 AM, Awanthika Senarath < >>>>>>>>>>>> awanth...@wso2.com> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> My ubuntu version : 14.04 >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> Attached is the script im running, >>>>>>>>>>>>> >>>>>>>>>>>>> I also tried deleting the first two lines of the script as >>>>>>>>>>>>> well. >>>>>>>>>>>>> >>>>>>>>>>>>> I have docker info as below: >>>>>>>>>>>>> >>>>>>>>>>>>> Client: >>>>>>>>>>>>> Version: 1.9.1 >>>>>>>>>>>>> API version: 1.21 >>>>>>>>>>>>> Go version: go1.4.2 >>>>>>>>>>>>> Git commit: a34a1d5 >>>>>>>>>>>>> Built: Fri Nov 20 13:12:04 UTC 2015 >>>>>>>>>>>>> OS/Arch: linux/amd64 >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> Awanthika Senarath >>>>>>>>>>>>> Software Engineer, WSO2 Inc. >>>>>>>>>>>>> Mobile: +94717681791 >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> On Wed, Jan 27, 2016 at 2:56 PM, Alexander Garagatyi < >>>>>>>>>>>>> agaraga...@codenvy.com> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> Please provide your version of ubuntu, bash and attach exact >>>>>>>>>>>>>> script that you launched (including your changes). Thank you. >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Wed, Jan 27, 2016 at 4:49 AM, Awanthika Senarath < >>>>>>>>>>>>>> awanth...@wso2.com> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> Hello Alexander, >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> I tried by removing the first two lines that was causing the >>>>>>>>>>>>>>> issue from the script, which resulted in the error [1]. I >>>>>>>>>>>>>>> removed the lines >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> set -e >>>>>>>>>>>>>>> set -o pipefail, from the script which I assume cause the >>>>>>>>>>>>>>> whole script to exit on failure according to [2]. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Any idea on how to get it to running? >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> [1] >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> trap: SIGHUP: bad trap >>>>>>>>>>>>>>> che.sh: 19: che.sh: function: not found >>>>>>>>>>>>>>> che.sh: 98: che.sh: Syntax error: "}" unexpected >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> [2] https://sipb.mit.edu/doc/safe-shell/ >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> thanks and regards >>>>>>>>>>>>>>> Awanthika >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Awanthika Senarath >>>>>>>>>>>>>>> Software Engineer, WSO2 Inc. >>>>>>>>>>>>>>> Mobile: +94717681791 >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Tue, Jan 26, 2016 at 4:54 PM, Awanthika Senarath < >>>>>>>>>>>>>>> awanth...@wso2.com> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Hello Alexander, >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Thanks, will try it out. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Awanthika Senarath >>>>>>>>>>>>>>>> Software Engineer, WSO2 Inc. >>>>>>>>>>>>>>>> Mobile: +94717681791 >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Tue, Jan 26, 2016 at 2:11 PM, Alexander Garagatyi < >>>>>>>>>>>>>>>> agaraga...@codenvy.com> wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Hi! >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> This check fails because you use shell that doesn't >>>>>>>>>>>>>>>>> support it. I think we should remove this check. I'll submit >>>>>>>>>>>>>>>>> PR for that. >>>>>>>>>>>>>>>>> To workaround that you can try start che inside bash shell >>>>>>>>>>>>>>>>> or remove that line >>>>>>>>>>>>>>>>> <https://github.com/codenvy/che/blob/master/assembly-main/src/assembly/bin/che.sh#L15> >>>>>>>>>>>>>>>>> . >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> On Tue, Jan 26, 2016 at 5:46 AM, Awanthika Senarath < >>>>>>>>>>>>>>>>> awanth...@wso2.com> wrote: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Hello, >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> I have attempted to start eclipse-che latest release >>>>>>>>>>>>>>>>>> downloaded from [1] following the documentation at [2]. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> The command in the documentation did not work, hence I >>>>>>>>>>>>>>>>>> used sh che.sh start command which gave me the error >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> * Illegal option -o pipefail * >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Appreciate any input on how to get the latest Che running >>>>>>>>>>>>>>>>>> in my local ubuntu machine. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> [1] http://www.eclipse.org/che/download/ >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> [2] >>>>>>>>>>>>>>>>>> https://eclipse-che.readme.io/docs/get-started-with-java-and-che >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Regards >>>>>>>>>>>>>>>>>> Awanthika Senarath >>>>>>>>>>>>>>>>>> Software Engineer, WSO2 Inc. >>>>>>>>>>>>>>>>>> Mobile: +94717681791 >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>>> che-dev mailing list >>>>>>>>>>>>>>>>>> che-...@eclipse.org >>>>>>>>>>>>>>>>>> To change your delivery options, retrieve your password, >>>>>>>>>>>>>>>>>> or unsubscribe from this list, visit >>>>>>>>>>>>>>>>>> https://dev.eclipse.org/mailman/listinfo/che-dev >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>> | Alexander Garagatyi | Developer | *Codenvy.com >>>>>>>>>>>>>>>>> <http://codenvy.com/> * >>>>>>>>>>>>>>>>> *Use Codenvy for Free Now <http://codenvy.com/>* >>>>>>>>>>>>>>>>> *Read the Codenvy Story <http://blog.codenvy.com/vision/>* >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> -- >>>>>>>>>>>>>> | Alexander Garagatyi | Developer | *Codenvy.com >>>>>>>>>>>>>> <http://codenvy.com/> * >>>>>>>>>>>>>> *Use Codenvy for Free Now <http://codenvy.com/>* >>>>>>>>>>>>>> *Read the Codenvy Story <http://blog.codenvy.com/vision/>* >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> | Alexander Garagatyi | Developer | *Codenvy.com >>>>>>>>>>>> <http://codenvy.com/> * >>>>>>>>>>>> *Use Codenvy for Free Now <http://codenvy.com/>* >>>>>>>>>>>> *Read the Codenvy Story <http://blog.codenvy.com/vision/>* >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> | Alexander Garagatyi | Developer | *Codenvy.com >>>>>>>>>> <http://codenvy.com/> * >>>>>>>>>> *Use Codenvy for Free Now <http://codenvy.com/>* >>>>>>>>>> *Read the Codenvy Story <http://blog.codenvy.com/vision/>* >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> che-dev mailing list >>>>>>>>>> che-...@eclipse.org >>>>>>>>>> To change your delivery options, retrieve your password, or >>>>>>>>>> unsubscribe from this list, visit >>>>>>>>>> https://dev.eclipse.org/mailman/listinfo/che-dev >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> *Susinda Perera* >>>>>>>>> Software Engineer >>>>>>>>> B.Sc.(Eng), M.Sc(Computer Science), AMIE(SL) >>>>>>>>> Mobile:(+94)716049075 >>>>>>>>> Blog: susinda.blogspot.com >>>>>>>>> WSO2 Inc. http://wso2.com/ >>>>>>>>> Tel : 94 11 214 5345 Fax :94 11 2145300 >>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> che-dev mailing list >>>>>>>>> che-...@eclipse.org >>>>>>>>> To change your delivery options, retrieve your password, or >>>>>>>>> unsubscribe from this list, visit >>>>>>>>> https://dev.eclipse.org/mailman/listinfo/che-dev >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> | Alexander Garagatyi | Developer | *Codenvy.com >>>>>>>> <http://codenvy.com/> * >>>>>>>> *Use Codenvy for Free Now <http://codenvy.com/>* >>>>>>>> *Read the Codenvy Story <http://blog.codenvy.com/vision/>* >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> che-dev mailing list >>>>>>>> che-...@eclipse.org >>>>>>>> To change your delivery options, retrieve your password, or >>>>>>>> unsubscribe from this list, visit >>>>>>>> https://dev.eclipse.org/mailman/listinfo/che-dev >>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> | Alexander Garagatyi | Developer | *Codenvy.com >>>>> <http://codenvy.com/> * >>>>> *Use Codenvy for Free Now <http://codenvy.com/>* >>>>> *Read the Codenvy Story <http://blog.codenvy.com/vision/>* >>>>> >>>> >>>> >>> >> > > > -- > | Alexander Garagatyi | Developer | *Codenvy.com <http://codenvy.com/> * > *Use Codenvy for Free Now <http://codenvy.com/>* > *Read the Codenvy Story <http://blog.codenvy.com/vision/>* >
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
