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

Xbase files dont get rebuilt if there are more than 100 java changes #2390

Open
cdietrich opened this issue Nov 15, 2017 · 7 comments
Open

Comments

@cdietrich
Copy link
Member

due to the use of State.structurallyChangedTypes xbase and thus xtend files wont get recompiled if there are more than 100 java changes

@cdietrich
Copy link
Member Author

see org.eclipse.jdt.internal.core.builder.State.MaxStructurallyChangedTypes

@iloveeclipse
Copy link
Contributor

@iloveeclipse
Copy link
Contributor

Christian, if this is reproducible, can you please create a bug for JDT?

@cdietrich
Copy link
Member Author

@iloveeclipse what i understood is that this is intended behaviour of jdt. unfortuantely this makes use of internal jdt api. so its us to blame.

@iloveeclipse
Copy link
Contributor

This looks like a dirty workaround, not like intended fix. If we have a bug describing how it breaks xtext, we can at least start the discussion about the proper solution, or at least a bigger default.

@cdietrich
Copy link
Member Author

big-jdt-changes.zip

@cdietrich
Copy link
Member Author

@cdietrich cdietrich transferred this issue from eclipse/xtext-eclipse Apr 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants