[#CODEBASE-12] to vendorize or not vendorize our gems

Blacklight Plugin

to vendorize or not vendorize our gems

Created: 11/Feb/09 12:50 PM Updated: 31/Jul/09 04:18 PM

Component/s:

None

Affects Version/s:

2.2

Fix Version/s:

Down the Road

Issue Links:

pre-requisite

This issue is a pre-requisite for:

~~CODEBASE-54~~ rake gems:install does not work

Description

« Hide

Naomi was thinking that the installation of blacklight might be simplified if we had require statements for the required gems (with particular versions, when that matters), and ?? used capistrano ?? to cope with the plugins ...

Maybe some QA built into code to ensure all the necessary pieces are there.

maybe including system gems and so on?

All

Comments

Change History

Sort Order:

[ Permalink | « Hide ]

Bess Sadler added a comment - 13/Feb/09 04:58 PM

I believe there is already a rake task that checks for these, but I can double-check that and write tests for it.

[ Permalink | « Hide ]

Jamie Orchard-Hays added a comment - 24/Mar/09 01:55 PM

Working on this today, I came across an issue that I later found Bess had already put a ticket in for:

http://blacklightopac.org:8080/jira/browse/CODEBASE-54

It is at least a partial blocker for this ticket.

[ Permalink | « Hide ]

Naomi Dushay added a comment - 15/May/09 01:48 PM

The required gems are now in the init.rb for the plugin.

We are talking about including some more gems with the plugin, at least temporarily. This should make it easier for sites to have the correct versions associated with the plugin.

The direction of Rails is going towards "pure" gems (I think this is what Jamie said), so "vendorizing" gems (putting them with vendor/plugin/blacklight) should be thought of as a short term solution.

Vendorizing gems when they are making rapid changes (e.g. rsolr) makes sense.

[ Permalink | « Hide ]

Bess Sadler added a comment - 31/Jul/09 04:18 PM

Vendorized!