From dev-return-35525-archive-asf-public=cust-asf.ponee.io@sqoop.apache.org Tue Jan 16 14:38:14 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id BEE9718065B for ; Tue, 16 Jan 2018 14:38:14 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id AF187160C34; Tue, 16 Jan 2018 13:38:14 +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 07E37160C26 for ; Tue, 16 Jan 2018 14:38:13 +0100 (CET) Received: (qmail 48826 invoked by uid 500); 16 Jan 2018 13:38:13 -0000 Mailing-List: contact dev-help@sqoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@sqoop.apache.org Delivered-To: mailing list dev@sqoop.apache.org Received: (qmail 48815 invoked by uid 99); 16 Jan 2018 13:38:13 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Jan 2018 13:38:13 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id B0A38180640 for ; Tue, 16 Jan 2018 13:38:12 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -107.911 X-Spam-Level: X-Spam-Status: No, score=-107.911 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id wuHEYn8BR2JL for ; Tue, 16 Jan 2018 13:38:12 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id C8A905F340 for ; Tue, 16 Jan 2018 13:38:11 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id BA31FE25BE for ; Tue, 16 Jan 2018 13:38:09 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id C3B7321307 for ; Tue, 16 Jan 2018 13:38:04 +0000 (UTC) Date: Tue, 16 Jan 2018 13:38:04 +0000 (UTC) From: "Anna Szonyi (JIRA)" To: dev@sqoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (SQOOP-3052) Introduce Maven/Gradle/etc. based build for Sqoop to make it more developer friendly / open MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/SQOOP-3052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Szonyi updated SQOOP-3052: ------------------------------- Attachment: SQOOP-3052.patch > Introduce Maven/Gradle/etc. based build for Sqoop to make it more developer friendly / open > ------------------------------------------------------------------------------------------- > > Key: SQOOP-3052 > URL: https://issues.apache.org/jira/browse/SQOOP-3052 > Project: Sqoop > Issue Type: Improvement > Reporter: Attila Szabo > Assignee: Anna Szonyi > Priority: Major > Fix For: 1.5.0 > > Attachments: SQOOP-3052.patch > > > The current trunk version can only be build with Ant/Ivy combination, which has some painful limitations (resolve is slow / needs to be tweaked to use only caches, the current profile / variable based settings are not working in IDEs out of the box, the current solution does not download the related sources, etc.) > It would be nice to provide a solution, which would give the possibility for the developers to choose between the nowadays well used build infrsturctures (e.g. Maven, Gradle, etc.). For this solution it would be also essential to keep the different build files (if there is more then one) synchronized easily, and the configuration wouldn't diverege by time. Test execution has to be solved also, and should cover all the available test cases. > In this scenario: > If we can provide one good working solution is much better, then provide three different ones which become out of sync easily. -- This message was sent by Atlassian JIRA (v7.6.3#76005)