lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jamie Orchard-Hays (JIRA)" <>
Subject [jira] Updated: (SOLR-154) Added package tasks for creating Rails plugin and namespaced both the rails and gem packaging
Date Fri, 09 Feb 2007 21:33:06 GMT


Jamie Orchard-Hays updated SOLR-154:

    Attachment: Rakefile_2.diff

I've removed the old package:vendor task and replaced it with rails:install_solrb. This task
depends on rails:package and takes the environment variable PLUGINS_DIR which is the path
to the vendor/plugins directory to which the user wants to install solrb. If PLUGINS_DIR is
not given, an exception with a message is raised. 

> Added package tasks for creating Rails plugin and namespaced both the rails and gem packaging
> ---------------------------------------------------------------------------------------------
>                 Key: SOLR-154
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>          Components: clients - ruby - flare
>         Environment: Ruby and Ruby on Rails
>            Reporter: Jamie Orchard-Hays
>         Attachments: Rakefile.diff, Rakefile_2.diff
> Solrb's (sol.rb's?) rake file has a package:vendor task that is not generating proper
rails plugin structure. Rather than just fix this, I've added a PackageTask to package up
a proper Rails plugin directory structure and also build distributable packages. Included
are the README, LICENSE.txt, and init.rb generated and destroyed on the fly. Also, I've namespaced
the Gem PackageTask and the Rails PackageTask, so the commands:
> rake rails:package (and repackage, clobber, clobber_package)
> rake gem:package (and the rest...)
> package their files up and dump them into pkg/rails and pkg/gem, respectively. Their
clobber tasks will only remove the sub-directory under pkg/, not pkg/ itself.
> rake package, rake repackage run both package tasks, while rake clobber and rake clobber_package
remove the complete pkg/ directory.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message