[GRADLE-3312] Error Code 301 when publishing with maven-publish and Gradle 2.4 Created: 25/Jun/15  Updated: 02/Jul/15  Resolved: 02/Jul/15

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: 2.5-rc-2

Type: Bug
Reporter: Sterling Greene Assignee: Adrian Kelly (Inactive)
Resolution: Fixed Votes: 0

Known Issue Of:



After upgrading from Gradle 2.3 to Gradle 2.4, it seems that something is broken with the "maven-publish" plugin.
We have a redirect in our url (i.e. https://my.company.com/snapshots should be redirect to the real url) that defines the path to our nexus. This redirect is properly and successfully handled with Gradle 2.3 (handled by sun.net.www.protocol.http.HttpURLConnection). However, the redirect fails with Gradle 2.4 (handled by org.apache.http.impl.conn.DefaultClientConnection). (error code 301 : Moved Permanently)
As a first fix, we provide now the real url but you may be interested in the issue.
Please also note that the issue is still the same with Gradle 2.5-RC1

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