ace-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Offermans (JIRA)" <>
Subject [jira] [Commented] (ACE-499) AceObrRepository doesn't work for repositories that require authentication
Date Wed, 03 Dec 2014 23:14:12 GMT


Marcel Offermans commented on ACE-499:

A possible "enhancement" of my proposed solution would be to proceed as follows if no BundleContext
could be obtained:
# Try to find a system property called "connectionfactory" and instantiate the class mentioned
there. Inject that in the component.
# If no system property is found, fallback to a "default" factory (that probably does not
support authentication).

TBH it's about time Bnd is refactored to use OSGi itself. :)

> AceObrRepository doesn't work for repositories that require authentication
> --------------------------------------------------------------------------
>                 Key: ACE-499
>                 URL:
>             Project: ACE
>          Issue Type: Bug
>    Affects Versions: 2.0.1
>            Reporter: Bram Pouwelse
> The AceObrRepository (at least in the way it's used in the gogo support functions) doesn't
support using a repository that requires authentication. 
> I've tried adding a Registry to the plugin to provide a "aQute.bnd.deployer.http.HttpBasicAuthURLConnector",
this resolves the issue for read actions but the upload method still doesn't work. The UrlConnector
interface currently only supports read actions so making this work would require a change
in bnd.
> Discussed this issue with [~marrs], he proposed to obtain a BundleContext using FrameworkUtil
to retrieve the Ace ConnectionFactory service. A possible drawback of this solution would
be that this doesn't work in case the AceObrRepository is used from bnd(tools)

This message was sent by Atlassian JIRA

View raw message