从opendaylight-startup-archetype构建的OpenDaylight Oxygen Deploy应用程序 [英] OpenDaylight Oxygen Deploy app built from opendaylight-startup-archetype

查看:460
本文介绍了从opendaylight-startup-archetype构建的OpenDaylight Oxygen Deploy应用程序的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

OpenDaylight Oxygen

Maven 3.3.9

Ubuntu 16.04

karaf 4

OpenDaylight Oxygen
Maven 3.3.9
Ubuntu 16.04
karaf 4

〜 /.m2/settings.xml - cp -n~ / .m2 / settings.xml {,。orig}; wget -q -O - https://raw.githubusercontent.com/opendaylight/odlparent/master/settings.xml> 〜/ .m2 / settings.xml

~/.m2/settings.xml - cp -n ~/.m2/settings.xml{,.orig} ; wget -q -O - https://raw.githubusercontent.com/opendaylight/odlparent/master/settings.xml > ~/.m2/settings.xml

用于创建骨架的流程

mvn archetype:generate -DgroupId = org.opendaylight.controller -DartifactId = testing -Dcopyright =None-DclassPrefix =\ $ {artifactId.substring(0,1 ).toUpperCase()} \ $ {artifactId.substring(1)}-DarchetypeGroupId = org.opendaylight.archetypes -DarchetypeArtifactId = opendaylight-startup-archetype -DarchetypeVersion = 1.1.0-SNAPSHOT -DinteractiveMode = false

mvn clean install -Dcheckstyle.skip

我正在尝试构建一个示例应用程序并将其部署在一个单独的ODL实例(karaf 4)上。我无法在任何地方找到合适的答案。

I'm trying to build a sample app and deploy it on a separate instance of ODL (karaf 4). I cannot find a working answer to this anywhere.

我已经尝试将PROJECT / karaf / target / assembly / system / org / opendaylight / controller的内容复制到另一个ODL实例上的等效文件夹。然后使用功能:add-repo添加功能。它能够检测到插件,但功能:安装odl-testing无法安装。

I've tried copying the contents of PROJECT/karaf/target/assembly/system/org/opendaylight/controller to the equivalent folder on the other ODL instance. Then used feature:add-repo to add the feature. It was able to detect the plugin, but feature:install odl-testing failed to install.

非常感谢任何帮助。

推荐答案

你不是当你说功能:安装odl-testing无法安装时,显示你遇到了什么确切的失败,但是大多数人实际上并没有使用你正在努力工作的过程..从技术上讲,你可以建立新的捆绑包和Karaf单独功能,然后手动添加它以部署在一个单独的ODL实例上...但我知道的每个项目都发现更容易让构建生成一个即用型Karaf发行版。

You are not showing what exact failure you hit when you say "feature:install odl-testing failed to install", but FYI most people don't actually use the process you are trying to get working.. it's technically possible to build your new bundles and Karaf feature separately and then manually add it to deploy on a separate instance of ODL... but every project I know of finds it easier to just let the build produce a ready-to-use Karaf distribution.

你可能已经看到了karaf / target / assembly中的发行版ODL原型(此处记录BTW ;注意使用archetypeGroupId更改为org.opendaylight.archetypes in刚刚发布的最新Fluorine版本产生?

You have probably seen the distro in karaf/target/assembly which the the ODL archetype (documented here BTW; note the use of archetypeGroupId changed to org.opendaylight.archetypes in the just released latest Fluorine version) produces?

所以你可以做的只是添加你的基础功能,你可能希望将你的功能添加到自定义功能的依赖项中。有了这个,您就可以获得可立即运行的自定义发行版,包括您的新代码以及您想要包含的其他任何ODL功能。

So what you can do instead is to just add your "base" feature which you are presumably wanting to add your feature into as a dependency to your custom feature. With this, you get your ready-to-run custom distribution including your new code and whatever other ODL features you want to include.

这篇关于从opendaylight-startup-archetype构建的OpenDaylight Oxygen Deploy应用程序的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆