Foros de discusión

No Liferay Server types after upgrade

David Weitzel, modificado hace 6 años.

No Liferay Server types after upgrade

Junior Member Mensajes: 65 Fecha de incorporación: 7/10/15 Mensajes recientes
I recently upgraded to LIferay IDE 3.1.2.20170901 and my servers that I have defined are no longer recognized as such (they appeared in the Servers panel of the Liferay IDE perspective but do not have start/stop options. If I try to create a new server there is no Liferay list of available servers
Is this due to finger trouble doing the eclipse / IDE updates, seems every time I do something in eclipse configuration/update something breaks.
Running:
Version: Neon.3 Release (4.6.3)
Build id: 20170314-1500
thumbnail
Gregory Amerson, modificado hace 6 años.

RE: No Liferay Server types after upgrade

Liferay Legend Mensajes: 1123 Fecha de incorporación: 16/02/10 Mensajes recientes
Hey Dave,

That should definitely not be happening. What version were you upgrading from? It sounds like there could be some other installation problem. If there is no 'liferay' server option, it sounds like something is starting.

Can you go to the OSGi Host Console and type
lb -s com.liferay.ide
and print out what returns here?
David Weitzel, modificado hace 6 años.

RE: No Liferay Server types after upgrade

Junior Member Mensajes: 65 Fecha de incorporación: 7/10/15 Mensajes recientes
WARNING: This console is connected to the current running instance of Eclipse!
osgi> lb -s com.liferay.ide
START LEVEL 6
ID|State |Level|Symbolic name
1866|Installed | 4|com.liferay.ide.alloy.core (3.1.2.201709011126-ga3)
1867|Installed | 4|com.liferay.ide.alloy.ui (3.1.2.201709011126-ga3)
1868|Installed | 4|com.liferay.ide.bndtools.core (3.1.2.201709011126-ga3)
1869|Starting | 4|com.liferay.ide.core (3.1.2.201709011126-ga3)
1870|Installed | 4|com.liferay.ide.gradle.core (3.1.2.201709011126-ga3)
1871|Installed | 4|com.liferay.ide.gradle.ui (3.1.2.201709011126-ga3)
1872|Installed | 4|com.liferay.ide.hook.core (3.1.2.201709011126-ga3)
1873|Installed | 4|com.liferay.ide.hook.ui (3.1.2.201709011126-ga3)
1874|Installed | 4|com.liferay.ide.kaleo.core (3.1.2.201709011126-ga3)
1875|Installed | 4|com.liferay.ide.kaleo.ui (3.1.2.201709011126-ga3)
1876|Installed | 4|com.liferay.ide.layouttpl.core (3.1.2.201709011126-ga3)
1877|Installed | 4|com.liferay.ide.layouttpl.ui (3.1.2.201709011126-ga3)
1878|Installed | 4|com.liferay.ide.maven.core (3.1.2.201709011126-ga3)
1879|Installed | 4|com.liferay.ide.maven.ui (3.1.2.201709011126-ga3)
1880|Installed | 4|com.liferay.ide.portlet.core (3.1.2.201709011126-ga3)
1881|Installed | 4|com.liferay.ide.portlet.ui (3.1.2.201709011126-ga3)
1882|Installed | 4|com.liferay.ide.portlet.vaadin.core (3.1.2.201709011126-ga3)
1883|Installed | 4|com.liferay.ide.portlet.vaadin.ui (3.1.2.201709011126-ga3)
1884|Installed | 4|com.liferay.ide.project.core (3.1.2.201709011126-ga3)
1885|Installed | 4|com.liferay.ide.project.ui (3.1.2.201709011126-ga3)
1886|Starting | 4|com.liferay.ide.scripting.core (3.1.2.201709011126-ga3)
1887|Starting | 4|com.liferay.ide.sdk.core (3.1.2.201709011126-ga3)
1888|Installed | 4|com.liferay.ide.server.core (3.1.2.201709011126-ga3)
1889|Installed | 4|com.liferay.ide.server.tomcat.core (3.1.2.201709011126-ga3)
1890|Installed | 4|com.liferay.ide.server.tomcat.ui (3.1.2.201709011126-ga3)
1891|Installed | 4|com.liferay.ide.server.ui (3.1.2.201709011126-ga3)
1892|Installed | 4|com.liferay.ide.service.core (3.1.2.201709011126-ga3)
1893|Installed | 4|com.liferay.ide.service.ui (3.1.2.201709011126-ga3)
1894|Installed | 4|com.liferay.ide.studio.ui (3.1.2.201709011126-ga3)
1895|Installed | 4|com.liferay.ide.theme.core (3.1.2.201709011126-ga3)
1896|Installed | 4|com.liferay.ide.ui (3.1.2.201709011126-ga3)
1897|Active | 4|com.liferay.ide.ui.notifications (3.1.2.201709011126-ga3)
1898|Installed | 4|com.liferay.ide.ui.snippets (3.1.2.201709011126-ga3)
1899|Installed | 4|com.liferay.ide.xml.search.ui (3.1.2.201709011126-ga3)
osgi>
thumbnail
Gregory Amerson, modificado hace 6 años.

RE: No Liferay Server types after upgrade

Liferay Legend Mensajes: 1123 Fecha de incorporación: 16/02/10 Mensajes recientes
Yeah this appears to be an installation issue. None of the liferay ide plugins have started. Can you run a 'diag' command for one of those bundles that are set to 'installed' instead of 'STARTING' ? Hopefully it will show what is going on.
David Weitzel, modificado hace 6 años.

RE: No Liferay Server types after upgrade

Junior Member Mensajes: 65 Fecha de incorporación: 7/10/15 Mensajes recientes
Hre is diag on the porject bundle:

diag 1884
com.liferay.ide.project.core [1884]
Unresolved requirement: Require-Bundle: com.liferay.ide.server.core; visibility:="reexport"
-> Bundle-SymbolicName: com.liferay.ide.server.core; bundle-version="3.1.2.201709011126-ga3"; singleton:="true"
com.liferay.ide.server.core [1888]
Bundle was not resolved because of a uses contraint violation.
org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource com.liferay.ide.server.core [osgi.identity; type="osgi.bundle"; versionemoticonersion="3.1.2.201709011126-ga3"; osgi.identity="com.liferay.ide.server.core"; singleton:="true"] because it is exposed to package 'aQute.bnd.util.dto' from resources biz.aQute.remote.api [osgi.identity; type="osgi.bundle"; versionemoticonersion="3.4.0.201707032202-SNAPSHOT"; osgi.identity="biz.aQute.remote.api"] and biz.aQute.bndlib [osgi.identity; type="osgi.bundle"; versionemoticonersion="3.5.0.201709291849"; osgi.identity="biz.aQute.bndlib"] via two dependency chains.

Chain 1:
com.liferay.ide.server.core [osgi.identity; type="osgi.bundle"; versionemoticonersion="3.1.2.201709011126-ga3"; osgi.identity="com.liferay.ide.server.core"; singleton:="true"]
require: (osgi.wiring.bundle=biz.aQute.remote.api)
|
provide: osgi.wiring.bundle: biz.aQute.remote.api
biz.aQute.remote.api [osgi.identity; type="osgi.bundle"; versionemoticonersion="3.4.0.201707032202-SNAPSHOT"; osgi.identity="biz.aQute.remote.api"]

Chain 2:
com.liferay.ide.server.core [osgi.identity; type="osgi.bundle"; versionemoticonersion="3.1.2.201709011126-ga3"; osgi.identity="com.liferay.ide.server.core"; singleton:="true"]
require: (&(osgi.wiring.bundle=biz.aQute.repository)(bundle-version>=3.1.0))
|
provide: osgi.wiring.bundle; bundle-versionemoticonersion="3.5.0.201709291849"; osgi.wiring.bundle="biz.aQute.repository"
biz.aQute.repository [osgi.identity; type="osgi.bundle"; versionemoticonersion="3.5.0.201709291849"; osgi.identity="biz.aQute.repository"]
import: (&(osgi.wiring.package=aQute.bnd.service)(&(version>=4.3.0)(!(version>=5.0.0))))
|
export: osgi.wiring.package: aQute.bnd.service; uses:=aQute.bnd.util.dto
export: osgi.wiring.package=aQute.bnd.util.dto
biz.aQute.bndlib [osgi.identity; type="osgi.bundle"; versionemoticonersion="3.5.0.201709291849"; osgi.identity="biz.aQute.bndlib"] Bundle was not resolved because of a uses contraint violation.
org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource com.liferay.ide.server.core [osgi.identity; type="osgi.bundle"; versionemoticonersion="3.1.2.201709011126-ga3"; osgi.identity="com.liferay.ide.server.core"; singleton:="true"] because it is exposed to package 'aQute.bnd.util.dto' from resources biz.aQute.remote.api [osgi.identity; type="osgi.bundle"; versionemoticonersion="3.4.0.201707032202-SNAPSHOT"; osgi.identity="biz.aQute.remote.api"] and biz.aQute.bndlib [osgi.identity; type="osgi.bundle"; versionemoticonersion="3.5.0.201709291849"; osgi.identity="biz.aQute.bndlib"] via two dependency chains.

Chain 1:
com.liferay.ide.server.core [osgi.identity; type="osgi.bundle"; versionemoticonersion="3.1.2.201709011126-ga3"; osgi.identity="com.liferay.ide.server.core"; singleton:="true"]
require: (osgi.wiring.bundle=biz.aQute.remote.api)
|
provide: osgi.wiring.bundle: biz.aQute.remote.api
biz.aQute.remote.api [osgi.identity; type="osgi.bundle"; versionemoticonersion="3.4.0.201707032202-SNAPSHOT"; osgi.identity="biz.aQute.remote.api"]

Chain 2:
com.liferay.ide.server.core [osgi.identity; type="osgi.bundle"; versionemoticonersion="3.1.2.201709011126-ga3"; osgi.identity="com.liferay.ide.server.core"; singleton:="true"]
require: (&(osgi.wiring.bundle=biz.aQute.repository)(bundle-version>=3.1.0))
|
provide: osgi.wiring.bundle; bundle-versionemoticonersion="3.5.0.201709291849"; osgi.wiring.bundle="biz.aQute.repository"
biz.aQute.repository [osgi.identity; type="osgi.bundle"; versionemoticonersion="3.5.0.201709291849"; osgi.identity="biz.aQute.repository"]
import: (&(osgi.wiring.package=aQute.bnd.service)(&(version>=4.3.0)(!(version>=5.0.0))))
|
export: osgi.wiring.package: aQute.bnd.service; uses:=aQute.bnd.util.dto
export: osgi.wiring.package=aQute.bnd.util.dto
biz.aQute.bndlib [osgi.identity; type="osgi.bundle"; versionemoticonersion="3.5.0.201709291849"; osgi.identity="biz.aQute.bndlib"]
thumbnail
Andy Wu, modificado hace 6 años.

RE: No Liferay Server types after upgrade

Regular Member Mensajes: 195 Fecha de incorporación: 5/05/15 Mensajes recientes
Hi David ,
your issue seems interesting , can you give us more detail about how to reproduc it ?
I mean , share your OS type and version and java version and eclipse version and ide original version and upgraded version.

Thanks in advance.
David Weitzel, modificado hace 6 años.

RE: No Liferay Server types after upgrade

Junior Member Mensajes: 65 Fecha de incorporación: 7/10/15 Mensajes recientes
Looking at the eclipse installation details on my windows PC _ I am guessing the macBook at home is similar
It is eclipse Neon original 4.6.2
I installed Liferay IDE 3.0.1.201606151031-ga2 in February
upgraded to Eclipse IDE for Java Developers 4.6.3.20170314-1500 in March
upgraded to Liferay IDE 3.1.0.201705141336-b1 in June
upgraded to Liferay IDE Enterprise 3.1.1.201708030520-ga2 in August
and then to Liferay IDE 3.1.2.201709011126-ga3 when the problems appeared

attached is the eclipse configuration

Archivos adjuntos:

thumbnail
Andy Wu, modificado hace 6 años.

RE: No Liferay Server types after upgrade

Regular Member Mensajes: 195 Fecha de incorporación: 5/05/15 Mensajes recientes
Hi David,
Sorry , I can't reproduce your problem .
My suggestion is just download the eclispe bundled with latest ide.
We will let you know if any updates.
David Weitzel, modificado hace 6 años.

RE: No Liferay Server types after upgrade

Junior Member Mensajes: 65 Fecha de incorporación: 7/10/15 Mensajes recientes
I have the same issue on my MacBook installation/upgrade. Also I get message about file associations when I boot up and wen I go to that page they are all shown as "(locked)" not sure if they normally are locked .
David Weitzel, modificado hace 6 años.

RE: No Liferay Server types after upgrade

Junior Member Mensajes: 65 Fecha de incorporación: 7/10/15 Mensajes recientes
previous IDE version was 3.1.1.201708030520