[ 
https://issues.apache.org/jira/browse/HTTPCLIENT-1840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15966759#comment-15966759
 ] 

Bindul Bhowmik commented on HTTPCLIENT-1840:
--------------------------------------------

While I agree this is not the easiest to navigate to, but Google helps. The 
information is at 
http://hc.apache.org/httpcomponents-client-4.5.x/httpclient/dependency-info.html
 or if you want to follow down the navigation path: 
bq. hc.apache.org > Components > HttpClient 4.5 > Documentation > Project 
Reports > HttpClient > Project Documentation > Project Information > Dependency 
Information

When you looked at the POM in the source zip file, you are looking at the 
parent POM of the Http Client, which is of packaging pom, so the Maven/Nexus 
repositories will only have the POM files. If you look in that POM, there are 
modules in that POM file and go to the specified directory (in this case 
httpclient), the POM there would have given you the right coordinates.

> I can't find any binaries for released versions in Nexus, only the POM is 
> there
> -------------------------------------------------------------------------------
>
>                 Key: HTTPCLIENT-1840
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1840
>             Project: HttpComponents HttpClient
>          Issue Type: Bug
>          Components: HttpClient (classic)
>    Affects Versions: 4.5.3
>         Environment: N/A
>            Reporter: John Geiglein
>            Priority: Minor
>
> It appears that only the POM has been posted to nexus. This may be because 
> the pom file is configured to produce only the pom file instead of deploying 
> the binaries.
> If the binaries are available, can the download page be updated to document 
> the correct maven dependency. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to