Re: mangled names, ah, you mean *Ruby* Ruby code, not Java Ruby code. But do you mean for internal libs (site-ruby) or apps? For apps, you can just include the real jar in the classpath (which is the situation I have, hence the potential version conflict).
On 6/14/08, Charles Oliver Nutter <[EMAIL PROTECTED]> wrote: > > Bill Dortch wrote: > >> The jar-complete ant target currently renames the ASM classes >> (org.objectweb.*), but not classes for Joda Time, JNA, and other external >> libs. Is there a reason not to rename the others? For orgs like mine, >> which prefer not to modify imported open source libs, it would be helpful if >> all external dependencies were also renamed, to avoid classpath conflicts. >> >> I can change this, but wanted to check first whether anyone sees a reason >> not to do so. >> > > I don't really see a reason not to, other than that JNA has native libs > that would not take kindly to package renaming. One thing I *don't* like > about the renaming is that if I want to use any of those libraries from > within Ruby code (like ASM) I have to import the mangled name. That kinda > sucks :( > > - Charlie > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > >
