Hey Andreas, It's been a while that I saw an email passing by in the dev channel about the sling ide tooling for intellij, do you maybe have any updates on that :)? Would be realy neat to have, definitly the exploded bundle hotswapping!
Cheers, Roy > Op 28 apr. 2015 om 18:02 heeft Andreas Schaefer Sr. <schaef...@me.com> het > volgende geschreven: > > Hi > > Most of the backend code inside the tooling project (api, impl-resources etc) > do not depend on Eclipse with the sole exception of impl-vlt which use the > Eclipse Plugin class inside the Activator and uses the Activator’s > getLogger() to obtain the logger inside that module. > > IntelliJ does not use an OSGi container and even though I could stub the > Eclipse Plugin class it does not seem right. > > Can we split that module into 2 parts where one only contains the backend > code and the second would contain the Eclipse Plugin service code and > configuration? > > The only sticky issue I see is the call inside classes like VltRepository to > obtain the Plugin Logger: Activator.getDefault().getPluginLogger(). One > solution would be to create another class like PluginLoggerProvider that has > a static method like getInstance() which has a setter and getter method for > the Plugin Logger. > > Cheers - Andy
