This release has the following dependencies:
| Apache Karaf | Apache Karaf v2.2.x Release Notes2.2.2-fuse-02-13 |
| Fuse Services Framework | 2.4.3-fuse-00-13 |
| Fuse Mediation Router | 2.8.0-fuse-01-13 |
| Fuse Message Broker | 5.5.1-fuse-01-13 |
| ESB Components | ESB Components v2011.02.1 Release Notes2011.02.1-fuse-02-13 |
| ESB NMR | ESB NMR v1.5.1 Release Notes1.5.1-fuse-01-13 |
This is a note if you are building Fuse ESB from source using the offline repository. You can ignore otherwise.
Several Eclipse artifacts use version ranges (ex.
org/eclipse/core/resources/3.3.0-v20070604/resources-3.3.0-v20070604.pom
depends on org.eclipse.core:expressions:[3.1.0,4.0.0)). In offline mode,
Maven cannot download metadata from a remote repository to determine what versions are
available because it requires local metadata. In the case of the Eclipse libraries, this
metadata is saved under the "nexus" host name. To get Maven to pick up this metadata, you
need the following settings.xml profile with a "nexus" repositories
added:
<settings>
<profiles>
<profile>
<id>offlinerepo</id>
<repositories>
<repository>
<id>nexus</id>
<url>file:///path/to/offline/repo</url>
</repository>
</repositories>
<pluginRepositories>
<pluginRepository>
<id>nexus</id>
<url>file:///x1/offlinerepos/repo</url>
</pluginRepository>
</pluginRepositories>
</profile>
</profiles>
<activeProfiles>
<activeProfile>offlinerepo</activeProfile>
</activeProfiles>
</settings>You only need this when using an offline repository locally to build from source. For example, if you build like this:
mvn clean install -Dmaven.repo.local=/path/to/offline/repo --offline
If you import the offline repository into a repository manager like Nexus or Artifactory on your local network then you will not encounter this issue.
The following bugs were fixed in this release:
The following improvements were made in this release:
SMX4-988 - should add delay to camel timer of camel-nmr and camel-nmr-blueprint example so that the nmr endpoint get chance to create








