Nearly there! I ran into an issue right away though:
ext-jruby-local ~/projects/jruby $ ruby -v
invalid version selected in build ("@jruby.default.ruby.version@"), using 1.8
jruby 1.7.5.dev (ruby-1.8.7p370) 2013-06-27 @jruby.revision@ on Java
HotSpot(TM) 64-Bit Server VM 1.7.0_11-b21 [darwin-x86_64]
Seems like Constants.java isn't getting populated right.
Other comments below.
On Thu, Jun 27, 2013 at 2:21 PM, kristian <m.krist...@web.de> wrote:
> copy with maven is such complicated thing :(
> maybe I find another way to include the depending jar and get the right name
> - just found
> http://maven.apache.org/plugins/maven-shade-plugin
> which will do the trick without copy :)
I have used the shade plugin for jarjar-like renaming in the past.
>> >> same with
>> >> lib/jni
>> >> which contains the native libs unpacked from
>> >> com.github.jnr:jffi:native:1.2.5
>>
>> What's the issue?
>
>
> when I unpack that artifact it creates
> lib/jni
> with all its native libs and not
> lib/native
> and again copy/move in maven is unpleasant.
>
> but let's see what is possible though I was hoping that changing the
> directory from 'native' to 'jni' could be a possibility ;)
It is a possibility. I don't see any reason why we have to stick with
lib/native.
>> >> actually there following native jars missing in the above artifact:
>> >> ppc-AIX
>> >> sparcv9-SunOS
>> >> x86_64-FreeBSD
>>
>> Ok, good to know. I think we have support for them in jffi, but not
>> sure why they're not in JRuby repo.
>
>
> they are in ./build_lib but not on maven central inside the native jar of
> jffi from maven central !!
Ok, we'll have to release an updated artifact that includes them.
>> yecht.jar is a bit of a special case since it's built out of another
>> repo and copied into JRuby. We can probably spin a maven artifact for
>> that to be fetched and copied into the right place.
>>
> I will put that one into
> ./localrepo
> just did not think about that earlier the same as I did with all the other
> jars.
Ok. Once we have this all working we can look at the stuff in
localrepo and get real artifacts created.
>> I feel like someone has to have done this before. If they have not, we
>> should probably work with joda folks to make it happen under their
>> group, so everyone can take advantage of it.
>>
> sounds good. anyways I will take the existing code to bundle it up - maybe
> that is a good starting point for the joda-folks ;)
Yeah, that's a great idea.
> let's say once maven runs the tests and they all pass then I feel ready :)
>
> the weekends are basically family days !!!
Ok :-)
- Charlie
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
