-
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
Upload documents in Vitro|VIVO #3683
Conversation
…tro RDF internationalization files
d090ebd
to
f3374f7
Compare
installer/home/pom.xml
Outdated
<groupId>org.vivoweb</groupId> | ||
<artifactId>vitro-languages-home-core</artifactId> | ||
<version>${project.version}</version> | ||
<type>tar.gz</type> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Out of curiosity, why is vivo-languages type pom and vitro-languages tar.gz?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think you are right, my thought it that as we publish poms it should be set to pom to be downloaded.
* feat: added config example for file upload * fix: Add vitro-languages-home-core as installer dependency to have Vitro RDF internationalization files * fix: change vitro-languages-core-home dependency type from tar.gz to pom * fix: for github action
VIVO GitHub issue: (please link to issue)
Goes with Vitro PR
Goes with Vitro-languages PR
Provides configuration example for document upload.
Adds dependency on vitro-languages-home-core
Interested parties
Tag (@ mention) interested parties or, if unsure, @VIVO-project/vivo-committers