Adding jars to your OpenShift remote Maven repo

If your OpenShift app has dependencies on other Jars that are not publicly available in the usual maven repos (for example, other Jars from your own projects), you can push them to your remote Maven repo used when your app builds remotely.

Commit the jar in the root of your OpenShift project.

Edit .openshift/action_hooks/pre_build and add the following, updating Jar name etc:

mvn install:install-file --debug -Dfile=../../YourProjectName/runtime/repo/YourJarName.jar
  -DgeneratePom=true -DartifactId=YourArtifactName -Dversion=0.0.1-SNAPSHOT
  -DgroupId=your.group.id -Dpackaging=jar

Commit your changes and push to OpenShift – the jar will get installed to your remote repo, and now you can add a Maven dependency against it in your project’s pom.xml.

VMWare rumor: new CEO stepping in and about to spin off CloudFoundry?

This is unexpected: according to sources, GigaOm say VMWare is taking a new CEO from majority shareholder EMC and is spinning off their PaaS offering, Cloud Foundry.  These changes are expected to be announced during their second quarter earnings call on July 23rd.

Rumors can always turn out to be nothing but a rumor, but GigaOm’s opinion on this move is that they’re attempting to distance Cloud Foundry’s association from VMWare and EMC, which may be holding back adoption of their service compared with other IaaS and PaaS offerings, since some perspective Cloud Foundry customers may be put off by the perceived platform lock-in by Cloud Foundry using VMWare and/or EMC products. Interesting point of view – have to see how this one turns out.

In a Nutshell: Deploying a Java webapp to Red Hat’s OpenShift

Deploying a Java webapp to OpenShift couldn’t be any simpler. In as few words as possible to show you how simple it is – here’s a quickstart:

 

… and that’s it. Your app is pushed to your remote Git repo, built with Maven, and deployed to JBoss 7.

That’s pretty simple, huh?