Ralph and Don unsure about whether there was a consensus about war files
Andrew working on a PR : if there is an empty VIVO home dir, the war file will populate it ; if it is there, but not empty, the war file will not change it. A recent pull-request is configured to make sure only the rdf files specified get loaded in the db -- but less a matter of technical detail, but vision. All the languages are included in the war file, but only the ones specified in the runtime.properties are loade
Andrew : need a consensus on that option.
Ralph : agrees
Don : what about the non i18n RDF files (abox, tbox) ? Otherwise, sounds good ; would be great for deployment on AWS
Benjamin : “all for this”
Brian: agrees too.
Michel : agrees : that solution is ok for people who just want to install VIVO; not optimal from a dev standpoint ; but as far as UQAM is concerned, we’ll be using our own installer.
Huda : “The streamlined approach seems like a good idea. I do wonder about debugging but that probably means I need to get better versed with debugging content in a .war file. That said, assuming this doesn't prevent download of the source as we normally have done it, but just adds an option for download and deployment, so in that case, anyone who wants to debug and develop the code should be set.”
Don and Ralph : discussions about CLI config maneuvers that would no longer be possible in that scenario??
Andrew : will move forward, since there seems to be consensus
Sacha : still has to test capability map, will test /review fixes, can test installs
Rachid Belkouch
Nic: will try to fix a few tickets, test events section, review fixes
Michel : fix bugs, make more regression tests, make an en_CA release (will need complex retagging in ontologies files -- will open a ticket about it > )
Andrew : will the Selenium tests will be incremental (several PR instead of a big one?) Michel : shall submit the tests by the end of sprint
Andrew : Benjamin has done rudimentary testing of a chinese version ; could it be useful to use it in the i18n testing process?
Andrew: other languages to add? (General “no”.)
Brian : will we eventually update lookup for Agrovoc vocabulary? Only available in English. (Andrew: interesting, but for another sprint?)