[GRADLE-3175] Disabling stderr generated by MavenDeployer Created: 28/Sep/14  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: 1


 Description   

Is there a way to disable stderr being written by the uploadArchives tasks? I'm unclear whether it's Gradle that's writing the "Uploading" traces into the stderr. See below:

Gradle version: 1.XX

apply plugin: 'maven'
apply plugin: 'java'
repositories {
mavenCentral()
maven

{ url "http://artifactory.xxx.com/artifactory/xxx-ci" }

}
dependencies {
testCompile "junit:junit:4.11"
compile "org.yaml:snakeyaml:1.13"
}
uploadArchives {
repositories {
mavenDeployer {
repository(url: "http://artifactory.xxx.com/artifactory/xxx-ci/")
}
}
}

If you run the below command:

$ ./gradlew --quiet uploadArchives
Uploading: com/xxx/releng/ci/pipeline/pipeline-yaml-parser/0.0.3/pipeline-yaml-parser-0.0.3.jar to repository remote at http://artifactory.xxx.com/artifactory/xxx-ci/
Transferring 13K from remote
Uploaded 13K
$ ./gradlew --quiet uploadArchives 2>/tmp/stderr
$ cat /tmp/stderr
Uploading: com/xxx/releng/ci/pipeline/pipeline-yaml-parser/0.0.3/pipeline-yaml-parser-0.0.3.jar to repository remote at http://artifactory.xxx.com/artifactory/xxx-ci/
Transferring 13K from remote
Uploaded 13K

Uploading: com/xxx/releng/ci/pipeline/pipeline-yaml-parser/0.0.3/pipeline-yaml-parser-0.0.3.jar to repository remote at [1]http://artifactory.xxx.com/artifactor...
Transferring 13K from remote
Uploaded 13K

Shouldn't be a warning/error I guess so

Thanks
----------------------------------------------------------------------------------------
[1] http://artifactory.xxx.com/artifactory/xxx-ci/



 Comments   
Comment by Lucian Varlan [ 20/May/15 ]

This is actually a big issue. Our builds are failing because they read stderr. And it always happens during upload task.

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