Publish Parent POM to simplify keeping Exporters in Sync
@poikilotherm is already working on this.
Since Jul 10, 2024.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
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?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.