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
Hi everyone,
I wonder what is the reason for having kcl only on github repo?
Using GitHub requires credentials to access Maven artifacts, which is inconvenient. It makes using kcl-lib harder, as build machines often don’t have GitHub credentials.
Is it possible to have kcl-lang artifact in the central repository?
The text was updated successfully, but these errors were encountered:
This issue is due to the fact that the groupId used by kcl java sdk is not our domain name, so we cannot upload to maven repository; this is a known issue and is being solved; it is expected to be solved in the next major version 0.12.0.
Hi everyone,
I wonder what is the reason for having kcl only on github repo?
Using GitHub requires credentials to access Maven artifacts, which is inconvenient. It makes using kcl-lib harder, as build machines often don’t have GitHub credentials.
Is it possible to have kcl-lang artifact in the central repository?
The text was updated successfully, but these errors were encountered: