2 Ways Of Ensuring You Keep Rocking All JBoss Integration & BPM Demos

As you might have noticed, all of the JBoss BRMS & JBoss BPM Suite demo projects you have come to enjoy were to be migrated into a new organizational group known as JBoss Demo Central.

If you follow me on twitter you would have seen quite a bit of activity over the last week as no less than 35 projects were migrated to JBoss Demo Central.

Not easy, all day to move #github repos, #JBoss #BRMS 6.x & #xPaaS projects, next BRMS 5.x https://t.co/zvGvGqiNxn pic.twitter.com/yNcW1cMlCQ
— Eric D. Schabell (@ericschabell) December 2, 2014

A nice thing to realize is that all of the original links from the original locations are forwarded to the new JBoss Demo Central locations.

This means your various cloned projects are still functioning just fine, but if you want to be able to just pull in future changes you will have one of two options to get in sync with your projects new home.

1. Search and destroy

This option is the most drastic and is fine if you have a good Internet connection. Just go to JBoss Demo Central, find the project you need to update, throw away your local copy and clone a new copy.

For example:

1. want to update the JBoss BPM Suite Travel Agency Demo.
2. locate project in JBoss Demo Central by searching for Travel (or just follow the link in step 1).
3. remove this locally on our machine:
• $ rm -rf bpms-travel-agency-demo
4. clone to our local machine:
• $ git clone 

Now you are ready to continue to pull updates as they are made available and push any improvements you might have to the project.

2. Modify in place

This option is for you should you not really want to re-clone an entire repository. We will just modify the link in the projects git configuration file to point to the new repo location.

For example:

1. want to update the JBoss BPM Suite Travel Agency Demo.
2. locate project in JBoss Demo Central by searching for Travel (or just follow the link in step 1).
3. copy the HTTPS clone URL:
• git@github.com:jbossdemocentral/bpms-travel-agency-demo.git
4. edit the existing local git configuration entry that contains reference to eschabell as follows:
• edit bpms-travel-agency-demo/.git/config

# The origin entry in your git configuration file for the project
# before moving it to JBoss Demo Central.
#
[remote "origin"]
	url = git@github.com:eschabell/bpms-travel-agency-demo.git
	fetch = +refs/heads/*:refs/remotes/origin/*

We update this link to point to JBoss Demo Central and do a fresh git pull.

# The new origin entry that points to the correct new demo location.
#
#   $ git pull  (to refresh)
#
[remote "origin"]
	url = git@github.com:jbossdemocentral/bpms-travel-agency-demo.git
	fetch = +refs/heads/*:refs/remotes/origin/*

You can also adjust the url for origin by using a git command:

• $ git remote set-url origin git@github.com:jbossdemocentral/bpms-travel-agency-demo.git 

That's it, now you are ready to continue using any JBoss Integration & BPM demo project you find need updating to their new home in JBoss Demo Central.