Return-Path: X-Original-To: apmail-buildr-users-archive@www.apache.org Delivered-To: apmail-buildr-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1501FF5B4 for ; Sun, 14 Apr 2013 10:47:59 +0000 (UTC) Received: (qmail 75248 invoked by uid 500); 14 Apr 2013 10:47:58 -0000 Delivered-To: apmail-buildr-users-archive@buildr.apache.org Received: (qmail 75083 invoked by uid 500); 14 Apr 2013 10:47:58 -0000 Mailing-List: contact users-help@buildr.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@buildr.apache.org Delivered-To: mailing list users@buildr.apache.org Received: (qmail 75069 invoked by uid 99); 14 Apr 2013 10:47:58 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 14 Apr 2013 10:47:58 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of peter.j.donald@gmail.com designates 209.85.212.179 as permitted sender) Received: from [209.85.212.179] (HELO mail-wi0-f179.google.com) (209.85.212.179) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 14 Apr 2013 10:47:52 +0000 Received: by mail-wi0-f179.google.com with SMTP id hn17so735232wib.0 for ; Sun, 14 Apr 2013 03:47:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=V47RMSwkouaAKiOXQ0chGLDn3k/ty7gtqCh3sXoephI=; b=SquFpHZ6RMXR9+yVgUa9EtWxADMBwYBOxXblY4R4mTg4P/hfAA9PhRIqnXkb2ga8BH oJi+S61rpgS4LodbJoeyW9I8FyxgcV3vviuut8RlkCS7u3mZHmc9tDKVe0vBTu1CsmMK I1zt2RDvPkKq/q0fYH5JOY6rY+ar1dPRYvYk9IxgUWJQkMQcOv4zxJ9MlgJfFvYGcFYi nbtU5XQcW9utglxDRYjaRVawb7cTfeaD0eY957Kq0Hf7gg1lKU/TEAfQ6JsxK84e7Z9S Thvy/LXvzdbQwnVT9zbBhhW46/fA2ZunIReDFgobX5eXJCazxIMJ3IvEEnlkAFrzbo4W TeSg== MIME-Version: 1.0 X-Received: by 10.194.82.104 with SMTP id h8mr26514501wjy.3.1365936451857; Sun, 14 Apr 2013 03:47:31 -0700 (PDT) Sender: peter.j.donald@gmail.com Received: by 10.194.43.132 with HTTP; Sun, 14 Apr 2013 03:47:31 -0700 (PDT) In-Reply-To: References: Date: Sun, 14 Apr 2013 20:47:31 +1000 X-Google-Sender-Auth: Lz8Cau5qBIU2BNpbeXy55gkoq18 Message-ID: Subject: Re: stand-alone jar From: Peter Donald To: users@buildr.apache.org Content-Type: multipart/alternative; boundary=047d7bb049d0ffb3cd04da4fdc35 X-Virus-Checked: Checked by ClamAV on apache.org --047d7bb049d0ffb3cd04da4fdc35 Content-Type: text/plain; charset=ISO-8859-1 On Sun, Apr 14, 2013 at 8:31 PM, Jason Hoogland wrote: > One more question: if the remote artifacts are specified in an array, how > would the "jar.include" change? I expect I'll be ok with figuring out > building the Class-Path string in a loop but if you have a suggestion for > that, it would be great. > Updated the example at https://gist.github.com/realityforge/5381737 HTH > hoogs > On Apr 14, 2013 3:36 PM, "Jason Hoogland" wrote: > > > Peter, > > > > Awesome, thank you SO much, looks like the trick. How do you find all > > these buildfiles? > > > > I think i love buildr, bye bye ant, xml! > > > > hoogs > > On Apr 14, 2013 3:02 PM, "Peter Donald" wrote: > > > >> Hi, > >> > >> Now I understand. An example for this is at > >> > >> https://gist.github.com/realityforge/5381737 > >> > >> On Sun, Apr 14, 2013 at 2:00 PM, Jason Hoogland > >> wrote: > >> > >> > To break this down to simpler questions: > >> > > >> > 1. How to access a subset of the jar files buildr remotely downloaded? > >> > 2. How to include this subset as jars, without modification, within a > >> new > >> > jar package? > >> > 3. How to create a Class-Path string, properly formatted, that > includes > >> > this subset of jars, for use in the final package manifest? (Ruby > >> newbie) > >> > > >> > hoogs > >> > On Apr 14, 2013 10:17 AM, "Jason Hoogland" > wrote: > >> > > >> > > Thanks Peter, > >> > > > >> > > I am having trouble finding useful buildfile examples so will check > >> this > >> > > out. > >> > > > >> > > I am trying to do the former, nesting the dep jars inside the final > >> jar. > >> > > Then I have only one manifest file to worry about. I find it a lot > >> > cleaner. > >> > > Currently my buildfile is doing what you do, just mash all the dep > >> files > >> > > together into the jar, the problem i've got there is that the > >> MANIFEST.MF > >> > > files seem to overwrite each other, but maybe that link will help. > >> > > > >> > > hoogs > >> > > On Apr 14, 2013 9:59 AM, "Peter Donald" > >> wrote: > >> > > > >> > >> On Sun, Apr 14, 2013 at 12:19 AM, Jason Hoogland < > hoogland@gmail.com > >> > > >> > >> wrote: > >> > >> > >> > >> > I'm trying to do what my old ant build.xml does, namely: > >> > >> > 1. compile my src code into classes > >> > >> > 2. packages them into a jar > >> > >> > 3. adds the dependency jars to this jar > >> > >> > 4. includes "Main-Class" and "Class-Path" attributes to > >> > >> > META-INF/MANIFEST.MF, the latter properly formatted, e.g.: > >> > >> > > >> > >> > >> > >> I am not sure I exactly follow. Do you want to include the jars as > >> > nested > >> > >> jars or just include the files form the jar in the final jar? > >> > >> > >> > >> I usually attempt the second option and use code that looks similar > >> to > >> > >> > >> > >> https://github.com/realityforge/spydle/blob/master/buildfile#L19 > >> > >> > >> > >> to achieve this goal. > >> > >> > >> > >> HTH (And sorry if I am missing what you are trying to do), > >> > >> > >> > >> Peter Donald > >> > >> > >> > > > >> > > >> > >> > >> > >> -- > >> Cheers, > >> > >> Peter Donald > >> > > > -- Cheers, Peter Donald --047d7bb049d0ffb3cd04da4fdc35--