From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 52194 invoked by alias); 6 Jan 2017 16:52:40 -0000 Mailing-List: contact kawa-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: kawa-owner@sourceware.org Received: (qmail 52169 invoked by uid 89); 6 Jan 2017 16:52:39 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.0 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RCVD_IN_SORBS_SPAM,SPF_PASS autolearn=ham version=3.3.2 spammy=Ivy, Upload, jars, jar X-HELO: mail-qt0-f172.google.com Received: from mail-qt0-f172.google.com (HELO mail-qt0-f172.google.com) (209.85.216.172) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 06 Jan 2017 16:52:28 +0000 Received: by mail-qt0-f172.google.com with SMTP id v23so83704762qtb.0 for ; Fri, 06 Jan 2017 08:52:28 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=NSYWtv6XtkXIrrB2keonnMVDe4OtohW5JlrUNT8ak3s=; b=bser02iRf38VZ4YfIpiN6/8tryia8vWVzsKT06lQ/4cpIAAV/WqAWvhLJKoWAalRrc qLNeQC3foMM1L9oqDfoik+jtXJLAwEL2Yht8ZZr32Ue6f9wa5K87WaoHpV7Pwb83se/k ZVVIEFtxxboO5/Ikr/d0M5oUreVux/CHaW4wEdEjjGLUDXL6Tgv8zmy6lg3hsLrN3h9I 7cCeL6v0IECpyJKhMrwqOxh9MbU/xkTfr5+aODb+nbosK7mzEJJsijruQ//bSDkvWIJP x/359t5FL3Ix3UhH2NJ3P3YE0Uxc3/Dy2W4oOUOuwnPFNDHFO/lpe3uX4MUTZ71LGR0+ Oirg== X-Gm-Message-State: AIkVDXLeLa6c76Fhn5HPvJt60k1odXyzhaXztBJCbjotgZNIJENzryCElevvVBsa0vVCy0INwlHOkO+2D7PnvQ== X-Received: by 10.200.47.100 with SMTP id k33mr1823414qta.241.1483721546889; Fri, 06 Jan 2017 08:52:26 -0800 (PST) MIME-Version: 1.0 Received: by 10.140.88.243 with HTTP; Fri, 6 Jan 2017 08:51:46 -0800 (PST) From: Duncan Mak Date: Fri, 06 Jan 2017 16:52:00 -0000 Message-ID: Subject: More changes to future Kawa releases? To: kawa mailing list Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes X-SW-Source: 2017-q1/txt/msg00011.txt.bz2 Hello Per, I know that the release process has changed quite a bit since the 2.0 release. I have a couple more suggestions. 1) Upload kawa jars to maven I noticed that the version listed on Maven central is pretty old. I think it will be good to have the latest jars available on Maven. https://search.maven.org/#search%7Cga%7C1%7Ckawa For the project that I'm working on right now, I checked in jar files into my repo, but moving forward, having artifacts hosted is the right thing to do, and will enable both Ant users (via Ivy) or Maven users to track dependencies without checking in binaries to the source tree. 2) Ship the build-tools classes in another jar? The Kawac ant task is built as part of the build-tools target, but it's not available outside of the kawa source tree. I tried to use the Kawac task in my own project, and I couldn't get it to work until I copied the 'tools' directory from the Kawa tree into my own. Once I have worked out a reasonable system, I plan to write out a set of instructions for building projects in Kawa. A good first step might be to ship the kawac ant task as part of the release. What do you think? Let me know where I can help. -- Duncan.