commit 62ad452af0bb943b5a9d32ced162796536b018b9
author Dale LaBossiere <dlaboss@us.ibm.com> Thu Sep 29 13:41:26 2016 -0400
committer Dale LaBossiere <dlaboss@us.ibm.com> Thu Sep 29 13:42:01 2016 -0400
tree 079a3f6f27c48f6c0f464e7ef893808a9556f007
parent 6437b2085e5ea83088c0b4e6e537fd4d381d0b2d

[WIP] [ci-skip] Edgent-251 adapt Eclipse to not use 3rd-party repo jars

- add 'setupExternalJars' gradle task
- change .classpath files to reference ext jars in
build/distribution/...

Note, the changes DO NOT include removal of the 3rd party jars from our
repo (though in my workspace I removed them and Eclipse builds/test of
Edgent worked fine).  A separate issue/PR will be used to remove them.

This approach has the same characteristics as the current Eclipse/ant
build environments: separate project dependency specifications, separate
class file locations, Eclipse builds/tests don't use the ant/gradle
built Edgent jars.

My initial experience trying to use the Buildship gradle/Eclipse
integration came up short.  The way it created/updated .classpath files
as a result of the way dependencies are expressed in our build.gradle
files was problematic.  So, I scoped back to the approach here to get to
the end-goal (removal of dependency of 3rd party jars in the repo) asap.
Should revisit the buildship env later to see if things can be made to
work.