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
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).
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
The text was updated successfully, but these errors were encountered: