June 2011 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-6369) Should support auto download of new container for Arquillian

by Aslak Knutsen (JIRA)

Should support auto download of new container for Arquillian ------------------------------------------------------------ Key: JBIDE-6369 URL: https://jira.jboss.org/browse/JBIDE-6369 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: testing Reporter: Aslak Knutsen This can be done using maven, but Tools needs some way to know which containers exists as they can be located in multiple repos and not necessarily a part of Arquillian project. -- 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

14 years, 6 months

11
15
0 / 0

[JBoss JIRA] Created: (TOOLSDOC-163) Insufficient instructions to configure other AS instance

by Joshua Wulf (JIRA)

Insufficient instructions to configure other AS instance -------------------------------------------------------- Key: TOOLSDOC-163 URL: https://issues.jboss.org/browse/TOOLSDOC-163 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Bug Security Level: Public (Everyone can see) Components: Getting Started Guide Reporter: Joshua Wulf Assignee: Isaac Rooskov In http://docs.redhat.com/docs/en-US/JBoss_Developer_Studio/4.0/html-single/... there are no instructions on the security settings needed to be able to deploy apps to an "other JBoss AS Server" using JBDevStudio. It seems that some particular configuration is needed to allow eclipse to deploy the app. This should be detailed. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-8855) Properties Editor doesn't reflect external changes to properties file

by Vlado Pakan (JIRA)

Properties Editor doesn't reflect external changes to properties file --------------------------------------------------------------------- Key: JBIDE-8855 URL: https://issues.jboss.org/browse/JBIDE-8855 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.2.1.M1 Environment: jbdevstudio-product-linux-gtk-4.1.0.v201105011951R-H359-M1, linux 32bit, java sun jdk 1.6_24 Reporter: Vlado Pakan Create project with .properties file Scenario 1: - open .properties file with JBoss Tools Properties Editor - remove .properties file from project via OS command - click on .properties file in JBDS - file disappear, expected behavior is to display dialog saying that file was deleted and asking if changes should be saved Scenario 2: - open .properties file with JBoss Tools Properties Editor - make some changes to .properties file via JBoss Tools Properties Editor and do not save them - make some changes to .properties file via external editor and save them - click on .properties file in JBDS - dialog informing that .properties file was externally modified and asking user if he wants to reload file is displayed - either user choose yes or no from this dialog changes are reloaded, expected behavior is that when user says no to reload changes changes are not reloaded -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

6
5
0 / 0

[JBoss JIRA] Created: (JBIDE-910) Servlet Generator for Dynamic Web Project is creating errornous web.xml files

by Steve Davidson (JIRA)

Servlet Generator for Dynamic Web Project is creating errornous web.xml files ----------------------------------------------------------------------------- Key: JBIDE-910 URL: http://jira.jboss.com/jira/browse/JBIDE-910 Project: JBoss Tools Issue Type: Bug Components: JBoss Tools Core Affects Versions: 2.0.0.Beta3 Environment: Windows XP Professionial SP2 Reporter: Steve Davidson When creating a Servlet using the New File - Servlet wizard in a Dynamic Web Project in a clean workspace, the web.xml file is not properly created. Specifically, this is what gets generated; <?xml version="1.0" encoding="UTF-8"?> <web-app id="WebApp_ID" version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"> <display-name> DemoFlaw</display-name> <servlet> <description> </description> <display-name> DemoServlet</display-name> <servlet-name>DemoServlet</servlet-name> <servlet-class> org.ccccd.webone.DemoServlet</servlet-class> </servlet> <servlet-mapping> <servlet-name>DemoServlet</servlet-name> <url-pattern>/DemoServlet</url-pattern> </servlet-mapping> <welcome-file-list> <welcome-file>index.html</welcome-file> <welcome-file>index.htm</welcome-file> <welcome-file>index.jsp</welcome-file> <welcome-file>default.html</welcome-file> <welcome-file>default.htm</welcome-file> <welcome-file>default.jsp</welcome-file> </welcome-file-list> </web-app> The extra whitespace at the end of the start tag <servlet-class> causes the deployment to fail. This is occuring on 100% of the computers in the Java Web Class that I am teaching. -Steve -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

4
7
0 / 0

[JBoss JIRA] Created: (JBIDE-6177) More convenient ant based examples import

by Jiri Peterka (JIRA)

More convenient ant based examples import ----------------------------------------- Key: JBIDE-6177 URL: https://jira.jboss.org/jira/browse/JBIDE-6177 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Archives Affects Versions: 3.1.0.GA Reporter: Jiri Peterka Fix For: 3.2.next Importing EAP and SOA ant based examples (not JBT examples) is quite uncomfortable (importing through file system). More advanced way should be provided for these imports. It should be at lease able to create project and perform basic project setting. -- 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
17
0 / 0

[JBoss JIRA] Created: (JBIDE-2726) Incorrect behavior of Server properties > Ports Monitoring

by Aliaksey Nis (JIRA)

Incorrect behavior of Server properties > Ports Monitoring ---------------------------------------------------------- Key: JBIDE-2726 URL: https://jira.jboss.org/jira/browse/JBIDE-2726 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.0.0.alpha Environment: WindowsXP SP2 JBoss Tools Version: 3.0.0.Alpha1 Build id: 200809010011-nightly Build date: 01 september 2008 JDK 1.5_08 Reporter: Aliaksey Nis Priority: Optional EXECUTE: Open Server view. EXECUTE: Right click on Server > Properties. EXECUTE: Select Monitoring. Press Add button. EXECUTE: Add port number in "Monitor port". Try to select something from drop-down menu "Content". FAILURE: Content menu is empty. But Ok button is enabled. When Ok button pressed - nothing happens (except wizard closing). -- 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

5
5
0 / 0

[JBoss JIRA] Created: (JBDS-1677) Server cannot be saved for the following reasons: One or more ports have an invalid value

by Rick Wagner (JIRA)

Server cannot be saved for the following reasons: One or more ports have an invalid value ----------------------------------------------------------------------------------------- Key: JBDS-1677 URL: https://issues.jboss.org/browse/JBDS-1677 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: integration Affects Versions: 4.0.0.GA Environment: JBDS running with a SOA-P server Reporter: Rick Wagner Bug is similar to what's described in JBIDE-5263. The user goes to save artifacts he is given a dialogue with the text "Server cannot be saved for the following reasons: One or more ports have an invalid value". This ticket differs from JBIDE-5263 in that the user is a Windows user, not Mac. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

5
10
0 / 0

[JBoss JIRA] Created: (JBIDE-9174) GenericExporter#testPropertySet() fails because of unclosed input stream

by Dmitry Geraskov (JIRA)

GenericExporter#testPropertySet() fails because of unclosed input stream ------------------------------------------------------------------------ Key: JBIDE-9174 URL: https://issues.jboss.org/browse/JBIDE-9174 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: 3.3.0.M2 Reporter: Dmitry Geraskov Assignee: Dmitry Geraskov Fix For: 3.3.0.M3 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

7
8
0 / 0

[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, 6 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, 6 months

8
23
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 June 2011