Re: [netvirt-dev] The correct approach to integrate NetVirt ownsub-module into ODL?
|
Sam Hague <shague@...>
On Tue, Aug 7, 2018 at 10:23 PM Irving <418624178@...> wrote:
Here is where knowing how maven works will help. When you build with maven it stores artifacts built locally in a ~/.m2 directory. Artifacts not built will be pulled from a remote m2 repository. When you do cd openflowplugin; mvn clean install - thsi will start the openflowplugin build, it will build some stuff and it will pull some stuff from the remote m2, but all of it will eventually end up in your ~/.m2/repository directory. Follow that path and you will see org/opendaylight/<project>/.... Everything will end up there. So you just keep building the projects one by one in the right order or dependencies: controller, ovsdb, openflowplugin, genius, netvirt. I think that order is correct. netvirt has to be last since it depends on all the others. Each project build adds stuff to the local m2 repo. Then each next build uses what is there, so eventually you get to the netvirt build and it is using all the stuff already built. Then you use just the netvirt karaf.zip for your distribution since that will have everything you just built from all the projects. When you do the last netvirt build, use mvn -nsu clean install. The -nsu is "no snapshot update". That makes sure that netvirt build will only use what was built in your local m2 - and not pull down new artifacts from remote.
|
|
|