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 each library to maven repository #148

Open
pahjbo opened this issue Dec 12, 2023 · 1 comment
Open

publish each library to maven repository #148

pahjbo opened this issue Dec 12, 2023 · 1 comment
Assignees

Comments

@pahjbo
Copy link

pahjbo commented Dec 12, 2023

It would make each library easier to consume in other projects if they were each separately published in a maven repository - preferably maven central or perhaps more easily as a github package

Note that even the current beta could be published as a SNAPSHOT in maven repository terms

@gmantele gmantele self-assigned this Dec 12, 2023
@gmantele
Copy link
Owner

Thank you for the suggestion. It is already in top (but not first) position of my TODO list.

A major improvement I wanted to do first is now done in the adql2.1 branch: separate each library in a different directory with a different Gradle project (more specifically: Gradle sub-projects).

One of the next steps is indeed to publish former versions of the libraries in Maven.

Speaking about the adql2.1 branch, note that it is only functional for ADQLLib ; not for TAPLib. Hence the beta version. There will still be some updates of ADQLLib before its official stable release, in order to make it work correctly with TAPLib (and TAP-1.1).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants