Chapter 1. Migration Paths for Fuse 7.0
1.1. Migration Path for Fuse 7.0 on Karaf
There is no automated migration path for Fuse 7.0. A new installation must be performed, with configuration and other modified files copied across manually. Applications will need to be recompiled to align with the new versions provided. Use the Maven Bill of Materials (BOM) file to migrate Maven dependencies to the new versions and see also Component Details.
1.2. Migration Path for Fuse 7.0 on EAP
There is no automated migration path to Fuse 7.0 on EAP from previous version of Fuse on EAP. To migrate to Fuse 7.0 you will need to make a new installation of Fuse 7.0 on JBoss EAP. After a successful installation, any existing deployments will need to be re-deployed to the new system. For installation information please see Installation on JBoss EAP and for deployment information see Deployment in the Management Console.
1.3. Deprecated and removed features
For the list of features that have been deprecated or removed in Fuse 7.0, see Release Notes.