Rails 2.3-style plugins

[Tom Rossi]

Is there a way to include Moonshine and avoid this annoying deprecation warning?

DEPRECATION WARNING: You have Rails 2.3-style plugins in vendor/plugins! Support for these plugins will be removed in Rails 4.0. Move them out and bundle them in your Gemfile, or fold them in to your app as lib/myplugin/* and config/initializers/myplugin.rb. See the release notes for more on this: http://weblog.rubyonrails.org/2012/1/4/rails-3-2-0-rc2-has-been-released. (called from <top (required)> at /srv/tick2/releases/20120830142309/Rakefile:7)

Thanks!

Tom

[Josh Nichols]

You'd have to disable all deprecation warnings, unfortunately. Here's some ways to do that: http://stackoverflow.com/questions/9027403/eliminating-rails-2-3-style-plugins-and-deprecation-warnings

Moonshine is more than a regular type plugin, so there's a lot more involved than just moving it into a gem, unfortunately. I have a branch around, but it needs more work

- Josh

--
You received this message because you are subscribed to the Google Groups "Moonshine" group.
To view this discussion on the web visit https://groups.google.com/d/msg/railsmachine-moonshine/-/U0inZHT2YyUJ.
To post to this group, send email to railsmachin...@googlegroups.com.
To unsubscribe from this group, send email to railsmachine-moon...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/railsmachine-moonshine?hl=en.

[Jarin Udom]

Josh,

Are you still working on this? Seems like Rails 4.0 is right around the corner!

Jarin

- Josh

To unsubscribe from this group, send email to railsmachine-moonshine+unsub...@googlegroups.com.

[Jarin Udom]

Or alternately, has anyone tested the alternate method of moving it to lib/moonshine and requiring it from config/initializers?

Jarin

[Josh Nichols]

It's still on the roadmap, yeah. I did find an upstream bug for puppet that is a blocker, but haven't been able to dig into try to fix it yet: http://projects.puppetlabs.com/issues/17616#change-78360

Moonshine is a lot more involved than moving to lib/moonshine and making an initializer. For starters, lib/ is supposed to be for your app, so vendor would be a better place. I think trying vendor/moonshine is worth a shot until that puppet blocker is fixed.

To view this discussion on the web visit https://groups.google.com/d/msg/railsmachine-moonshine/-/yhJwql3aTB8J.

To post to this group, send email to railsmachin...@googlegroups.com.

To unsubscribe from this group, send email to railsmachine-moon...@googlegroups.com.

[Jarin Udom]

Hey great, looks like you got that bug resolved. If there's any way I can assist with any remaining blockers I will be happy to do what I can.

Jarin

[Josh Nichols]

It's not resolved yet. I have a fix, but it needs some work to be (hopefully) accepted. After that, either we need to update shadow_puppet to use a released version with that change, or update shadow_puppet to monkey patch puppet with the fix.

After that is going, then we need to make sure all moonshine things can be run under a bundled environment as gems. Once that is going, then the fun starts with identifying and fixing anything new in Rails 4 :)

To unsubscribe from this group and stop receiving emails from it, send an email to railsmachine-moon...@googlegroups.com.

To post to this group, send email to railsmachin...@googlegroups.com.

Visit this group at http://groups.google.com/group/railsmachine-moonshine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.