[GRADLE-2611] 'uploadArchives' succeeds on empty URL Created: 27/Dec/12  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

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


 Description   

When I specify an empty string for the repository URL of the `uploadArchives` task, the task will report success when executed. What did actually happen? Did it publish the artifacts anywhere?

The configuration of the task is the following:

uploadArchives {
repositories {
mavenDeployer {
repository(url: '')

{ authentication(userName: '', password: ''); }

snapshotRepository(url: '')

{ authentication(userName: '', password: ''); }

}
}
}

and this is the output of uploadArchives:

Uploading: [relative path of artifact] to repository remote at
Transferring 26K from remote
Uploaded 26K

 Comments   
Comment by Gradle Forums [ 27/Dec/12 ]

Hello Attila,
your snippet currently defaults to an absolute path where the file is stored on your local machine. While reproducing this on my mac the uploadArchives tries to put the artifact into a directory structure with the pattern: "/group/name/version". This is not a very sensible default for an empty url string. I raise an issue for that.

cheers,
René

Comment by Attila Kelemen [ 27/Dec/12 ]

As you said, I have found the artifacts in the root directory.

I, personally, expected uploadArchives to fail but if you think it should not, then please display the folder to where the task will copy the artifacts in the output (in the currenty case '/' for nix systems and 'C:\' for Windows).

On bright side, I didn't know that Gradle can copy the artifacts to a specified directory (instead of uploading it to a remote repository). Actually, this is something useful to me.

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