Skip to content
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

Publish Parent POM to simplify keeping Exporters in Sync #10482

Open
qqmyers opened this issue Apr 10, 2024 · 0 comments
Open

Publish Parent POM to simplify keeping Exporters in Sync #10482

qqmyers opened this issue Apr 10, 2024 · 0 comments
Labels
Type: Feature a feature request
Milestone

Comments

@qqmyers
Copy link
Member

qqmyers commented Apr 10, 2024

Overview of the Feature Request
Several recent automated PRs in the dataverse-exporters repo are to update libraries that are also in use in Dataverse. It would be useful to be able to keep those in sync with the version in Dataverse, which, per @poikilotherm , would be easier if the Dataverse parent pom is published to maven central. We discussed today that this might be something that could be looked into around ~June 2024 (If anyone has time before then feel free to pick this up!) with work to update the example and current external exporters to adopt using the Dataverse parent pom being done ~ in parallel. Having the pom available from maven could help other projects as well and may also allow exporters to be smaller (and use the libraries already deployed in the war).

Any brand new behavior do you want to add to Dataverse?
This is nominally a change in the repo rather than the Dataverse software per se.

Any open or closed issues related to this feature request?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Feature a feature request
Projects
Status: No status
Development

No branches or pull requests

1 participant