Skip to content
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

Deffer accessing to apollo extension properties until task execution #979

Merged

Commits on Jul 17, 2018

  1. Deffer accessing to apollo extension properties until task execution

    The issue has been discovered with plain java projects that seems gradle evaluate differently than android projects. All plugin configuration extension properties were ignored because they were accessing too soon. This PR wraps plugin extension properties with `Property` class to provide lazy evaluation for tasks during their execution. By using `Property` wrapper the min required version of gradle is bumped to 4.+. Some classes were converted back to groovy, that is done intentionally as there is some `black magic` is going on by gradle generating additional code for properties.
    sav007 committed Jul 17, 2018
    Configuration menu
    Copy the full SHA
    a643126 View commit details
    Browse the repository at this point in the history

Commits on Jul 23, 2018

  1. Configuration menu
    Copy the full SHA
    670f7a9 View commit details
    Browse the repository at this point in the history