An annoyance with Buildship is developing a build and/or plugins in Eclipse on Windows with Exec commands for which the real destination is a some unix system somewhere. I’d like the convenience of being able to code the thing in Eclipse, but the Gradle-refresh and import-Gradle features will fail because Gradle can’t find the commands on the Windows system.
Would be nice if there was some way to avoid the failing of the refresh/import in this situation.
Sounds like you are running the exec-commands during the configuration phase, which makes it impossible for Gradle to configure the project on Windows. You’ll have to make sure that your exec-actions are either skipped on Windows or only run during the execution phase.
Yeah that’s it, thanks. But in my case the command is explicitly part of the configuration process. So I either check the os before or catch the Exception.