Right now Metro provides official off-line installation scripts for GlassFish v2 and Tomcat as part of the standalone Metro bundle. If you want to use latest Metro with GlassFish v3, you should update Metro installation via GlassFish v3 Update Center.
While updating Metro installation on GlassFish v3 via Update Center is really strongly encouraged and preferred way for most Metro users, there are cases when it would be really good to be able to update Metro on GlassFish v3 using an off-line installer. Off-line installer is especially helpful when trying to install Metro built from sources or trying to test latest nightly build of Metro that may not be available through the GlassFish v3 Update Center yet.
Unfortunately, there was no such installer available in the Metro bundle... until now. I have just added a first experimental version of such installer to the Metro workspace and it should be available for use with the Metro v2.0 nightly build tomorrow. Here's how to invoke the installer from the Bash command line, once you download and unpack the Metro bundle:
cd <metro-bundle-dir> export AS_HOME=<gfv3-install-dir>/glassfish ant -f metro-on-glassfish-v3.xml install
Simple, isn't it? For more information on the Ant targets available in the script file, just type
ant -f metro-on-glassfish-v3.xml help
I hope you will enjoy this small improvement, yet remember – this is an experimental installer, use it at your own risk. And don't forget to send me any issues you may encounter with the installer!
For a longer time we have been thinking about Metro and WSIT mavenization. The day has come close. I have put together a first draft of the proposal. Metro is an open-source project and so is WSIT, as one of the main parts of Metro project. So community feedback is really encouraged and more than welcome. Please have a look at the proposal draft and send me your comments.
Thank you in advance.
I am moving my old blog. It has been a while since I first started to play with this idea, but now I actually decided to take action, register my own domain and install my own blog engine. Last thing that convinced me to really do it was a chat with Martin, who has started his own internet domain and blog recently and told me how easy it was.
There are multiple reasons for me to abandon the old blog:
- The blog engine on the old blogging site simply failed to provide an easy to use administration UI
- The choice of plugins and themes was poor and it was near impossible to install any new plug-ins or setup a nice theme
- Overall, I didn't feel I have the full control of the blog
- The connection to the old blog's administration page tends to be reeeaaaalyyy slow, in fact I am just now trying to log in to write my last blog entry there and it's been more than 2 minutes since I pressed the "Log in" button but the page hasn't loaded yet
- And last but not least, I always wanted to have my blog hosted on my personal domain anyway
What do I expect from this change? Well, definitely improvements in points 1-5 and more importantly, I hope that — with the new blog running on a very user-friendly blog engine — I start blogging more often. So, let's see...