[GRADLE-3297] Deprecation warning when using ’–offline' Created: 08/May/15  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 2.4
Fix Version/s: None

Type: Bug
Reporter: René Gröschke (Inactive) Assignee: Unassigned
Resolution: Won't Fix Votes: 2


originally reported via forum at https://discuss.gradle.org/t/deprecation-warning-when-using-offline/9530

I do have a multi project build. It works pretty OK, but when I start the build using the option "--offline", then I'll get error messages like this:

Attempting to change configuration ':xxx:compile' after it has been included in dependency resolution. This behaviour has been deprecated and is scheduled to be removed in Gradle 3.0
It this a known bug? I think I see it since 2.4-rc-1 (or 2). Currently, I'm on 2.4 and I'm getting the error. Shall I try to produce a small example project on github?

Thanks a lot, Uli

sample project to reproduce: https://github.com/uli-heller/uli-gradle/tree/master/e01-offline

Comment by Luke Daley [ 10/May/15 ]

Related: https://discuss.gradle.org/t/attempting-to-change-configuration-deprecation-warning/9544

Comment by Luke Daley [ 10/May/15 ]

Related: https://discuss.gradle.org/t/applying-idea-plugin-to-multi-project-java-build-throws-spurious-deprecation-warnings-with-gradle-2-4/9541/1

Comment by Luke Daley [ 10/May/15 ]

Related: https://discuss.gradle.org/t/warning-in-dependency-resolution-when-using-2-4/9481

Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

Generated at Wed Jun 30 12:45:05 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.