Hello all, I apologize it has taken so long to release a new version of Liferay IDE that supports Liferay 7 development. But today we are pleased to announce the first milestone release for Liferay IDE 3.0. And to quote a famous first line of a movie recently released: "This will begin to make things right."

For Eclipse Luna (4.4) and Mars (4.5), you can install from following updatesite URL:

New Features in Liferay IDE 3.0 M1

Liferay 7 Server Support

Now you can setup and run/debug Liferay 7 servers. Note that this supports all Liferay 7.x bundles, including non-tomcat bundles.

Also the server publishing of modules has been improved to directly publish bundles to the module framework in Liferay portal since webapp deployment is no longer supported going forward, all modules (even wars) will be installed via the module framework. During development if you have deployed any modules, any changes you make to the bundle, on save of the file, the bundle will be immediately rebuilt and reinstalled into the running Liferay 7 module framework.

Once you have launched Liferay 7 server, and you want to interact with OSGi runtime you can do that with the new Gogo shell integration.

Liferay 7 Module Dev Support

In Liferay 7 the new method of extending / customizing Liferay is through modules (OSGi bundles). So in Liferay IDE we have added support for developing these modules through New Project wizards, recognizing both gradle and maven based module projects, and deploying these modules to Liferay 7.

New Liferay Module Project Wizard

In this wizard you can create new individual module projects based on different templates. For 3.0 M1 only "gradle" type of modules can be created. We are working on maven versions that should be ready 3.0 GA.

The 2nd page of the wizard gives you ability to customize the Java class that will be the DS Component class.

If you choose "service" as the module template then on this page you can specify which "service" you are trying to implement. This is useful for implementing on of the many OSGi integration points for extending Liferay 7 UI.

Gradle / Maven bundle projects

We have included Gradle support through Eclipse Buildship plugin that is bundled with Liferay IDE. Maven bundle project support is via the Eclipse m2e plugin (also available as a Liferay IDE feature).

For a bundle project that uses gradle, you can import it with the File > Import > Gradle project. Any gradle project that applies either the Liferay gradle plugin or bnd builder gradle plugin will be recognized as a "Liferay 7 module".

Maven projects that use either "maven-bundle-plugin" or "bnd-maven-plugin" are recognized as "Liferay 7 module" projects.

Any project that is a "Liferay 7 bundle" can be published (deployed) to Liferay 7 server in the servers view. And for each resource in the bundle that is modified in the IDE, the bundle will immediately be rebuilt and reinstalled into Liferay 7 module framework.

Future Blog posts

There are many new development tools related to Liferay IDE and Liferay 7 that I would like to show you but I want to split that out into a few other blog posts, call it a series... :)

Liferay IDE and "Workspaces"

Introducing blade cli tool

Legacy plugin sdks projects in Liferay IDE 3

Migration tools for Liferay 6.2 projects

As always find us on the forums if you have questions or suggestions or bugs (warning this is milestone there are going to be some!)

Just a quite notice that we have pushed a new release of Liferay IDE version 2.2.1 that just pushes a few fixes for the latest major release including a nasty memory, GC bug here that would affect anyone with portal-source open in their workspace. Also this release prepares us for the upcoming Liferay Developer Studio 2.2 release which will be available on December 1st.

JavaScript / AlloyUI

We are very excited about this release because we have finally for the first time have some real AlloyUI support along with the brand new JavaScript development support features. In order to give Eclipse developers the type of JavaScript coding support that they have come to expect from the java tools, we have integrated a new framework called tern.java which bundles liferay and aui plugins for tern.

TL;DR type inference for AUI rocks!

Not only AUI but YUI types as well

Also jQuery is supported as well and AlloyUI4 support will be added in IDE 3.0

Liferay JavaScript object

And also commonly used javascript anonymous functions has type inferrencing

AlloyUI Feature

In order to use these new features you have to make sure to select the new top level feature on the update site when you install this release:

Go here to see description of all the new features related to AlloyUI and JavaScript support.

Portlet Development UX

Recently our team ate our own dog food and developed a few portlets for internal use and we found ourselves wanting some new features that would make portlet development more productive so we've added many new features targeted at portlet development. Most of those revolve around improvements we made to the Eclipse JSP editor to support Liferay portlet dev features.

<aui:script> tag support, now finally good javascript support in a JSP!

Quick-fix and quick assist for portlet resource bundles

Fix one or fix several with just a few clicks

If you want to fix more than one of the same warning just select all and fix at once

Or invoke quick assist (ctrl+1) and never show the popup dialog

Portlet action method completion

Quick assist here as well

There are too many of those features to list them all here so we created a special page for all the noteworthy portlet development features here.

New Editors

All of our XML editors have been redesigned to open very fast, as fast as the plain text editor. Try it for a spin and feel the difference. Also, for this release we have several new specialized eclipse editors, for portal.properties and portal-ext.properties, liferay-portlet.xml, and a improved layout template editor that supports 6.2 style layouts finally!

Other Features

Many eclipse developer have multiple workspaces, but it is a pain to have to re-define each of your SDKs, runtimes and servers for each of those workspaces. Now when you open a new workspace you will see a notification popup informing you that you can import all of your Liferay settings(not projects) from the previous workspace is you would like. HT to Kamesh for the initial code contribution.

To see the rest of the "other" features added to this release see this page.

Special Thanks

Thanks so much to the other members of the IDE team in China: Ashley, Vicky, Kuo, Lilu, Simon, Terry, XuYing, and Eric (recently joined so he isn't in the photo) who worked so hard on this release. Also thanks to all of those community members who submitted bug reports and feedback. A special mention goes out to Angelo Zerr the author of the tern.java and eclipse-wtp-xml-search plugins that we have integrated in this latest release giving Liferay developer lots of new goodies to play with. Please give us feedback or let us know what problems you may be running into over on our forums. Good luck!

Full list of issues can be see here. Actually we have had severalreleases of Liferay IDE since my last blog post. I'll try to do a better job of keeping you up2date in the future. We have some exciting things planned for Liferay IDE 2.2, namely, better AlloyUI/JavaScript support!

Brand New Liferay Plugin Project Wizard

The biggest new feature of M3 is the new completely re-written New Liferay Plugin Project Wizard that provides two big new features 1) Maven project support for projects using liferay-maven-plugin, 2) Freestyle SDK project (you can create SDK projects at any desired location)

Maven project support

With the new Liferay Plugin Project Wizard in M3 you can select a different build type: Maven

Once you have selected Maven you can specify maven options like artifact version and top level package. Also there is a place for you to associate Maven profiles to activate on your project that most developers will use to attach developer machine specific properties like the Liferay version or local Liferay bundle properties.

Flexible project location support in Plugins SDK

Now in the latest version of Plugins SDK you can create projects that live outside of the Plugins SDK folder structure. In the new Liferay Plugin Project Wizard you can activate this feature two ways 1) selecting to not Use Default location and specifying your own location

Feedback

We really need the communities help in providing feedback on this milestone release. Especially issues involved in migrating from IDE 1.6.x projects, or using Maven and Ivy enabled projects. Post issues to Liferay IDE Forums or the JIRA project. Thanks!

We here on the IDE team are pleased to announce the new release of Liferay IDE: Liferay IDE 2.0 Milestone 1. Since this is an Eclipse release all you need is to use the following update site url in the Help > Install New Software... dialog.

This milestone release is the first in a series of milestones leading up to Liferay IDE 2.0 GA release that is planned for just after Liferay Portal 6.2 GA. Below are some highlights Liferay IDE 2.0 M1:

Milestone Releases

The reason that we are releasing 2.0 in a series of milestones is because of all the changes that happened since 1.6.x namely the integration of maven projects which have a totally different layout than ordinary SDK based projects. So we need your feedback if you run into problems when you upgrade from previous version. We plan to have at least 2 more milestones of IDE 2.0 until we are all finished with adding the planned features.

Liferay Portal 6.2 Support

Now that the Liferay Portal 6.2 Beta releases are out IDE uses can finally have a way to use them using the Eclipse server adapter support. The new 6.2 runtime/servers have been added right along side 6.0/6.1.

Liferay Maven Project Support - New m2e-liferay Feature

One of the most requested features for Liferay IDE has been maven support. This release now provides that support through a separate installable feature called m2e-liferay.

This is an extension of the existing Eclipse built-in maven support (m2e) but specialized to support the liferay-maven-plugin available for Liferay projects. This topic is quite log and involved so it needs its own page about m2e-liferay. But below is an image that shows a properly configured Liferay Portlet project that is using the liferay-maven-plugin and is correctly configured in Liferay IDE 2.0M1. Notice that the Liferay Portlet facets are installed and that you can drag-n-drop these projects onto the Liferay Portal Server adapter.

Ivy support for Plugins SDK projects

In the latest version of the portal 6.1.2, 6.1.30, and upcoming 6.2.0 Ivy support has been added to the Plugins SDK. So now some of the projects created by SDK will come with their own ivy.xml file for dependency management along with the common infrastructure for Ivy (cache dir) residing in the root of the Plugins SDK. In order for these projects to work full in Eclipse (all classes compile) we need to enable Ivy dependency management for Eclipse. This is going to be accomplished by integrating the great work by the IvyDE team, using their plugin for Eclipse (IvyDE) to support Ivy enabled Liferay plugin projects.

So starting with 2.0M1 of Liferay IDE it will come bundled with IvyDE plugin. Also if any project that is created in the SDK contains an ivy.xml file (e.g. JSF projects) then the New Liferay Wizard will automatically add a Ivy nature, add an Ivy container configured to use Plugins SDK cache and ivy-settings.xml from the Plugins SDK and will also automatically invoke the resolve for the container (i.e. download the dependencies).

Theme Improvements

If in the new project wizard you select that you want to create theme project, you can see additional options for specifiying the theme parent and the template langauge you want to use. By default we have switched to Freemarker mainly because of the next biggest new feature, the Freemarker debugger.

Freemarker Debugger

Included in the 2.0M1 release is a new feature for debugging Freemarker templates executed for Liferay theme plugins. This feature creates a Freemarker debugger client integrated with Eclipse debug view. When you launch a Liferay Portal 6.2 Server in "Debug" mode it will automatically enable the embedded Freemarker debugger. Then you can add breakpoints to any FTL file that is opened with the Liferay Freemarker Editor. When the Portal evaluates those FTL templates it will pause execution and activate the debug view Eclipse.

You can then inspect variables, step, resume as you would expect in normal java debugger.

Also you can suspend the calling Java thread in order to see the stacktrace from Liferay that calls into the Freemarker template engine.

There are some missing features that you would expect, like watchpoints, native stepping, run-to-line, making changes to stack, etc. We are working with Freemarker team in order to deliver a advanced debugger for future versions of Freemarker that will have more features equivalent with all modern java debuggers.

Other highlights

Various Layout Template Visual Editor improvements

Remote server adapter supports proxy servers

Portlet wizard now supports adding portlets to Control Panel

Feedback

We really need the communities help in providing feedback on this milestone release. Especially issues involved in migrating from IDE 1.6.x projects, or using Maven and Ivy enabled projects. Also since the Maven support (m2e-liferay) is in its first version so there are going to be some rough edges to be smoothed out in the upcoming milestone releases. But the quality will be much better if the community will report issues they have with 2.0M1. Post issues to Liferay IDE Forums or the JIRA project.

Special Thanks

Before I finished this blog post I wanted to mention a couple of words of thanks. Firstly, I need to mention my QA team members, Ashley Yuan and Vicky Wang that were in charge of QA for the 2.0M1 release. They have written lots of UI functional tests and regresion tests the past year as we have been working up to this release. A massive change in the codebase that this involved would have been impossible with their efforts. Thanks team!

Also special thanks goes out to a couple of other super-smart engineers, Neil Griffin and Mika Koivisto for all of their help with maven. Neil for being my maven mentor and Mika for fielding my pull requests and helping me understand the liferay-maven-plugin when both of those guys are super busy and have bigger fish to fry! :)

Serveral weeks ago we updated the Remote IDE Connector application to version 1.0.1. This new update fixed the issues that we found with the 1.0.0 version of the Remote IDE Connector. Namely, it works correctly now :) **Update** I forgot to say thanks to the Marketplace team. They did a ton of work to improve Marketplace infrastructure to be able to roll out changes to apps that had bug-fixes such as this. Thanks for everything you do guys!

So Liferay IDE users can now install (or update) this application into their remote portal instances and then setup a new Remote Liferay Portal Server adapter in Liferay IDE to connect to it and use it as a development and deployment target just like they would a local instance of Liferay Portal running on your machine.

To help out new users we've created a special wiki page for now to demostrate how to configurate it. I hope to get this information moved over to official documentation for Liferay IDE in the near future. For now if you have any problems with either the Remote IDE Connector or the Liferay Remote Server Adapter be sure to create a new thread in the Liferay IDE Forums.

Today, the Liferay IDE team has released Liferay IDE 1.6.2. This release is minor release that only fixes a couple of issues found with Eclipse Juno SR compatibility. So if you are using Eclipse Juno SR2 or want to upgrade, you will need to upgrade or install Liferay IDE 1.6.2 first from the normal updatesite URL:

Stay tuned to this blog for more updates related to Liferay IDE, namely Remote IDE connector update and also some news about upcoming 2.0-Milestone-1 version of Liferay IDE that will have Liferay Portal 6.2 milestone server adapter support and also support for projects built with the Liferay Maven Plugin SDK. :)

Just before the holidays I'd like to let everyone know about the two most recent releases of Liferay developer tooling. Back in November, we released a bug-fix release of Liferay IDE version 1.6.1. Now today we are releasing a new release of Liferay Developer Studio v1.6.1. This release is primarily for bringing Developer Studio up-to-date with the latest Liferay IDE release along with some additional bug fixes from the previous Studio 1.6.0 release. This new version of Developer Studio also includes all of the latest fix-packs for the bundled Liferay Portal and Plugins SDK as well.

Just to recap the previous Liferay Developer Studio release, the most notable feature was the new Kaleo Designer for Java that you can see a demo of here.

Today we are pleased to announce the latest release of Liferay Developer Studio version 1.6.0. Here on my blog I usually just cover Liferay IDE releases, so just to bring everyone up to speed, Liferay Developer Studio is our own branded Eclipse-based product that is built on top of Liferay IDE along with some additional enterprise features (e.g. WebSphere server adapter). It also contains the latest versions of Liferay Portal EE and Plugins SDK bundled and pre-configured to work out of the box.

If you're ready to give it a try, you can download a trial version here.

Kaleo Designer for Java

Liferay Portal EE already contains a visual Kaleo workflow designer built-in to the Kaleo Forms application. However, we wanted to create a new tool directly targeted at back-end Java developers, so we decided to add this to our Eclipse-based dev environment, Liferay Developer Studio. The Kaleo Designer for Java is a multi-page editor that allows editing of Kaleo workflows either as a visual diagram or a XML source editor. There are also related tools, wizards, and property views, content-assist associated with this visual editor that most Eclipse Java developers have become accustomed to with other tooling. The biggest productivity enhancements for Java developers in this version is the integration of the Java/Groovy script editor for editing Kaleo workflow action and condition scripts and the Freemarker/Velocity template editor for creating notofication templates.

There will be more available articles and extended documentation about the Kaleo Designer for Java in the upcoming weeks, but for now, instead of posting a lot of screenshots, we decided to record a short demo video instead.http://vimeo.com/48315976

If you are a Java developer and need to create a new or modiify an existing workflow process in Liferay, I hope you will give Kaleo Designer for Java a try.

The latest release of Liferay IDE version 1.6.0 has been made available today. Head over to the downloads page if you want to grab an archived updatesite or an "all-in-one" bundle of both Eclipse Juno and Liferay IDE. The new version brings compatibility with the most recent Eclipse Juno (4.2) release. Please use the following updatesite for Eclipse Juno:

If you are using an older version of Eclipse (3.6, 3.7) this latest release is also available to you as an update. From your Eclipse installation that contains Liferay IDE just do Help > Check for updates... If you do not already have a Liferay IDE installation, here is the Eclipse update site URL for new installations:

If you find any issues with this new version please head over to Liferay IDE forums and post the issue or create a ticket in JIRA.

In addition to being compatible with Eclipse Juno and several bug fixes, there were several minor enhancements that I'd like to mention from this release below. Also, special thanks to Kamesh Sampath for contributing an enhancement to enable non-default ROOT configurations for Tomcat bundles.

Automated source attachment for Liferay Portal classes

Having access to the Liferay source for debugging Liferay Portal applications is almost a must. This process of attaching source location to jars in Eclipse classpath containers is tedious and you have to do it again for each new project. Now this can be done only once in Liferay IDE and then all new Liferay jars that are added to projects will automatically have the proper source attachment. Simply go to the 2nd page of the Liferay Portal runtime wizard and specify a location (either a jar file or a exploded directory) of the Liferay Portal sources (portal sources are available for each release in portal downloads area).

Then once you create a project that has Liferay jars added (runtime or API classpath container) you will automatically have the sources attached and available when you open Liferay classes.

Added support for supported JSF Component Suites

Recently Neil Griffin added support to the Plugins SDK for additional JSF project templates that support all of the various JSF component suites that are supported on Liferay, e.g., Liferay Faces, ICEfaces, PrimeFaces, etc. In this release of Liferay IDE support** for these various templates has been made available on the 2nd page of the New Liferay Project wizard if you select JSF as your portlet framework.

Thanks Neil for the help with this feature!

Zoom, Print, Save as Image actions available for Service Builder Diagrams

You can now perform several useful actions on service builder diagrams like: zoom, print and save as an Image.

Now you can finally print off a relationship diagram of Liferay Portal services and try to understand it all. FYI, be sure to have several pages loaded in your printer first. :)

Whats next for Liferay IDE?

What up next for Liferay IDE project is version 2.0, which should bring remote portal structured content editing, the much-awaited Maven support along with some better theme development support. If you want to help with testing these new 2.0 features, just add the Juno nightly build URL below:

Eclipse Juno (3.8/4.2) is scheduled to be released today (June 27th). However, the current stable build of Liferay IDE (1.5.3) is not compatible with Eclipse Juno. It will be a few more days before I can create a new stable build of Liferay IDE (1.6.0) since there are a few remaining issues that need to be resolved.

However, in the meantime we are going to make a Juno compatible build of Liferay IDE available on the nightly build updatesite. Here is the new one that you can use for Juno (updatesite should be available by the 27th).

This release fixes a regression in the New Liferay Project wizard for Eclipse 3.7.2 users where the default output folder for the java web project would cause the classes to not be deployed to Liferay Tomat server when deployed through Add/Remove Modules... wizard.

Another important update in this release is an improvement to the Theme project development workflow. Here is how Theme project development worked previously(<= 1.5.2):

Create a new theme project

Deploy to Liferay Tomcat Server through Add/Remove Modules dialog...

Make a change in the _diffs folder under docroot/

Liferay IDE detected this change and would invoke a "ant compile" in the background for the theme This would copy hundreds of files into the root of the docroot folder (to full compile the theme from the declared parent)

Liferay IDE would publish the delta changes to the docroot of the project out into the webapps/ folder in Tomcat

Tomcat would detect these changes and redeploy if it saw changes to descriptor files (web.xml)

View the theme in the Portal

Make another change to any _diffs resource

"ant compile" is re-invoked and all of the changed files are deployed to tomcat webapps/ folder once again.

Tomcat may redeploy and restart the context

Refresh the browser to see the change to the theme.

This recompiling and redeploying would happen automatically for every change in the _diffs folder no matter how small. The reason for this is that Liferay does not read the css files from the _diffs folder. It reads it from the compiled files in the root webapp (docroot). So to see the changes made in _diff you had to make sure the theme was re-compiled to copy the changes from _diffs out to the parent docroot. This caused lots of problems for tomcat as it had to constantly redeploying and restart the theme context if it saw changes to that many files, which led to instability in the development process.

Now lets look at what happens with Theme projects in latest version of Liferay IDE (1.5.3).

Create a new theme project

During the creation of the project the theme is pre-compiled so it doesn't wait on the auto-compile to happen from first change to _diffs

Deploy to Liferay Tomcat Server through Add/Remove Modules dialog...

View the theme in the Portal

Now when changes are made to _diffs/**/* resource, Liferay IDE detects this change and just copies the single small delta change into the docroot parent.

Auto-publish event is triggered for the Liferay Tomcat server and this same small delta update is made to the theme published in the webapps/ folder in tomcat. Tomcat does not redeploy or restart the context single only a small change (single css or tempalte file) was modified.

Refresh the page in the browser to see the update in the portal

This should be a much improved development experience for Theme developers with Liferay IDE (or Developer Studio). We have more improvements for Theme developers planned for the upcoming 1.6/2.0 release, so now is a good time to head over to the Liferay IDE forums to make a feature enhancement suggestion or report issues found with the latest 1.5.3 release.

We just released version 1.5 of Liferay IDE (Eclipse plugins). From your Eclipse installation that contains Liferay IDE just do Help > Check for updates... If you do not already have a Liferay IDE installation, here is the Eclipse update site URL for new installations.

There is a new Liferay IDE 1.5 Release page where you can see some details and screenshots about the new release. Here are the most important new features available in this release:

Liferay Hook Configuration Editor

Support for importing Liferay binary plugins as new projects

JSP Debugging for projects deployed to Remote Liferay Servers

Support for Glassfish as a Remote Liferay Server (through server-manager-web Liferay plugin)

Here are a couple of screenshots of the new features in action:

I'll be checking the Liferay IDE forums if anyones has problems with upgrade or installation.

**Update**

Lastly I wanted to mention again a Liferay IDE contributor to this release of Kamesh Sampath. He wrote the new Binary Import wizards with very little help from my part, just knocked out that feature all on his own. Also, he wrote the first version of the liferay-hook.xml before it went through additional revisions leading up to the 1.5 release. Thanks again Kamesh for all your hard work!

I'd like to mention one of the new features in the upcoming release of Liferay 6.1, which is the remote development and deployment support from Liferay IDE. The idea is that with this feature you can build Liferay projects in Liferay IDE like normal but instead of the Liferay server running locally it is running on a remote host. This is accomplished through two things, 1) new remote server adapter in Liferay IDE and 2) Server manager plugin (new in 6.1) deployed to the remote Liferay server

This feature will be officially available with the Liferay 6.1 CE release, but since it is only in beta, now is a good time to try it out and give feedback.

For those who wish to try this out here are the steps to setting it up.

Now when you modify files in your project, every 15 seconds it will publish the delta of any changes to remote server. However, you can publish changes immediately using the "publish" action in the servers view. If you want to change the automatic publish rate you can do that in the server configuration editor (double click server in Servers view).

For anyone who decides to try this out and want to give feedback with suggestions or problems please either open a JIRA ticket for the IDE project or enter a new topic on the IDE forums.

Liferay 6.1 (nightly/trunk) recently switched to Tomcat 7 so we've now added support for launching Tomcat7 in Liferay IDE with a new server type.

Also in this new release there is a new portlet configuration editor available by default. Before showing off any screenshots of the editor, I would like to publically thank a Liferay community member, Kamesh Sampath for contributing the code for this editor. He volunteered many hours of his own personal time to build it and is committed to make it a first-class editor for Liferay and portlet developers. Personally it has been a pleasure for me to collaborate with Kamesh over last few weeks working on this editor. I look forward to seeing more excellent features from him on both Liferay IDE and Lifery Portal in the future. If you like the new editor, feel free to drop him a note on his profile page.

That is it for now. I'm actually just about to head to Hong Kong with my familiy this week since its October Holiday here in China and the office is shut down for the week. I'll be checking the Liferay IDE forums at least one a day to help any users with upgrade issues.

Liferay IDE 1.3 Now Available to Download

If you already have Liferay IDE installed in Eclipse Helios you can check for updates to pull down the new release. If you are has Eclipse Indigo installed, here is the stable update-site URL for Indigo:

The detailed installation guide for Liferay IDE can be found here. However, it has not been updated with the latest URLs for installing 1.3 but you can use either of the URLs above depending on your Eclipse version.

Just a quick note Liferay IDE users who are wanting to upgrade to Eclipse Indigo. At the moment the stable version of LIferay (1.2.3) does not support Eclipse Indigo. However, the next version of Liferay IDE (1.3) that is due to be out next month does support Indigo. If you want to upgrade to Eclipse Indigo now and continue to use Liferay IDE you will need to install the development build (nightly) of Liferay IDE built for Indigo which can be found here:

Since this is a nightly build it will be subject to frequent changes over the next few weeks as the 1.3 release is completed but it should be ready for everyday use in its current state. If you run into issues be sure and either post a question on the Liferay IDE forums or create an issue on the Liferay IDE JIRA project.

I just noticed that Eclipse has released Eclipse Helios SR2 (3.6.2). Also last week we released a bug fix release for Liferay IDE 1.2.1. Unfortunately I have just verified that the latest Eclipse release (3.6.2 and WTP 3.2.3) is not compatible with Liferay IDE 1.2.1 (as well as previous versions). If you upgrade to Helios SR2 there will be a new blocking issue introduced during publishing of projects (deployment) that will cause it to fail. There is no workaround that I know of at this time other than to use Plugins SDK deployment via "ant deploy" build.

This issue can be fixed but it wont be available until next week, Monday at the earliest. Sorry for the inconveince.

*Update* Version 1.2.2 has been released that contains a fix for the previous incompatibility.. So just "Check for updates..." to get the latest version.