Hi Christian.
Regarding parallel download, AFAIK, Maven leverages aether to perform
parallel download. So aether should already supports this. Maybe it's
just a limitation introduced by pax-url-aether. I will take a look, but
it should work anyway.
Regarding the completion, it's a good idea but I'm not sure that a
service is mandatory. Currently pax-url doesn't expose service but
provide API to perform action. So a completer that uses such completion
should do the trick. Like this we don't introduce an OSGi locking in
pax-url.
Regards
JB
On 06/26/2012 11:50 AM, Christian Schneider wrote:
Hi all,
I would like to offer two aether features as an OSGi service.
- Getting the available versions of an OSGi service
I would like to use this in the feature:repo-add to offer completion for
well known feature files like:
feature:repo-add camel <tab>
This should show the available versions of the apache camel feature file.
- Resolving a whole list of artifacts by their mvn: url to speed up
downloads
Currently we resolve one artifact after the other when using pax url. So
for example if we install a feature we download one jar after the other.
I would like
to use the above service method to resolve the whole list of artifacts
for a feature so aether can download them in parallel. So we could call
this service before doing the
normal feature install.
The main question is where to locate such a service. As aether is not
yet available as an OSGi bundle we need to embed it. As pax url aether
already does this it could make sense to locate the service there.
Another argument to add the service to pax url aether is that we need to
share the maven config.
What do you think?
Christian
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
