此内容没有您所选择的语言版本。
1.3. Fabric Migration
Overview 复制链接链接已复制到粘贴板!
复制链接链接已复制到粘贴板!
If you use Fuse Fabric containers to deploy your applications, you should read this section to understand the issues that affect migration to JBoss A-MQ. If you use standalone containers, however, you can ignore this section.
Fabric package has changed 复制链接链接已复制到粘贴板!
复制链接链接已复制到粘贴板!
In JBoss Fuse 6.1 and JBoss A-MQ 6.1, the Fabric package name has changed from
org.fusesource.fabric
to io.fabric8
, which has the following migration impact:
- Configuration PIDs for Fabric have been renamed from
org.fusesource.fabric.name
toio.fabric8.name
. For example, this affects the names of the following configuration files under theetc/
directory:io.fabric8.datastore.cfg io.fabric8.fab.osgi.url.cfg io.fabric8.maven.cfg
io.fabric8.datastore.cfg io.fabric8.fab.osgi.url.cfg io.fabric8.maven.cfg
Copy to Clipboard Copied! Toggle word wrap Toggle overflow - If you use any Fabric APIs directly in your own application code, you must replace references to the
org.fusesource.fabric
package name byio.fabric8
. - If your Maven
pom.xml
files have any direct dependencies on Fabric artifacts, you need to change the Maven GroupId fromorg.fusesource.fabric
toio.fabric8
(as well as updating the dependency version). For example, the followingfabric-zookeeper
dependency:<dependency> <groupId>org.fusesource.fabric</groupId> <artifactId>fabric-zookeeper</artifactId> <version>7.2.0</version> </dependency>
<dependency> <groupId>org.fusesource.fabric</groupId> <artifactId>fabric-zookeeper</artifactId> <version>7.2.0</version> </dependency>
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Should be replaced by the following dependency:<dependency> <groupId>io.fabric8</groupId> <artifactId>fabric-zookeeper</artifactId> <version>1.0.0.redhat-379</version> </dependency>
<dependency> <groupId>io.fabric8</groupId> <artifactId>fabric-zookeeper</artifactId> <version>1.0.0.redhat-379</version> </dependency>
Copy to Clipboard Copied! Toggle word wrap Toggle overflow