Done:
> * From old jar building: install spi services stuff under meta-inf
> * From old test runs: compile test files. I'm hoping these can be run
> as part of the maven build and we won't actually need to add them to
> the rake test runs (i.e. these can be our smoke tests during
> packaging)
I a
Ok, things are slowly falling together, so he's another update.
New working:
* tzdata stuff (waiting on confirmation from Hiro)
Known remaining:
* tests passing (they're closer but embed tests and a couple main
tests still fail)
* OSGi bnd bundle stuff from jar-jruby-dist into maven (I tried us
Update! And good news!
The following items are now working properly:
* CI green (usually, as before) and running the same sets of tests as before
* Simplified bootstrapping (more on that below)
I have commited BUILDING.md which describes how to get up and going. I
have preferred to recommend usi
On 3 July 2013 16:31, Charles Oliver Nutter wrote:
> * cext handling?
Kill it! Kill it with fire!
As much as I don't like breaking backward compatibility in a minor
point release, cext is pretty broken as it stands right now, and if
the external project is ready to roll, then there is a path f
On Wed, Jul 3, 2013 at 2:55 AM, Wayne Meissner wrote:
> On 3 July 2013 16:31, Charles Oliver Nutter wrote:
>
>> * cext handling?
>
> Kill it! Kill it with fire!
>
> As much as I don't like breaking backward compatibility in a minor
> point release, cext is pretty broken as it stands right now, a
On Wed, Jul 3, 2013 at 7:31 AM, Charles Oliver Nutter
wrote:
> What else?
readline and openssl depends on jruby-core-1.7.4 from maven central which
is not really nice especially if I think of OS distribution trying to
bootstrap a jruby build.
yesterday I tried to get the whole thing working wi
it is based on the pom.xml from two days ago - so the test part is not
working as on master.
the main difference is the the java sources and tests went into the
jruby-core directory (jruby-core/src/main/java, jruby-core/test).
for eclipse project use jruby-core and activate maven on eclipse and
On Wed, Jul 3, 2013 at 8:35 AM, kristian wrote:
> it is based on the pom.xml from two days ago - so the test part is not
> working as on master.
>
> the main difference is the the java sources and tests went into the
> jruby-core directory (jruby-core/src/main/java, jruby-core/test).
I'm willing
On Wed, Jul 3, 2013 at 4:27 PM, Charles Oliver Nutter
wrote:
> I'm willing to entertain this, but having our sources *four* levels
> deep in the repository is pretty unpleasant. Of course it would be
> three levels deep if we just did src/main/java.
>
I did follow the maven conventions on purpose
Updates... we're nearly there, I think :-)
We have continue reorganizing the repository into maven modules, which
makes it possible to isolate subsystems more easily. This work is
being done on the branch "stripped_project".
The branch has the following:
* build_lib is gone (yay!). Resulting src
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
chan
hi,
On Sat, Jul 6, 2013 at 8:30 AM, Charles Oliver Nutter
wrote:
>
> 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
On Sat, Jul 6, 2013 at 10:46 AM, kristian wrote:
> On Sat, Jul 6, 2013 at 8:30 AM, Charles Oliver Nutter
> 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 the gems we bootstrap with,
On Sat, Jul 6, 2013 at 10:35 PM, Charles Oliver Nutter
wrote:
> On Sat, Jul 6, 2013 at 10:46 AM, kristian 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.
Responses and updates!
On Sun, Jul 7, 2013 at 6:42 AM, kristian wrote:
> it turns out to be to error prone to keep things consistent over time. there
> are gems. specifications and bin files to be deleted and they need to be
> hardcoded for clean up. so better leave the gems installed :)
That se
15 matches
Mail list logo
