Closed advayDev1 closed 8 years ago
I'm not a fan of having to constantly remerge master into pluginHead. If you've got a better idea, let's do that and delete this branch (it has no effect on master yet).
We can get it to build to the latest version by querying the repo tags - see comments about this.
My big question is how is this build triggered? On a time basis, e.g. every 24 hours? It looks like Travis-CI isn't interested in kicking off a build based on a dependant repo: https://github.com/travis-ci/travis-ci/issues/631
Per https://github.com/j2objc-contrib/j2objc-common-libs-e2e-test/pull/38#discussion_r40638717 I'm just closing this PR for now.
We don't need this complexity.
And document it.
Fixes #33
NOTE: This is a merge of a branch in the main repo to master. I could not figure out a way to propose a merge request from my fork to a not-yet-existent branch in the upstream. After this PR goes through we would keep pluginHead, and then merge master into pluginHead whenever new libraries are added.