You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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?
The text was updated successfully, but these errors were encountered: