Blacklight Plugin

Currently, if you use the template installer, and ask it to install jetty for you, it puts it inside the blacklight plugin:

your_app/vendor/plugins/blacklight/jetty

I see two problems with this.

1) I think an expected use case for this installed jetty is that the local maintainer will begin modifying it to meet their needs. However, if they do so, and later update their blacklight plugin -- that jetty can easily be lost, depending on how they do the upgrade. In general, I don't think we should encouraging any localized stuff to be in the blacklight plugin directory, it should remain pristine, so it can be upgraded simply by replacing the whole directory.

2) That is the same location that "git submodule update" will try to put the 'test' jetty for running tests against, and that the BL tests will expect a test jetty to be. But I could see easily wanting both a test jetty (entirely unmodified, goes with the version/snapshot of BL you have, matching it's tests), AND wanting a sample jetty to get started customizing for my actual app. They ought not to be expected to be in the same place.

Proposal:

Change the template installer to put the optional jetty install at your own app's RAILS_ROOT/jetty . Change any built-in default config to expect jetty for production and development to by default be at that location. (jetty for test remains where it is).


Any downsides to this? Please comment with concerns or support or opinions in this ticket. If I get no comments, I'll assume everyone's okay with it, and do it!