Che: Eliminate necessity for the extensions to depend on the IDE App module
There are about 30 IDE extensions, in the CHE/Codenvy assemblies, which must depend on the IDE App (che-core-ide-app module) in order to use just a few interfaces/classes. Like org.eclipse.che.ide.CoreLocalizationConstant,
org.eclipse.che.ide.newresource.AbstractNewResourceAction, etc. Having a such dependency really is a bad practice for the IDE extensions.
The goal of this task is to eliminate the necessity for the IDE extensions to depend on the che-core-ide-app module. This may require moving some interfaces/classes from che-core-ide-app to che-core-ide-api or improve IDE API in some way.
azatsarynnyy
All 5 comments
Totally agree, let's clean framework and make a real distinction between framework and app on top.
gazarenkov
on 26 Jun 2017
+1 on this since Che aims for modularization, this is a step forward
sr229
on 29 Jun 2017
@vparfonov what are the state of this issue?
skabashnyuk
on 27 Jun 2018
@azatsarynnyy @vparfonov
Let's review and try to find a "golden mean" (not putting a lot of effort).
Indeed, let's do not consider a "refactoring" but be dependent on other module just due to a couple of constants does not look that reasonable.
Thoughts?
gazarenkov
on 27 Jun 2018
Closing as Che 6 editor is no longer under active development
gorkem
on 23 Aug 2019
Related issues
vanzhiganov
路
3Comments
sleshchenko
路
3Comments
sudheerherle
路
3Comments
dmytro-ndp
路
3Comments
SkorikSergey
路
3Comments
Most helpful comment
@azatsarynnyy @vparfonov
Let's review and try to find a "golden mean" (not putting a lot of effort).
Indeed, let's do not consider a "refactoring" but be dependent on other module just due to a couple of constants does not look that reasonable.
Thoughts?