So you want to supply modified poms for everything in maven central to correct the dependencies that every project has gotten wrong?
My experience with this is that you will quickly have an unmaintainable disaster on your hands. I don't know if karat obr support has kept up with the resolver spec in osgi, but that at least has some hope of working consistently because the bundles won't work without fairly accurate provides-requires information. thanks david jencks On Mar 27, 2013, at 5:40 PM, Andrei Pozolotin <[email protected]> wrote: > Hello. > > I did little eval of obr for my use case, and ran into some issues > https://github.com/barchart/barchart-service/wiki/OBR > > Bottom line: obr is a great idea, but 1000 times less mature then maven. > > Then it occurred to me: why do we keep building all these > feature.xml files > when all maven resolver machinery is already in karaf via pax url / > aether. > > Can we have feature resolver=mvn? And use it at karaf run time with > mvn instead of obr? > > Does the idea make sense? > > Thank you, > > Andrei >
