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 passing.
>
> Please let me know if you have any issues on master. The only major
> change to BUILDING workflow is that you can use "mvn" or "mvn package"
> to bootstrap *and* do update builds. Everything else remains pretty
> much the same (and doing "mvn verify" won't cause any issues, since we
> don't have phases after "package" doing anything special right now).
>
> 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,
> and it seems pretty clean at the moment.
>
> FWIW the JRuby maven plugins snapshots *were* pushed, but were not
> specified in pluginRepositories section.
>
> Still remaining to do:
>
> * 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 the gems we bootstrap with, or not wiping out this dir at
> all.
> * The Java-based unit tests still don't pass completely.
> * Dist artifacts need to be reassembled.
> * Continued tidying up of repository.
> * Additional submodules (probably) for:
> ** spec (or this may move under test
> ** lib/** (to allow building managing maven artifacts for different
> stdlib versions)
> ** bench (or this may move under test)
> ** tool (utilities for preparing releases, updating stdlib, etc
>
> At some point I'll review these threads to make sure we have not
> missed anything else.
>
> - Charlie
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 build with the latest version, core/pom.xml
must be modified, which is a bit awkward.
jar-complete target needs to be converted. (Did I miss this?)
