mapbox / mapbox/mapbox-navigation-android
Install dependency without token
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 651
- Forks
- 321
- PR merge metrics
- No merged PRs in 30d
Description
Hi, I want to write a public react-native plugin for the mapbox-navigation and therefore cannot include a private token for the dependency.
Right now you have to do that though. Is there a way to avoid that?
The current version doesn't seem to be available on bintray either.
From the docs:
````
allprojects {
repositories {
maven {
url 'https://api.mapbox.com/downloads/v2/releases/maven'
authentication {
basic(BasicAuthentication)
}
credentials {
// Do not change the username below.
// This should always be `mapbox` (not your username).
username = "mapbox"
// Use the secret token you stored in gradle.properties as the password
password = project.properties['MAPBOX_DOWNLOADS_TOKEN'] ?: ""
}
}
}
}
````
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue points to the Gradle Maven repository configuration shown in the body; begin by tracing how the SDK dependency is published and resolved for plugin consumers. Define done as a documented or implemented token-free installation path with the current version publicly resolvable, then verify that a public React Native plugin can consume it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- build-system, mobile
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100