Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Error] when configuring Superdev Mode for Eclipse #1861

Closed
BingxuHong opened this issue Jul 19, 2016 · 26 comments
Closed

[Error] when configuring Superdev Mode for Eclipse #1861

BingxuHong opened this issue Jul 19, 2016 · 26 comments
Labels
kind/bug Outline of a bug - must adhere to the bug report template.

Comments

@BingxuHong
Copy link

BingxuHong commented Jul 19, 2016

I tried to configure Superdev Mode for Eclipse, but there was an error while Compiling module org.eclipse.che.ide.IDE.

image

The following is my dev env and what I did:

Dev env:

Che version: [latest]
OS and version: [windows 10]
Docker version: [docker toolbox]
Che install: [Yatta]

What I did:

  1. Install pre-requirements and download source from Yatta.
  2. mvn clean install at \che\assembly.
  3. Configure Superdev Mode following the website.
    https://eclipse-che.readme.io/docs/setup-che-workspace
    And my Arguments is:
    -noincremental
    -src target/generated-sources/gen
    org.eclipse.che.ide.IDE

I didn't make any change to the source code, and all my settings are following the Eclipse Che Documents in the web site.

@TylerJewell
Copy link

@BingxuHong - we will have QA take a look at the instructions and the docs. Question - you said you used the Yatta installer. Did you get the source code through the Yatta installer, too? Trying to understand which pieces came from the repo vs. Yatta. Thanks.

@ghost
Copy link

ghost commented Jul 19, 2016

@TylerJewell looks like there are issues with Yatta installer. Not all modules are imported. I am investigating it an the moment.

@BingxuHong
Copy link
Author

@TylerJewell All of the source code were automatically downloaded through the Yatta installer. And I didn't make any change about source code.

@TylerJewell
Copy link

Ok, seems like this is related to #1858 and that there is an issue with the yatta installer. Maybe you can try just cloning the repository without the yatta installer and trying it from scratch?

@BingxuHong
Copy link
Author

@TylerJewell Actually I want to try to debug Eclispse Che source code. But I'm not familiar with the Java language and the Eclispse IDE. I have no idea to make it without any guide. Anyway, thanks for your answer. I will try outer ways..

@TylerJewell
Copy link

We have these pages on the docs which document how to setup a development environment for Che for building extensions. It's how we debug the core code. We haven't added these links into the wiki yet, but will do so.

https://eclipse-che.readme.io/docs/setup-che-workspace

@BingxuHong
Copy link
Author

@TylerJewell The web site you linked is that I was following to configure Superdev mode today.. Is there a way to debug the core code except for Google Plug-in?

@TylerJewell
Copy link

I am not sure I understand the question. Che is comprised of three systems:

  1. Che server
  2. Workspace plugins, which are server-side in a workspace.
  3. IDE plugins, which are compiled into JavaScript.

Items 1 and 2, do not need GWT for debugging. They are Java apps that run in a Tomcat server, so you can just debug them using any Java IDE debugger connectivity. Tomcat has its debug port published, so you can connect to that.

The GWT superdev mode is for debugging the IDE extensions only.

I think we document all of this properly on the pages that you have. Is there something missing?

@BingxuHong
Copy link
Author

@TylerJewell Thank you. As you said, I will get the source code from the repository and try it again.

@ghost ghost added the kind/bug Outline of a bug - must adhere to the bug report template. label Jul 20, 2016
@ghost
Copy link

ghost commented Jul 20, 2016

@BingxuHong it looks like when Yatta profile imports a project not all modules are imported, and the error is caused by missing modules. There are related issues:

#1858
#1740

@zenobios
Copy link
Contributor

@BingxuHong We just fixed the issue #1740. Now all all required modules are imported into the workspace.

@BingxuHong
Copy link
Author

BingxuHong commented Jul 20, 2016

@zenobios I deleted my workspace and downloaded the source code from Yatta Installer again. The error seems to be clear at the Project Explorer, but when I try to run Super dev mode, there was still that error massage.

image

By the way, It looks like there is a problem with Projects structure in the new Yatta profile. It loaded the same project twice.
image

@zenobios
Copy link
Contributor

If it's a problem with having both parent and child maven projects in the workspace, try to close/delete (make sure to only delete it from the workspace) the parent project and see if it works.

I'm currently not in the office so I can't try it myself right now.

@BingxuHong
Copy link
Author

Can any one teach me how to set up eclipse to debug like the video from the link below?
I want to connect eclipse to the tomcat already running for debug.
https://www.youtube.com/watch?v=MSiIGBmGBEw&app=desktop

@BingxuHong
Copy link
Author

I dealt with the issue #1876 , even though I don't know how it works this time, because I followed same steps as last time.

  1. Install pre-requirements and download source from Yatta.
  2. mvn clean install at \che\assembly.
  3. run 'che --debug start' at \che\assembly\assembly-main\target\eclipse-che-4.6.0-SNAPSHOT\eclipse-che-4.6.0-SNAPSHOT\bin.
  4. debug remote Java Application in Eclispse IDE.
    image

Then debugger stopped at the breakpoint.
image
image

Now, I will try the Super dev mode..
Anyway, Thank you.

@JamesDrummond
Copy link
Contributor

@BingxuHong Have all your issues been resolved on this?

@BingxuHong
Copy link
Author

@JamesDrummond Not yet. I couldn't make Superdev mode to work.. Recently, I had been working on different projects so I am not sure.

@ghost
Copy link

ghost commented Aug 8, 2016

@BingxuHong #1740 it should work now. Are you seeing the same super dev mode error?

@BingxuHong
Copy link
Author

@eivantsov @JamesDrummond I updated the Yatta Profile then tried it again. But it is still not working.

image

@ghost
Copy link

ghost commented Aug 8, 2016

@BingxuHong can you share your superdev mode config? As a screenshot.

@BingxuHong
Copy link
Author

@eivantsov

image

image

image

@TylerJewell
Copy link

@eivantsov @ddementieva - do we have an update?

@ghost
Copy link

ghost commented Aug 29, 2016

@TylerJewell not yet. Will do this week

@ghost
Copy link

ghost commented Aug 29, 2016

@BingxuHong we tried it with the same run configurations on 2 different Ubuntu machines. @ddementieva can confirm it works on her machine as well.

We haven't tried it on Windows though. I think that your problem is related with some missing sources - thus invalid import.

@pavandaga
Copy link

pavandaga commented Sep 1, 2016

The superdevmode does not work on Eclipse in Windows

@slemeur
Copy link
Contributor

slemeur commented Apr 18, 2017

Closing due to inactivity on this issue.
Please refer to the developer guide: https://github.com/eclipse/che/wiki/Development-Workflow for more info

@slemeur slemeur closed this as completed Apr 18, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Outline of a bug - must adhere to the bug report template.
Projects
None yet
Development

No branches or pull requests

6 participants