Hi Guillaume,
Thanks for the reply! I'll look forward to 4.0.8. However, I have found some additional behavior regarding `feature:repo-add -i` documented below, showing that the command behaves differently when executed from the Karaf client (bin/client) vs the interactive console. Guillaume Nodet-2 wrote > The commands may not be available yet when the script is started. > I think this should be fixed in 4.0.8. I attempted a work around: 1) Start Karaf 2) Use the client to connect and install the features For example: bin/start && \ bin/client -r 10 -d 5 "feature:repo-add -i mvn:edu.amherst.acdc/acrepo-karaf/LATEST/xml/features" && \ bin/stop However, there does not seem to be parity between `feature:repo-add -i` when executed from the Karaf client, vs execution from the interactive Karaf console. When `feature:repo-add -i` is executed by the client in a non-interactive fashion (per my example above), features will be in the 'STARTED' state, but their bundles will be in the 'INSTALLED' state (https://goo.gl/7mnYxG). When `feature:repo-add -i` is executed from the interactive Karaf console, features will be in the 'STARTED' state, AND the bundles will be in the 'ACTIVE' state (https://goo.gl/S87ThA). I wanted to bring this to your attention in case it can be addressed for 4.0.8. Best, Elliot -- View this message in context: http://karaf.922171.n3.nabble.com/feature-repo-add-i-broken-in-4-0-4-tp4046143p4048279.html Sent from the Karaf - User mailing list archive at Nabble.com.
