It's better maintained and it seems to provide more features
as well.

Vet, Owner, Visit. The Visit "aggregate" is a little artificial
but it demonstrates a useful point about not holding on to
references of "parent" (reference data) objects, i.e. the Visit has
an Integer petId, instead of a Pet field. In principle this app is
now almost ready to migrate to multiple services if anyone wanted
to do that.

I saw on twitter the reference of an article (in french):
http://javaetmoi.com/2016/08/migrer-vers-spring-boot/

That article concludes with something along the lines of  "Besides the
EhCache and Maven configuration, Petclinic does not hold a single line
of XML anymore".

Looking at the code, we can remove more XML if you want. This PR migrates
the cache infrastructure to EhCache 3 and JCache (JSR-107). This also
reduces the number of dependencies.

responsive menu fix - data-target attribute added

responsive menu fix - data-target attribute added

This reverts commit be048ae2.

- petclinic.css is now auto generated, therefore it is put in the
ignore list
- vendor folder is removed in favour of webjars
- remove several maven dependencies which are already managed by spring
boot
- unfortunately, lesscss maven plugin does NOT support importing from
classpath, as a result, bootstrap is unpacked during process-resources
phase, we need need to find a better resolution
- remove bower integration

- remove custom xml view, use springboot builtin xml view
- remove oxm maven dependency
- remove json-simple maven dependency (seems not relevant anymore)
- update vetsXml test using xpath

abstract the page layout into “layout.tag”

abstract the page layout into “layout.tag”

- In the Jdbc implementation: pets belonging to a visit were not added.
- In the Jpa implementation: query variable was wrong.
- Test case: AbstractClinicServiceTests.shouldFindVisitsByPetId()