Skip to content

Indexer starts to soon after creation of project #1163

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.

Sign up for GitHub

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

Jump to bottom
Closed
jantje opened this issue Mar 31, 2020 · 3 comments
Closed

Indexer starts to soon after creation of project #1163

jantje opened this issue Mar 31, 2020 · 3 comments
Labels
importance: improvement request status: fixed in 4.4.0 fixed in 4.4.0

Comments

@jantje
Copy link
Member

jantje commented Mar 31, 2020

Basically the project creation is bogus.
On Linux this means sometimes libraries are added that are not needed after project creation.
I guess that due to lower performance this is not so visible on windows.
@jantje jantje mentioned this issue May 21, 2020
Closed
jantje pushed a commit that referenced this issue May 27, 2020
#1163 a working version but not yet testable
2f90a55
@jantje jantje mentioned this issue Jun 6, 2020
Closed
jantje added a commit that referenced this issue Jul 7, 2020
@jantje
Merge pull request #1201 from Sloeber/#1163_create_project_the_cdt_way
584cd0d 
#1163 create project the cdt way
@jantje
Copy link
Member Author

jantje commented Aug 31, 2020

This should hold off the indexer
https://bugs.eclipse.org/bugs/show_bug.cgi?id=218286

jantje pushed a commit that referenced this issue Oct 3, 2020
#1163 simplify the threading
67f895e 
use WorkspaceModifyOperation instead of WorkspaceModifyOperation and
ICoreRunnable together
jantje pushed a commit that referenced this issue Oct 3, 2020
#1163 do not act on config changes during project creation
0dba549
jantje pushed a commit that referenced this issue Oct 3, 2020
#1163 indexlistener is buggy and unreliable
6f96605 
It probably needs some synchronisation code as well but I lack the java
experiance to do this confortably in a listener.
So I assume that due to the nature of the calling events it is not
nessesary
@jantje
Copy link
Member Author

jantje commented Oct 3, 2020

This does it for testing in eclipse.
There is still a problem when running maven tests

@jantje jantje added the status: fixed in 4.4.0 fixed in 4.4.0 label Oct 3, 2020
@jantje
Copy link
Member Author

jantje commented Oct 3, 2020

I'm closing this as fixed in the nightly as the maven test is treated in #1204
Note however that the nightly update site is currently not updated due to the java11 upgrade and #1204

@jantje jantje closed this as completed Oct 3, 2020
jantje pushed a commit that referenced this issue Oct 12, 2020
#1163 the default excludes had disappeared
f9f2b8f 
Added them the cdt way in the plugin.xml
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
importance: improvement request status: fixed in 4.4.0 fixed in 4.4.0
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jantje