Hi all,
For a general perspective, I think it's a good idea. I added the OSS
Sonatype repo yesterday to be able to install the jclouds features (as
the Guava OSGi bundle is not on central, it's only available on OSS
Sonatype).
Now, regarding the implementation, in the feature, we already have a
<repository/> tag to define features descriptor. Why not reusing it to
store "really" repository ?
I think that, more than setting the repo ID in <bundle/>, I will
implicitly add the repo in the repository set. We can add an attribute
priority on <repository/> to define in the repository is resolved
before the default one or after.
WDYT ?
Regards
JB
On 07/28/2011 07:21 AM, Ioannis Canellos wrote:
Except for the point that I have no idea how we could "marry" this idea
with
PAX-URL +1 :-) This could be definitely useful. This might be also
interesting for Karaf Cave in future versions (I could imagine).
A possible solution could be to have a tag like:
<mavneRepository id="my-repo" url="http://www.awsome-repo.com/maven2";>
The user would be able to define a repository and then add a reference to
the repository on the bundle like that:
<feature name="awsome-feature">
<bundle repo="my-repo">mvn:com.awsome/bundle/1.0</bundle>
</feature>
When the user installs awsome feature, the maven repo could be added to
pax-url config.
wdyt?
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
