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

Brian Topping commented on KARAF-1400:
--------------------------------------

Thanks Freeman, I'll give that a shot.  It probably should not fail silently, 
but this is a great work around.  Thank you for passing that along.
                
> Karaf repository silently fails to examine repositories requiring 
> authorization
> -------------------------------------------------------------------------------
>
>                 Key: KARAF-1400
>                 URL: https://issues.apache.org/jira/browse/KARAF-1400
>             Project: Karaf
>          Issue Type: Improvement
>          Components: karaf-repository
>    Affects Versions: 2.2.7
>            Reporter: Brian Topping
>
> When a remote Maven repository is protected by a password and that repository 
> is added to org.ops4j.pax.url.mvn.repositories, an artifact that is only 
> available from the repository will not be found.  Further, no error or 
> warning is emitted at the console or in the Karaf log indicating that a 
> protected repository was in the repository list and was ignored.
> Ideally, Aether would be used to read the remote repository, leveraging 
> ~/.m2/settings.xml for a password, but it should still give indication of 
> failure in any event.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to