librariesio / gradle-parser

:coffee: Parse gradle files and return JSON

Gradle parser

A tiny node.js web service for parsing dependency information from build.gradle files for Libraries.io.

Development

Source hosted at GitHub. Report issues/feature requests on GitHub Issues. Follow us on Twitter @librariesio. We also hangout on Slack.

Running locally

docker run -p 5000:5000 -it $(docker build -q .)

Note on Patches/Pull Requests

• Fork the project.
• Make your feature addition or bug fix.
• Add tests for it. This is important so I don't break it in a future version unintentionally.
• Add documentation if necessary.
• Commit, do not change procfile, version, or history.
• Send a pull request. Bonus points for topic branches.

Copyright

Copyright (c) 2017 Andrew Nesbitt. See LICENSE for details.

gradle-parser's Issues

Support dependencies with inline variables

Current state

• Dependencies with the version specified as an inline text are picked up, e.g. compile "com.squareup.okhttp3:okhttp:3.11.0" (example)
• Dependencies with the version specified as an inline variable are not picked up, e.g. compile "com.squareup.okhttp3:okhttp:$okhttpVersion" (example)

Target state

• Both, versions defined as inline text or an inline variable are picked up.

Background

• Groovy allows to use inline variables in double quoted strings. The variable is typically defined in the same .gradle file or in a separate file such as build.gradle in the root of the project or in properties.gradle which can be stored in different locations and also gets read in by gradle.
• Another common pattern is to store versions and dependencies strings in the special buildSrc/ module. Here is an example implemented in Kotlin but used from within the Groovy build.gradle files.