Skip to content
This repository has been archived by the owner on Apr 2, 2021. It is now read-only.

Drop scala :) #4

Open
nixel2007 opened this issue Nov 11, 2018 · 13 comments
Open

Drop scala :) #4

nixel2007 opened this issue Nov 11, 2018 · 13 comments

Comments

@nixel2007
Copy link
Member

Pure java FTW :)

@nixel2007
Copy link
Member Author

TODO: make scala2java roadmap

@NipunaRanasinghe
Copy link
Member

If we are rewriting this using Java (I think we should :)), IMO we can do that separately (maybe in a separate repo)? WDYT?

@nixel2007
Copy link
Member Author

I hope, that we can start with rewriting tests to java, then some parts of scala classes. Scala can use java classes (can't it?), so we can rewrite it partialy in long time.
I really don't want to use some other repo instead of feature branches for it. Sync problems and long-living-branch problems, you know.

@NipunaRanasinghe
Copy link
Member

NipunaRanasinghe commented Nov 12, 2018

Yeah you are right. I meant if we could create a separate organization and start working on a fork there, it will be better for #5 and #6 as well. Any way we can move with after having some progress and considering the other's ideas as well :) @cdietrich WDYT?

@cdietrich
Copy link

i am not too fond of scala. is more than ten years ago i really did a lot with it. having java 8 and lambdas gives already a lot of options

@nixel2007
Copy link
Member Author

@NipunaRanasinghe, ah, got the point. I could create an "intellij-lsp" organinization and transfer this repo to it. Ok?

@nixel2007
Copy link
Member Author

@NipunaRanasinghe moved!

@NipunaRanasinghe
Copy link
Member

@nixel2007 Exactly! :) IMO by that we could make these as more community-driven projects and probably gather JetBrains related language server clients into one place in the long run. Thanks for your effort on this!

@NipunaRanasinghe
Copy link
Member

@nixel2007 One small suggestion, since we will be making this organization as the 'Home' for more jetbrains + language server developments in the long run, shall we name this organization in a more general sense ( maybe something like lsp4jetbrains ;) ) ?

@nixel2007
Copy link
Member Author

@NipunaRanasinghe the platform is called "IntelliJ Platform", LSP is LSP... :) So i think we can leave this name for organization. We could try to rename the repo itself in more specific to "plugin" way. like intellij-lsp-plugin

@NipunaRanasinghe
Copy link
Member

@nixel2007 +1 :)

@gayanper
Copy link
Collaborator

Guys i'm back after a while on Idea development again, well you have made great progress, so are we planning to move forward with this repo instead of the original ? May be we might need to publish the plugin with a different ID then. What do you guys think ?

@cdietrich
Copy link

@gayanper Guillaume seems to be back so i think we should join efforts at the original repo

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants