Peter, Works marvellously, and doing it this way is substantially faster to package with builder, from 20-30s on my machine down to 1.5s.
You've got an unmatched [, and the Class-Path only works for me if the comma join is replaced by a space. hoogs On Sun, Apr 14, 2013 at 6:47 PM, Peter Donald <[email protected]>wrote: > On Sun, Apr 14, 2013 at 8:31 PM, Jason Hoogland <[email protected]> > 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" <[email protected]> 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" <[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 > > >> > > > > > > > > > -- > Cheers, > > Peter Donald >
