[GRADLE-2087] Project status always reverting to integration Created: 08/Feb/12  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Bug
Reporter: Gradle Forums Assignee: Unassigned
Resolution: Won't Fix Votes: 5


 Description   

I'm seeing the status in my generated ivy.xml file as always "integration", even though I have status='release' in either the build.gradle or the gradle.properties. I've tracked it to the ModuleDescriptor for the :archives configuration, which is getting set via BasePlugin.configureConfigurations, which has these two lines (line 169, in m7):

ConfigurationContainer configurations = project.getConfigurations();
project.setProperty("status", "integration");

That's overriding what I had up until that point. It's very explicitly overriding the status, why? Or better stated, how should I set the status on the project, so that the ivy.xml gets marked as "release"?

 Comments   
Comment by Gradle Forums [ 08/Feb/12 ]

If I move the status further down into the build.gradle, past the "apply plugin", I properly get the status I set. Blah. This is a work around, but this still prevents me from specifying the status on the command line via -P or via gradle.properties. I'm really curious how this isn't messing up other gradle developers, unless I'm missing something. If someone can chime in if they have this problem, I can file a bug.

Comment by Richard Murray [ 06/Mar/12 ]

The documentation still states the default should be 'release' - see

http://www.gradle.org/docs/current/dsl/org.gradle.api.Project.html#org.gradle.api.Project:status

Could the docs be updated until the bug is fixed?

I found uploading to ivy it defaulted to 'integration' if no status was explicity set.

Comment by Justin Ryan [ 01/Apr/13 ]

Still exists:

https://github.com/gradle/gradle/blob/master/subprojects/plugins/src/main/groovy/org/gradle/api/plugins/BasePlugin.java#L130

Comment by Justin Ryan [ 30/Sep/13 ]

Pull request sent.

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:12:27 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.