Hi, I am still unable to reproduce this under Ruby 2.0.0-p247. In this project do you do anything different regarding packaging or use any particular addons that may be interacting with packages. What specific version of buildr/ruby/os are you using?
On Fri, Nov 1, 2013 at 1:40 AM, Chris Bozic <[email protected]> wrote: > This happens for javadoc packages as well. > > > On Wed, Oct 30, 2013 at 12:06 PM, Chris Bozic <[email protected]> wrote: > >> Peter, >> >> This is really interesting... I can see the behavior I described using >> the simple project definition you sent. It seems to be occurring only when >> I install Buildr against Ruby 2.0.0 If I use a 1.9 version of Ruby, >> everything is fine. >> >> At least I have a workaround but I'm wondering if you also see the issue >> against Ruby 2.0.0. >> >> $ruby --version >> ruby 2.0.0p247 (2013-06-27 revision 41674) [x86_64-darwin12.3.0] >> >> Thanks, >> Chris >> >> >> >> On Tue, Oct 29, 2013 at 4:07 PM, Peter Donald <[email protected]>wrote: >> >>> Hi, >>> >>> Can you give a small snippet that exhibits this behaviour? If I do >>> something like the following I get the expected source jar created >>> (x-1.0.0-sources.jar). >>> >>> define "x" do >>> project.version = '1.0.0' >>> project.group = 'x' >>> >>> package(:jar) >>> package(:sources) >>> end >>> >>> >>> -- >>> Cheers, >>> >>> Peter Donald >>> >> >> -- Cheers, Peter Donald
