Still no luck. Here is my list of openflow features (after the change you suggested ):
odl-openflowplugin-app-forwardingrules-manager │ 0.6.2 │ │ Started │ odl-openflowplugin-app-forwardingrules-manager │ OpenDaylight :: Openflow Plugin :: Application - odl-openflowplugin-libraries │ 0.6.2 │ │ Started │ odl-openflowplugin-libraries │ OpenDaylight :: Openflow Plugin :: Libraries odl-openflowplugin-app-config-pusher │ 0.6.2 │ │ Started │ odl-openflowplugin-app-config-pusher │ OpenDaylight :: Openflow Plugin :: Application - odl-openflowplugin-nsf-model │ 0.6.2 │ │ Started │ odl-openflowplugin-nsf-model │ OpenDaylight :: OpenflowPlugin :: NSF :: Model odl-openflowjava-protocol │ 0.6.2 │ │ Started │ odl-openflowjava-0.6.2 │ ODL :: openflowjava :: odl-openflowjava-protocol odl-openflowplugin-app-topology │ 0.6.2 │ │ Started │ odl-openflowplugin-app-topology │ OpenDaylight :: Openflow Plugin :: Application - odl-openflowplugin-flow-services │ 0.6.2 │ │ Started │ odl-openflowplugin-flow-services │ OpenDaylight :: Openflow Plugin :: Flow Services odl-openflowplugin-southbound │ 0.6.2 │ │ Started │ openflowplugin-0.6.2 │ OpenDaylight :: Openflow Plugin :: Li southbound odl-openflowplugin-app-reconciliation-framework │ 0.6.2 │ │ Started │ odl-openflowplugin-app-reconciliation-framework │ OpenDaylight :: Openflow Plugin :: Application - I still don't understand one thing -- why is the port being used BEFORE I start my application? It appears that the openflow features are already running when the container is started. Indeed when I do a feature list BEFORE starting my own feature I get the SAME list as above. (i.e. the features are in the started state already). This is different from my previous version (i.e. Nitrogen ) where these features where listed in an Uninstalled state. Thanks, Ranga On Sat, Aug 4, 2018 at 7:42 PM, Luis Gomez <ece...@gmail.com> wrote: > This dependency breaks your feature: > > <dependency> > <groupId>org.opendaylight.openflowplugin</groupId> > <artifactId>features-openflowplugin</artifactId> > <type>xml</type> > <classifier>features</classifier> > </dependency> > > > With the above you are installing all features available in openflowplugin > and some of them are not compatible with each other, so instead of bringing > the full repo just bring one by one the features (odl-openflowplugin-*) > that you need, for example: > > <dependency> > <groupId>org.opendaylight.openflowplugin</groupId> > <artifactId>odl-openflowplugin-southbound</artifactId> > <type>xml</type> > <classifier>features</classifier> > </dependency> > > BR/Luis > > > On Aug 4, 2018, at 3:41 PM, M. Ranganathan <mra...@gmail.com> wrote: > > > > <pom.xml> > > -- M. Ranganathan
_______________________________________________ openflowplugin-dev mailing list openflowplugin-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
