September 2010 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-6137) JBoss ESB Runtimes preference page Version: label issue

by Brian Fitzpatrick (JIRA)

JBoss ESB Runtimes preference page Version: label issue ------------------------------------------------------- Key: JBIDE-6137 URL: https://jira.jboss.org/jira/browse/JBIDE-6137 Project: Tools (JBoss Tools) Issue Type: Bug Components: esb Reporter: Brian Fitzpatrick Assignee: Denny Xu Priority: Minor Fix For: 3.2.next, 3.1.x While testing the patch for JBIDE-5522, I noticed this issue with the column label on the JBoss ESB Runtimes preference page. The middle column is labeled "Version:" and it doesn't really need a colon and should just be "Version". -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

3
8
0 / 0

[JBoss JIRA] Created: (JBIDE-6295) New Faces Config Wizard creates invalid faces-config.xm v.2

by Alexey Kazakov (JIRA)

New Faces Config Wizard creates invalid faces-config.xm v.2 ----------------------------------------------------------- Key: JBIDE-6295 URL: https://jira.jboss.org/browse/JBIDE-6295 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 3.2.next Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.2.next 1. New->JBoss Tools->JSF->Faces Config (version - 2.0) 2. Close and re-open Eclipse. 3. Open created faces-config.xml 4. The file is marked as invalid: Value cannot be empty. -- 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, 10 months

5
9
0 / 0

[JBoss JIRA] Created: (JBDS-1263) Not able to add this Excel File to BRMS

by Jim Tyrrell (JIRA)

Not able to add this Excel File to BRMS --------------------------------------- Key: JBDS-1263 URL: https://jira.jboss.org/browse/JBDS-1263 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Affects Versions: 3.0.0.GA Environment: Possibly only on a Mac Reporter: Jim Tyrrell For some reason the Add icon in JBDS under Govnor is grayed out and does not allow for the uploading of the attached Excel file. I both dragged and dropped it into the Repo and also saved it directly into the workspace with the same effect. I am told on Windows that this works without any hiccups. -- 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, 10 months

5
15
0 / 0

[JBoss JIRA] Created: (JBIDE-6962) jBPM sub process moving isn't proceeded correctly

by Jiri Peterka (JIRA)

jBPM sub process moving isn't proceeded correctly ------------------------------------------------- Key: JBIDE-6962 URL: https://jira.jboss.org/browse/JBIDE-6962 Project: Tools (JBoss Tools) Issue Type: Bug Components: jbpm Affects Versions: 3.2.0.M2 Environment: JBDS 4.0.0.v201008261621R-H420-M2, Linux 64 Reporter: Jiri Peterka Steps: 1. Have jBPM 3 project 2. Create process1 3. Create process2 under project1 4. Try to move it ERROR: Drag&Drop -> process2 into src/main/jpdl ---> Name conflict ERROR: Context Menu -> Refactor -> Move ----> A package cannot be moved to its own parent I guess both is wrong behaviour, Drag and Drop should work in standard way and process should be able to move into src/main/jpdl folder -- 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, 10 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-6959) Wrong link on the New jBPM Process Project wizard page

by Jiri Peterka (JIRA)

Wrong link on the New jBPM Process Project wizard page ------------------------------------------------------ Key: JBIDE-6959 URL: https://jira.jboss.org/browse/JBIDE-6959 Project: Tools (JBoss Tools) Issue Type: Bug Components: jbpm Affects Versions: 3.2.0.M2 Environment: JBDS 4.0.0.v201008261621R-H420-M2, Linux 64, JDK 1.6 Reporter: Jiri Peterka Steps: 1. New -> jBPM 3 Project, Next, Next 2. Click on "Download the JBoss jBPM package..." See screenshot Link points to: http://www.jboss.org/jbpm/downloads/ --> Page not found result Possible page: http://sourceforge.net/projects/jbpm/files/ -- 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, 10 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-5912) Error when moving jBPM process package in the project

by Jiri Peterka (JIRA)

Error when moving jBPM process package in the project ----------------------------------------------------- Key: JBIDE-5912 URL: https://jira.jboss.org/jira/browse/JBIDE-5912 Project: Tools (JBoss Tools) Issue Type: Bug Components: jbpm Affects Versions: 3.1.0.CR2 Environment: JBDS 3.0.0 CR2 #173 Reporter: Jiri Peterka Fix For: 3.1.0.CR3 Steps: 1. Create jbpm3 process definition in the root of the project 2. Move (drag&drop) process definition package into src/main/jpdl 3. Edit process in GPD and save. ERROR: Save Failed, processimage.jpg is still expected in root directory (see screenshot) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

5
7
0 / 0

[JBoss JIRA] Created: (JBIDE-6104) Save Local Server and Deployment Server Settings

by Rafael Liu (JIRA)

Save Local Server and Deployment Server Settings ------------------------------------------------ Key: JBIDE-6104 URL: https://jira.jboss.org/jira/browse/JBIDE-6104 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: bpm Reporter: Rafael Liu Usually Save Local Server and Deployment Server Settings doesn't change, but today we have to retype these addresses every time the JPDL is reopened. It would make developer's life easier to save those. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

4
6
0 / 0

[JBoss JIRA] Created: (JBIDE-6529) jsf test failures

by Nick Boldt (JIRA)

jsf test failures ----------------- Key: JBIDE-6529 URL: https://jira.jboss.org/browse/JBIDE-6529 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: JSF Reporter: Nick Boldt Assignee: Alexey Kazakov From: http://hudson.qa.jboss.com/hudson/view/DevStudio/job/jbosstools-3.2.0.M1/... Tests run: 7, FAILUREs: 1, Errors: 0, Skipped: 0, Time elapsed: 82.709 sec <<< FAILURE! testJbide1791(org.jboss.tools.jst.jsp.test.ca.Jbide1791Test) Time elapsed: 10.575 sec <<< FAILURE! junit.framework.AssertionFailedError: Proposal h1 not found! at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at org.jboss.tools.jst.jsp.test.ca.ContentAssistantTestCase.checkProposals(ContentAssistantTestCase.java:100) at org.jboss.tools.jst.jsp.test.ca.ContentAssistantTestCase.checkProposals(ContentAssistantTestCase.java:55) at org.jboss.tools.jst.jsp.test.ca.Jbide1791Test.testJbide1791(Jbide1791Test.java:65) -- Tests run: 1, FAILUREs: 0, Errors: 1, Skipped: 0, Time elapsed: 0.04 sec <<< FAILURE! initializationError(org.jboss.tools.jst.text.ext.test.JsfExtAllTests) Time elapsed: 0.005 sec <<< ERROR! java.lang.Exception: No runnable methods at org.junit.runners.BlockJUnit4ClassRunner.validateInstanceMethods(BlockJUnit4ClassRunner.java:171) at org.junit.runners.BlockJUnit4ClassRunner.collectInitializationErrors(BlockJUnit4ClassRunner.java:115) at org.junit.runners.ParentRunner.validate(ParentRunner.java:269) at org.junit.runners.ParentRunner.<init>(ParentRunner.java:66) at org.junit.runners.BlockJUnit4ClassRunner.<init>(BlockJUnit4ClassRunner.java:59) at org.junit.internal.builders.JUnit4Builder.runnerForClass(JUnit4Builder.java:13) at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.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, 10 months

4
6
0 / 0

[JBoss JIRA] Created: (JBIDE-7037) Unable to isntall jboss tools via p2

by Libor Zoubek (JIRA)

Unable to isntall jboss tools via p2 ------------------------------------ Key: JBIDE-7037 URL: https://jira.jboss.org/browse/JBIDE-7037 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng Affects Versions: 3.2.0.M2 Reporter: Libor Zoubek Assignee: Nick Boldt I am trying to install tools from command line via p2 using our latest M2 update-site zip. I am getting: Error at line 16583, column 25: Duplicate singleton element in element "repository": <references size="24"> It seems like our content.xml in content.jar is somehow invalid. -- 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, 10 months

2
8
0 / 0

[JBoss JIRA] Created: (JBIDE-6536) seam.xml test failures

by Nick Boldt (JIRA)

seam.xml test failures ---------------------- Key: JBIDE-6536 URL: https://jira.jboss.org/browse/JBIDE-6536 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: Seam Affects Versions: 3.2.0.M1 Reporter: Nick Boldt Assignee: Alexey Kazakov From: http://hudson.qa.jboss.com/hudson/view/DevStudio/job/jbosstools-3.2.0.M1/... Tests run: 2, FAILUREs: 2, Errors: 0, Skipped: 0, Time elapsed: 0.049 sec <<< FAILURE! testXMLModel(org.jboss.tools.seam.xml.test.SeamXMLModelTest) Time elapsed: 0.01 sec <<< FAILURE! junit.framework.AssertionFailedError: Cannot create XModel object for file components22.xml. at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at junit.framework.Assert.assertNotNull(Assert.java:214) at org.jboss.tools.seam.xml.test.SeamXMLModelTest.testXMLModel(SeamXMLModelTest.java:60) -- testNavigationPagesComponent(org.jboss.tools.seam.xml.test.SeamXMLModelTest) Time elapsed: 0 sec <<< FAILURE! junit.framework.AssertionFailedError: Cannot create XModel object for file components22.xml. at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at junit.framework.Assert.assertNotNull(Assert.java:214) at org.jboss.tools.seam.xml.test.SeamXMLModelTest.testNavigationPagesComponent(SeamXMLModelTest.java:77) -- 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, 10 months

4
5
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 September 2010