Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 54143200B67 for ; Tue, 16 Aug 2016 20:22:28 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 52E90160AA8; Tue, 16 Aug 2016 18:22:28 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 74638160A74 for ; Tue, 16 Aug 2016 20:22:27 +0200 (CEST) Received: (qmail 89717 invoked by uid 500); 16 Aug 2016 18:22:26 -0000 Mailing-List: contact dev-help@edgent.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@edgent.apache.org Delivered-To: mailing list dev@edgent.apache.org Received: (qmail 89702 invoked by uid 99); 16 Aug 2016 18:22:26 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Aug 2016 18:22:26 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 455AA1A5556 for ; Tue, 16 Aug 2016 18:22:26 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -4.646 X-Spam-Level: X-Spam-Status: No, score=-4.646 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id M0PHKeFBE_JP for ; Tue, 16 Aug 2016 18:22:22 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with SMTP id 81F955FBD4 for ; Tue, 16 Aug 2016 18:22:21 +0000 (UTC) Received: (qmail 89390 invoked by uid 99); 16 Aug 2016 18:22:20 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Aug 2016 18:22:20 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 9D6372C02A4 for ; Tue, 16 Aug 2016 18:22:20 +0000 (UTC) Date: Tue, 16 Aug 2016 18:22:20 +0000 (UTC) From: "Dale LaBossiere (JIRA)" To: dev@edgent.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (EDGENT-139) Adopt a build system, such as gradle, that supports transitive dependency management MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 16 Aug 2016 18:22:28 -0000 [ https://issues.apache.org/jira/browse/EDGENT-139?page=3Dcom.atlassia= n.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale LaBossiere updated EDGENT-139: ----------------------------------- Description:=20 By moving to a build system that supports transitive dependency management,= the repository size can be decreased and users can more easily integrate q= uarks with their own applications by allowing the version of a dependency t= o float within an acceptable range, assuming proper semantic versioning of = the dependencies. [~bjhargrave] has created the initial set of gradle files with PR-131. The= gradle work is still WIP. The existing build mechanisms are still in plac= e and are to be used. TODOs - Add license headers to gradle files - QUARKS-203 - Update build doc EDGENT-240 - Java7 build support - Android build support - add manifest classpath entries EDGENT-240 - Release target, creating the target/=E2=80=A6 structure - QUARKS-204, QUA= RKS-240 - Junit parity - QUARKS-223, QUARKS-237, QUARKS-239 - need top level aggregating report - Javadoc parity - QUARKS-205 - Jacoco parity - QUARKS-237 - building from Eclipse - .classpath files have refs to ext jars that will be removed from the re= po - switch travis-ci to gradle - cleanup - remove ext jars from repo. =20 Question: ext contains LICENSE/NOTICE/README files. =20 Note needed anymore as Quarks repo won=E2=80=99t contain the jars? Just want something in README.md or such to list the dependencies? - remove the ant build related files [ Original from [~lfeagan] I have an initial set of work for this effort completed using gradle. Nearl= y all sub-projects build at this time--the notable exception being the andr= oid-dependent sub-projects. The other notable missing element is the integr= ation of JaCoCo. In both cases, these should be simple additions. ] was: By moving to a build system that supports transitive dependency management,= the repository size can be decreased and users can more easily integrate q= uarks with their own applications by allowing the version of a dependency t= o float within an acceptable range, assuming proper semantic versioning of = the dependencies. [~bjhargrave] has created the initial set of gradle files with PR-131. The= gradle work is still WIP. The existing build mechanisms are still in plac= e and are to be used. TODOs - Add license headers to gradle files - QUARKS-203 - Update build doc - Java7 build support - Android build support - add manifest classpath entries - Release target, creating the target/=E2=80=A6 structure - QUARKS-204, QUA= RKS-240 - Junit parity - QUARKS-223, QUARKS-237, QUARKS-239 - need top level aggregating report - Javadoc parity - QUARKS-205 - Jacoco parity - QUARKS-237 - building from Eclipse - .classpath files have refs to ext jars that will be removed from the re= po - switch travis-ci to gradle - cleanup - remove ext jars from repo. =20 Question: ext contains LICENSE/NOTICE/README files. =20 Note needed anymore as Quarks repo won=E2=80=99t contain the jars? Just want something in README.md or such to list the dependencies? - remove the ant build related files [ Original from [~lfeagan] I have an initial set of work for this effort completed using gradle. Nearl= y all sub-projects build at this time--the notable exception being the andr= oid-dependent sub-projects. The other notable missing element is the integr= ation of JaCoCo. In both cases, these should be simple additions. ] > Adopt a build system, such as gradle, that supports transitive dependency= management > -------------------------------------------------------------------------= ----------- > > Key: EDGENT-139 > URL: https://issues.apache.org/jira/browse/EDGENT-139 > Project: Edgent > Issue Type: Improvement > Components: Analytics, API, Applications, Connectors, Console, D= ocumentation, Miscellaneous, Runtime, Samples, Test, Utils > Reporter: Lance Feagan > Assignee: Dale LaBossiere > Labels: build > Original Estimate: 168h > Remaining Estimate: 168h > > By moving to a build system that supports transitive dependency managemen= t, the repository size can be decreased and users can more easily integrate= quarks with their own applications by allowing the version of a dependency= to float within an acceptable range, assuming proper semantic versioning o= f the dependencies. > [~bjhargrave] has created the initial set of gradle files with PR-131. T= he gradle work is still WIP. The existing build mechanisms are still in pl= ace and are to be used. > TODOs > - Add license headers to gradle files - QUARKS-203 > - Update build doc EDGENT-240 > - Java7 build support > - Android build support > - add manifest classpath entries EDGENT-240 > - Release target, creating the target/=E2=80=A6 structure - QUARKS-204, Q= UARKS-240 > - Junit parity - QUARKS-223, QUARKS-237, QUARKS-239 > - need top level aggregating report > - Javadoc parity - QUARKS-205 > - Jacoco parity - QUARKS-237 > - building from Eclipse > - .classpath files have refs to ext jars that will be removed from the = repo > - switch travis-ci to gradle > - cleanup > - remove ext jars from repo. =20 > Question: ext contains LICENSE/NOTICE/README files. =20 > Note needed anymore as Quarks repo won=E2=80=99t contain the jars? > Just want something in README.md or such to list the dependencies? > - remove the ant build related files > [ Original from [~lfeagan] > I have an initial set of work for this effort completed using gradle. Nea= rly all sub-projects build at this time--the notable exception being the an= droid-dependent sub-projects. The other notable missing element is the inte= gration of JaCoCo. In both cases, these should be simple additions. ] -- This message was sent by Atlassian JIRA (v6.3.4#6332)