On the 1st February, the RAP 2.0 RC2 was released - http://www.eclipse.org/rap/noteworthy/2.0/?build=RC2 Since that time I am unable to start NetXMS RAP application under eclipse. The most obvious error is "Unable to locate installable unit org.eclipse.rap.equinox.target.feature.feature.group" and there are hundreds of more unresolved dependencies because of that.
My colleague can see the same message in the RAP target definition, but he can still run the application because he did not update the target definition.

I tried to create a new workspace and setup the RAP target once more from the scratch as described on wiki (http://wiki.netxms.org/wiki/How_to_setup_Eclipse/RAP). The first step that asks for installation of "Rich Ajax Platform (RAP)" from "RAP 2.0 Tooling" probably needs to be changed - in my case the following is available:


Apart from that, everything seems to be all right until the dependencies should be resolved. Now comes the part that I do not understand. For example netxms Core bundle requires org.eclipse.core.runtime;bundle-version="3.9.0" . This particular line in the MANIFEST file was not changed since December 13th 2012 (revision 6886).
My local eclipse installation (Juno Service Release 1 Build id: 20121004-1855) shows org.eclipse.core.runtime;bundle-version="3.8.0.v20120521-2346". So obviously the requirement is not fulfilled.
I was able to run NetXMS on last Friday under the same eclipse installation.... strange, right?

Any ideas what I should try to get back to state when RAP application can be properly imported and started?

Thanks,
Lukas

Hi!

Just committed changes necessary to run on RAP 2.0 RC2 - mostly changing dependencies to 3.8.0. It's strange, but in RC2 versions of eclipse packages changed to 3.8 from 3.9. After these changes, web ui seems to work fine. The only one strange issue I encounter so far is extremely large fonts in some places. I'll investigate it a bit later.

And I created new runtime platform from scratch. I encounter some strange issues in the past when trying to upgrade existing runtime platform, so to be on a safe side it's better to always create new one.

Best regards,
Victor

I can confirm that it works now.
Thank you Victor.