@debug Ok. I suggest you hold off until I get my changes in (hopefully this weekend). I’ll ping you. In the meantime, it’s probably safer to work on brand new features than refactoring existing ones, if there’s something you’d like to work on

Well, actually I wanted to add that update feature. And the best way to accomplish that would be Server-JSON style as discussed. I only tried to refactor to get it easy for me to make things run.

What update feature?

.\kobaltw --update

from the menu

I did PR (174) to Kobalt with proxy support. Now it should be possible to configure proxy without auth in settings.xml. Also I did some small PR (13) to IDEA plugin which move plugin.xml to the right place. And I have additional small improvement to idea plugin: reimport of Build.kt module if needed and call "save all documents" before sync/run actions - not yet PR, will be after PR13 merge 😉

@dmitry.zhuravlev: Merged your 2 PR’s, thanks!

Btw, why is the git repo currently targeting version 0.744?

Also trying to build Kobalt, but the wrapper jar doesn't have

kobalt.properties

when its complete.

That happened for a version because of a bug, make sure your repo is up to date

I just built the with the latest 0.746 and I get:

$ jar tf modules/wrapper/kobaltBuild/libs/kobalt-wrapper.jar
META-INF/MANIFEST.MF
com/beust/kobalt/wrapper/Main.class
kobalt.properties

It's very weird that sometimes on forking repos on github results in a stale fork, I'll merge and try now

Usually it’s because your repo is blocking the merge but sometimes, you miss it and you think you’re up to date

Found some bug with duplicated runners (default and kobalt). Fixed in next PR. Also added ability to hide plugin functionality if project contains no Build.kt file.

Just merged it, thanks! simple smile

😉

FYI (and @debug too) I’m investigating getting rid of the external server process and instead, calling Kobalt in-process

Presents some interesting classloading challenges

Actually, it’s probably not feasible without including kobalt.jar in the IDEA plug-in, which means the plug-in is now stuck with that version of kobalt. Thoughts about that limitation?

Hm… not thought about it. But I think this should not be bundled with IDEA plugin. Just look on Maven, Gradle implementations. Both have ability to execute bundled and non-bundled gradle\maven engine.

Yeah

Managing an external process is a pain though

However in idea API there is a lot things already implemented to manage external processes…. “external-system-api” - Gradle plugin implement it.

Ah I need to look into this

I already started implementing some of this but the external process problem is a subset of that

Happy to let you take over that part, @dmitry.zhuravlev simple smile

Actually there is a 3 different kinds of plugin: Ant plugin - leverage the low level API because of old implementation. Maven - leverage “medium” level API, more up to date.. And Gradle use the most recent one - “external-system-api"

@cedric: I’d definitely vote for keeping things separated as much as possible

@eddie: Ok, done.

whoo