Yikes. I understand now, thanks. Kind of darned if we do, darned if we don't.
On 10/29/07, Ola Bini <[EMAIL PROTECTED]> wrote: > > Chris Nelson wrote: > > > > > > On 10/27/07, *Charles Oliver Nutter* <[EMAIL PROTECTED] > > <mailto:[EMAIL PROTECTED]>> wrote: > > > > Also...on the "import" deprecation issue: we kinda made our bed in > 1.0 > > by including "import", and we can't really deprecate it on the 1.0 > > line. > > But we could deprecate it in 1.1 and provide an alternative. I'd > feel > > better about that than saying it's deprecated across the board. > > > > > > Can we get more detail on this? Sounds like a pretty terrible > > regression if import doesn't work anymore. Any way we can fix this > > rather than taking it away? I think you may have some pretty > > frustrated users if you do that, since that would break a lot of code > > I should think. Is there a bug to look at? > > > > --Chris > > > Import have _never_ worked correctly. The problem is that rake defines a > global import-method on Kernel, which clashes with our Java integration > import. The way I discovered this was when writing my book, I created an > example that imported Java code in the Rails lib-directory. But as soon > as I tried to do rake db:migrate or rake test, it failed because the > files in lib couldn't be loaded. This was back in April/May, and the > JIRA issues dates back to then. > > Cheers > > -- > Ola Bini (http://ola-bini.blogspot.com) > JRuby Core Developer > Developer, ThoughtWorks Studios (http://studios.thoughtworks.com) > Practical JRuby on Rails (http://apress.com/book/view/9781590598818) > > "Yields falsehood when quined" yields falsehood when quined. > > > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email > >
