[Pete Helgren]

I just upgraded from ME 10 to ME 2014 and I am having difficultly getting the Liferay IDE plugin to work. I had great difficulty getting the plugin to install but it looks like ME finally installed the 1.6.x version (I think the latest is 2.1.x). If I try to deploy using the plugin I get the error:

Error running SDK command deploy
java.lang.NullPointerException

If I try to edit the Service Builder XML I get this error:

Caused by: java.lang.NoSuchMethodError: org.eclipse.sapphire.ui.swt.xml.editor.SapphireEditorForXml.<init>(Ljava/lang/String;)V

Saw a post about something similar and the workaround was to install the 1.6.x version of the plugin (which IS installed in my case).

Pretty much dead in the water now since I cannot deploy or edit Liferay components. Any suggestions?

[support-pradeep]

phelgren,

Sorry that you are seeing this issue. We are unable to replicate the issue at our end on ME 2014 and Liferay 1.6 plugin.

> I have created a LifeRay project with ‘Tomcat 7’ Liferay portal runtime and ‘Portlet’ plugin type. Then ran the deploy command from project context menu > Liferay > SDK > deploy and couldn’t replicate the issue. If there are any other steps that should be done to replicate the issue, please mention those steps.

> Can you please make sure whether the ‘Ant’ settings are correct ? Also make sure that the Liferay settings are correct under Window > Preferences > Liferay ?

I suggest you to cross post on LifeRay forums to check if they can provide any solution for this issue, since it looks like a Liferay configuration related issue.

[Pete Helgren]

Thanks Pradeep…..I can do the same but it is the migrated projects from ME10 that have this issue….I am using the 32 bit JVM version if that is of any interest.

I couldn’t upgrade to the current Liferay IDE (2.1) because of site connection issues so I went ahead and downloaded the archive version and installed it. It initially said it couldn’t install and then calculated a different way (it was a status message with 15 steps…?). It DID say it was going to uninstall ME2014 (which didn’t make sense!) I was able to install the 2.1 IDE but when I restarted ME 2104, I got the following error:

“The MyEclipse executable launcher was unable to locate it’s companion shared library”. Re-running the ME2014 installer also died with the error “Fatal error in DeliveryCheckAvailableInstallOptionsProcessor”.

Sounds like the Liferay 2.1 IDE install completely hammers ME 2014. What do you suggest I do?

[support-pradeep]

phelgren,

LifeRay IDE 2.1 depends on Sapphire 8, while MyEclipse 2014 use Sapphire 0.6. Since both versions of Sapphire cannot co-exist in the same configuration, the installation of this version of LifeRay will fail.

Regarding the ‘MyEclipse Executable’ error, since you have removed MyEclipse 2014 you are seeing that error. I recommend you to rename the .deliverycenter.installs file located in C:\Users\<username> and then rerun the MyEclipse 2014 installer to install a new copy of MyEclipse without any issues.

Regarding the deploy issue in Liferay 1.6.2 plugin, Can you please answer some more queries to help us investigate further :
> Can you please share your MyEclipse installation details from MyEclipse > Installation summary > Installation details ?
> Can you please clarify whether the Liferay SDK version and the Tomcat runtime version used in MyEclipse 2014 is the same/higher when compared to SDK and tomcat versions used in MyEclipse 10 ? Also clarify which version of plugin did you install in MyEclipse 10 ?
> Can you please mention the exact steps you followed to install the Liferay 1.6.2 plugin in MyEclipse 2014 ?

As suggested in my previous response, can you please post the issue on Liferay plugin forums for a solution ,as this looks like a Liferay configuration problem.

[Pete Helgren]

Pradeep,

Thanks again. Here is the installation summary (for the second time I installed ME2014)

*** Date:
Monday, April 14, 2014 1:36:03 PM CDT

*** System properties:
OS=Windows7
OS version=6.1.0
OS arch=x86
Profile arch=x86
Window system=win32
Java version=1.7.0_45
Workspace=file:/E:/workspaces-ME2014/bsf606/
VM Args=-Xmx768m
-XX:MaxPermSize=320m
-XX:ReservedCodeCacheSize=64m
-Dosgi.nls.warnings=ignore
-Djava.class.path=C:\OTHERP~1\MYECLI~2\plugins/OR8508~1.JAR

*** Subscription information
Product Id: E3MP (MyEclipse Professional Subscription)
License version: 3.0
Full Maintenance Included
Subscription expiration date (YYYYMMDD): 20150519
Number of users: 1

*** Eclipse details:
MyEclipse Enterprise Workbench

Version: 2014
Build id: 12.0.0-20131202

Blueprint: N/A

com.genuitec.eclipse.mobile.feature – 12.0.0.201311260528
com.genuitec.myeclipse.database – 12.0.0.me201311281640
com.genuitec.myeclipse.desktop – 12.0.0.me201311281640
com.genuitec.myeclipse.enterprise.workbench – 12.0.0.me201311281640
com.genuitec.myeclipse.geronimo – 12.0.0.me201311281640
com.genuitec.myeclipse.glassfish – 12.0.0.me201311281640
com.genuitec.myeclipse.icefaces.feature – 12.0.0.me201311281640
com.genuitec.myeclipse.imageeditor – 12.0.0.me201311281640
com.genuitec.myeclipse.jboss – 12.0.0.me201311281640
com.genuitec.myeclipse.jetty – 12.0.0.me201311281640
com.genuitec.myeclipse.jonas – 12.0.0.me201311281640
com.genuitec.myeclipse.jrun – 12.0.0.me201311281640
com.genuitec.myeclipse.jsf – 12.0.0.me201311281640
com.genuitec.myeclipse.maven – 12.0.0.me201311281640
com.genuitec.myeclipse.oracle – 12.0.0.me201311281640
com.genuitec.myeclipse.orion – 12.0.0.me201311281640
com.genuitec.myeclipse.persistence – 12.0.0.me201311281640
com.genuitec.myeclipse.reports – 12.0.0.me201311281640
com.genuitec.myeclipse.resin – 12.0.0.me201311281640
com.genuitec.myeclipse.struts – 12.0.0.me201311281640
com.genuitec.myeclipse.sun – 12.0.0.me201311281640
com.genuitec.myeclipse.tomcat – 12.0.0.me201311281640
com.genuitec.myeclipse.uml2 – 12.0.0.me201311281640
com.genuitec.myeclipse.visualvm – 12.0.0.me201311281640
com.genuitec.myeclipse.visualvm.server – 12.0.0.me201311281640
com.genuitec.myeclipse.weblogic – 12.0.0.me201311281640
com.genuitec.myeclipse.websphere – 12.0.0.me201311281640
com.genuitec.myeclipse.ws – 12.0.0.me201311281640
org.eclipse.birt – 4.3.1.me201311281640
org.eclipse.datatools.connectivity.feature – 1.11.1.me201311281640
org.eclipse.datatools.enablement.feature – 1.11.1.me201311281640
org.eclipse.datatools.modelbase.feature – 1.11.1.v201306041610-7707GCcNBHLDaKTEcRi
org.eclipse.datatools.sqldevtools.feature – 1.11.1.me201311281640
org.eclipse.emf – 2.9.1.v20130902-0605
org.eclipse.gef – 3.9.1.201308190730
org.eclipse.graphiti.feature – 0.10.1.v20130918-0838
org.eclipse.jpt.jpa.feature – 3.3.1.me201311281640
org.eclipse.jpt.jpadiagrameditor.feature – 1.2.0.me201311281640
org.eclipse.jst.common.fproj.enablement.jdt – 3.4.0.me201311281640
org.eclipse.jst.enterprise_ui.feature – 3.5.0.me201311281640
org.eclipse.jst.server_adapters.ext.feature – 3.3.103.me201311281640
org.eclipse.jst.server_adapters.feature – 3.2.201.me201311281640
org.eclipse.jst.server_ui.feature – 3.4.1.me201311281640
org.eclipse.jst.ws.axis2tools.feature – 1.1.200.me201311281640
org.eclipse.m2e.feature – 1.4.0.me201311281640
org.eclipse.sapphire.platform – 0.6.6.201310081535
org.eclipse.wst.common.fproj – 3.4.0.me201311281640
org.eclipse.wst.server_adapters.feature – 3.2.300.me201311281640
org.eclipse.xsd – 2.9.1.v20130902-0605
org.springframework.ide.eclipse.feature – 3.3.0.me201311281640

com.liferay.ide.eclipse.tools – 1.6.2.v201303111029
fr.obeo.acceleo.bridge.feature – 2.6.0.me201311281640
org.eclipse.cvs – 1.4.0.v20130911-1000
org.eclipse.draw2d – 3.9.1.201308190730
org.eclipse.e4.rcp – 1.2.1.v20130910-2014
org.eclipse.egit – 3.1.0.201310021548-r
org.eclipse.epp.mpc – 1.2.1.I20130917-2019
org.eclipse.equinox.p2.core.feature – 1.2.1.v20130827-1605
org.eclipse.equinox.p2.discovery.feature – 1.0.100.v20130502-0334
org.eclipse.equinox.p2.extras.feature – 1.2.0.v20130827-1605
org.eclipse.equinox.p2.rcp.feature – 1.2.0.v20130828-0031
org.eclipse.equinox.p2.user.ui – 2.2.0.v20130828-0031
org.eclipse.help – 2.0.1.v20130911-1000
org.eclipse.jdt – 3.9.1.v20130911-1000
org.eclipse.jgit – 3.1.0.201310021548-r
org.eclipse.jsf.feature – 3.7.0.me201311281640
org.eclipse.mylyn.bugzilla_feature – 3.9.1.v20130917-0100
org.eclipse.mylyn.commons – 3.9.1.v20130917-0100
org.eclipse.mylyn.commons.identity – 1.1.1.v20130917-0100
org.eclipse.mylyn.commons.notifications – 1.1.1.v20130917-0100
org.eclipse.mylyn.commons.repositories – 1.1.1.v20130917-0100
org.eclipse.mylyn.context_feature – 3.9.1.v20130917-0100
org.eclipse.mylyn.cvs – 1.1.1.v20130917-0100
org.eclipse.mylyn.discovery – 3.9.1.v20130917-0100
org.eclipse.mylyn.git – 1.1.1.v20130917-0100
org.eclipse.mylyn.ide_feature – 3.9.1.v20130917-0100
org.eclipse.mylyn.java_feature – 3.9.1.v20130917-0100
org.eclipse.mylyn.monitor – 3.9.1.v20130917-0100
org.eclipse.mylyn.tasks.ide – 3.9.1.v20130917-0100
org.eclipse.mylyn.team_feature – 3.9.1.v20130917-0100
org.eclipse.mylyn.versions – 1.1.1.v20130917-0100
org.eclipse.mylyn_feature – 3.9.1.v20130917-0100
org.eclipse.ocl – 3.1.0.v20110606-1427
org.eclipse.pde – 3.9.1.v20130911-1000
org.eclipse.platform – 4.3.1.v20130911-1000
org.eclipse.rcp – 4.3.1.v20130911-1000
org.eclipse.wb.core.feature – 1.6.1.r43x201309092314
org.eclipse.wb.core.java.feature – 1.6.1.r43x201309092318
org.eclipse.wb.core.ui.feature – 1.6.1.r43x201309092325
org.eclipse.wb.core.xml.feature – 1.6.1.r43x201309092330
org.eclipse.wb.doc.user.feature – 1.6.1.r43x201309092334
org.eclipse.wb.layout.group.feature – 1.6.1.r43x201309092345
org.eclipse.wb.rcp.SWT_AWT_support – 1.6.1.r43x201309100026
org.eclipse.wb.rcp.doc.user.feature – 1.6.1.r43x201309100019
org.eclipse.wb.rcp.feature – 1.6.1.r43x201309100008
org.eclipse.wb.swing.doc.user.feature – 1.6.1.r43x201309100012
org.eclipse.wb.swing.feature – 1.6.1.r43x201309100023
org.eclipse.wb.swt.feature – 1.6.1.r43x201309092350
org.eclipse.wb.xwt.feature – 1.6.1.r43x201309100031
org.sonatype.m2e.mavenarchiver.feature – 0.15.0.201207090125-signed-20130612210623

Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-showsplash
-launcher
C:\Other Programs\MyEclipse Professional 2014\myeclipse.exe
-name
Myeclipse
–launcher.library
C:\Other Programs\MyEclipse Professional 2014\plugins/org.eclipse.equinox.launcher.i18n.win32.win32.x86_3.2.0.v201103301700\eclipse_3215.dll
-startup
C:\Other Programs\MyEclipse Professional 2014\plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar
-install
C:\Other Programs\MyEclipse Professional 2014
-launcher
C:\Other Programs\MyEclipse Professional 2014\myeclipse.exe
-install
C:\Other Programs\MyEclipse Professional 2014
-launcher
C:\Other Programs\MyEclipse Professional 2014\myeclipse.exe
-install
C:\Other Programs\MyEclipse Professional 2014
-data
E:\workspaces-ME2014\bsf606
-launcher
C:\Other Programs\MyEclipse Professional 2014\myeclipse.exe
-install
C:\Other Programs\MyEclipse Professional 2014
-vm
C:\Other Programs\MyEclipse Professional 2014\binary/com.sun.java.jdk7.win32.x86_1.7.0.u45/jre/bin/client/jvm.dll

———————————————————————————–

There have been no changes to the Liferay SDK installations. Both the SDK and the Tomcat installations are exactly the same. In fact, the workspace in ME10 still references those SDK’s/Tomcall install and all is well with them.

I have installed the 1.6.2 version of the Liferay IDE plugin.

In this second installation (since I removed the earlier one inadvertently) I installed from the myeclipse-pro-2014-GA-offline-installer-windows.exe file downloaded from your site. When that install completed, I installed the Liferay IDE from the sourceforge site (as an archive – liferay-ide-eclipse-updatesite-1.6.2.zip ) I restarted ME after the plugin installed. I created a test portlet in a new workspace and all is well so I switched back to the workspace that had the migrated projects in it and none of those project will build or deploy. New projects are fine, existing projects that were migrated are the problem.

The only thing I noticed is that the migrated source has multiple project errors. Most notably, it can’t seem to locate the package com.liferay.util.service which would indicate a build path issue. Yet, I see no errors in the build path settings in the migrated projects. The new projects I create have a library included called “Liferay Portlet Plugin API”. In the migrated projects I do not see this library listed, I only see an entry of “com.liferay.ide.eclipse.server.plugin.container/portlet”. When I remove this entry and select the “Liferay Portlet Plugin API” library entry it returns the same reference as before – “com.liferay.ide.eclipse.server.plugin.container/portlet” rather than the Library.

Not sure what is going on. Somehow the migration is not bringing something across correctly. I will post over at the LR forum but I am going to guess that they will say it is a migration issue with ME2014 and you folks will say that it is an issue with the Liferay IDE plugin….

Meanwhile I am going to try to try a couple of more things while I wait for you folks and the LR folks to sort through the details….

Thanks,

Pete

[support-pradeep]

Pete,

After further investigation, it looks like the issue is with Liferay SDK configuration for the migrated project. The Liferay SDK configuration and Liferay 6.1 (Tomcat) libraries are missing if the project is imported normally (from File > Import > General > Existing projects into workspace). You need to import the liferay projects using File > Import > LifeRay > LifeRay project from existing source or LifeRay project from plugins SDK.

To import an existing Liferay portlet project into MyEclipse, you need to follow these steps –
> Navigate to File > Import > LifeRay > LifeRay project from existing source.
> Browse the Liferay project location from <Liferay SDK directory>/portlets folder.
> Select the Liferay Target runtime, which is Liferay Tomcat 7 and click Finish to import the existing project into MyEclipse

Alternatively, you can import your existing Liferay portlet project from Plugins SDK. You need to follow these steps –
> Navigate to File > Import > LifeRay > LifeRay project from plugins SDK
> Select the LifeRay SDK from the LifeRay plugins SDK drop down. (Configure the SDK if it is not yet configured)
> Once the SDK is selected, all the projects under the selected SDK will be listed. Select a project to be imported
> Select the Liferay Target runtime, which is Liferay Tomcat 7 and click Finish to import the existing project into MyEclipse

I suggest you to follow this LifeRay tutorial for more information on import Liferay projects.

Finally after importing the projects, you need to add the Liferay Tomcat 7 libraries to the project to remove any errors (The superclass “javax.servlet.http.HttpServlet” was not found on the Java Build Path) in the project. Right click on your LifeRay project > Build path > Add Library > User Library > Click on User libraries > Click New in the User libraries preferences window and enter a name and click Ok > Click ‘Add external jars’ and select all the jars from <Liferay tomcat dir>/lib folder > Click Ok > Select/check the user library created and click Finish > Click Ok in the properties window.

Let us know how it works for you.

[Udo Held]

Checking what our developers are doing I figured they are using the free Spring STS edition again. Asking them why, they told me that MyEclipse 2014 isn’t working with the Liferay SDK for Liferay 6.2.

We recently renewed 14 licenses and half of our developers cannot use it. If Spring STS uses a newer Sapphire XML library, why cannot Bling use the same one as well?

Please look into it soon.

Thanks
clavis_uhe

[support-pradeep]

clavis_uhe,

A bug report is already filed for this issue and our dev team is looking into it.
Sorry for the inconvenience caused.

[Pete Helgren]

I hacked around the issues after the migration by comparing the .classpath entries after the migration step and figured out that something was amiss. This is the .classpath for a project after migration:

<?xml version=”1.0″ encoding=”UTF-8″?>
<classpath>
<classpathentry kind=”src” path=”docroot/WEB-INF/src”/>
<classpathentry kind=”con” path=”org.eclipse.jst.j2ee.internal.web.container”/>
<classpathentry kind=”con” path=”org.eclipse.jst.j2ee.internal.module.container”/>
<classpathentry kind=”con” path=”com.liferay.ide.eclipse.server.plugin.container/portlet”>
<attributes>
<attribute name=”org.eclipse.jst.component.nondependency” value=””/>
</attributes>
</classpathentry>
<classpathentry kind=”con” path=”org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/JavaSE-1.6″>
<attributes>
<attribute name=”owner.project.facets” value=”java”/>
</attributes>
</classpathentry>
<classpathentry kind=”con” path=”org.eclipse.jst.server.core.container/com.liferay.ide.eclipse.server.tomcat.runtimeClasspathProvider/Liferay v6.0 CE (Tomcat 6)”>
<attributes>
<attribute name=”owner.project.facets” value=”jst.web”/>
</attributes>
</classpathentry>
<classpathentry kind=”output” path=”docroot/WEB-INF/classes”/>
</classpath>

######

And this was the .classpath for a newly created portlet project:

<?xml version=”1.0″ encoding=”UTF-8″?>
<classpath>
<classpathentry kind=”src” path=”docroot/WEB-INF/src”/>
<classpathentry kind=”con” path=”org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/Liferay v6.0 CE (Tomcat 6) JRE”>
<attributes>
<attribute name=”owner.project.facets” value=”java”/>
</attributes>
</classpathentry>
<classpathentry kind=”con” path=”org.eclipse.jst.server.core.container/com.liferay.ide.eclipse.server.tomcat.runtimeClasspathProvider/Liferay v6.0 CE (Tomcat 6)”>
<attributes>
<attribute name=”owner.project.facets” value=”jst.web”/>
</attributes>
</classpathentry>
<classpathentry kind=”con” path=”org.eclipse.jst.j2ee.internal.web.container”/>
<classpathentry kind=”con” path=”org.eclipse.jst.j2ee.internal.module.container”/>
<classpathentry kind=”con” path=”com.liferay.ide.eclipse.server.plugin.container/portlet”>
<attributes>
<attribute name=”org.eclipse.jst.component.nondependency” value=””/>
</attributes>
</classpathentry>
<classpathentry kind=”output” path=”docroot/WEB-INF/classes”/>
</classpath>

Basically I backed up and then copied the new project .classpath into the migrated project and most of the compile and deploy issues resolved.

Hacky…but so far it seems to be working OK.

[support-pradeep]

Pete,

We couldn’t find any issues after importing an existing Liferay portlet project into MyEclipse using the steps mentioned in my earlier response. Anyway glad that you got it working and thanks for posting your workaround that could help other users who are facing this issue.
Let us know if you see any issues in MyEclipse.

[Pete Helgren]

That fix wasn’t perfect and I still needed to fix some build path issues. The biggest issue here is that even if you back up your workspace, ME2014 and the LR IDE plugin makes changes to the LifeRay SDK folders where the plugin projects reside so installing ME2014 and running a migration can lead to broken projects, even if you revert back to ME10 (in my case).

So the advice is to back up the workspace AND the Liferay SDK folders before you attempt an upgrade, otherwise you could end up with undeployable projects no matter which version of ME you use.

[support-pradeep]

phelgren,

Thanks for the workaround and the suggestions which could help other users who are seeing this problem.
Let us know if you see any issues in MyEclipse.

[support-swapna]

phelgren,

LifeRay 2.0.1 IDE can now be installed to latest MyEclipse 2015 without any issues. Please update to MyEclipse 2015 Stable or MyEclipse 2015 CI 11, if you are comfortable working with a continuous integration stream.

If you are already working with MyEclipse 2015, go to Help > Check for Updates and update to the latest release.

You can also download the latest installer from here : https://www.genuitec.com/products/myeclipse/download/

Let us know if you see any issues.

[Author]

Posts