I can further sugared of course
On 4/19/07, Fausto Lelli <[EMAIL PROTECTED]> wrote:
> Here's the hipotesys I was working on to restyle war.rb.
> looks quite terse to me. I wouldn't go to Initializer style config
> unless some "gem" require work would be done. We could use
> both approaches though, in fact I believe rails uses the initializer
> and configures startup in environment.rb.
> I first tried YAML but I didn't seem flexible enough.
> I'm obviously open to change my mind
>
> war_file 'helloworld'
> compile_ruby true
> add_gem_dependencies false
> keep_source false
>
> libraries =
> {
> 'bsf' => {:versions => '2.2.1', :locations => 'http://www.google.it'}
> }
>
> for lib_name,lib_props in libraries
> include_library lib_name , :versions => lib_props[:versions],
> :locations => lib_props[:locations]
> end
>
> On 4/19/07, Charles Oliver Nutter <[EMAIL PROTECTED]> wrote:
> > Jon Tirsen wrote:
> > > Sure, my patch is only about fixing the fact that there are a lot
> > > more things you can do with the Configuration object than you can do
> > > with the "DSL". I definitely don't need "per-task" configurations.
> > >
> > > In general the war.rb "DSL" is a bit quirky. I think something along
> > > the lines of the standard config/environment.rb would be more
> > > familiar to Rails developers. That would have the added benefit that
> > > we wouldn't need to mirror the API of War::Configuration into a
> > > special War::Configuration DSL.
> > >
> > > Example:
> > >
> > > War::Configuration.setup do |config|
> > > config.add_jetty_library(config.java_library('jetty', '6.6.1'))
> > > # ... etc ...
> > > end
> >
> > What about YAML?
> >
> > - Charlie
> > _______________________________________________
> > Jruby-extras-devel mailing list
> > [email protected]
> > http://rubyforge.org/mailman/listinfo/jruby-extras-devel
> >
>
_______________________________________________
Jruby-extras-devel mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/jruby-extras-devel
