July 2011 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-8919) Recognize and define ESB Runtime from SOA-P product

by Vlado Pakan (JIRA)

Recognize and define ESB Runtime from SOA-P product --------------------------------------------------- Key: JBIDE-8919 URL: https://issues.jboss.org/browse/JBIDE-8919 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: runtimes Affects Versions: 3.2.1.M1 Reporter: Vlado Pakan Assignee: Snjezana Peco When searching for runtimes (Menu Window > Preferences > JBoss Tools > JBoss Tools Runtimes) SOA-P is properly recognized as SOA-P Runtime but contained ESB Runtime is not added to defined ESB Runtimes. Doesn't work with these SOA-P versions 5.0.2, 5.1.0, 4.3.CP.04. JBT should automatically detect ESB Runtime within SOA-P product and define it for later use. Has to be working also with SOA-P Standalone products. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

8
21
0 / 0

[JBoss JIRA] Created: (JBDS-1655) Recognize and define Drools Runtime from SOA-P standalone product during installation

by Vlado Pakan (JIRA)

Recognize and define Drools Runtime from SOA-P standalone product during installation ------------------------------------------------------------------------------------- Key: JBDS-1655 URL: https://issues.jboss.org/browse/JBDS-1655 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Affects Versions: 4.1.0.M1 Reporter: Vlado Pakan When searching for runtimes during installation SOA-P is properly recognized as SOA-P Runtime but contained ESB Runtime is not added to defined ESB Runtimes when installed JBDS is run. Doesn't work with these SOA-P versions 5.0.2, 5.1.0, 4.3.CP.04. JDBS should automatically detect ESB Runtime within SOA-P product during installation and define it for later use. Has to be working also with SOA-P Standalone products. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

10
15
0 / 0

[JBoss JIRA] Created: (JBIDE-3113) Consolidation/clean up of preference pages

by John Graham (JIRA)

Consolidation/clean up of preference pages ------------------------------------------ Key: JBIDE-3113 URL: https://jira.jboss.org/jira/browse/JBIDE-3113 Project: Tools (JBoss Tools) Issue Type: Bug Components: common, drools, jbpm Affects Versions: 3.0.0.cr1 Environment: JBossTools-3.0.0.CR1-N200811050757-ALL-linux-gtk Reporter: John Graham Priority: Minor JBT currently has three preference page categories: 1. Drools 2. JBoss jBPM 3. JBoss Tools The first two should be listed as subsections of the JBoss Tools category. Alternatively, I suggest that the top level category should just be JBoss: - JBoss -- Drools -- jBPM Also, the JBoss Tools and JBoss jBPM top level pages in each of these categories do not expose preferences, but rather the default buttons or simply a label ("JBoss Tools"). These top level pages should show overall JBT preferences. See the Java preferences or other examples in the Eclipse platform for this idea. (Also note that the DTP 1.6.x way of doing this is wrong... ;) ) -- 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

14 years, 6 months

6
19
0 / 0

[JBoss JIRA] Created: (JBIDE-9259) Show RichFaces 4 components in Palette by default.

by Alexey Kazakov (JIRA)

Show RichFaces 4 components in Palette by default. -------------------------------------------------- Key: JBIDE-9259 URL: https://issues.jboss.org/browse/JBIDE-9259 Project: Tools (JBoss Tools) Issue Type: Task Components: JSF Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.3.0.M3 Now it's hidden by default. We should show it and hide RichFaces 3 instead. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-9408) JBoss Tools XML Editor should not format XML if the file is edited in Source tab.

by Alexey Kazakov (JIRA)

JBoss Tools XML Editor should not format XML if the file is edited in Source tab. --------------------------------------------------------------------------------- Key: JBIDE-9408 URL: https://issues.jboss.org/browse/JBIDE-9408 Project: Tools (JBoss Tools) Issue Type: Bug Components: XML Structured Editor Affects Versions: 3.3.0.M3 Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.3.x EXECUTE: Create JSF KickStart project EXECUTE: Open web.xml with JBoss Tools XML Editor EXECUTE: Re-format the text (use Ctrl+A & Ctrl+Shift+F for example) EXECUTE: Save the file EXECUTE: Change {code}<load-on-startup>1</load-on-startup>{code}to{code}<load-on-startup>some string</load-on-startup>{code} EXECUTE: Save the file {color:green}ASSERT:{color} Text keeps current format. {color:red}FAILURE:{color} The text is re-formated back. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

6
8
0 / 0

[JBoss JIRA] Created: (JBIDE-9427) "JBoss Tools Editor might not fully work in project... add JSF capabilities?" dialog appears when it should not

by Yahor Radtsevich (JIRA)

"JBoss Tools Editor might not fully work in project... add JSF capabilities?" dialog appears when it should not --------------------------------------------------------------------------------------------------------------- Key: JBIDE-9427 URL: https://issues.jboss.org/browse/JBIDE-9427 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Yahor Radtsevich "JBoss Tools Editor might not fully work in project... add JSF capabilities?" dialog may appear for HTML projects where it is unnecessary. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

6
12
0 / 0

[JBoss JIRA] Created: (JBIDE-8126) Manage Keys Dialog: should select keys and close dialog on double click

by Andre Dietisheim (JIRA)

Manage Keys Dialog: should select keys and close dialog on double click ----------------------------------------------------------------------- Key: JBIDE-8126 URL: https://issues.jboss.org/browse/JBIDE-8126 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: deltacloud Affects Versions: 3.2.0.CR1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.2.x -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

2
4
0 / 0

[JBoss JIRA] Created: (JBIDE-8290) Delete hotkey should do nothing unless all selections are DeltaCloud objects (not instances)

by Rob Stryker (JIRA)

Delete hotkey should do nothing unless all selections are DeltaCloud objects (not instances) -------------------------------------------------------------------------------------------- Key: JBIDE-8290 URL: https://issues.jboss.org/browse/JBIDE-8290 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: deltacloud Affects Versions: 3.2.0.CR1 Reporter: Rob Stryker Assignee: Andre Dietisheim Fix For: 3.2.1 I continually end up deleting my entire cloud by accident. I select a few instances, try to delete them (which is of course impossible), and quickly press enter, and then my entire cloud is removed. This is a big pain. It'd be better if the delete hotkey did nothing if the selection is not only DeltaCloud objects -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

3
7
0 / 0

[JBoss JIRA] Created: (JBIDE-8944) Unable to start eclipse after JbossTools installed

by Libor Zoubek (JIRA)

Unable to start eclipse after JbossTools installed --------------------------------------------------- Key: JBIDE-8944 URL: https://issues.jboss.org/browse/JBIDE-8944 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.3.0.M1 Reporter: Libor Zoubek Priority: Blocker Fix For: 3.3.0.M1 I've installed all features from updatesite zip on top of eclipse-jee-indigo-M6a http://download.jboss.org/jbosstools/builds/development/3.3.0.M1a/2011-05... {noformat} !SESSION 2011-05-13 09:37:08.483 ----------------------------------------------- eclipse.buildId=I20110310-1119 java.version=1.6.0_25 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US Framework arguments: -product org.eclipse.epp.package.jee.product Command-line arguments: -os linux -ws gtk -arch x86 -product org.eclipse.epp.package.jee.product !ENTRY org.teiid.designer.datatools 4 0 2011-05-13 09:37:16.097 !MESSAGE FrameworkEvent ERROR !STACK 0 java.util.zip.ZipException: Exception in opening zip file: /data/eclipse/jbosstools-3.3.0a-M1-H2359/eclipse/plugins/org.teiid.designer.datatools_7.5.0.v20110511-0152-H402-M1.jar at org.eclipse.osgi.framework.util.SecureAction.getZipFile(SecureAction.java:287) at org.eclipse.osgi.baseadaptor.bundlefile.ZipBundleFile.basicOpen(ZipBundleFile.java:87) at org.eclipse.osgi.baseadaptor.bundlefile.ZipBundleFile.getZipFile(ZipBundleFile.java:100) at org.eclipse.osgi.baseadaptor.bundlefile.ZipBundleFile.checkedOpen(ZipBundleFile.java:73) at org.eclipse.osgi.baseadaptor.bundlefile.ZipBundleFile.getEntry(ZipBundleFile.java:245) at org.eclipse.osgi.baseadaptor.BaseData.getEntry0(BaseData.java:114) at org.eclipse.osgi.baseadaptor.BaseData.getEntry(BaseData.java:105) at org.eclipse.osgi.framework.internal.core.AbstractBundle.getEntry0(AbstractBundle.java:1246) at org.eclipse.osgi.framework.internal.core.AbstractBundle.getEntry(AbstractBundle.java:1241) at org.eclipse.core.internal.registry.osgi.EclipseBundleListener.getExtensionURL(EclipseBundleListener.java:120) at org.eclipse.core.internal.registry.osgi.EclipseBundleListener.addBundle(EclipseBundleListener.java:163) at org.eclipse.core.internal.registry.osgi.EclipseBundleListener.processBundles(EclipseBundleListener.java:90) at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.onStart(RegistryStrategyOSGI.java:224) at org.eclipse.core.internal.registry.ExtensionRegistry.<init>(ExtensionRegistry.java:725) at org.eclipse.core.runtime.RegistryFactory.createRegistry(RegistryFactory.java:58) at org.eclipse.core.internal.registry.osgi.Activator.startRegistry(Activator.java:137) at org.eclipse.core.internal.registry.osgi.Activator.start(Activator.java:56) at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:711) at java.security.AccessController.doPrivileged(Native Method) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:702) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:683) at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381) at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:299) at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:440) at org.eclipse.osgi.internal.loader.BundleLoader.setLazyTrigger(BundleLoader.java:268) at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:107) at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:460) at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:216) at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:400) at org.eclipse.osgi.internal.loader.SingleSourcePackage.loadClass(SingleSourcePackage.java:35) at org.eclipse.osgi.internal.loader.MultiSourcePackage.loadClass(MultiSourcePackage.java:31) at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:473) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:429) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:417) at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107) at java.lang.ClassLoader.loadClass(ClassLoader.java:247) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:169) at org.eclipse.equinox.internal.app.Activator.start(Activator.java:55) at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:711) at java.security.AccessController.doPrivileged(Native Method) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:702) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:683) at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381) at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:299) at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:440) at org.eclipse.osgi.internal.loader.BundleLoader.setLazyTrigger(BundleLoader.java:268) at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:107) at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:460) at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:216) at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:400) at org.eclipse.osgi.internal.loader.SingleSourcePackage.loadClass(SingleSourcePackage.java:35) at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:473) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:429) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:417) at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107) at java.lang.ClassLoader.loadClass(ClassLoader.java:247) at org.eclipse.core.internal.runtime.PlatformActivator.startAppContainer(PlatformActivator.java:44) at org.eclipse.core.internal.runtime.PlatformActivator.start(PlatformActivator.java:31) at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:711) at java.security.AccessController.doPrivileged(Native Method) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:702) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:683) at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381) at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:389) at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1130) at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:559) at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:544) at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:457) at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:243) at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:438) at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:1) at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340) Caused by: java.util.zip.ZipException: error in opening zip file at java.util.zip.ZipFile.open(Native Method) at java.util.zip.ZipFile.<init>(ZipFile.java:127) at java.util.zip.ZipFile.<init>(ZipFile.java:144) at org.eclipse.osgi.framework.util.SecureAction.getZipFile(SecureAction.java:274) ... 73 more {noformat} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

7
16
0 / 0

[JBoss JIRA] Created: (JBDS-1757) JBDS50_0301: [Uncommit] (Dev) Cloud Deploy: OpenShift Flex

by mark yarborough (JIRA)

JBDS50_0301: [Uncommit] (Dev) Cloud Deploy: OpenShift Flex ---------------------------------------------------------- Key: JBDS-1757 URL: https://issues.jboss.org/browse/JBDS-1757 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: Requirements Reporter: mark yarborough -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 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 July 2011