Hi David,
did you do:
cave:repository-proxy foo http://path/to/your/artifacts
?
Or did you provide directly the index.xml ?
Regards
JB
On 11/19/2015 03:20 PM, David Leangen wrote:
Hi!
Based on the recent discussion in bndtools…
On 19/11/15 14:33, Timothy Ward wrote:
The indexes generated by a LocalIndexedRepo (the type of release repository
that you’re talking about) will always use relative URIs to locate the bundles.
This is what the Local in LocalIndexedRepo means. There is no facility to
provide non relative URIs in this repository type.
On Thursday, November 19, 2015 at 2:38:47 PM UTC+1, Ferry Huberts wrote:
You could also update the spec to say that relative URL must also be supported.
IMHO a much better option and it will involve only minor effort on Karaf et al.
On Nov 19, 2015, at 10:53 PM, Jean-Baptiste Onofré wrote:
Yes, it makes sense, we would just need to know a base URL to apply/prefix the
URL.
As a workaround, it's already possible to load the index.xml generated by bndtools in
Karaf Cave, and so, Cave will "façade" the index.xml, updating the URL.
I have tried this with cave:repository-populate and cave:repository-proxy.
Absolutely nothing happens. :-(
As I wrote in a previous post:
In [Cave], I can only add a single jar at a time, not an entire repo index.
Even in the code, I noticed that cave only accepts files of type:
application/java-archive
application/octet-stream
application/vnd.osgi.bundle
Anything other than those files types gets ignored.
As a side note: to make my bundles work, I needed to add to the code this mime
type:
application/x-java-archive
I could find out that is a registered mime type, though I do not know the
history as to where there is both application/java-archive and
application/x-java-archive.
Am I misunderstanding how this is supposed to work?
Cheers,
=David
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
