[JBoss JIRA] (JBIDE-10754) Hyperlink tests failure
by Alexey Kazakov (JIRA)
Alexey Kazakov created JBIDE-10754:
--------------------------------------
Summary: Hyperlink tests failure
Key: JBIDE-10754
URL: https://issues.jboss.org/browse/JBIDE-10754
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: CDI, common/jst/core, jsp/jsf/xml source editing, Seam 2
Affects Versions: 3.3.0.Beta1
Reporter: Alexey Kazakov
Assignee: Victor Rubezhny
Priority: Critical
Fix For: 3.3.0.Beta1
For example:
{code}
Running org.jboss.tools.cdi.seam.text.ext.test.CdiSeamTextExtAllTests
Tests run: 13, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 21.012 sec <<< FAILURE!
testSeamConfigTagNameHyperlink(org.jboss.tools.cdi.seam.text.ext.test.SeamConfigTagNameHyperlinkTest) Time elapsed: 0.186 sec <<< FAILURE!
junit.framework.AssertionFailedError: Can't find HyperLink
at junit.framework.Assert.fail(Assert.java:47)
at org.jboss.tools.cdi.text.ext.test.CDIHyperlinkTestUtil.checkHyperLinkInXml(CDIHyperlinkTestUtil.java:226)
at org.jboss.tools.cdi.seam.text.ext.test.SeamConfigTagNameHyperlinkTest.testSeamConfigTagNameHyperlink(SeamConfigTagNameHyperlinkTest.java:34)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
{code}
{code}
Tests run: 78, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 511.708 sec <<< FAILURE!
testSeamViewPartitioner(org.jboss.tools.seam.ui.test.hyperlink.SeamViewHyperlinkPartitionerTest) Time elapsed: 33.838 sec <<< ERROR!
java.lang.AbstractMethodError
at org.jboss.tools.common.text.ext.hyperlink.AbstractHyperlinkPartitioner.getChildPartitionRegion(AbstractHyperlinkPartitioner.java:48)
at org.jboss.tools.common.text.ext.hyperlink.AbstractHyperlinkPartitioner.getChildPartitionRegion(AbstractHyperlinkPartitioner.java:55)
at org.jboss.tools.common.text.ext.hyperlink.AbstractHyperlinkPartitioner.getChildPartitionRegion(AbstractHyperlinkPartitioner.java:55)
at org.jboss.tools.common.text.ext.hyperlink.HyperlinkDetector.getPartitions(HyperlinkDetector.java:74)
at org.jboss.tools.seam.ui.test.hyperlink.TestHyperlinkDetector.getPartitions(SeamViewHyperlinkPartitionerTest.java:297)
at org.jboss.tools.seam.ui.test.hyperlink.SeamViewHyperlinkPartitionerTest.testSeamViewPartitioner(SeamViewHyperlinkPartitionerTest.java:124)
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] (JBIDE-10756) Debug button attempts to start already running server, reports port in use
by James Wilson (JIRA)
James Wilson created JBIDE-10756:
------------------------------------
Summary: Debug button attempts to start already running server, reports port in use
Key: JBIDE-10756
URL: https://issues.jboss.org/browse/JBIDE-10756
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Indigo (Win XP)
Reporter: James Wilson
Assignee: Rob Stryker
Priority: Optional
I've added a JBoss AS (4.2) server to the Servers view. I select it and then press the "Start the server in debug mode" button on the Servers view toolbar. When I want to run my application I usually click on the Debug button on the main Eclipse toolbar, which launches the last configuration run. In my Ganymede setup (so I think JBoss Tools 3.0) that didn't include starting the JBoss AS server, but in Indigo/JBoss Tools 3.3 (M5) it does. Thus the tooltip for the debug button becomes "Debug JBoss v4.2 at localhost (already running)", and if I click on it I get a message box stating:
'Launching JBoss v4.2 at localhost' has encountered a problem.
Server port In Ue 80080-Http
In the Servers view my JBoss 4.2 AS server then shows as stopped. I can start it again and it all works fine after that.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months