Is it allowed to depend on binaries, which are pre-built in openwhisk about openwhisk-catalog HOT 4 CLOSED

@markusthoemmes Hi Markus. I think we are running into the above issue in gradle. We would like to receive your opinion and help. Thank you.

from openwhisk-catalog.

Depending on prebuilt binaries indeed doesn't sound like a good idea to me.

Two ideas:

1. Create a dependency against the test source files directly (adding them to the srcDirs
2. Don't depend on openwhisk's tests at all? Which parts of the repo do you really need? Catalog tests presumably are mostly about wsk action create, wsk action invoke, wsk activation get, right? Does a thin testwrapper make sense? It could be shared across all catalog repos via something like https://jitpack.io/

from openwhisk-catalog.

@markusthoemmes Thank you, Markus. Could you give me some more information about the first approach?

Suppose I have a repo of openwhisk-catalog and a repo of openwhisk. They are not necessarily put in the same folder. The only thing that openwhisk-catalog knows is an absolute path where openwhisk is located. I am not sure how to refer to openwhisk project in the build.gradle of openwhisk-catalog.

I have found many suggestions like
dependencies {
testCompile project(path ':a', configuration: 'tests')
}
How can I use an absolute path as the path param for project?

from openwhisk-catalog.

http://stackoverflow.com/questions/14729072/having-difficulty-setting-up-gradle-multiproject-build-for-existing-repository-l

https://looksok.wordpress.com/2014/07/12/compile-gradle-project-with-another-project-as-a-dependency/

The above links are useful, I believe.
@markusthoemmes @jasonpet @daisy-ycguo @lzbj

from openwhisk-catalog.