[GRADLE-3049] Resolution of maven module with packaging='pom' fails with private Artifactory repository Created: 18/Mar/14  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Bug
Reporter: Daz DeBoer Assignee: Unassigned
Resolution: Won't Fix Votes: 0


 Description   

With authentication enabled, Artifactory will return with a 403 for a missing resource, even when it is located 'within' a public repository on the Artifactory instance. When resolving a maven module with packaging='pom', Gradle will speculatively attempt to include a module jar file, ignoring it if it doesn't exist.

The issue is that Gradle expects a 404 for a jar that doesn't exist: 403 is considered a failure to resolve, so the missing jar causes resolution to fail.

I expect this also to be an issue when Gradle attempts to detect the presence of source and javadoc jar files.

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