rebar/rebar — pull request #9 by andrzejsliwa (2012-11-05 21:39:23+00:00)
Title: handle qc for PropEr

@tuncer even generic solution like:

https://github.com/tuncer/rebar/commit/2dcdc1060e005fcad4791a0da764d750fcd8a61b

is not enough because PropEr have different schema of api:

QC:module(M, Opts)

instead of

QC:module(Opts, M) %% eqc

or

QC:module(M) %% triq

I still thinking that handling PropEr not violate license of PropEr it self.

Most developers have configuration like that (~/.erlang):

true = code:add_pathz(os:getenv("HOME")++"/.erlang.d/deps/quviq/eqc-X.Y.Z/ebin").

or

true = code:add_pathz(os:getenv("HOME")++"/.erlang.d/deps/proper/ebin").

and we dont providing in rebar any dependency, we just using some schema of API,
and api schema like M:Fun(...) can't be copyrighted it self. If we handling in same way full version of eqc which is commercially licensed why not support PropEr too (especialy when support means only call M:F(...)) ?

@manopapad, @kostis - could you confirm that we will not violate license of PropEr in that way?