[JBoss JIRA] (TOOLSDOC-338) Review: Devs to review JBoss Central & JBoss Perspective chapter for JBDS 7.0.
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-338?page=com.atlassian.jira.plug... ]
Alexey Kazakov commented on TOOLSDOC-338:
-----------------------------------------
{quote}
There are a number of perspectives available in the IDE. When the IDE starts, the default perspective is used as the
current perspective. If you use the tabs, menus or toolbars of the JBoss perspective frequently, you may want to make it
the default perspective.
{quote}
It seams that the default perspective is used only for the first start after installation/switching to a new workspace. Otherwise the last used perspective is used regardless what perspective is default.
> Review: Devs to review JBoss Central & JBoss Perspective chapter for JBDS 7.0.
> ------------------------------------------------------------------------------
>
> Key: TOOLSDOC-338
> URL: https://issues.jboss.org/browse/TOOLSDOC-338
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: User Guide - JBoss Central & JBoss Perspective
> Affects Versions: 4.1.0
> Reporter: Michelle Murray
> Assignee: Fred Bricon
> Fix For: 4.1.0
>
> Attachments: UserGuide_Central.pdf
>
>
> Please review the content of the JBoss Central/JBoss Perspective chapter from a technical viewpoint:
> 1) Are features correctly documented?
> 2) Are there any features that are missing?
> Screenshots are currently missing and will be added closer to GA.
> For ease of tracking by docs, please give feedback as comments in this JIRA.
> The chapter is available here as a pdf. The pdf has some layout issues so please disregard these and only comment on the technical content.
> Alternatively, the complete user guide to date is also available form:
> http://documentation-devel.engineering.redhat.com/docs/en-US/JBoss_Develo...
> https://github.com/jbosstools/jbosstools-documentation/tree/master/docs/J... (build with: mvn compile)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] (JBIDE-14852) test failures in Seam (JavaEE)
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-14852:
----------------------------------
Summary: test failures in Seam (JavaEE)
Key: JBIDE-14852
URL: https://issues.jboss.org/browse/JBIDE-14852
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam 2
Affects Versions: 4.1.0.Beta2
Reporter: Nick Boldt
{code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Trunk/job/jbosstools-javaee_master/404/testReport/}
>>> org.jboss.tools.seam.core.test.SerializationTest.testCleanBuild 2.3 sec 1
Error Message
expected:<95> but was:<21>
Stacktrace
junit.framework.AssertionFailedError: expected:<95> but was:<21>
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.Assert.failNotEquals(Assert.java:329)
at junit.framework.Assert.assertEquals(Assert.java:78)
at junit.framework.Assert.assertEquals(Assert.java:234)
at junit.framework.Assert.assertEquals(Assert.java:241)
at junit.framework.TestCase.assertEquals(TestCase.java:409)
at org.jboss.tools.seam.core.test.SerializationTest.testCleanBuild(SerializationTest.java:143)
>>> org.jboss.tools.seam.xml.test.SeamXMLModelTest.testDebugAttribute 3.9 sec 53
Error Message
Validator failed to report an error in component org.jboss.seam.core.init1
Stacktrace
junit.framework.AssertionFailedError: Validator failed to report an error in component org.jboss.seam.core.init1
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.Assert.assertTrue(Assert.java:22)
at junit.framework.TestCase.assertTrue(TestCase.java:192)
at org.jboss.tools.seam.xml.test.SeamXMLModelTest.testDebugAttribute(SeamXMLModelTest.java:106)
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] (JBIDE-14851) 7 test failures in Server
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-14851:
----------------------------------
Summary: 7 test failures in Server
Key: JBIDE-14851
URL: https://issues.jboss.org/browse/JBIDE-14851
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.1.0.Beta2
Reporter: Nick Boldt
org.jboss.ide.eclipse.archives.test.core.ant.SimpleAntTest.testOne has been failing for the past 32 builds. The rest, for the past 5 builds.
{code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Trunk/job/jbosstools-server_master/304/testReport/}
All Failed Tests
Test Name Duration Age
>>> org.jboss.ide.eclipse.as.internal.management.as7.tests.AS7ManagementServiceStartupShutdownTest.dummyTest[2] 1 min 6 sec 5
>>> org.jboss.ide.eclipse.as.internal.management.as7.tests.AS7ManagerIntegrationTest.canGetServerState[2] 1 min 6 sec 5
>>> org.jboss.ide.eclipse.as.internal.management.as7.tests.AS7ManagerIntegrationTest.getDisabledStateIfDeploymentIsOnlyAdded[2] 1 ms 5
>>> org.jboss.ide.eclipse.as.internal.management.as7.tests.AS7ManagerIntegrationTest.getErrorIfDeploymentIsNotDeployed[2] 1 ms 5
>>> org.jboss.ide.eclipse.as.internal.management.as7.tests.AS7ManagerIntegrationTest.deployedWarIsResponding[2] 1 ms 5
>>> org.jboss.ide.eclipse.as.internal.management.as7.tests.AS7ManagerIntegrationTest.getEnabledStateIfDeploymentIsDeployed[2] 1 ms 5
>>> org.jboss.ide.eclipse.archives.test.core.ant.SimpleAntTest.testOne 47 ms 32{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] (JBIDE-14670) Automatically notify browsers after user edited a file, even *before* saving it
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14670?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-14670:
----------------------------------
Fix Version/s: 4.1.x
(was: 4.1.0.Beta2)
> Automatically notify browsers after user edited a file, even *before* saving it
> -------------------------------------------------------------------------------
>
> Key: JBIDE-14670
> URL: https://issues.jboss.org/browse/JBIDE-14670
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: livereload
> Affects Versions: 4.1.0.Beta2
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: 4.1.x
>
>
> The idea is to notify the livereload server which in turn will notify browser that are connected to the proxy to access local files. when the browser will send a request to the proxy, this latter one will not return the content of the resource on the FS but rather, it will first check if there's an open editor for that resource and then, it will send the working copy instead.
> This should be an option in the LiveReload Proxy Configuration
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months