This is one of the presentations I did at JavaOne this year. I have uploaded the slides to Slideshare.

DZone launched a new microzone today that will focus on the evolving HTML5 standard, along with CSS3, ECMAScript, and other emerging web standards through blogs, tutorials, videos and news.

Check it out here: http://www.dzone.com/mz/html5

JavaOne 2011 got off to a bit of a shaky start this morning with there being a lack of seating in the Grand Ballroom of the Hilton, leading to the escalators eventually being blocked by physically meek, yet surly, security guards and having people being redirected to smaller rooms somewhere else in the rabbit warren that is the Hilton’s conference and event space. However that didn’t happen until after a couple hundred poor souls were left standing at the back of the room to endure a 2 hour-long dry and technical keynote.

Then Mark Reinhold went missing. Not sure what happened there but awkwardly is name was announced and someone else took the stage with no real explanation about why. He then went on to introduce Doug Fisher, VP Intel, who was supposed to be the 2nd half of the keynote. The Intel guys and their Oracle counterparts presented myriad of numbers and graphs to prove that Java runs well on the Intel architecture. Not really sure anyone needed a lot of convincing of that, but their results were impressive nonetheless.

Continue reading »

At a minimum, a Java PaaS solution provides a JVM based execution environment, built on top of production-ready cloud infrastructure, that allows for the easy deployment of applications, without having to provision or configure low-level system resources.

I just finished publishing a new machine image that includes improvements to integrate to the new repo.adobe.com Maven repository, and to also deploy CQ as a service so that it will startup and shutdown with the operating system.

Check the details here:

http://cqblueprints.com/xwiki/bin/view/Blue+Prints/CQ+Development+Team+Server+%22In+A+Box%22

I just finished doing a major update to the CQ Blueprints page about using Nexus as a Maven Repository for CQ development. The Blueprint now demonstrates how to make use of the repo.adobe.com repository that Adobe has recently made available.

Customers who wisely choose Maven as their build tool should setup their own Maven Repositories and configure them to proxy the repo.adobe.com repository to provide access to the CQ related artifacts for your team. Some possibly outdated documentation on the Day/Adobe sites recommends installing and using Apache Archiva as your local repository. However, since Nexus is now being used actively to manage the Maven Central repository it has become the defacto standard for Maven Repository management tools. As a result, we recommend the use of Nexus over any other Maven Repository management tools, including Archiva.

via Using Nexus as a Maven Repository for CQ Team Development Blue Prints.Using Nexus as a Maven Repository for CQ Team Development – XWiki.

We understand that the new rates surprised some of you. We’ve been listening closely to your feedback, and we wanted to share an update on the changes we’re making to help ensure you have an accurate picture of how the new pricing will affect your app. Although prices will increase, we’re confident that you’ll find App Engine still provides great value.

via Google App Engine Blog: A few adjustments to App Engine’s upcoming pricing changes.

I just finished writing another Blueprint over on the CQ Blueprints site. This time I talk about how to go about setting up and using Nexus as your team’s Maven Repository when working with Adobe CQ (now Adobe ADEP / CEM).

Check it out here: http://www.cqblueprints.com/xwiki/bin/view/Blue+Prints/Using+Nexus+as+a+Maven+Repository+for+CQ+Team+Development