-
Notifications
You must be signed in to change notification settings - Fork 127
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VIVO-1443: Decouple VIVO build from installation #3034
Comments
Andrew Woods said: Notes:
Notes revisited (2019-05-17):
|
Graham Triggs said: The pom.xml in the installer project is designed to do nothing if you do not provide any of the configuration that is in the (example-)settings.xml. Additionally, if you run Maven with the installer profile de-activated (-P!installer), then it wont include that project. In either case, Maven will generate artifacts that are then installed in the local Maven repository. But in most cases, if you are doing full source builds, it is better to be working in a single reactor, otherwise you quickly run into a confusion as to whether you are using up to date assets, assets from Maven central, etc. |
Andrew Woods said: Related PRs: Accompanying instructions for "third-tier" builds: |
Andrew Woods said: Guidelines for iteration on this task after 2020-10-23 conversation with Brian and Benjamin.
|
Andrew Woods said: With the exception of moving the "themes" into the "home-files.tar", the other sub-tasks listed above are not included in the previous pull-requests: |
Andrew Woods said: The additions to pr-VIVO-197 and pr-Vitro-192 work well. |
Andrew Woods said: Resolved with: ..and supported with: https://github.com/vivo-community/vivo-custom-webapp |
Brian Lowe said: War deployment reverted with commits To be further discussed for next release in order to ensure that existing custom installations are not left behind. |
Andrew Woods (Migrated from VIVO-1443) said:
This task is to decouple the Maven build process:
mvn clean install
, from the installation process.Building VIVO should run the unit and integration tests as well as generate artifacts that can subsequently be installed.
Draft installation requirements:
The text was updated successfully, but these errors were encountered: