April 2011 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-4792) CA works wrong with installed maven's plug-ins for xhtml pages

by Yura Zhishko (JIRA)

CA works wrong with installed maven's plug-ins for xhtml pages -------------------------------------------------------------- Key: JBIDE-4792 URL: https://jira.jboss.org/jira/browse/JBIDE-4792 Project: Tools (JBoss Tools) Issue Type: Bug Components: common, jsp/jsf/xml source editing Affects Versions: 3.1.0.M3 Environment: Eclipse 3.5 win_32 with DTP, EMF, XSD, GEF, WTP plug-ins installed. Maven plug-ins were installed from http://m2eclipse.sonatype.org/update/ update site (exclude Maven SCM handler for Subclipse and Maven Integration for AJDT) JBT were installed from http://download.jboss.org/jbosstools/updates/nightly/trunk/ update site. Reporter: Yura Zhishko Assignee: Alexey Kazakov 1) Create JSF Kick Start Project with Facelets 2) Open inputName.xhtml 3) Call CA as shown on screenshot-1 ASSERT: CA should appear with JSF HTML tags proposals ASSERT FAILED: There is no any proposals for JSF HTML tags in CA. This situation is reproducible only for maven configuration (screenshot-2). CA works only for jsp tags, but it doesn't see tags from taglib definitions. If we have no maven plug-ins installed, there are no jsp tags in proposal list, but all tags from taglib definitions are there. -- 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, 3 months

6
8
0 / 0

[JBoss JIRA] Created: (JBIDE-4764) OpenOns don't work for xhtml pages with installed maven's plug-ins.

by Yura Zhishko (JIRA)

OpenOns don't work for xhtml pages with installed maven's plug-ins. ------------------------------------------------------------------- Key: JBIDE-4764 URL: https://jira.jboss.org/jira/browse/JBIDE-4764 Project: JBoss Tools Issue Type: Bug Components: common, jsp/jsf/xml source editing, Visual Page Editor core Affects Versions: 3.1.0.M3 Environment: Eclipse 3.5 win_32 with DTP, EMF, XSD, GEF, WTP plug-ins installed. Maven plug-ins were installed from http://m2eclipse.sonatype.org/update/ update site (exclude Maven SCM handler for Subclipse and Maven Integration for AJDT) JBT were installed from http://download.jboss.org/jbosstools/updates/nightly/trunk/ update site. Reporter: Yura Zhishko Assignee: Alexey Kazakov Priority: Critical 1) Create new JSF kick start Project with Facelets 2) Open inputName.xhtml with JBossTools editor 3) Try to make Open-On on a "/templates/common.xhtml" link RESULT: Nothing. Open-On doesn't work. The possible reason is a conflict with Doxia Xhtml Editor. When we try to make Open-On in this editor an exception is thrown: java.lang.AbstractMethodError at org.eclipse.mylyn.internal.tasks.ui.TasksUiPlugin$11.run(TasksUiPlugin.java:1164) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.runtime.Platform.run(Platform.java:888) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:48) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) at org.eclipse.mylyn.internal.tasks.ui.TasksUiPlugin.getRepositoryForResource(TasksUiPlugin.java:1157) at org.eclipse.mylyn.tasks.ui.AbstractTaskHyperlinkDetector.getTaskRepository(AbstractTaskHyperlinkDetector.java:166) at org.eclipse.mylyn.tasks.ui.AbstractTaskHyperlinkDetector.getTaskRepositories(AbstractTaskHyperlinkDetector.java:130) at org.eclipse.mylyn.internal.tasks.ui.editors.TaskHyperlinkDetector.detectHyperlinks(TaskHyperlinkDetector.java:38) at org.eclipse.mylyn.tasks.ui.AbstractTaskHyperlinkDetector.detectHyperlinks(AbstractTaskHyperlinkDetector.java:93) at org.eclipse.ui.texteditor.HyperlinkDetectorRegistry$HyperlinkDetectorDelegate.detectHyperlinks(HyperlinkDetectorRegistry.java:80) at org.eclipse.jface.text.hyperlink.HyperlinkManager.findHyperlinks(HyperlinkManager.java:263) at org.eclipse.jface.text.hyperlink.HyperlinkManager.mouseMove(HyperlinkManager.java:439) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:199) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3880) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3473) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194) 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:368) 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:585) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514) at org.eclipse.equinox.launcher.Main.run(Main.java:1311) at org.eclipse.equinox.launcher.Main.main(Main.java:1287) -- 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, 3 months

8
23
0 / 0

[JBoss JIRA] Created: (JBDS-1525) Windows 7 64-bit with 64-bit JVM compatible build of JBDS/JBoss Tools

by Burr Sutter (JIRA)

Windows 7 64-bit with 64-bit JVM compatible build of JBDS/JBoss Tools --------------------------------------------------------------------- Key: JBDS-1525 URL: https://issues.jboss.org/browse/JBDS-1525 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Reporter: Burr Sutter This includes both the installer https://issues.jboss.org/browse/JBDS-1379 Identify the components/features/plug-ins that are unable to run on a 64-bit JVM on 64-bit Windows and remove them. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

6
9
0 / 0

[JBoss JIRA] Created: (JBIDE-3235) Missing properties view for servers elements

by Max Rydahl Andersen (JIRA)

Missing properties view for servers elements -------------------------------------------- Key: JBIDE-3235 URL: https://jira.jboss.org/jira/browse/JBIDE-3235 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Reporter: Max Rydahl Andersen Fix For: 3.0.0.cr1 Before I could directly edit properties for ports in properties view. Now I need to right click and choose Change Value and get a non-standard edit in the tree. This I could probably live with if I could just double click the value and edit it like in properties view. Properties view was though also nice to give other details than just access to edit. i.e.. I could copy values to get the value of file names etc. I can't copy elements from the tree and get a textual representation. -- 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, 3 months

5
11
0 / 0

[JBoss JIRA] Created: (JBDS-1509) JBDS thread looping after call to OS - Seen in DTP connection profile-setting

by Paul Nittel (JIRA)

JBDS thread looping after call to OS - Seen in DTP connection profile-setting ----------------------------------------------------------------------------- Key: JBDS-1509 URL: https://issues.jboss.org/browse/JBDS-1509 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: integration Affects Versions: 4.0.0.CR1 Environment: JBDS 4.0 H65 CR1, Fedora 12, Java SE Runtime Environment (build 1.6.0_21-b06) Reporter: Paul Nittel While testing Teiid Designer, I found the software wold go into a loop when I was interacting with the new connection profile process. The point at which the looping started was sonewhat variable, but seemed repeatable within the new CP set of dialogs. To simplify things, I started JBDS and went to the Database Development perspective (rather than Teiid Designer) and stepped through the new CP process. While completing the database connection information, the looping began. Here's part of the stack trace from running it in debug: Thread [main] (Suspended) OS.Call(int, int, int, int) line: not available [native method] Display.sleep() line: 4021 WizardDialog(Window).runEventLoop(Shell) line: 826 WizardDialog(Window).open() line: 801 NewProfileAction(AddProfileViewAction).run() line: 246 NewProfileAction(Action).runWithEvent(Event) line: 498 ActionContributionItem.handleWidgetSelection(Event, boolean) line: 584 ActionContributionItem.access$2(ActionContributionItem, Event, boolean) line: 501 ActionContributionItem$5.handleEvent(Event) line: 411 EventTable.sendEvent(Event) line: 84 MenuItem(Widget).sendEvent(Event) line: 1258 Display.runDeferredEvents() line: 3540 Display.readAndDispatch() line: 3161 Workbench.runEventLoop(Window$IExceptionHandler, Display) line: 2640 Workbench.runUI() line: 2604 Workbench.access$4(Workbench) line: 2438 Workbench$7.run() line: 671 Realm.runWithDefault(Realm, Runnable) line: 332 Workbench.createAndRunWorkbench(Display, WorkbenchAdvisor) line: 664 PlatformUI.createAndRunWorkbench(Display, WorkbenchAdvisor) line: 149 IDEApplication.start(IApplicationContext) line: 115 EclipseAppHandle.run(Object) line: 196 EclipseAppLauncher.runApplication(Object) line: 110 EclipseAppLauncher.start(Object) line: 79 EclipseStarter.run(Object) line: 369 EclipseStarter.run(String[], Runnable) line: 179 NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method] NativeMethodAccessorImpl.invoke(Object, Object[]) line: 39 DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 25 Method.invoke(Object, Object...) line: 597 Main.invokeFramework(String[], URL[]) line: 619 Main.basicRun(String[]) line: 574 Main.run(String[]) line: 1407 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

3
4
0 / 0

[JBoss JIRA] Created: (JBDS-1600) Creating mysql data source creates wrong JAR reference

by Peter Larsen (JIRA)

Creating mysql data source creates wrong JAR reference ------------------------------------------------------ Key: JBDS-1600 URL: https://issues.jboss.org/browse/JBDS-1600 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Environment: RHEL6 Reporter: Peter Larsen Fix For: 4.0.0.GA When adding a driver, for instance mySQL, to JBDS, the dialog puts a wrong reference to the JAR file which needs to be corrected by the user. If there's no automatic way to detect the location my the driver file, I suggest changing the dialog so the user is told to locate the file instead of hiding the option and having the user correct auto-generated material. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

4
12
0 / 0

[JBoss JIRA] Created: (JBDS-1557) Errors in JBoss Server Manager Reference Guide

by Vlado Pakan (JIRA)

Errors in JBoss Server Manager Reference Guide ---------------------------------------------- Key: JBDS-1557 URL: https://issues.jboss.org/browse/JBDS-1557 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: Doc - JBossAS Affects Versions: 4.0.0.CR1 Reporter: Vlado Pakan There are these errors in JBoss Server Manager Reference Guide http://download.jboss.org/jbosstools/nightly-docs/en/as/html/index.html: Chapter 1.1 - wrong link label "runtimes_servers" Chapter 2.1.2. - wrong screenshot dialog UI was changed update also related text of chapter Missing icon after "Reset Default Button " above Figure 2.12. Figure 2.13 - Added Group "Server Behaviour" add also related descritpion Figure 3.15., 3.16., 3.20. - obsolete screenshots add description of changes Figure 4.1. - obsolete new tree item "Filter" added Figure 4.3. - new facesets added update also descritpion Figure 4.4. - new facesets Figure 5.5. - there is no menu item "Deploy To Server" in package explorer Chapter 5.1.2. - Deploying single files is maybe obsolete Chapter 6.1 - link to JBoss TPTP profile feature at http://www.jboss.org/tools/download/stable is not working there is no update site on mentioned URL -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

5
15
0 / 0

[JBoss JIRA] Created: (TOOLSDOC-140) Document Externilize string wizard for JSF pages

by Maxim Areshkau (JIRA)

Document Externilize string wizard for JSF pages ------------------------------------------------ Key: TOOLSDOC-140 URL: https://issues.jboss.org/browse/TOOLSDOC-140 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JSF Tools Reference Guide Affects Versions: 3.x-Helios Reporter: Maxim Areshkau Assignee: Isaac Rooskov Externilize string wizard has been added to jsf tools. So this should be documented https://issues.jboss.org/browse/JBIDE-6287 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

6
6
0 / 0

[JBoss JIRA] Created: (JBIDE-4167) Add support for RestEasy as a Project Facet

by Joao Paulo Viragine (JIRA)

Add support for RestEasy as a Project Facet ------------------------------------------- Key: JBIDE-4167 URL: https://jira.jboss.org/jira/browse/JBIDE-4167 Project: Tools (JBoss Tools) Issue Type: Feature Request Environment: JBDS 2.0.0.GA Reporter: Joao Paulo Viragine Priority: Minor If project is a Dinamic Web Project, JBDS should include all required libs and all modification in web.xml (as described here: http://www.jboss.org/file-access/default/members/resteasy/freezone/docs/1...) If project is a Seam Web Project, include required libs as described here: http://docs.jboss.com/seam/2.1.1.GA/reference/en-US/html_single/#d0e21523 -- 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, 3 months

3
3
0 / 0

[JBoss JIRA] Created: (JBDS-1634) Detail what platforms and OS requirements are needed for JBDS 5

by Nick Boldt (JIRA)

Detail what platforms and OS requirements are needed for JBDS 5 --------------------------------------------------------------- Key: JBDS-1634 URL: https://issues.jboss.org/browse/JBDS-1634 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Reporter: Nick Boldt We already have installers for the following 5 platforms: Lin32/64 OSX Cocoa 32/64 Win32 Additionally, Win64 (Assume WinXP and Win7) has been requested: * https://issues.jboss.org/browse/JBIDE-2720 * https://issues.jboss.org/browse/JBDS-411 * https://issues.jboss.org/browse/JBDS-1379 All the above ought to be contained in a single JBDS JIRA, including mentioning underlying platform prereqs (eg., on linux, need gtk2 installed [0], [1]) [0] http://www.eclipse.org/projects/project-plan.php?projectid=eclipse#target... (Eclipse 3.7 / JBT 3.3 / JBDS 5) [1] http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclip... (Eclipse 3.6 / JBT 3.2 / JBDS 4.x) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

10
17
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 April 2011