-
Notifications
You must be signed in to change notification settings - Fork 12
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
Content Assist not working when 3.4.0 update is installed in Eclipse for Java Developers #486
Comments
This was apparently due to the logger issues. Once that got sorted out a bit CA started working. |
Has stopped working again. |
I need to know what did you change. Do you have a branch or a PR with the changeset? I can look into the issue this week. |
The branch on which the update occurred was "jena3.16". When it appeared that all was well (all tests passed) it was merged into development. |
@kittaakos , I went through the warnings and fixed a) easy ones, e.g., unused imports, and b) ones that looked like they might have significant consequences. I didn't know how to fix the first 3. |
I will look into it tomorrow, please commit your changeset to somewhere. |
Here is the changeset so far: 6af2b08...85fad7c |
As all tests pass, I have pushed my changes to resolve warnings to development branch. |
I could not reproduce the problem. It worked for me. I did the following:
|
@kittaakos , if I do what you outline above it works for me as well. However, if I install the SADL p2 into a brand new Eclipse for Java Developers 2020-03 it does not work. This is a change. In the past I could install the SADL p2 into either Eclipse for DSL Developers OR Eclipse for Java Developers and it worked equally well. So has something dropped out of the SADL p2 that is in the DSL version but not the Java version? @tuxji , want to include you in this question. |
I do not know what you mean, but I did exactly that. Built the SADL p2 from the sources and installed it into a 2020-03 Eclipse for DSL developers: #486 (comment).
|
If I install into a brand new Eclipse for DSL Developers 2020-03 it works. |
BTW, what does |
Thank you!
Resets the repository to a fresh-clone state. |
This is the error I see when I install the p2 into Eclipse 2020-03 for Java developers.
I am checking why... |
@crapo, I downloaded the latest 3.3 SADL release from here: https://github.com/crapo/sadlos2/releases/latest |
The problem here is that we pull Xtext 2.22 although we develop against 2.21. I'll try to set an upper bound for Xtext: |
I don't fully understand. I think that you're saying that the previous release also did not work if installed on the Java Developer Eclipse and I just didn't notice.
not sure what pulls... the Installation of the SADL p2?
Should we be developing against 2.22? I think you're saying that you'll try to make it pull 2..21, correct? |
Do you want me to update Xtext to 2.22? |
I'm asking what you recommend. I don't have enough information to have an informed opinion... Unless there's a good reason, we should do what takes the least effort. |
Signed-off-by: Akos Kitta <[email protected]>
I have pinned the versions. The PR is here: #492 As a verification:
|
GH-486: Pinned Xtext version to [2.21.0,2.22.0)
@kittaakos , this one has me stumped. The development branch has jena3.16 merged with it, updating Apache Jena from a 5+ year-old version and updating the SADL version to 3.4.0. The Jena logging changed, which required some tweaks. But now when run from the development environment everything seems to work OK but when I install the update zip file into an Eclipse 2020-03, content assist does not work at all. This is true for two different installations on two different machines. I'm kind of clueless as to how to identify a problem only existing in an installed plugin, not in the development environment.
The text was updated successfully, but these errors were encountered: