Wild Web Developer slows down/delays automatic eclipse build step on resource change

Open
#775 7 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
java
Domain
tooling

Research direction

Reproduce the delay by changing and saving a Java file with Wild Web Developer installed, then compare it with the plugin removed as described in the issue. Trace the interaction between Wild Web Developer and Eclipse's automatic build step; done means Java changes trigger rebuilding promptly without the multi-second or multi-minute delay.

Written by the indexing model from the issue text.

Description

I use the latest eclipse IDE and latest (snapshot) version of wwd. I have the problem described in https://bugs.eclipse.org/bugs/show_bug.cgi?id=570794. In short: If I change any java file (does not matter, junit or any other), then I have to wait too long for eclipse compile-step. So I sit on my IDE, click here and there, edit a java file without any sense only to trigger the automatic compile step by eclipse. It can be after 10 seconds or after 2- 5 minutes after ecllipse makes its automatic rebuild. That's too long! I thought that the problem was because of https://bugs.eclipse.org/bugs/show_bug.cgi?id=570794, however, I removed the wwd plugin completely, restarted the IDE and now the rebuild triggers immediately (1-2 seconds) after I change and save a java file. So I assume that wwd prevents this eclipse compile step for any reason. Maybe there is any conflict in rebuilding step from wwd and eclipse which leads to this eclipse defect.

Dominant language
Java
Stars
203
Forks
76
Avg merge
1d 5h
Merged PRs (30d)
30

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from eclipse-wildwebdeveloper/wildwebdeveloper

All issues in eclipse-wildwebdeveloper/wildwebdeveloper

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.