[JBoss JIRA] (JBIDE-24873) Add management itests to eap jbds compatibility jenkins job
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24873?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-24873:
-------------------------------------
So... I've tried this locally:
mvn clean install -Djbosstools.test.jre.8=/home/rob/apps/java/java8/jdk1.8.0_05/ -Djbosstools.test.singleruntime.location=/home/rob/apps/jboss/unzipped/jboss-eap-7.1 -Djbosstools.test.jboss.home.eap.7.1=/home/rob/apps/jboss/unzipped/jboss-eap-7.1 -DskipPrivateRequirements=false
It passes with 17 tests run and 0 fails. I'll keep investigating but I'm not seeing anything too weird on my end.
List of jars in my wf11 plugin (used to talk to eap7.1):
jboss-dmr-1.4.1.Final.jar
jboss-logging-3.3.1.Final.jar
jboss-remoting-5.0.0.CR5.jar
jboss-threads-2.2.1.Final.jar
wildfly-client-config-1.0.0.CR3.jar
wildfly-common-1.2.0.CR1.jar
wildfly-controller-client-3.0.0.Beta30.jar
wildfly-elytron-1.1.0.CR4.jar
wildfly-protocol-3.0.0.Beta30.jar
xnio-api-3.5.0.CR2.jar
xnio-nio-3.5.0.CR2.jar
List of jars in actual EAP 7.1:
jboss-dmr-1.4.1.Final-redhat-1.jar
jboss-logging-3.3.1.Final-redhat-1.jar
jboss-remoting-5.0.0.Final-redhat-1.jar
jboss-threads-2.2.1.Final-redhat-1.jar
wildfly-client-config-1.0.0.Final-redhat-1.jar
wildfly-common-1.2.0.Final-redhat-1.jar
wildfly-controller-client-3.0.1.Final-redhat-1.jar
wildfly-elytron-tool.jar
wildfly-elytron-integration-3.0.1.Final-redhat-1.jar
wildfly-elytron-1.1.1.Final-redhat-1.jar
wildfly-protocol-3.0.1.Final-redhat-1.jar
xnio-api-3.5.1.Final-redhat-1.jar
xnio-nio-3.5.1.Final-redhat-1.jar
> Add management itests to eap jbds compatibility jenkins job
> -----------------------------------------------------------
>
> Key: JBIDE-24873
> URL: https://issues.jboss.org/browse/JBIDE-24873
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 4.5.0.Final
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.5.1.AM2
>
>
> The EAP team would like us to add this test
> org.jboss.tools.as.management.itests
> to their compatibility job:
> https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP7/view/EAP...
> details here: EAP7-194
> The test to be added is run here:
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> Cc: [~rob.stryker]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24573) Issue deploying EAR project from eclipse to Wildfly using JBoss Tools Plugin
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24573?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-24573.
---------------------------------
Resolution: Done
Well... it looks like Fred accidntally deleted your original project, because the two remaining zip files seem to be identical.
I guess I'll have to close this and you can re-open it if Fred's proposed fixes didn't fix your issue?
Good luck!
> Issue deploying EAR project from eclipse to Wildfly using JBoss Tools Plugin
> ----------------------------------------------------------------------------
>
> Key: JBIDE-24573
> URL: https://issues.jboss.org/browse/JBIDE-24573
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven, server, upstream
> Affects Versions: 4.4.4.Final
> Environment: windows 7 eclipse neon maven
> Reporter: stefano canu
> Assignee: Rob Stryker
> Fix For: 4.5.1.AM2
>
> Attachments: fixed-pfi-test.zip, pfi-test.zip, pom.xml
>
>
> I 'm tryng to deploy to wildfly 10 an ear project (maven) composed by one war and one jar (ejb) project, but the ear deployed with eclipse wildfly connector is different form one present in the target foleder, library in web-inf lib is missing.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24763) Some server itests are failing on Jenkins
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24763?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-24763:
------------------------------------
Latest params for the job [1] for 4 OSes:
[1] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/server.i...
{code}
16:05:51 [win81] $ cmd.exe /C "\mnt\hudson_workspace\tools\hudson.tasks.Maven_MavenInstallation\maven-3.3.9\bin\mvn.cmd -s C:\Users\jbossqa\AppData\Local\Temp\settings7229513778735293013.xml -Djdk=openjdk-1.8 -Dlabel_exp=win81 -Ddownload.cache.directory=${HUDSON_STATIC_ENV}/devstudio/download-cache -Dsurefire.timeout=10000 "-DJOB_NAME=server.it.weekly/jdk=openjdk-1.8,label_exp=win81" -DBUILD_NUMBER=24 -DskipPrivateRequirements=false
-Djbosstools.test.jre.8=T:\opt\windows\amd64\jdk1.8.0_last -Dsurefire.itests.timeout=10000
-Djbosstools.test.jre.7=T:\opt\windows\amd64\jdk1.7.0_last
-Djbosstools.test.jre.6=T:\opt\windows\amd64\jdk1.7.0_last
-Djbosstools.test.jre.5=T:\opt\windows\amd64\jdk1.7.0_last
-DskipBaselineComparison=true -Dmaven.test.error.ignore=true -Dmaven.test.failure.ignore=true clean install -B -U -fae -e -P "hudson,pack200,unified.target,maximum"
-DjgitDirtyWorkingTree=warning && exit %%ERRORLEVEL%%"
16:05:48 [win10] $ cmd.exe /C "\mnt\hudson_workspace\tools\hudson.tasks.Maven_MavenInstallation\maven-3.3.9\bin\mvn.cmd -s C:\Users\jbossqa\AppData\Local\Temp\settings8339429706904285132.xml -Djdk=openjdk-1.8 -Dlabel_exp=win10 -Ddownload.cache.directory=${HUDSON_STATIC_ENV}/devstudio/download-cache -Dsurefire.timeout=10000 "-DJOB_NAME=server.it.weekly/jdk=openjdk-1.8,label_exp=win10" -DBUILD_NUMBER=24 -DskipPrivateRequirements=false
-Djbosstools.test.jre.8=T:\opt\windows\amd64\jdk1.8.0_last -Dsurefire.itests.timeout=10000
-Djbosstools.test.jre.7=T:\opt\windows\amd64\jdk1.7.0_last
-Djbosstools.test.jre.6=T:\opt\windows\amd64\jdk1.7.0_last
-Djbosstools.test.jre.5=T:\opt\windows\amd64\jdk1.7.0_last
-DskipBaselineComparison=true -Dmaven.test.error.ignore=true -Dmaven.test.failure.ignore=true clean install -B -U -fae -e -P "hudson,pack200,unified.target,maximum"
-DjgitDirtyWorkingTree=warning && exit %%ERRORLEVEL%%"
16:05:48 [rhel7] $ /mnt/hudson_workspace/tools/hudson.tasks.Maven_MavenInstallation/maven-3.3.9/bin/mvn -s /tmp/settings2086504014812240990.xml -Djdk=openjdk-1.8 -Dlabel_exp=rhel7 -Ddownload.cache.directory=/home/hudson/static_build_env/devstudio/download-cache -Dsurefire.timeout=10000 -DJOB_NAME=server.it.weekly/jdk=openjdk-1.8,label_exp=rhel7 -DBUILD_NUMBER=24 -DskipPrivateRequirements=false
-Djbosstools.test.jre.8=/qa/tools/opt/x86_64/jdk1.8.0_last -Dsurefire.itests.timeout=10000
-Djbosstools.test.jre.7=/qa/tools/opt/x86_64/jdk1.7.0_last
-Djbosstools.test.jre.6=/qa/tools/opt/x86_64/jdk1.6.0_last
-Djbosstools.test.jre.5=/qa/tools/opt/x86_64/jdk1.5.0_last
-DskipBaselineComparison=true -Dmaven.test.error.ignore=true -Dmaven.test.failure.ignore=true clean install -B -U -fae -e -P hudson,pack200,unified.target,maximum
-DjgitDirtyWorkingTree=warning
16:05:46 [macosx] $ /jenkins/tools/hudson.tasks.Maven_MavenInstallation/maven-3.3.9/bin/mvn -s /var/folders/tp/hcfshtz152n2t8y4jfl08w140000gp/T/settings6780477723089804684.xml -Djdk=jdk1.8 -Dlabel_exp=macosx -Ddownload.cache.directory=${HUDSON_STATIC_ENV}/devstudio/download-cache -Dsurefire.timeout=10000 -DJOB_NAME=server.it.weekly/jdk=jdk1.8,label_exp=macosx -DBUILD_NUMBER=24 -DskipPrivateRequirements=false
-Djbosstools.test.jre.8=/qa/tools/opt/osx/jdk1.8.0_last -Dsurefire.itests.timeout=10000
-Djbosstools.test.jre.7=/qa/tools/opt/osx/jdk1.7.0_last
-Djbosstools.test.jre.6=/qa/tools/opt/osx/jdk1.8.0_last
-Djbosstools.test.jre.5=/qa/tools/opt/osx/jdk1.8.0_last
-DskipBaselineComparison=true -Dmaven.test.error.ignore=true -Dmaven.test.failure.ignore=true clean install -B -U -fae -e -P hudson,pack200,unified.target,maximum
-DjgitDirtyWorkingTree=warning
{code}
So... looks like none of the tests are actually using openjdk right now for the jre.* parameters, even if the BUILDS are running w/ openJDK 8
> Some server itests are failing on Jenkins
> -----------------------------------------
>
> Key: JBIDE-24763
> URL: https://issues.jboss.org/browse/JBIDE-24763
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.5.0.AM2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.5.1.AM2
>
>
> Here's the job:
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> Currently we got around 30 failures:
> {code}
> All Failed Tests
> Test Name
> Duration
> Age
> org.jboss.tools.as.itests.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[1] 5.3 sec 1
> org.jboss.tools.as.management.itests.AS7ManagerIntegrationTest.canGetServerState[7] 76 ms 1
> org.jboss.tools.as.ui.bot.itests.parametized.server.RuntimeDetectionDuplicatesTest.duplicateRuntimes default [0] 17 sec 1
> org.jboss.tools.as.itests.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[4] 1.7 sec 2
> org.jboss.tools.as.itests.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[4] 5.3 sec 2
> org.jboss.tools.as.itests.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[1] 2.3 sec 3
> org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[0] 4.4 sec 6
> org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[1] 2.1 sec 6
> org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[2] 2.1 sec 6
> org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[3] 2.2 sec 6
> org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[4] 2.1 sec 6
> org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[5] 2.1 sec 6
> org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[6] 2.1 sec 6
> org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[7] 2.3 sec 6
> org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[8] 2 sec 6
> org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[9] 2.1 sec 6
> org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[10] 2.1 sec 6
> org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[11] 2 sec 6
> org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[12] 2 sec 6
> org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[13] 2 sec 6
> org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[14] 2 sec 6
> org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[15] 2.1 sec 6
> org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[16] 2 sec 6
> org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[17] 2 sec 6
> org.jboss.tools.as.itests.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[0] 1.7 sec 6
> org.jboss.tools.as.ui.bot.itests.parametized.server.ServerRuntimesTest.operateDeploy default [0] 1 min 49 sec 6
> org.jboss.tools.as.ui.bot.itests.parametized.server.ServerRuntimesTest.operateDeploy default [1] 1 min 43 sec 6
> org.jboss.tools.wtp.runtimes.tomcat.itests.ServerUtilTest.testUniqueServerName 2.6 sec 6
> org.jboss.tools.wtp.runtimes.tomcat.itests.TomcatDetectionTest.testTomcatDetection 0.13 sec 6
> org.jboss.tools.as.itests.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[2] 1.7 sec 7
> {code}
> Nick already shared some details in JBIDE-22799
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24886) deprecate JDK5-dependent tests or enable a way to skip them on OSX (as no JDK5 is available there)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24886?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-24886:
------------------------------------
Seems that running the JDK5 and JDK6 tests on OSX using these:
{code}
-Djbosstools.test.jre.8=/qa/tools/opt/osx/jdk1.8.0_last
-Djbosstools.test.jre.7=/qa/tools/opt/osx/jdk1.7.0_last
-Djbosstools.test.jre.6=/qa/tools/opt/osx/jdk1.8.0_last
-Djbosstools.test.jre.5=/qa/tools/opt/osx/jdk1.8.0_last {code}
... results in 4153 successful tests (with 2 skipped), and a green ball:
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/server.i...
So maybe we don't actually need to remove/deprecate the tests, if they run w/ JDK8?
> deprecate JDK5-dependent tests or enable a way to skip them on OSX (as no JDK5 is available there)
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24886
> URL: https://issues.jboss.org/browse/JBIDE-24886
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.5.1.AM1
> Reporter: Nick Boldt
> Assignee: Rob Stryker
> Fix For: 4.5.1.AM2
>
>
> In searching for */JRE_5_HOME\|jre.5\|jre5\|jdk5\|jdk.5/*, I've only found TWO files which make use of the JDK5/JRE5 constants, so this might be fairly simple.
> {code:title=as/plugins/org.jboss.ide.eclipse.as.wtp.core/src/org/jboss/ide/eclipse/as/core/util/IJBossRuntimeResourceConstants.java}
> 63: public static final String AOP_JDK5_DEPLOYER = "jboss-aop-jdk50.deployer"; //$NON-NLS-1$
> 65: public static final String JBOSS_AOP_JDK5_JAR = "jboss-aop-jdk50.jar"; //$NON-NLS-1$
> 93: public static final String JBOSS_ASPECT_LIBRARY_JDK5_0 = "jboss-aspect-library-jdk50.jar"; //$NON-NLS-1$
> {code}
> {code:title=as/tests/org.jboss.tools.as.test.core/src/org/jboss/tools/as/test/core/TestConstants.java}
> 45: public static final String JRE_5_HOME = System.getProperty("jbosstools.test.jre.5", "C:\\apps\\java\\jre5.0\\");
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24953) [jst] Code completion fails with Unhandled event loop exception
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24953?page=com.atlassian.jira.plugi... ]
Nick Boldt reassigned JBIDE-24953:
----------------------------------
Assignee: Jeff MAURY
> [jst] Code completion fails with Unhandled event loop exception
> ---------------------------------------------------------------
>
> Key: JBIDE-24953
> URL: https://issues.jboss.org/browse/JBIDE-24953
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jst
> Affects Versions: 4.4.4.Final
> Reporter: Nick Boldt
> Assignee: Jeff MAURY
> Fix For: 4.5.x
>
>
> In BZ 520211, s3lvatico(a)gmail.com reported:
> {quote}
> What steps will reproduce the problem?
> 1. While working on a maven project, define a composite jsf component in another maven project (inside the same workspace)
> 2. While authoring a new jsf (xhtml) page, use the newly created component
> 3. Activate the code completion feature (CTRL-space) inside the component's tag OR in any other jsf tag.
> + jboss tools 4.4.4
> {code}
> -- Error Details --
> Date: Wed Jul 26 15:08:46 CEST 2017
> Message: Unhandled event loop exception
> Severity: Error
> Product: Eclipse 4.6.3.20170314-1500 (org.eclipse.epp.package.jee.product)
> Plugin: org.eclipse.ui
> Session Data:
> eclipse.buildId=4.6.3.M20170301-0400
> java.version=1.8.0_121
> java.vendor=Oracle Corporation
> BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
> Framework arguments: -product org.eclipse.epp.package.jee.product
> Command-line arguments: -os win32 -ws win32 -arch x86_64 -product org.eclipse.epp.package.jee.product -data C:\dev\eclipse\jee.neon.3.3\ws0 -clean
> Exception Stack Trace:
> java.lang.StackOverflowError
> at org.eclipse.wst.xml.core.internal.catalog.Catalog$InternalResolver.resolveRewrite(Catalog.java:303)
> at org.eclipse.wst.xml.core.internal.catalog.Catalog$InternalResolver.resolveURI(Catalog.java:368)
> at org.eclipse.wst.xml.core.internal.catalog.Catalog.resolveURI(Catalog.java:759)
> at org.eclipse.wst.xml.core.internal.catalog.Catalog.resolveSubordinateCatalogs(Catalog.java:736)
> at org.eclipse.wst.xml.core.internal.catalog.Catalog$InternalResolver.resolveURI(Catalog.java:380)
> at org.eclipse.wst.xml.core.internal.catalog.Catalog.resolveURI(Catalog.java:759)
> at org.jboss.tools.jst.web.kb.taglib.TagLibraryManager.getStaticTLD(TagLibraryManager.java:92)
> at org.jboss.tools.jst.web.kb.internal.StaticLibraries.getLibraries(StaticLibraries.java:44)
> at org.jboss.tools.jst.web.kb.internal.KbProject.getTagLibraries(KbProject.java:135)
> at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getCompositeLibraries(FaceletTagLibrary.java:90)
> at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:128)
> at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
> at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
> at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
> at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
> at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
> at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
> at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
> at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
> at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
> at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
> at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
> at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
> at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
> at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
> at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
> at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
> at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
> at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
> at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
> at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
> at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
> at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
> at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
> at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
> [... the stack trace goes on and on...]{code}{quote}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24953) [jst] Code completion fails with Unhandled event loop exception
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24953?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-24953:
-------------------------------
Fix Version/s: 4.5.x
> [jst] Code completion fails with Unhandled event loop exception
> ---------------------------------------------------------------
>
> Key: JBIDE-24953
> URL: https://issues.jboss.org/browse/JBIDE-24953
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jst
> Affects Versions: 4.4.4.Final
> Reporter: Nick Boldt
> Assignee: Jeff MAURY
> Fix For: 4.5.x
>
>
> In BZ 520211, s3lvatico(a)gmail.com reported:
> {quote}
> What steps will reproduce the problem?
> 1. While working on a maven project, define a composite jsf component in another maven project (inside the same workspace)
> 2. While authoring a new jsf (xhtml) page, use the newly created component
> 3. Activate the code completion feature (CTRL-space) inside the component's tag OR in any other jsf tag.
> + jboss tools 4.4.4
> {code}
> -- Error Details --
> Date: Wed Jul 26 15:08:46 CEST 2017
> Message: Unhandled event loop exception
> Severity: Error
> Product: Eclipse 4.6.3.20170314-1500 (org.eclipse.epp.package.jee.product)
> Plugin: org.eclipse.ui
> Session Data:
> eclipse.buildId=4.6.3.M20170301-0400
> java.version=1.8.0_121
> java.vendor=Oracle Corporation
> BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
> Framework arguments: -product org.eclipse.epp.package.jee.product
> Command-line arguments: -os win32 -ws win32 -arch x86_64 -product org.eclipse.epp.package.jee.product -data C:\dev\eclipse\jee.neon.3.3\ws0 -clean
> Exception Stack Trace:
> java.lang.StackOverflowError
> at org.eclipse.wst.xml.core.internal.catalog.Catalog$InternalResolver.resolveRewrite(Catalog.java:303)
> at org.eclipse.wst.xml.core.internal.catalog.Catalog$InternalResolver.resolveURI(Catalog.java:368)
> at org.eclipse.wst.xml.core.internal.catalog.Catalog.resolveURI(Catalog.java:759)
> at org.eclipse.wst.xml.core.internal.catalog.Catalog.resolveSubordinateCatalogs(Catalog.java:736)
> at org.eclipse.wst.xml.core.internal.catalog.Catalog$InternalResolver.resolveURI(Catalog.java:380)
> at org.eclipse.wst.xml.core.internal.catalog.Catalog.resolveURI(Catalog.java:759)
> at org.jboss.tools.jst.web.kb.taglib.TagLibraryManager.getStaticTLD(TagLibraryManager.java:92)
> at org.jboss.tools.jst.web.kb.internal.StaticLibraries.getLibraries(StaticLibraries.java:44)
> at org.jboss.tools.jst.web.kb.internal.KbProject.getTagLibraries(KbProject.java:135)
> at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getCompositeLibraries(FaceletTagLibrary.java:90)
> at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:128)
> at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
> at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
> at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
> at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
> at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
> at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
> at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
> at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
> at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
> at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
> at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
> at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
> at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
> at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
> at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
> at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
> at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
> at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
> at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
> at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
> at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
> at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
> at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
> at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
> [... the stack trace goes on and on...]{code}{quote}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24953) [jst] Code completion fails with Unhandled event loop exception
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-24953:
----------------------------------
Summary: [jst] Code completion fails with Unhandled event loop exception
Key: JBIDE-24953
URL: https://issues.jboss.org/browse/JBIDE-24953
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jst
Affects Versions: 4.4.4.Final
Reporter: Nick Boldt
In BZ 520211, s3lvatico(a)gmail.com reported:
{quote}
What steps will reproduce the problem?
1. While working on a maven project, define a composite jsf component in another maven project (inside the same workspace)
2. While authoring a new jsf (xhtml) page, use the newly created component
3. Activate the code completion feature (CTRL-space) inside the component's tag OR in any other jsf tag.
+ jboss tools 4.4.4
{code}
-- Error Details --
Date: Wed Jul 26 15:08:46 CEST 2017
Message: Unhandled event loop exception
Severity: Error
Product: Eclipse 4.6.3.20170314-1500 (org.eclipse.epp.package.jee.product)
Plugin: org.eclipse.ui
Session Data:
eclipse.buildId=4.6.3.M20170301-0400
java.version=1.8.0_121
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
Framework arguments: -product org.eclipse.epp.package.jee.product
Command-line arguments: -os win32 -ws win32 -arch x86_64 -product org.eclipse.epp.package.jee.product -data C:\dev\eclipse\jee.neon.3.3\ws0 -clean
Exception Stack Trace:
java.lang.StackOverflowError
at org.eclipse.wst.xml.core.internal.catalog.Catalog$InternalResolver.resolveRewrite(Catalog.java:303)
at org.eclipse.wst.xml.core.internal.catalog.Catalog$InternalResolver.resolveURI(Catalog.java:368)
at org.eclipse.wst.xml.core.internal.catalog.Catalog.resolveURI(Catalog.java:759)
at org.eclipse.wst.xml.core.internal.catalog.Catalog.resolveSubordinateCatalogs(Catalog.java:736)
at org.eclipse.wst.xml.core.internal.catalog.Catalog$InternalResolver.resolveURI(Catalog.java:380)
at org.eclipse.wst.xml.core.internal.catalog.Catalog.resolveURI(Catalog.java:759)
at org.jboss.tools.jst.web.kb.taglib.TagLibraryManager.getStaticTLD(TagLibraryManager.java:92)
at org.jboss.tools.jst.web.kb.internal.StaticLibraries.getLibraries(StaticLibraries.java:44)
at org.jboss.tools.jst.web.kb.internal.KbProject.getTagLibraries(KbProject.java:135)
at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getCompositeLibraries(FaceletTagLibrary.java:90)
at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:128)
at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
at org.jboss.tools.jst.web.kb.internal.taglib.FaceletTagLibrary.getComponent(FaceletTagLibrary.java:130)
[... the stack trace goes on and on...]{code}{quote}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months