Repository: incubator-edgent Updated Branches: refs/heads/master bd71ad824 -> 7961bb524
[gradle] more doc and cleanup Project: http://git-wip-us.apache.org/repos/asf/incubator-edgent/repo Commit: http://git-wip-us.apache.org/repos/asf/incubator-edgent/commit/7961bb52 Tree: http://git-wip-us.apache.org/repos/asf/incubator-edgent/tree/7961bb52 Diff: http://git-wip-us.apache.org/repos/asf/incubator-edgent/diff/7961bb52 Branch: refs/heads/master Commit: 7961bb52434177453321c7d7f0e9aa046733920c Parents: bd71ad8 Author: Dale LaBossiere <[email protected]> Authored: Fri Sep 30 12:09:08 2016 -0400 Committer: Dale LaBossiere <[email protected]> Committed: Fri Sep 30 12:09:08 2016 -0400 ---------------------------------------------------------------------- DEVELOPMENT.md | 14 +++++++++++++- build.gradle | 3 +++ 2 files changed, 16 insertions(+), 1 deletion(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/incubator-edgent/blob/7961bb52/DEVELOPMENT.md ---------------------------------------------------------------------- diff --git a/DEVELOPMENT.md b/DEVELOPMENT.md index eb353c7..db3cf7f 100644 --- a/DEVELOPMENT.md +++ b/DEVELOPMENT.md @@ -23,6 +23,18 @@ ant based tooling will no longer work. **See _Using Eclipse_ below for a gradle task that must be run to make the 3rd party jars available to an Eclipse Edgent runtime development environment.** +Gradle tooling: +- creates release images under `<edgent>/build/release-edgent` +- creates build artifacts under `<edgent>/build/distributions` and `<edgent>/<project>/build` + +Ant tooling: +- creates release images under `<edgent>/release-edgent` +- creates build artifacts under `<edgent>/target` and `<edgent>/<project>/{classes,test.classes}` + +Eclipse: +- creates build artifacts under `<edgent>/<project>/bin` + + Timeline: - Sep 27 - Start using the gradle build tooling for developing Edgent. See below for using gradle. @@ -346,6 +358,6 @@ are best ignored. Builds and junit testing of Edgent in Eclipse is independent from the artifacts generated by the gradle/ant build tooling. Neither environment is affected by the other. This is not ideal but it's where things are at at this time. -Both sets of tooling can be and, typically are, used in the same workspace. +Both sets of tooling can be, and typically are, used in the same workspace. Note. Specifics may change depending on your version of Eclipse or the Eclipse Git Team Provider. http://git-wip-us.apache.org/repos/asf/incubator-edgent/blob/7961bb52/build.gradle ---------------------------------------------------------------------- diff --git a/build.gradle b/build.gradle index 6fe9d8f..e4422fe 100644 --- a/build.gradle +++ b/build.gradle @@ -29,6 +29,9 @@ allprojects { } apply plugin: 'java' +jar { + deleteAllActions() // Avoid creating/staging an empty jar for the "root" +} ext {
