-
Notifications
You must be signed in to change notification settings - Fork 11
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
Remove guava in wikitext #562
Remove guava in wikitext #562
Conversation
+ org.eclipse.mylyn.wikitext eclipse-mylyn#521
Various strategies applied:
|
My goal is to find out if eclipse-jdt/eclipse.jdt.ui#1472 could be implemented with wikitext (markdown) and without guava. For that task I don't expect to need any of the *.ui bundles, as rendering to HTML should be fully sufficient for JDT. In particular no markdown editing is planned. |
This looks promising. |
How will this work live with #521? |
If I understand correctly, it provides direct implementations that address #521 (comment) for the non-ui parts. |
I admit I found #530 only after submitting this PR :) So the current PR is much narrower in scope, but succeeds to fully eliminate guava dependency from the core plugin without adding any other dependency. I'm open to discussions to find the best of all worlds. I'm driven by the fact that JDT needs markdown rendering by September the latest. |
@stephan-herrmann thank you for your PR! Perhaps it was my fault to not mention an existing #530 explicitly during our discussion I would prefer to have #530 merged first, since it was prepared earlier in the scope of #521 and using the same approach as we already have in other parts of Mylyn codebase, and then discuss your change on top of it to reduce the number of required 3rd party libraries. I hope this is fine with you.
@gnl42 could you please resolve conflicts for #530 so we can merge it and proceed with further discussion? |
Sure, I certainly didn't mean to jump the queue :)
If in doubt, some of the more involved changes, that might require a discussion, could perhaps be postponed for later? |
@stephan-herrmann Can you recreate your changes against the current main? |
See new PR #568 |
Hopefully #568 will take this to completion. |
#521