Move bgee-webapp to its own project
Currently, we have
bgee-webapp in the same git project. The problem is that, each time we want to release a minor modification of the webapp interface, we need to deploy it as a hot-fix (create a branch from
master, do the update, then merge back into both
bgee-core is not stable at this point.
- keep a long-running branch, e.g.,
webapp-master. Any branch created to modify the webapp should be created from it, and this branch cold be easily merged into
master, without the need for a hot-fix. Problem is, when a
bgee-corefeature is ready to be released, we should merge the "regular"
webapp-master, then into the "real"
master. This is error-prone.
- Move the webapp to a separate project.
bgee-corewould be used as a regular dependency, so that we could point in the webapp to a stable version of it, while still being actively working on it. Small modifications to the webapp would be deployed in its regular
masterbranch, with no need to deploy a hot-fix each time.
It was decided to move the webapp to a separate project. TODOs:
- move directory with git history to new project
- allow deployment of bgee-core to maven central as a snapshot though our maven account
bgee-webapp/pom.xmlto use bgee-core snapshots.
- Should we also have a separate parent
pom.xmlto be included by all Bgee projects?
It was decided to move bgee-webapp to its own git project.