Red Hat DocumentationFuse ESBToggle FramesPrintFeedback

What's new in Fuse ESB 4.4.1-fuse-03-06, March 08, 2012

Dependency versions

This release has the following dependencies:

Apache Karaf Apache Karaf v2.2.x Release Notes2.2.2-fuse-04-06
Fuse Services Framework 2.4.3-fuse-01-02
Fuse Mediation Router 2.8.0-fuse-03-06
Fuse Message Broker 5.5.1-fuse-03-06
ESB Components ESB Components v2011.02.1 Release Notes2011.02.1-fuse-04-06
ESB NMR ESB NMR v1.5.1 Release Notes1.5.1-fuse-03-06

Note

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.

Bug

The following bugs were fixed in this release:

  • ESB-1661 - There is a segmentation violation when starting the karaf wrapper on 64 bit linux machines.

  • ESB-1662 - On Windows 2008 sp2+ 64 bit with a 32 bit JVM you get the error: "Could not initialize class org.fusesource.jansi.internal.Kernel32".

Comments powered by Disqus