I think that's because the repositories are loaded lazily when features are actually needed. To overcome that, the valid/invalid flag has been added to actually see which repositories have been read. We may want to reconsider this lazy loading though ...
On Mon, Dec 6, 2010 at 13:48, Charles Moulliard <[email protected]> wrote: > Is it a normal behavor that invalid features repo are added in karaf > > ka...@root> features:addurl mvn:org.apache.camel.karaf/apache-camel/2.5.0 > Could not add Feature Repository: > java.io.IOException: URL [mvn:org.apache.camel.karaf/apache-camel/2.5.0] > could not be resolved. : mvn:org.apache.camel.karaf/apache-camel/2.5.0 > > > ka...@root> features:listUrl > mvn:org.apache.camel.karaf/apache-camel/2.5.0 invalid > mvn:org.apache.karaf/apache-karaf/2.1.99-SNAPSHOT/xml/features valid > > Regards, > > Charles > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
