Hi All! I think the question about where to find real world examples of build files is a really valid question. I find the buildr documentation great except for that part. A collection of real world build files would help a lot, especially when one is new to buildr.
Btw, since I started to use buildr, I have never looked back. Regards, Magnus El 14 apr 2013, a las 09.36, Jason Hoogland escribió: > 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" <[email protected]> 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 <[email protected]> >> 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" <[email protected]> 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" <[email protected]> >> wrote: >>>> >>>>> On Sun, Apr 14, 2013 at 12:19 AM, Jason Hoogland <[email protected]> >>>>> 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 >>
