Thanks for the heads up. We haven't this issue but I must admit that we only use native ruby these days so it could have slipped past. I will try and fix it tonight if I get the chance
On Thu, May 4, 2017 at 4:09 AM, Dieter Vrancken <dieter.vranc...@luciad.com> wrote: > Dear list, > > I am trying to upgrade to Buildr 1.5.2 (running on JRuby 9.1.7.0, on > 64-bit Arch Linux). Unfortunately, with this version, my build fails during > the package :jar task. This cause seems to be the POM-related changes in > 1.5.1 and 1.5.2. Below is partial output from the bundle exec buildr > package: > > Buildr aborted! >> NameError : undefined local variable or method `pom' for >> #<Buildr::Packaging::Java::JarTask:0x1b065145> >> Did you mean? p >> com >> /home/dieterv/.rbenv/versions/jruby-9.1.7.0/lib/ruby/gems/sh >> ared/gems/buildr-1.5.2-java/lib/buildr/java/packaging.rb:214:in `block >> in initialize' >> /home/dieterv/.rbenv/versions/jruby-9.1.7.0/lib/ruby/gems/sh >> ared/gems/rake-0.9.2.2/lib/rake/task.rb:205:in `block in execute' >> org/jruby/RubyArray.java:1733:in `each' >> /home/dieterv/.rbenv/versions/jruby-9.1.7.0/lib/ruby/gems/sh >> ared/gems/rake-0.9.2.2/lib/rake/task.rb:200:in `execute' >> /home/dieterv/.rbenv/versions/jruby-9.1.7.0/lib/ruby/gems/sh >> ared/gems/buildr-1.5.2-java/lib/buildr/core/application.rb:661:in `block >> in invoke_with_call_chain' >> /home/dieterv/.rbenv/versions/jruby-9.1.7.0/lib/ruby/stdlib/monitor.rb:214:in >> `mon_synchronize' >> /home/dieterv/.rbenv/versions/jruby-9.1.7.0/lib/ruby/gems/sh >> ared/gems/buildr-1.5.2-java/lib/buildr/core/application.rb:647:in >> `invoke_with_call_chain' >> ... >> > The code at packaging.rb:214 is the line containing pom: > > class JarTask < ZipTask >> >> def initialize(*args) #:nodoc: >> super >> enhance do >> pom.invoke rescue nil if pom && pom != self && classifier.nil? >> end >> end >> > My project does not have a .pom file, nor is it configured to generate a > custom pom. It looks to me like 'pom' simply isn't defined as a method in > this case. > > Can this be fixed? As a workaround I'll just downgrade to 1.5.0 for now. > That one does work as expected. > > Thanks, > Dieter > > -- Cheers, Peter Donald
