[JBoss JIRA] (JBIDE-27314) JSF Content Assist for EL not working
by Stephane Bouchet (Jira)
[ https://issues.redhat.com/browse/JBIDE-27314?page=com.atlassian.jira.plug... ]
Stephane Bouchet updated JBIDE-27314:
-------------------------------------
Fix Version/s: 4.17.0.AM1
(was: 4.16.0.Final)
> JSF Content Assist for EL not working
> -------------------------------------
>
> Key: JBIDE-27314
> URL: https://issues.redhat.com/browse/JBIDE-27314
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html-source-editing
> Affects Versions: 4.15.0.Final
> Reporter: Thomas Kernstock
> Assignee: Jeff MAURY
> Priority: Major
> Fix For: 4.17.0.AM1
>
> Attachments: image-2020-06-11-14-42-01-984.png, image-2020-06-11-14-43-41-583.png, image-2020-06-11-14-47-04-927.png, image-2020-06-11-14-50-58-420.png, image-2020-06-11-14-55-50-831.png
>
>
> Hi,
> I'm using Eclipse 2020-03 and JBoss 4.15.0. Since the last Update my content assist in XHTML files fails somehow.
> These are the installed modules:
> !image-2020-06-11-14-42-01-984.png!
> These are the content assist properties for HTML (XML is the same)
> !image-2020-06-11-14-50-58-420.png!
> These are the project natures:
> !image-2020-06-11-14-43-41-583.png!
>
> I do not get any assistence for beans like facesContext, request, etc.
>
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 8 months
[JBoss JIRA] (JBDS-4850) Installing studio from marketplace throws Exception in org.eclipse.equinox.internal.p2.reconciler.dropins.Activator.start()
by Stephane Bouchet (Jira)
[ https://issues.redhat.com/browse/JBDS-4850?page=com.atlassian.jira.plugin... ]
Stephane Bouchet commented on JBDS-4850:
----------------------------------------
seems similar to [https://bugs.eclipse.org/bugs/show_bug.cgi?id=392818]
> Installing studio from marketplace throws Exception in org.eclipse.equinox.internal.p2.reconciler.dropins.Activator.start()
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4850
> URL: https://issues.redhat.com/browse/JBDS-4850
> Project: Red Hat CodeReady Studio (devstudio)
> Issue Type: Bug
> Components: marketplace
> Affects Versions: 12.15.0.GA
> Reporter: Ondrej Dockal
> Assignee: Stephane Bouchet
> Priority: Major
> Fix For: 12.x
>
>
> {code}
> eclipse.buildId=4.16.0.I20200604-0540eclipse.buildId=4.16.0.I20200604-0540java.version=1.8.0_252java.vendor=Oracle CorporationBootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_USFramework arguments: -product org.eclipse.epp.package.jee.productCommand-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.jee.product
> org.eclipse.equinox.p2.reconciler.dropinsErrorWed Jul 15 09:21:20 CEST 2020FrameworkEvent ERROR
> org.osgi.framework.BundleException: Exception in org.eclipse.equinox.internal.p2.reconciler.dropins.Activator.start() of bundle org.eclipse.equinox.p2.reconciler.dropins. at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:864) at org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:792) at org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:1015) at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:365) at org.eclipse.osgi.container.Module.doStart(Module.java:605) at org.eclipse.osgi.container.Module.start(Module.java:468) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel$2.run(ModuleContainer.java:1845) at org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor$1$1.execute(EquinoxContainerAdaptor.java:136) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1838) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1781) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1743) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1665) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1) at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:234) at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:345)Caused by: java.lang.IllegalStateException: Profile epp.package.jee is not current. Expected timestamp 0 but was 0. at org.eclipse.equinox.internal.p2.engine.SimpleProfileRegistry.lockProfile(SimpleProfileRegistry.java:865) at org.eclipse.equinox.internal.p2.engine.Engine.perform(Engine.java:72) at org.eclipse.equinox.internal.p2.engine.Engine.perform(Engine.java:48) at org.eclipse.equinox.internal.p2.reconciler.dropins.ProfileSynchronizer.executePlan(ProfileSynchronizer.java:792) at org.eclipse.equinox.internal.p2.reconciler.dropins.ProfileSynchronizer.performAddRemove(ProfileSynchronizer.java:205) at org.eclipse.equinox.internal.p2.reconciler.dropins.ProfileSynchronizer.synchronize(ProfileSynchronizer.java:144) at org.eclipse.equinox.internal.p2.reconciler.dropins.Activator.synchronize(Activator.java:444) at org.eclipse.equinox.internal.p2.reconciler.dropins.Activator.start(Activator.java:179) at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:843) at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:1) at java.security.AccessController.doPrivileged(Native Method) at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:835) ... 14 moreRoot exception:java.lang.IllegalStateException: Profile epp.package.jee is not current. Expected timestamp 0 but was 0. at org.eclipse.equinox.internal.p2.engine.SimpleProfileRegistry.lockProfile(SimpleProfileRegistry.java:865) at org.eclipse.equinox.internal.p2.engine.Engine.perform(Engine.java:72) at org.eclipse.equinox.internal.p2.engine.Engine.perform(Engine.java:48) at org.eclipse.equinox.internal.p2.reconciler.dropins.ProfileSynchronizer.executePlan(ProfileSynchronizer.java:792) at org.eclipse.equinox.internal.p2.reconciler.dropins.ProfileSynchronizer.performAddRemove(ProfileSynchronizer.java:205) at org.eclipse.equinox.internal.p2.reconciler.dropins.ProfileSynchronizer.synchronize(ProfileSynchronizer.java:144) at org.eclipse.equinox.internal.p2.reconciler.dropins.Activator.synchronize(Activator.java:444) at org.eclipse.equinox.internal.p2.reconciler.dropins.Activator.start(Activator.java:179) at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:843) at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:1) at java.security.AccessController.doPrivileged(Native Method) at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:835) at org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:792) at org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:1015) at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:365) at org.eclipse.osgi.container.Module.doStart(Module.java:605) at org.eclipse.osgi.container.Module.start(Module.java:468) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel$2.run(ModuleContainer.java:1845) at org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor$1$1.execute(EquinoxContainerAdaptor.java:136) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1838) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1781) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1743) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1665) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1) at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:234) at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:345)
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 8 months
[JBoss JIRA] (JBIDE-27424) Server ITests: VerifyJREFlagsTest is failing on interop infra
by Josef Kopriva (Jira)
Josef Kopriva created JBIDE-27424:
-------------------------------------
Summary: Server ITests: VerifyJREFlagsTest is failing on interop infra
Key: JBIDE-27424
URL: https://issues.redhat.com/browse/JBIDE-27424
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: integration-tests, server
Affects Versions: 4.17.0.AM1
Reporter: Josef Kopriva
Assignee: Robert Stryker
ITest fails with error:
java.lang.AssertionError: Java 8 binary does not exist
at org.jboss.tools.as.management.itests.VerifyJREFlagsTest.testJavaHomesSet(VerifyJREFlagsTest.java:24)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 8 months
[JBoss JIRA] (JBIDE-27262) Wildfly 19 not recognized as JEE 8 compliant in eclipse
by Mounir Dabbabi (Jira)
[ https://issues.redhat.com/browse/JBIDE-27262?page=com.atlassian.jira.plug... ]
Mounir Dabbabi commented on JBIDE-27262:
----------------------------------------
Hi, this issue still not fixed in
Eclipse IDE for Enterprise Java Developers (includes Incubating components)
Version: 2020-06 (4.16.0)
Build id: 20200615-1200
Regards
> Wildfly 19 not recognized as JEE 8 compliant in eclipse
> -------------------------------------------------------
>
> Key: JBIDE-27262
> URL: https://issues.redhat.com/browse/JBIDE-27262
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.15.0.Final
> Reporter: Juan Antonio Viñuales Martínez
> Assignee: Robert Stryker
> Priority: Major
> Fix For: 4.16.0.AM1
>
> Attachments: error1.png, error2.png
>
>
> In Eclipse (2020-03 version), when creating a new Enterprise Application Project, if you select WildFly 19 as target runtime, the JEE version only goes up to 7. However, if you select WildFly 18 as target runtime, JEE version goes up to 8, as expected.
> Alternatively, if you have already a JEE 8 project, and then you try to add it to an existing WildFly 19 server, you receive the following message:
> The server does not support version 8.0 of the J2EE Enterprise application specification
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 8 months