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 7A034200B66 for ; Thu, 18 Aug 2016 16:27:13 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 78A9E160AAE; Thu, 18 Aug 2016 14:27:13 +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 BE643160A86 for ; Thu, 18 Aug 2016 16:27:12 +0200 (CEST) Received: (qmail 25073 invoked by uid 500); 18 Aug 2016 14:27:12 -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 25062 invoked by uid 99); 18 Aug 2016 14:27:11 -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; Thu, 18 Aug 2016 14:27:11 +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 46BD61A0C5D for ; Thu, 18 Aug 2016 14:27:11 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -5.446 X-Spam-Level: X-Spam-Status: No, score=-5.446 tagged_above=-999 required=6.31 tests=[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 Sqt9wzDQQp22 for ; Thu, 18 Aug 2016 14:27:10 +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 791DE5F23D for ; Thu, 18 Aug 2016 14:27:09 +0000 (UTC) Received: (qmail 25046 invoked by uid 99); 18 Aug 2016 14:27:08 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Aug 2016 14:27:08 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 8E2ACE040F; Thu, 18 Aug 2016 14:27:08 +0000 (UTC) From: xuanyue202 To: dev@edgent.incubator.apache.org Reply-To: dev@edgent.incubator.apache.org Message-ID: Subject: [GitHub] incubator-edgent pull request #181: Enable Edgent to publish to maven reposi... Content-Type: text/plain Date: Thu, 18 Aug 2016 14:27:08 +0000 (UTC) archived-at: Thu, 18 Aug 2016 14:27:13 -0000 GitHub user xuanyue202 opened a pull request: https://github.com/apache/incubator-edgent/pull/181 Enable Edgent to publish to maven repository WIth the updated build.gradle, one can publish edgent to local maven repository via: gradle publishToMavenLocal This is especially useful when edgent is used with another Maven/Gradle project. You can merge this pull request into a Git repository by running: $ git pull https://github.com/xuanyue202/incubator-edgent master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-edgent/pull/181.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #181 ---- commit 4adaaedbbd7e17e3ceb32d82787d53022723c1b5 Author: Yaoliang Chen Date: 2016-08-15T06:40:22Z add maven reop support for gradle commit 6606e62fa4d4d1e97eb573c0efca9a0ca0b179a2 Author: Yaoliang Chen Date: 2016-08-15T06:46:09Z formatting build.gradle commit 5477795e0807554895d6b0f1401b982edfd236bf Author: Yaoliang Chen Date: 2016-08-18T14:24:44Z Merge branch 'master' of https://github.com/apache/incubator-edgent ---- --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastructure@apache.org or file a JIRA ticket with INFRA. ---