Skip to main content

題外話- 在Mac OS X 上面切換不同 Java 版本

因為最近同時要看好多不同的版本的JBoss BPMS, EAP, Fuse 等等... 發現就會碰到Java SE 7 的BUG,等不及Orcale 修復了,所以不得不切回 Java SE 6, 但是有時,又需要切回 Java SE 7 去測試校能等等..

我那個在Ubuntu 工作有強力系統潔癖的工程師老公,看到我切來切去,就回我一句,你不會弄好幾個VM 然後裝我們家的Ubuntu 分不同的VM去測就好了喔~ 這樣你的OS 才不會一團亂啊...!
但是,這不是VM 的問題啊~ 我喜歡在Mac 的環境下工作咩,不然我花大錢買Mac 是幹嘛?錢多喔!! 所以,他的建議馬上就被我丟到垃圾桶去了。

這裡註記一下怎麼切換,所以我下次才不會忘記。我不知道這是不是最正確的做法拉,可以提供參考。

要知道現在的電腦裡有哪些版本的Java 請打

/usr/libexec/java_home -V




如果你想用某幾個版本的Java SE, 不用我教你吧,請自己去Oracle 的官網上下載。下載安裝之後,如果你以為這樣就結束了,那就不用有這篇了吧~

所以,要看目前的Runtime 請直接打 (這應該大家都會吧 ... )
java -version

他就會顯示目前你的default Java 執行環境。
要把default 的java 連結改過去,
先到 /usr/bin 下面,看一下java 的連結在哪裡,

cd /usr/bin/
ls -ln java







發現還是在舊的,所以請砍掉這兩個連結,

sudo rm -f java
sudo rm -f javac

直接連結到剛剛安裝的Java SE 版本路徑下
sudo ln -s /Library/Java/JavaVirtualMachines/jdk1.x.x_x.jdk/Contents/Home/bin/java java
sudo ln -s /Library/Java/JavaVirtualMachines/jdk1.x.x_x.jdk/Contents/Home/bin/javac javac



這樣再去執行
java -version 就會發現已經改好了。


還沒完~如果你跟我一樣有設定JAVA_HOME的話,記得去把位置改一下

vi ~/.bash_profile 

裡面把JAVA_HOME的位置改掉就好囉!

export JAVA_HOME=/Library/Java/JavaVirtualMachines/jdk1.x.x_xx.jdk/Contents/Home


然後打
source ~/.bash_profile  讓它生效。




切回 1.6 的參數如下:

ln -s /Library/Java/Home/bin/java java
ln -s /Library/Java/Home/bin/javac javac

export JAVA_HOME=/System/Library/Frameworks/JavaVM.framework/Versions/CurrentJDK/Home

以上。跟JBoss 沒啥關係的題外話。

Comments

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

jboss-devstudio-9.0.0.GA-installer-eap.jar
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 …