Skip to main content

JBoss Fuse - Tips, Offline Repository in Fuse

JBoss Fuse relies very heavy on maven, as it uses maven to control the dependencies for projects and jars it is using. Most of the repository settings can be found in this configuration file:

Under $FUSE_INSTALL_FOLDER/etc/ org.ops4j.pax.url.mvn.cfg

Inside this file, take a look at 2 configurations,

  • org.ops4j.pax.url.mvn.defaultRepositories
  • org.ops4j.pax.url.mvn.repositories
Or if you are using fabric, the same settings are available under in your  default profile.

The org.ops4j.pax.url.mvn.defaultRepositories, sets the location of the local repository for your Fuse to look up.  The default location are under the system folder.

And of course org.ops4j.pax.url.mvn.repositories are the external repository settings for your fuse to scan. Here are the list of default repos.   

But there are often time where you don't have limited access to the world wide web, maybe it's just bad internet connection or security issues.

Inside Red Hat Fuse documentation, they showed you how to create a custom repository, where they showed you how to properly use the "" plugin to generate the necessary repo. I highly recommend you read through the documentations if you have time.

However a lazy person like me, I always tried to find some easy way out of configuring and setups. Just want to warn you, this may not be the proper way. But it works for me :)

First thing first, you got to have maven installed in your local machine, and that's about it! And I am assuming you have setup to connect to the Fuse and other needed repo too.

Find the setting.xml file, with

  • Mac or Unix, 
    • ~/.m2
  • Windows 
    • D:\Documents and Settings\{your-username}\.m2
  • Linux
    • /home/{your-username}/.m2/

And under the settings.xml, find the tag name:


if you have a brand new maven installed, then you may have to create the xml file and add the tag by yourself.

OK, now,create a NEW temporary working folder and place the path in  "localRepository" tag. I prefer to put it in the same folder as the local system folder as later on I need to compare it using my script.


Next, go back to your IDE, run a simple mvn clean install, so what this does, it actually starts download all the needed dependencies into the folder, by all, I mean it. So it is going to take a very long time to download.

Once you got everything downloaded, I want to quickly show you something, check your local repo in the system folder with your new temporary working folder. you will find there are lots of duplications of files. That is because we tried to download all the dependency to local, and we don't know which one has already existed, that's why it downloads them all.

Now we have the entire dependency repo, you can either point to this local repo directly in your org.ops4j.pax.url.mvn.defaultRepositories setting, or you can clean it up a bit using my script.

#create directories in the new repo that are not exist in the system folder
diff -r tmprepo/ system/ | grep "Only in tmprepo" | xargs -n2 | grep tmprepo | tr ":" "/"| tr -d " \t\r" |xargs -I{} bash -c 'if [ -d {} ]; then mkdir -p newrepo/{} ; fi '

#create directories in the new repo that are not exist in the system folder
diff -r tmprepo/ system/ | grep "Only in tmprepo" | xargs -n2 | grep tmprepo | tr ":" "/"| tr -d " \t\r" |xargs -I{} bash -c 'if [ ! -d {} ]; then mkdir -p newrepo/$(dirname {}) ; fi '

#copy all files over to the new repo that are not exist in the system folder
diff -r tmprepo/ system/ | grep "Only in tmprepo" | xargs -n2 | grep tmprepo | tr ":" "/"| tr -d " \t\r" | xargs -I{} cp -rf {} newrepo/{}

This script checks for the repo that are not in system, can copy them out to another folder called "newrepo". So I have actually clean up the files and jars that are existed in the system folder.
(Tested on Mac and Linux, please contribute the Window version, sorry, I am not a windows person :p )

So far so good, now we are ready to point the org.ops4j.pax.url.mvn.defaultRepositories to our new repo

And remove all proxy maven look up by adding "#" in-front all of them.

That's all. For me, this is much easier then to config a bunch so set ups. But again, this is just a tip, the recommended way is to use the one in the documentations!


Popular posts from this blog

Red Hat JBoss Fuse/A-MQ - Fuse and A-MQ Version 6.3 GA is released!

Fuse and A-MQ 6.3 GA has just went out. Maybe, you would think this is just only a minor version release why should I care? Hold your thoughts on that! Because they have done a lot of improvements and also added many new features into this release.

Besides various bug fixes and making sure Fuse Fabric is much more stable. There are two major change in this version update:

New Tooling in JBoss Developer Studio (JBDS) 9.1 GA. Newer Apache Camel version – Camel v2.17. I was really impressed by the work put in to make developing Camel application much simpler. First is the installation of tooling itself. Now it has a all-in-one installer so you don't need to worry about which plugins you need to check. See the videos below to see the new "Getting Started" of Fuse 6.3.

And If you notice from the above video, the presentation of camel route in JBDS has also updated. It fixed some of the miss representation of logic and making it easier to read.

Old Camel Route
New Camel Route
On …

Fuse Integration Service - Setup JBDS and create first quickstart application

Before we go and start creating our first application, I want to show you how to setup your JBoss Developer Studio, create a small application from the quickstart example and then running it on Fuse Integration Service.

I am using JBoss Developer Studio version 9, you can find it here.
After download the

double-click it, and start installing with default values.

After successful installation, we will need install the plugins for Fuse, on JBoss Central view, select software update, select enable early access.

And select JBoss Fuse Development for the plugin,

Click on install, and we are all set to go!

First thing first, we want to create a Fuse project to deploy on the base of Fuse Integration Service, which is OpenShift. If you have not installed it, please go back to my previous post for instructions. So on your JBDS, right click and start creating the project. Select new, maven project, if you have installed the plugin correctly, you should …

Red Hat JBoss Fuse - Getting Started with Fuse Integration Service 2.0 Tech preview

I just realized that I did not do a getting started for Fuse Integration Service 2.0 Tech preview before I did the pipeline demo, thanks for those of you who reminded me! :)

To get started with FIS 2.0, for people who has just getting to know the technology, here is how I interpret it. Basically, it's divide into two aspect,

1. Integration development, FIS uses Apache Camel as the core technology that creates, orchestrate, compose microservices into a super lightweight thin integration layer, and become the API provider and service orchestrator through exposing RESTful or messaging service endpoints. And you can choose to either package and run it with Spring-Boot or Karaf.

2. Application Deployment and Management, FIS takes advantages of OpenShift platform, and allows you to separately deploy the micro-integration service among distributed environment, at the same time takes care of the failover, high availability, load balancing and service lookup problem for you.

So, now we know …