[Archivesspace_Users_Group] Plugin Gem Best Practices
mark at dishevelled.net
Fri Nov 4 06:09:38 EDT 2016
This is a bit of a shot in the dark, but for the Newrelic gem I found I
had to add a snippet to the top of the plugin Gemfile like this:
The call to `ASpaceGems.setup` takes care of setting the gem load path
You're not supposed to have to do this, so if you find it magically
fixes things, I'll take a look and see if the situation can be
improved. The backend is supposed to take care of all of this, but
perhaps the Gemfile is being loaded earlier than expected.
Alexander Duryee <alexanderduryee at nypl.org> writes:
> Thanks! I unzipped a fresh release of ASpace, set up a plugin with a
> Gemfile, and ran initialize_plugin. It pulled in the gem + dependencies
> into gems/ without issue. However, when trying to run ASpace with the
> plugin (empty except for the gems), I got:
> Bundler::GemNotFound: Could not find gem 'timetwister (= 0.2.7) java' in
> any of the gem sources listed in your Gemfile or available on this machine.
> The gem is installed both on my machine and in the plugin's gems
> directory. It's a locally-developed gem, so I didn't explicitly build it
> for JRuby - is this necessary to load it into ASpace?
<mark at dishevelled.net>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Archivesspace_Users_Group