Fix build jinja2

[pwalczysko]

I have declared

declaring jinja2 as a dependency of omero-mapr

as per #85 (comment).

@will-moore : Is there any reason why you went for the (imho much more complex) options in #87 ?

[pwalczysko]

@will-moore @jburel : Maybe there was some larger plan about why not to go the declare jinja2 as dep way. But here now the tests are passing -> possibly there could be some value in simply going with the option as declared here ?

[will-moore]

@pwalczysko That's great - thanks. I started trying to fix this one way and ended up taking a more complex route, but this way is nice.

[pwalczysko]

@jburel Do you want to merge please ? I think this would unblock @will-moore with minimal effort expended

[snoopycrimecop]

Conflicting PR. Removed from build OMERO-plugins-push#227. See the console output for more details.
Possible conflicts:

• PR mapr extension of webclient #74 will-moore 'mapr extension of webclient'
  • requirements.txt

--conflicts

[snoopycrimecop]

Conflicting PR. Removed from build OMERO-plugins-push#228. See the console output for more details.
Possible conflicts:

• PR mapr extension of webclient #74 will-moore 'mapr extension of webclient'
  • requirements.txt

--conflicts

[will-moore]

Hmmm - just looking at this again because of the conflicts. I don't think I really looked at this closely before as I realise now this is updating the installation dependencies so that anyone installing mapr will also install jinja2. This is not ideal as the app has no requirement for jinja2 - it's only needed for testing because the testing setup imports omero.util which imports jinja. And it only imports omero.util to perform populate metadata, since omero.util did that before we had the omero-metadata plugin.

[jburel]

This adds a dependency not required by the app