I have merged stripped_project back to master. With this merge and a
subsequent commit, build_lib/ and build/ are gone,
bootstrap/incremental build is reduced to just mvn package or mvn,
and CI tests appear to be passing.
Please let me know if you have any issues on master. The only major
change
On Jul 6, 2013, at 3:30 AM, Charles Oliver Nutter head...@headius.com wrote:
I have merged stripped_project back to master. With this merge and a
subsequent commit, build_lib/ and build/ are gone,
bootstrap/incremental build is reduced to just mvn package or mvn,
and CI tests appear to be
hi,
On Sat, Jul 6, 2013 at 3:10 PM, Hirotsugu Asari asari.r...@gmail.comwrote:
Good to see a lot of progress being made here (especially CI!). Some
remaining issues:
- tzdata stuff is still a bit iffy. The tzdata version that jruby-core
uses is hard-coded as ${tzdata.version}. To
hi,
On Sat, Jul 6, 2013 at 8:30 AM, Charles Oliver Nutter
head...@headius.comwrote:
With this we've mostly drunk the full mvn kool-aid as far as modules
and source layout, though there will be ongoing tweaks and reorg for
nonstandard parts of JRuby. But I'm happy to see where this is going,
On Sat, Jul 6, 2013 at 10:38 AM, kristian m.krist...@web.de wrote:
currently you can do
$ mvn -Dtzdata.version=2013c -Ptzdata
but the 2013c artifact does exists and must exists before.
one why to make it more convenient is to hardcode the 2013c in to
core/pom.xml for -Ptzdata case that means
On Sat, Jul 6, 2013 at 10:46 AM, kristian m.krist...@web.de wrote:
On Sat, Jul 6, 2013 at 8:30 AM, Charles Oliver Nutter head...@headius.com
wrote:
* The clean phase for the test module wipes out all gems installed
in jruby.home (lib/ruby/gems/shared). We should probably only be
wiping out
On Sat, Jul 6, 2013 at 5:32 PM, Charles Oliver Nutter
head...@headius.com wrote:
I think we should set up a project and start pushing artifacts to
central that contain the tzdata. Then we only have to create the
artifacts for different tzdata versions once, and use the -D flag
after that to
