when we have all the maven artifacts in place I feel that the biggest step is done (I might be wrong ;)
currently I use the same build directory structure as ant uses (up to one or two exceptions). so something like $ mvn package $ ant dist should/will still work. I personally find it important if people start using the new build as soon as possible problems as early as possible, like Charles Constants.java issue which I could not see on my side. but in the end every one should feel comfortable when we switch !!! - christian On Fri, Jun 28, 2013 at 12:02 AM, Thomas E Enebo <tom.en...@gmail.com>wrote: > On phone so this will be brief. How about what was ant dist? That one is > important since it is for more than maven artifacts. > > -Tom > On Jun 27, 2013 4:24 PM, "kristian" <m.krist...@web.de> wrote: > >> hi Wayne, >> >> jnr/jffi has no issues :( >> other repos in jnr do have issues though. >> - christian >> >> >> >> On Thu, Jun 27, 2013 at 10:02 PM, Wayne Meissner <wmeiss...@gmail.com>wrote: >> >>> On 28 June 2013 05:21, kristian <m.krist...@web.de> wrote: >>> >>> >> >> 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 !! >>> >>> Kristian, can you open an issue at https://github.com/jnr/jffi (just a >>> list of the missing ones will be fine) , and I will include those in >>> the next jffi release. >>> >>> --------------------------------------------------------------------- >>> To unsubscribe from this list, please visit: >>> >>> http://xircles.codehaus.org/manage_email >>> >>> >>> >>
