According to the polygerrit "development story", any changes related
to polymer components (aka bower_components) involves buck invocations:
buck run //tools/js:bower2buck -- -o /tmp/newbuck
That why it doesn't really make sense to try to optimize for this use
case and to refresh polymer components in running container. This only
makes polygerrit development unnecessary slow. We are getting the main
use case to refresh the polygerrit sources in running container for
granted due to mounting the PolyGerritUiServlet to the source path.
Remove bower components rebuild filter and store zip file system in
bower component own servlet instead of leaking it to GerritLauncher
instance. Eclipse project generation depends now also on polymer
components.
Test Plan:
* Run:
buck build polygerrit && \
java -jar buck-out/gen/polygerrit/polygerrit.war daemon \
--polygerrit-dev -d ../gerrit_testsite
* Change polygerrit sources, refresh the browser window and observe
that the changes are reflected and that there is no delay for
unnecessary `buck build //polygerrit-ui:polygerrit_components`
invocations, every time browser window is refreshed.
Change-Id: If86bbbe14b9ddf0fa5001b2bbb9a39629e9b383f
d383d114c4