At commit 310e8f39 when running mvn from a clean checkout I was getting:
error: package org.joda.time does not exist
After adding joda-time dependency to core/pom.xml in commit 70efe89a8 things
started building successfully with a clean checkout.
I'm not not a maven guru so I'm not sure
I am very interested in speeding up the build for a single change. Right
now, edit any source file and "mvn" takes almost 50s on my system. With the
incremental compile that dropped to 29s.
A good portion is also the double shading. Perhaps we can do both in
parallel or defer one to a dist profile
I reverted the commit it since it is not working with this UnsafeHolder
class. I was too focus on incremental compilation that I did not do a clean
in the end :(
- christian
On Mon, Jul 8, 2013 at 8:24 PM, Hirotsugu Asari wrote:
> Hello.
>
>
> https://github.com/jruby/jruby/commit/3f93c50aa743
Hello.
https://github.com/jruby/jruby/commit/3f93c50aa743aec03d6b93f4eeecea804ff1dc2c
broke the Travis build rather spectacularly.
https://travis-ci.org/jruby/jruby/builds/8859478
Could someone with immense maven knowledge take a look?
Thanks!
hi,
after breaking the build again though it ran clean locally - the default
profile did not get activated on travis for whatever reason. but when the
joda-timezones come as separate deps from joda-time things can be cleaned
up here.
the org.jruby:jruby maven artifact is working as well the org.j
