December 2010 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-7242) Support for <note>, <tip>, <warning> and <caution> elements in DocBook editor

by Pete Muir (JIRA)

Support for <note>, <tip>, <warning> and <caution> elements in DocBook editor ----------------------------------------------------------------------------- Key: JBIDE-7242 URL: https://jira.jboss.org/browse/JBIDE-7242 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Visual Page Editor Templates Affects Versions: 3.2.0.M2 Reporter: Pete Muir Assignee: Maxim Areshkau Typical usage is: <note> <para> The <code>ProcessAnnotatedType</code> container lifecycle event will be called for vetoed types. </para> </note> Dobcook renders this inside a box, with either the title specified by the <title> element nested, or by default Note, Tip, Warning, or Caution -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

4
3
0 / 0

[JBoss JIRA] Created: (JBIDE-7177) Don't render <colspec> in JBoss Tools Docbook Editor

by Pete Muir (JIRA)

Don't render <colspec> in JBoss Tools Docbook Editor ---------------------------------------------------- Key: JBIDE-7177 URL: https://jira.jboss.org/browse/JBIDE-7177 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Visual Page Editor Templates Affects Versions: 3.2.0.M2 Reporter: Pete Muir Assignee: Maxim Areshkau <colspec> is a non-rendering element giving instructions to the table in which it is nested -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

4
3
0 / 0

[JBoss JIRA] Created: (JBIDE-7176) Support for xref in JBoss Tools Docbook Editor

by Pete Muir (JIRA)

Support for xref in JBoss Tools Docbook Editor ---------------------------------------------- Key: JBIDE-7176 URL: https://jira.jboss.org/browse/JBIDE-7176 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Visual Page Editor Templates Affects Versions: 3.2.0.M2 Reporter: Pete Muir Assignee: Maxim Areshkau Ideally it would resolve the linkend, however if this can't be done, rendering it inline like <xref linkend="foo" /> would be an improvement over rendering it as a block element with no attributes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

4
3
0 / 0

[JBoss JIRA] Resolved: (JBIDE-6347) Teiid should appear as a first-class source in Seam Tools

by John Doyle (JIRA)

[ https://jira.jboss.org/browse/JBIDE-6347?page=com.atlassian.jira.plugin.s... ] John Doyle resolved JBIDE-6347. ------------------------------- Fix Version/s: 3.2.0.CR1 (was: 3.2.0.Beta2) Resolution: Done Resolved JBDS-1421. > Teiid should appear as a first-class source in Seam Tools > --------------------------------------------------------- > > Key: JBIDE-6347 > URL: https://jira.jboss.org/browse/JBIDE-6347 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: teiid > Reporter: Van Halbert > Assignee: John Doyle > Fix For: 3.2.0.CR1 > > > As part of the PRD, Teiid should appear as a first-class source in Seam Tools. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBIDE-7114) Upgrade from Seam BIRT project created on JBoss Tools 3.1.0/BIRT 2.5.1 having incompatibility issue when running report on latest JBoss Tools version

by Indra Gunawan (JIRA)

Upgrade from Seam BIRT project created on JBoss Tools 3.1.0/BIRT 2.5.1 having incompatibility issue when running report on latest JBoss Tools version ---------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-7114 URL: https://jira.jboss.org/browse/JBIDE-7114 Project: Tools (JBoss Tools) Issue Type: Bug Components: birt, integration, usage Affects Versions: 3.2.0.M2, 3.1.1 Environment: Fedora 12 (2.6.32.21-166.fc12.i686.PAE) Reporter: Indra Gunawan Assignee: Snjezana Peco Priority: Minor I have a Seam Birt project that I created with JBoss Tools 3.1.0 (BIRT version 2.5.1/3.2.20), then I decided to upgrade my IDE using JBoss Tools 3.2.0 on Eclipse 3.6 (BIRT version 2.6.0/3.2.21). I have no problem on editing project report design file and saved it using built in designer, except the IDE is much slower than before (I realize that this are related to WTP bug that has been fixed on Eclipse 3.6.1). I revert back to older release JBoss Tools 3.1.x (BIRT version 2.5.2/3.2.21), at this time my IDE is running normal like before. Then I try running my project on JBoss AS 5.0.1 and run a report that I've edited with current IDE and report designer (JBoss Tools 3.1.x (BIRT version 2.5.2/3.2.21)) but it throws: + There is no report design object available. I'm able to give temporary work around with this problem by changing report version on XML view from 3.2.21 to 3.2.20 although there are many different between both version specially on the use of scalar parameter dataType and nativeDataType (but I'm not sure this will cause problem or not). Because I couldn't find solution/steps about upgrading Seam BIRT version from 2.5.1 to 2.5.2 (from 3.2.20 to 3.2.21), I decided to revert back again to my old IDE (JBoss Tools 3.1.0 (BIRT version 2.5.1/3.2.20)). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

5
7
0 / 0

[JBoss JIRA] Created: (JBIDE-7489) org.jboss.tools.jst.jsp.test.ca.ExternalizeCommandTest failure

by Alexey Kazakov (JIRA)

org.jboss.tools.jst.jsp.test.ca.ExternalizeCommandTest failure -------------------------------------------------------------- Key: JBIDE-7489 URL: https://jira.jboss.org/browse/JBIDE-7489 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.2.0.Beta2 Reporter: Alexey Kazakov Assignee: Maxim Areshkau Fix For: 3.2.0.Beta2 Failed tests: testExternalizeCommand(org.jboss.tools.jst.jsp.test.ca.ExternalizeCommandTest) Tests in error: testExternalizeCommand(org.jboss.tools.jst.jsp.test.ca.NewEditorSideBySideCommandTest) testExternalizeCommand(org.jboss.tools.jst.jsp.test.ca.ExternalizeCommandTest) Time elapsed: 6.447 sec <<< FAILURE! junit.framework.AssertionFailedError: Ext command should be enabled with current selection expected:<true> but was:<false> at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.failNotEquals(Assert.java:283) at junit.framework.Assert.assertEquals(Assert.java:64) at junit.framework.Assert.assertEquals(Assert.java:143) at org.jboss.tools.jst.jsp.test.ca.ExternalizeCommandTest.testExternalizeCommand(ExternalizeCommandTest.java:65) ... testExternalizeCommand(org.jboss.tools.jst.jsp.test.ca.NewEditorSideBySideCommandTest) Time elapsed: 5.864 sec <<< ERROR! org.eclipse.core.commands.common.NotDefinedException: Cannot get the name from an undefined object. org.jboss.tools.sidebyside.newEditor at org.eclipse.core.commands.common.NamedHandleObject.getName(NamedHandleObject.java:71) at org.eclipse.core.commands.NamedHandleObjectWithState.getName(NamedHandleObjectWithState.java:83) at org.jboss.tools.jst.jsp.test.ca.NewEditorSideBySideCommandTest.testExternalizeCommand(NewEditorSideBySideCommandTest.java:60) ... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-6901) Expanding in Smooks Java Bean Instance dialog affects how bean is inserted

by Jiri Peterka (JIRA)

Expanding in Smooks Java Bean Instance dialog affects how bean is inserted -------------------------------------------------------------------------- Key: JBIDE-6901 URL: https://jira.jboss.org/browse/JBIDE-6901 Project: Tools (JBoss Tools) Issue Type: Bug Components: smooks Affects Versions: 3.2.0.M2 Environment: JBT 3.2.0 M2, Linux 64 Reporter: Jiri Peterka Steps: 1. Have Java Mapping task in smooks-config editor 2. Add Java Class on canvas 3. Select composited bean class (like Order - containing OrderItem, Header) or any other class composed like that 4. Click OK 5. Try to do it again with expanding (and/or collapsing) tree in the dialog. Let everything checked as it is ASSERT: Result should be the same ASSERT: Both steps should result to expanded model on canvas (as it seems to be selected by default) Note: Possibly linked with https://jira.jboss.org/browse/JBIDE-5358 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

5
13
0 / 0

[JBoss JIRA] Created: (JBIDE-7430) VPE Selection Bar is not visible by default

by Yahor Radtsevich (JIRA)

VPE Selection Bar is not visible by default ------------------------------------------- Key: JBIDE-7430 URL: https://jira.jboss.org/browse/JBIDE-7430 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.2.0.Beta1 Reporter: Yahor Radtsevich Assignee: Maxim Areshkau Fix For: 3.2.0.Beta2 STEPS TO REPRODUCE: 1. Run JBoss Tools. 2. Open ant .html file in the VPE. 3. Set VPE Selection Bar to be shown ("Toggle Selection Bar" button). 4. Restart Tools. RESULT: The "Toggle Selection Bar" button is pressed, but the Selection Bar itself is not shown (see screenshot-1.png). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

2
7
0 / 0

[JBoss JIRA] Created: (JBIDE-7490) org.jboss.tools.jst.jsp.test.ca.SelectionBarTest failure

by Alexey Kazakov (JIRA)

org.jboss.tools.jst.jsp.test.ca.SelectionBarTest failure -------------------------------------------------------- Key: JBIDE-7490 URL: https://jira.jboss.org/browse/JBIDE-7490 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.2.0.Beta2 Reporter: Alexey Kazakov Assignee: Maxim Areshkau Fix For: 3.2.0.Beta2 Failed tests: testSelectionBarCommandState(org.jboss.tools.jst.jsp.test.ca.SelectionBarTest) testSelectionBarCommandState(org.jboss.tools.jst.jsp.test.ca.SelectionBarTest) Time elapsed: 6.218 sec <<< FAILURE! junit.framework.AssertionFailedError: check command enabled command status expected:<false> but was:<true> at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.failNotEquals(Assert.java:283) at junit.framework.Assert.assertEquals(Assert.java:64) at junit.framework.Assert.assertEquals(Assert.java:143) at org.jboss.tools.jst.jsp.test.ca.SelectionBarTest.testSelectionBarCommandState(SelectionBarTest.java:57) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-7369) Invoking new jBPM project wizard fails sometimes

by Jiri Peterka (JIRA)

Invoking new jBPM project wizard fails sometimes ------------------------------------------------ Key: JBIDE-7369 URL: https://jira.jboss.org/browse/JBIDE-7369 Project: Tools (JBoss Tools) Issue Type: Bug Components: jbpm Affects Versions: 3.2.0.Beta1 Environment: JBDS 4.0.0.beta1 #52, Linux 64 Reporter: Jiri Peterka Fix For: 3.2.0.Beta2 Steps: 1. New workspace 2. New -> Create new jBPM 3 Project ERROR: Wizard invocation sometimes fails with this.It can be quite hard to replicate but I've seen this for several times from time to time. Problems occurred when invoking code from plug-in: "org.eclipse.jface". java.lang.IllegalArgumentException: Path must include project and resource name: / at org.eclipse.core.runtime.Assert.isLegal(Assert.java:63) at org.eclipse.core.internal.resources.Workspace.newResource(Workspace.java:1795) at org.eclipse.core.internal.resources.Container.getFolder(Container.java:221) at org.jbpm.gd.jpdl.wizard.NewProcessDefinitionWizardPage.getProcessFolder(NewProcessDefinitionWizardPage.java:243) at org.jbpm.gd.jpdl.wizard.NewProcessDefinitionWizardPage.processExists(NewProcessDefinitionWizardPage.java:236) at org.jbpm.gd.jpdl.wizard.NewProcessDefinitionWizardPage.checkProcessNameText(NewProcessDefinitionWizardPage.java:224) at org.jbpm.gd.jpdl.wizard.NewProcessDefinitionWizardPage.checkPage(NewProcessDefinitionWizardPage.java:193) at org.jbpm.gd.jpdl.wizard.NewProcessDefinitionWizardPage.createControl(NewProcessDefinitionWizardPage.java:96) at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:170) at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:734) at org.eclipse.jface.wizard.WizardDialog.setWizard(WizardDialog.java:1162) at org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDialog.java:1221) at org.eclipse.jface.wizard.WizardDialog.access$4(WizardDialog.java:1218) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

2
3
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues December 2010