We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Suggestion to publish as an android library, instead of building an application.
Apps could use this and mobly-snippet-lib in their own codebase in an artifact published to maven central.
The text was updated successfully, but these errors were encountered:
I think we already publish to Android maven, no?
Sorry, something went wrong.
mobly-snippet-lib is published to Maven, but mobly-bundled-snippets is not.
Yeah, my issue is that I'd like to use these for different apps, but with this project being targetted to a specific package, it isn't easy to reuse.
I'd like a clean dependency I can pull in, and only have additional snippets in my app specific mobly module.
Yeah, it would be ideal if we can pull the individual snippet classes as needed. But is that feasible in maven?
This might also remove the concern around targetSdk in #158, since that shouldn't apply to libraries.
xianyuanjia
No branches or pull requests
Suggestion to publish as an android library, instead of building an application.
Apps could use this and mobly-snippet-lib in their own codebase in an artifact published to maven central.
The text was updated successfully, but these errors were encountered: