-
Notifications
You must be signed in to change notification settings - Fork 1
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 Kuksa SDK Snapshot Builds to MavenLocal #6
Comments
Closes: eclipse-kuksa#6 Signed-Off-By: Andre Weber <[email protected]>
Closes: eclipse-kuksa#6 Signed-Off-By: Andre Weber <[email protected]>
Closes: eclipse-kuksa#6 Signed-Off-By: Andre Weber <[email protected]>
GitHub Packages requires each user to provide a custom api key to download our dependencies. Therefore GitHub Packages is out of the question for now. An issue was created inside the eclipse helpdesk (https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/3684), however that topic might take some more time. Changing the scope of this ticket therefore from "Publish to a global repository" to "Publish to MavenLocal" for now, so we can use it internally for testing until the issues are sorted out. |
Closes: eclipse-kuksa#6 Signed-Off-By: Andre Weber <[email protected]>
Closes: #6 Signed-Off-By: Andre Weber <[email protected]>
Is your feature request related to a problem? Please describe.
We want to provide an easy way to integrate the Kuksa SDK along with it's dependencies.
Describe the solution you'd like
To provide an easy way to integrate the Kuksa SDK, we should publish our Kuksa SDK to Maven Local
the GitHub Packages Registry (https://docs.github.com/en/packages/working-with-a-github-packages-registry). This allows an easy retrieval of the Kuksa SDK using Maven / Gradle dependency resolution.Whenever something is merged to main, the resulting Kuksa SDK should be published as a snapshot build.Non-Snapshot Builds / Releases will be part of a separate ticket.
The text was updated successfully, but these errors were encountered: