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
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
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 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
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
