Some of the views expressed so far:

i) Allow defining an alternate location for a feature repository.
ii) Allow overriding a feature repository or bundle url using a mapping.
iii) Using version feature version ranges to resolve the right version to
use.

Some thoughts about each idea.

i) I'd love to be able to do that, even though in most cases modifying the
feature repo in the system directory does work for me.
We could take this one step further an be able to modify the feature repo
itself, using the editor we have in trunk (mostly as a dev tool).

ii) I like this idea too. This would solve the recent problem we had with
spring versions. We could just let the user define a mapping like
mvn:org.springframework/*/[3,4] = mvn:org.springframework/*/3.1.2.RELEASE
and it would be awesome.

iii) This would definetely solve a lot of problems, without direct user
interaction. I think that we should maybe start with this point but maybe
also grant the user the power to do things like i) and ii).

I hope I didn't miss anything.

-- 
*Ioannis Canellos*
*

**
Blog: http://iocanel.blogspot.com
**
Twitter: iocanel
*

Reply via email to