July 2011 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBDS-1607) Wrong JBDS datasheet link on the devstudio product page

by Jiri Peterka (JIRA)

Wrong JBDS datasheet link on the devstudio product page ------------------------------------------------------- Key: JBDS-1607 URL: https://issues.jboss.org/browse/JBDS-1607 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Affects Versions: 4.0.0.GA Reporter: Jiri Peterka There are two links on JBDS product page (http://www.jboss.com/products/devstudio/) One of them is incorrect (http://www.redhat.com/f/pdf/jbds_datasheet.pdf). It's pointing to old JBDS3 datatsheet It should be http://www.jboss.com/pdf/jboss_dev_studio_data_sheet.pdf -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

5
4
0 / 0

[JBoss JIRA] Created: (JBIDE-9217) FunCBRRules Method for XPath Broken in Tooling

by Brian Fitzpatrick (JIRA)

FunCBRRules Method for XPath Broken in Tooling ---------------------------------------------- Key: JBIDE-9217 URL: https://issues.jboss.org/browse/JBIDE-9217 Project: Tools (JBoss Tools) Issue Type: Bug Components: esb Affects Versions: 3.2.0.Final Reporter: Brian Fitzpatrick Assignee: Viacheslav Kabanovich Priority: Critical Fix For: 3.2.1.CR2, 3.3.0.M3 Hey Slava - if you have time, can you look into this for the ESB editor in the 3.2.x branch and trunk? (from SOA-2747) When adding an ContentBasedRouter with the following configuration in JBoss Developer Studio, switching between Tree and Source view will remove the namespace tag. <action class="org.jboss.soa.esb.actions.ContentBasedRouter" name="validateAndRoute"> <property name="cbrAlias" value="XPath"/> <property name="destinations"> <namespace prefix="m" uri="http://amentra.com/mentoring" /> <route-to expression="//m:id > '0'" service-category="student-esb-services" service-name="AsyncSetAdvisorGraduateStudentService"/> </property> </action> This results in the following after toggling and adding another action. <action class="org.jboss.soa.esb.actions.ContentBasedRouter" name="validateAndRoute"> <property name="cbrAlias" value="XPath"/> <property name="ruleLanguage"/> <property name="destinations"> <route-to expression="//m:id > '0'" service-category="student-esb-services" service-name="AsyncSetAdvisorGraduateStudentService"/> </property> </action> Note that the namespace tag under property "destinations" has been removed by the tooling. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

4
6
0 / 0

[JBoss JIRA] Created: (JBIDE-9077) org.jboss.tools.common.model.ui.dialog.test.ErrorDialogTest.testOkPressed() should not send any emails

by Alexey Kazakov (JIRA)

org.jboss.tools.common.model.ui.dialog.test.ErrorDialogTest.testOkPressed() should not send any emails ------------------------------------------------------------------------------------------------------ Key: JBIDE-9077 URL: https://issues.jboss.org/browse/JBIDE-9077 Project: Tools (JBoss Tools) Issue Type: Bug Components: common Affects Versions: 3.2.0.Final Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.3.0.M2 JUnit test org.jboss.tools.common.model.ui.dialog.test.ErrorDialogTest.testOkPressed sends emails when it passes: JBoss Tools Common 3.3.0.v20110606-0053-H660-M2, Eclipse 3.7.0.v201105261708 unknown, Java 1.6.0_24, Linux ------Type your additional comment here-------- ----------------------------------------------- Exception Message java.lang.Exception: Exception Message at org.jboss.tools.common.model.ui.dialog.test.ErrorDialogTest.testOkPressed(ErrorDialogTest.java:63) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at junit.framework.TestCase.runTest(TestCase.java:168) at junit.framework.TestCase.runBare(TestCase.java:134) at junit.framework.TestResult$1.protect(TestResult.java:110) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.framework.TestResult.run(TestResult.java:113) at junit.framework.TestCase.run(TestCase.java:124) at junit.framework.TestSuite.runTest(TestSuite.java:243) at junit.framework.TestSuite.run(TestSuite.java:238) at junit.framework.TestSuite.runTest(TestSuite.java:243) at junit.framework.TestSuite.run(TestSuite.java:238) at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127) at org.apache.maven.surefire.Surefire.run(Surefire.java:177) at org.codehaus.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:75) at org.codehaus.tycho.surefire.osgibooter.AbstractUITestApplication$1.run(AbstractUITestApplication.java:25) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3561) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3210) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123) at org.codehaus.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:21) at org.codehaus.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:109) at org.codehaus.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:27) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) at org.eclipse.equinox.launcher.Main.main(Main.java:1386) to exadelstudiobugs(a)exadel.com We should disable this sending in the test. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-8476) JBoss Rich Faces Editor causes Java refactoring failures for read/only SCM systems (Perforce)

by joe freeman (JIRA)

JBoss Rich Faces Editor causes Java refactoring failures for read/only SCM systems (Perforce) --------------------------------------------------------------------------------------------- Key: JBIDE-8476 URL: https://issues.jboss.org/browse/JBIDE-8476 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 3.2.0.CR1 Environment: 3.2.0 GA Rich Faces Editor Mac and Windows Eclipse 3.6 Perforce (or possibly other READ/ONLY based SCM) Reporter: joe freeman Assignee: Alexey Kazakov We have a large project that uses Perforce as SCM. Perforce leaves files read/only until they have been modified at which point they are checked out and made writable. Eclipse refactoring modifies files and automatically engages the SCM Eclipse plugins on changes to optionally check the files out. In the case of Perforce, this makes the files writable on modification which allows changes to be saved. This works fine under Eclipse 3.5 with Jboss Tools. This is broken under Eclipse 3.6, Jboss tools 3.2 when the RichFaces editor is installed and a developer attempts to rename a method using "refactor Method name". You get a set of error messages where it looks like the refactoring is trying to change read-only files. Many of the files listed are not changed by the refactoring. It's almost like the Rich Faces editor/refactor hooks is stat'ing or touching the files maybe without changing. Removing the RichFaces editor stops the problem for occurring. No work around exists. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

5
12
0 / 0

[JBoss JIRA] Created: (JBIDE-9346) Include m2e-wtp 0.13.1 in target platforms and composite reqs mirrors

by Nick Boldt (JIRA)

Include m2e-wtp 0.13.1 in target platforms and composite reqs mirrors --------------------------------------------------------------------- Key: JBIDE-9346 URL: https://issues.jboss.org/browse/JBIDE-9346 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven, updatesite Affects Versions: 3.3.0.M2, 3.2.1.CR2 Reporter: Nick Boldt Assignee: Fred Bricon Fix For: 3.2.1.CR3, 3.3.0.M3 When it's available, move the TPs and composite reqs sites for Helios and Indigo up to include this updated version of m2e-wtp. Assigned to Fred as reminder to get 0.13.1 out the door, then to bounce this back to me for the next part. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

3
8
0 / 0

[JBoss JIRA] Created: (JBDS-1570) Document that BPEL is a Tech preview in the JBDS 4.0 release

by Shaun Appleton (JIRA)

Document that BPEL is a Tech preview in the JBDS 4.0 release ------------------------------------------------------------ Key: JBDS-1570 URL: https://issues.jboss.org/browse/JBDS-1570 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: documentation Affects Versions: 4.0.0.GA Reporter: Shaun Appleton JBDS-1360 states BPEL is a tech release for JBDS 4.0 The docs need to state this to and should say that, as such, it is not supported - but we welcome feedback. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

3
4
0 / 0

[JBoss JIRA] Created: (JBDS-1716) A misleading typo in all the samples for ESB for SOA-P 5.0

by JC Li (JIRA)

A misleading typo in all the samples for ESB for SOA-P 5.0 ---------------------------------------------------------- Key: JBDS-1716 URL: https://issues.jboss.org/browse/JBDS-1716 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Affects Versions: 4.0.0.GA Environment: RHEL 6.1, JBoss SOA-P 5.1.0.GA Reporter: JC Li In JBDS, when you click Help-->Project Examples to import examples, all the descriptions for the examples in "ESB for SOA-P 5.0" share a same typo. "jboss-soa-p.5.0 Runtime" should read "jboss-soa-p-5.0 Runtime", since the later is what is set in the samples. Also, all the "readme" files have the same typo. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

4
15
0 / 0

[JBoss JIRA] Created: (JBDS-1717) Hide JBDS Extras feature (com.jboss.jbds.product.extra.feature) from Extras site

by Nick Boldt (JIRA)

Hide JBDS Extras feature (com.jboss.jbds.product.extra.feature) from Extras site -------------------------------------------------------------------------------- Key: JBDS-1717 URL: https://issues.jboss.org/browse/JBDS-1717 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: 3rdPartyDependencies, updatesite Affects Versions: 5.0.0.M2, 4.1.0.CR3 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 4.1.0.GA, 5.0.0.M3 Per discussion on today's call (July 14), Max would like the com.jboss.jbds.product.extra.feature to be hidden from the update site. Affects both 4.1 and 5.0 Extras update sites. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
5
0 / 0

[JBoss JIRA] Created: (JBDS-1784) Upgrade bundled EAP to 5.1.1

by Lukas Jungmann (JIRA)

Upgrade bundled EAP to 5.1.1 ---------------------------- Key: JBDS-1784 URL: https://issues.jboss.org/browse/JBDS-1784 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: Build Reporter: Lukas Jungmann Assignee: Nick Boldt since EAP 5.1.1 is about to be released we should try to get to JBDS4.1.0GA -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

4
8
0 / 0

[JBoss JIRA] Created: (JBDS-1709) Unable to install BPEL extras

by Libor Zoubek (JIRA)

Unable to install BPEL extras ----------------------------- Key: JBDS-1709 URL: https://issues.jboss.org/browse/JBDS-1709 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: updatesite Affects Versions: 4.1.0.CR2 Reporter: Libor Zoubek Priority: Blocker Fix For: 4.1.0.CR2 I cannot install BPEL extra plugins from http://www.qa.jboss.com/binaries/RHDS/updates/development/4.1.0.CR2_extras/ on top of http://machydra.brq.redhat.com/www.qa.jboss.com/binaries/RHDS/builds/deve... {noformat} Cannot complete the install because one or more required items could not be found. Software being installed: BPEL Editor (Certified) 1.0.0.v20110705-1603-H948-CR2 (com.jboss.jbds.bpel.feature.feature.group 1.0.0.v20110705-1603-H948-CR2) Missing requirement: BPEL Editor (Certified) 1.0.0.v20110705-1603-H948-CR2 (com.jboss.jbds.bpel.feature.feature.group 1.0.0.v20110705-1603-H948-CR2) requires 'com.jboss.jbds.bpel.examples 0.0.0' but it could not be found {noformat} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

4
12
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 July 2011