Open cmeiklejohn opened 8 years ago
That makes sense to me, usually the eqc plugin should live in a own profile. i.e. in the eqc profile, that way it only gets loaded when that profile is used (wich it shouldn't on non eqc machines)
Two points here:
ifdef
's to prevent this?I've had those errors before when I didn't have eqc installed, but it didn't affect building the rest of the project. Is there a negative effect other than the error output from the plugin that you're seeing and trying to work around?
You're right, that's not causing the build to fail. I am still wondering why it's not picking up the test suites when moved to a profile's plugin list.
Did you try ./rebar3 as eqc eqc
after moving the plugin to the eqc profile? That seems to work for me.
Is there a recommended way to do this?