Escalante 0.3.0 out now with Play Framework 2.1 support!

We're pleased to announce the next official release of Escalante - version 0.3.0. We consider this release to be beta quality, and lacks some of the features and API stability that will end up in the 1.0.0 release.

What is Escalante?

If this is the first time you've ever heard of Escalante, check out our FAQ section to find out more about Escalante.

What's in this release?

The main focus of this release has been adding support for Play Framework 2.1 scala web applications to Escalante. This means that Play 2.1 applications can be built, deployed and run on top of Escalante just like a normal Play application but with some limitations. To help Play users deploy applications on top of Escalante, quickstart applications have been developed and these are the best starting point.

Here's a summary of other highlights of this release:

  • Lift integration has been enhanced in order to support Lift 2.5 applications. The "Hello World" Lift quickstart has been upgraded to use Lift 2.5, but the other Lift quickstarts remain using Lift 2.4. This has been done on purpouse so that different Lift quickstarts can demonstrate not only different functionality, but they can also demonstrate that Lift applications can be deployed on top of Escalante, side by side, even if they use different Lift and/or Scala versions!

  • Support for Lift applications needing Scala 2.10 has been added. In fact, Escalante is now based on Scala 2.10 and resolves other Scala version as needed depending on the deployment.

  • Escalante SBT plugin version 0.2.0 has been released with added support for Play applications to be built, deployed and run on top of Escalante. In order to avoid issues with Escalante SBT plugin, please follow the methods shown in the quickstarts on how to define the Escalante SBT plugin version to use.

  • Escalante Quickstarts have now been tagged for version 0.3.0 and the great news is two new Escalante Play Quickstarts have been added with SBT build files. Also, the SBT based quickstarts now define the Escalante SBT plugin dependency via Git URI in order to avoid the dependency resolution issue on SBT/Ivy mentioned earlier.

What's next?

In next release, Escalante will be moving to being based on top of Widlfly and both Lift and Play integrations will be further enhanced. If there's anything in particular you'd like to see done with regards to Lift or Play integration, let us know!

Get It

The simplest way to install 0.3.0 is downloading our binary distribution.

Get In Touch

If you have any questions, issues, or other feedback about Escalante, you can find us on #escalante on freenode or our public forums.

Twitter

If you're interested in anything Escalante related, make sure you follow @escalanteio to find out first :). If you want to make any comments on Twitter, make sure you use the #escalante hash tag.

Escalante SBT plugin 0.1.2 out now!

We've just released version 0.1.2 of the Escalante SBT plugin.

What's in this release?

Extra dependencies other than Lift and Scala ones are now included in WEB-INF/lib directory within the generated Lift war archive. Once again thansk to Ali Salim Rashid for spotting and fixing this issue!! :))

How to use it?

To use this new version, update the SBT plugin version to be used in your project, i.e.

addSbtPlugin("io.escalante.sbt" % "sbt-escalante" % "0.1.2")

Check the Escalante SBT Git repo to find out out more about the Escalante SBT plugin.

Warning

Seems like the wrong dependency resolution issue has resurfaced as seen by this user forum post. It appears that a workaround has been found, but we're waiting for full confirmation before suggesting users to configure the Escalante SBT plugin that way.

Once confirmed, README files and quickstarts will be updated to show the recommended way to configure the plugin.

Get In Touch

If you have any questions, issues, or other feedback about Escalante, you can find us on #escalante on freenode or our public forums.

Twitter

If you're interested in anything Escalante related, make sure you follow @escalanteio to find out first :). If you want to make any comments on Twitter, make sure you use the #escalante hash tag.

Escalante SBT plugin 0.1.1 out now!

We've just released version 0.1.1 of the Escalante SBT plugin.

What's in this release?

The primary reason for the release is that some users could encounter an SBT issue that was causing the wrong dependency to be resolved, and since this dependency didn't exist at all, that would render the plugin unusable. This new SBT plugin version gets around the issue adding a explicit dependency on the library that caused issues. On top of that, a minor issue with the location of the JBoss Home folder has been fixed.

Many thanks to Ali Salim Rashid for spotting and fixing both issues!! :))

How to use it?

To use this new version, update the SBT plugin version to be used in your project, i.e.

addSbtPlugin("io.escalante.sbt" % "sbt-escalante" % "0.1.1")

Check the Escalante SBT Git repo to find out out more about the Escalante SBT plugin.

Get In Touch

If you have any questions, issues, or other feedback about Escalante, you can find us on #escalante on freenode or our public forums.

Twitter

If you're interested in anything Escalante related, make sure you follow @escalanteio to find out first :). If you want to make any comments on Twitter, make sure you use the #escalante hash tag.

Escalante 0.2.0 out now with SBT plugin!

We're pleased to announce the second official release of Escalante - version 0.2.0. We consider this release to be beta quality, and lacks some of the features and API stability that will end up in the 1.0.0 release.

What is Escalante?

If this is the first time you've ever heard of Escalante, check out our FAQ section to find out more about Escalante.

What's in this release?

This second release focuses on improving support for Lift web applications within Escalante. These are the highlights:

  • Escalante-optimised Lift applications are now supported in any Lift version (as long as Maven resolution succeeds, see documentation for more info), including latest milestone Lift 2.5-M4 release.

  • The way Lift applications define metadata so that Escalante can resolve Scala/Lift dependencies has changed. Instead of the old WEB-INF/lift.xml archive, Escalante now searches for META-INF/escalante.yml file, which is a much more human readable archive thanks to the use of YAML, and a lot easier to work with from a parsing perspective. For more info, check the documentation.

  • Escalante optimised Lift applications can now select which extra Lift modules to use (i.e. mapper, jpa, record...etc) by defining them in META-INF/escalante.yml, hence reducing burden on permanent space to only those modules needed. To find out more, check the documentation.

  • A SBT plugin fully dedicated to Escalante is now available!! Version 0.1.0 is now available from JBoss Nexus repository. This plugin allows several for Escalante-optimised Lift WAR applications to be created (including generation of META-INF/escalante.yml), and it can deploy these applications to an Escalante instance (embedded, no separate process!) from the SBT console thanks to the escalante-run command. I'd like to personally thank Josh Suereth for the chat we had at Devoxx 2012 that kicked off the development of the SBT plugin, and David Pollak, Lift founder and lead, for motivating me to enable Escalante instances to be started from SBT. Thanks guys!! Check the Escalante SBT Git repo to find out out more about the Escalante SBT plugin.

  • Escalante Quickstarts have now been tagged for version 0.2.0 and the great news is Escalante Quickstarts now have SBT build files as well as the existing Maven files. So, regardless of whether you use SBT or Maven, Escalante's got you covered :). The SBT files are configured with the Escalante SBT plugin, so you can get started with the newly created Escalant SBT plugin right away!

  • A new Escalante Quickstart has been added showcasing interaction of Lift applications with JPA 2.0. Although injection of @PersistenceContext or @PersistenceUnit instances is not yet available, Lift developers wanting to run their JPA applications in Escalante are recommended that they bind the EntityManagerFactory instance to JNDI.

What's next?

This new Escalante version uses a newer base JBoss EAP version than the one you can currently access via OpenShift, so the previous instructions provided to run Escalante in OpenShift might not work as expected. Over the next few weeks we'll be working on getting Escalante 0.2.0 working on OpenShift, hopefully with a dedicated cartdridge.

On top of that, now that Escalante SBT integration is in place, we'll start looking into how to get Play applications run on top of Escalante, as well as carry on developing Escalante Lift integration adding more quickstarts...etc.

Get It

The simplest way to install 0.2.0 is downloading our binary distribution.

Get In Touch

If you have any questions, issues, or other feedback about Escalante, you can find us on #escalante on freenode or our public forums.

Twitter

If you're interested in anything Escalante related, make sure you follow @escalanteio to find out first :). If you want to make any comments on Twitter, make sure you use the #escalante hash tag.

Escalante 0.1.0 Released

We're pleased to announce the first official release of Escalante - version 0.1.0. We consider this release to be beta quality, and lacks some of the features and API stability that will end up in the 1.0.0 release.

What is Escalante?

Escalante is an application server for Scala. It's an integrated platform built on JBoss AS7 that aims to provide an environment for deploying and running Scala applications that is easier to use and more efficient to run than other existing solutions.

What's in this release?

For this first release, we've focused on Lift web applications, trying to make them easier and leaner to deploy compared to other plattforms. With just a little bit of information, Escalante can vastly reduce the size of your deployments and can make it more efficient to run multipl Lift applications in paralell within the same Escalante server. You can find out more by checking Escalante's documentation.

What's next?

Now that we have 0.1.0 out the door, we'll be focusing on:

  • OpenShift cartdridge for Lift applications
  • Providing more Lift quickstarts
  • Investigate other Scala frameworks
  • SBT build files for Escalante quickstarts

Get It

The simplest way to install 0.1.0 is downloading our binary distribution.

Get In Touch

If you have any questions, issues, or other feedback about Escalante, you can find us on #escalante on freenode or our public forums.

Twitter

If you're interested in anything Escalante related, make sure you follow @escalanteio to find out first :). If you want to make any comments on Twitter, make sure you use the #escalanteio hash tag.

Thank you

From here I'd like to thank everyone who's been encouraging and helping me get this first Escalante release out. From Mark, who a less than a year ago inspired me to get Escalante started, to the Project:odd team who have been helping me with all the pain points of doing your first ever release, setting up the site, put up with my questions...etc ;). Thanks you all.