So you're saying buildr is creating an invalid entry "." in your jar ?
Can you open a bug, attach such a jar, and a small project that shows the problem ? We have plenty of specs that bundle jars, so maybe you're doing something unexpected/untested. And also... can you try with our latest RC ? Our clone on github is not up-to-date with our latest changes (from the last 2 weeks) I think. On Tue, Jun 15, 2010 at 11:19, Peter Maas <[email protected]> wrote: > All, > > I'm running buildr from a github clone (made today) and have the following > problem: > > If I use the package target, or when doing a custom package the created jar > file can not be extracted: > > Peter-Maass-MacBook-Pro:target peter$ jar -tvf > dataservices-httpsession-1.jar > 1826 Tue Jun 15 20:12:34 CEST 2010 . > 0 Tue Jun 15 20:12:34 CEST 2010 META-INF/ > 193 Tue Jun 15 20:12:34 CEST 2010 META-INF/MANIFEST.MF > 0 Tue Jun 15 20:12:34 CEST 2010 META-INF/spring/1 > 1826 Tue Jun 15 20:12:34 CEST 2010 META-INF/spring/pu.xml > Peter-Maass-MacBook-Pro:target peter$ jar -xvf > dataservices-httpsession-1.jar > created: META-INF/ > inflated: META-INF/MANIFEST.MF > java.io.FileNotFoundException: . (No such file or directory) > at java.io.FileOutputStream.open(Native Method) > at java.io.FileOutputStream.<init>(FileOutputStream.java:179) > at java.io.FileOutputStream.<init>(FileOutputStream.java:131) > at sun.tools.jar.Main.copy(Main.java:783) > at sun.tools.jar.Main.extractFile(Main.java:933) > at sun.tools.jar.Main.extract(Main.java:852) > at sun.tools.jar.Main.run(Main.java:242) > at sun.tools.jar.Main.main(Main.java:1149) > > > > This happens with every jar created by buildr. > > Environment: > > * OSX 10.6.3 > * Ruby: ruby 1.8.7 (2009-06-08 patchlevel 173) [universal-darwin10.0] > * java version "1.6.0_20" > Java(TM) SE Runtime Environment (build 1.6.0_20-b02-279-10M3065) > Java HotSpot(TM) 64-Bit Server VM (build 16.3-b01-279, mixed mode) > * list of installed gems attached > > If I create a jar with the jar command supplied by the install JDK I can > unpack it without any problems. > > Any suggestions? > > -P > > > > > > > > > > >
