For now i added this in my root rakefile
namespace :install do
desc "Install development gems"
task :dev_gems do
dev_gems = Dir.glob("#{Merb.root}/gems/development/*")
dev_gems.each do |dev_gem|
Merb.logger.info("Installing #{dev_gem}")
Merb::RakeHelper.install_gem_from_source(dev_gem, :install_dir
=> "#{Merb.root}/gems", :ignore_dependencies => true)
end
end
end
I know is not the best way because for every edit I need to do rake
install:gem_dev, but in this way the structure is very clean.
Any suggestion?
On 12 Nov, 09:55, DAddYE <[EMAIL PROTECTED]> wrote:
> Yehuda,
>
> I do:
>
> $ merb-gen plugin myplugin
> $ mv myplugin gems/gems
> $ cd gems/gems/myplugin
> $ rake gemspec
> $ mv myplugin.gemspec ../../specifications
>
> Then I added a dependency in dependency.rb
>
> dependency "myplugin"
>
> but I've:
>
> FATAL: The file backend was not found
>
> but with gem "myplugin" everything work fine.
>
> Why?
>
> For example for me that I come from rails Ive my own plugins, like
> fileupload/managment, backend, usermanagment (with roles modules and a
> lot of fatures)...
>
> I need to port this for merb, and I love the new philosophy where
> plugins are gems, but manage in dev modode 3/4 plugins is very very
> hard, If I need to add/remove a new file in my gems/plugins I need to
> rake a new gemspec an repeat the last 3 steps.
>
> Is possible improve this process making a new dir in gems called "dev"
> or "development" where we can put the source of our gems and test it
> in our app?
>
> Many Thanks!
>
> On 11 Nov, 17:38, DAddYE <[EMAIL PROTECTED]> wrote:
>
> > Yehuda, many thanks! I love this philosophy ;)
>
> > On 11 Nov, 17:31, "Yehuda Katz" <[EMAIL PROTECTED]> wrote:
>
> > > Once you bundle gems in your app, you can continue to make changes inside
> > > your <app-root>/gems/gems directory, which will work like Rails editing.
> > > It's important that we retain the "plugins are gems" philosophy.
> > > -- Yehuda
>
> > > On Tue, Nov 11, 2008 at 10:23 AM, DAddYE <[EMAIL PROTECTED]> wrote:
>
> > > > Re-write in some understandable language :D
>
> > > > I know that plugins are "gems" but one question, for simplify the
> > > > development stage is possible "a la rails" the live editing ?
>
> > > > For some people can be a problem for every change do rake install.
> > > > What do you think about?
>
> > > > If now work, can be in future inside a plugin development directory?
>
> > > > On 11 Nov, 16:20, DAddYE <[EMAIL PROTECTED]> wrote:
> > > > > Ha! Okey!
>
> > > > > I now that are plugins are "gems" but one question, for simplify the
> > > > > development stage is possible "a la rails" the live editing?
>
> > > > > For some people can be a problem for every change do rake install.
>
> > > > > What do you think ?
>
> > > > > On 11 Nov, 16:11, "Yehuda Katz" <[EMAIL PROTECTED]> wrote:
>
> > > > > > If that works, it's by accident. Plugins are just gems and should be
> > > > treated
> > > > > > like gems. We'll try to get a more detailed tutorial soon, but the
> > > > basics
> > > > > > are that you generate a plugin, and then install it (into your
> > > > > > system
> > > > or
> > > > > > your app). They're not like Rails plugins that just loosely hang
> > > > > > out in
> > > > your
> > > > > > app.
> > > > > > -- Yehuda
>
> > > > > > On Tue, Nov 11, 2008 at 10:06 AM, DAddYE <[EMAIL PROTECTED]> wrote:
>
> > > > > > > Hello Yehuda,
>
> > > > > > > one question, If I do mymerbapp$ merb-gen plugin myplugin
>
> > > > > > > Inside my merb app myplugin will be loaded correctly.
>
> > > > > > > So is not possible put it in another dir like plugins?
>
> > > > > > > On 11 Nov, 15:57, "Yehuda Katz" <[EMAIL PROTECTED]> wrote:
> > > > > > > > I think there's a misunderstanding here.
> > > > > > > > DAddYE, plugins in Merb are just gems. The plugin generator in
> > > > > > > > Merb
> > > > is
> > > > > > > > designed to be used outside of a Merb app, and then you just
> > > > > > > > load
> > > > them in
> > > > > > > > via the regular dependencies. To make the gem, run rake package
> > > > > > > > or
> > > > rake
> > > > > > > > install inside the generated package.
>
> > > > > > > > -- Yehuda
>
> > > > > > > > On Tue, Nov 11, 2008 at 9:29 AM, Michael Klishin <
>
> > > > > > > > [EMAIL PROTECTED]> wrote:
>
> > > > > > > > > 2008/11/11 DAddYE <[EMAIL PROTECTED]>:
>
> > > > > > > > > > Michael,
>
> > > > > > > > > > thanks for your suggestion, last question, how Merb can
> > > > > > > > > > know if
> > > > there
> > > > > > > > > > is a new directory/plugin in root app? Do you know the
> > > > > > > > > > piece of
> > > > code?
>
> > > > > > > > > If what you mean here is "how to enable autoload for
> > > > > > > > > spinoffs",
> > > > > > > > > I need to find out if I added it using Merb.push_path or it
> > > > > > > > > just
> > > > works
> > > > > > > > > somehow.
>
> > > > > > > > > Actually I did not notice I did any server restarts, but I
> > > > > > > > > doubt
> > > > it's
> > > > > > > gonna
> > > > > > > > > work
> > > > > > > > > this way out of the box. I'll look it up later today or
> > > > > > > > > tomorrow.
> > > > > > > > > --
> > > > > > > > > MK
>
> > > > > > > > --
> > > > > > > > Yehuda Katz
> > > > > > > > Developer | Engine Yard
> > > > > > > > (ph) 718.877.1325
>
> > > > > > --
> > > > > > Yehuda Katz
> > > > > > Developer | Engine Yard
> > > > > > (ph) 718.877.1325
>
> > > --
> > > Yehuda Katz
> > > Developer | Engine Yard
> > > (ph) 718.877.1325
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"merb" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/merb?hl=en
-~----------~----~----~----~------~----~------~--~---
