April 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-2084) Add new status for when a deployment fails on server

by Mustafa Musaji (JIRA)

Mustafa Musaji created JBDS-2084: ------------------------------------ Summary: Add new status for when a deployment fails on server Key: JBDS-2084 URL: https://issues.jboss.org/browse/JBDS-2084 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Security Level: Public (Everyone can see) Components: servers Affects Versions: 5.0.0.Beta1 Environment: JBoss Developer Studio 5 Beta JBoss Enterprise Application 6 Beta Reporter: Mustafa Musaji Priority: Minor When deployment of an application fails on JBoss EAP, JBoss Tools doesn't recognize this as failure and continues to report the status as [Started, Synchronized]. This a request to add the ability for JBDS to report back via the console when a deployment fails due to application errors. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-8276) Suggest removing related servers when removing RSE connection

by Libor Zoubek (JIRA)

Suggest removing related servers when removing RSE connection ------------------------------------------------------------- Key: JBIDE-8276 URL: https://issues.jboss.org/browse/JBIDE-8276 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS Reporter: Libor Zoubek Assignee: Rob Stryker If a server is created using deltacloud it is related to RSE connection. If user removes RSE Connection and then tries to start server, he gets error about possibly deleted connection, which is fine. Is it possible to suggest him deleting related servers when deleting RSE Connection like it is when server runtime is deleted? -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

5
7
0 / 0

[JBoss JIRA] (JBIDE-10267) JBoss AS7 mgmt API integration tests should be run on hudson

by Andre Dietisheim (Created) (JIRA)

JBoss AS7 mgmt API integration tests should be run on hudson ------------------------------------------------------------ Key: JBIDE-10267 URL: https://issues.jboss.org/browse/JBIDE-10267 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS/Servers Affects Versions: 3.3.0.M4 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.0.Beta1 We currently have as7 integration tests, but these tests are not run on jenkins since the test does not start the server, it's expecting a running server. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

4
10
0 / 0

[JBoss JIRA] (JBIDE-11318) Put all Hudson-related scripts in a folder and poll only this one in component jobs

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-11318: -------------------------------------- Summary: Put all Hudson-related scripts in a folder and poll only this one in component jobs Key: JBIDE-11318 URL: https://issues.jboss.org/browse/JBIDE-11318 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: Build/Releng Reporter: Mickael Istria Assignee: Mickael Istria For all component jobs EXCEPT "central" (which has a dependency on a build.xml in its pom): * Put Hudson-related scripts (collect-test-results and publish.sh) in the same folder * Get jobs only poll this folder instead of the whole build/folder -> More consistency, less executions triggered by stuff that is not related to building this compoennt -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

2
19
0 / 0

[JBoss JIRA] (JBIDE-11588) Open-on of EL from Visual Page Editor works incorrectly

by Viacheslav Kabanovich (JIRA)

Viacheslav Kabanovich created JBIDE-11588: --------------------------------------------- Summary: Open-on of EL from Visual Page Editor works incorrectly Key: JBIDE-11588 URL: https://issues.jboss.org/browse/JBIDE-11588 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.3.0.Beta2 Reporter: Viacheslav Kabanovich Assignee: Yahor Radtsevich Case 1. EXECUTE: Write <p>#{user.name} works at #{employee.name}</p> in a page, where 'user' is a bean with property 'name'. EXECUTE: Find this text in Visual editor and double click against 'name' in the second instance of EL. ASSERT: Source of bean 'employee' is open with method getName() selected. FAILURE: Source of bean 'user' is open, no method is selected. Case 2. EXECUTE: <h:outputLabel value="#{user.name}" /> in a page. (or h:outputText) EXECUTE: Find this text in Visual editor and double click against 'name'. ASSERT: Source of bean 'user' is open with method getName() selected. FAILURE: Source of bean 'user' is open, but no method is selected. Methods DocbookTextTemplate.getSourceRegionForOpenOn() and AbstractEditableJsfTemplate.getSourceRegionForOpenOn() find position for open-on as TextUtil.getStartELDocumentPosition(sourceNode), which finds first occurence of '#{' and first non-space symbol after it; the exact position of double click is neglected. The two cases above can be fixed by {code} Point selection = pageContext.getSourceBuilder().getSelectionRange(); if(selection != null) { return new Region(selection.x, 0); } {code} inserted in the beginning of these methods, because double click in Visual part selects a word, so that selection in source is correct. Unfortunately, there are other cases, e.g. <h:inputText value="#{user.name}"/> (or h:commandButton, h:inputTextArea, etc.). In these cases, double click does not select a word, so that source selection will not be correct. Why? Attribute 'value' that is used for rendering these elements is often bound by EL to a bean property. I suggest that selecting/editing text in 'value' in h:inputText (as well as in all similar cases) be implemented as it is in h:outputText. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-2625) add an "application stop/application start" option to jboss server view

by Francisco Jose Peredo Noguez (JIRA)

add an "application stop/application start" option to jboss server view ----------------------------------------------------------------------- Key: JBIDE-2625 URL: https://jira.jboss.org/jira/browse/JBIDE-2625 Project: Tools (JBoss Tools) Issue Type: Feature Request Affects Versions: 2.1.2 Reporter: Francisco Jose Peredo Noguez Sometimes, and application just enters an infinte loop (because of a programming error, because it can not find a class, etc) in those cases one needs to stop all the application server but sometimes, the problem can be solved simply by stopping that particular application, fixing the problem, and starting it again, and, since one doesn't have to restart Jboss, it takes a lot less time. -- 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

13 years, 6 months

9
25
0 / 0

[JBoss JIRA] (JBIDE-11008) ASTools and ArchiveTools has empty try/catch blocks

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-11008: ----------------------------------- Summary: ASTools and ArchiveTools has empty try/catch blocks Key: JBIDE-11008 URL: https://issues.jboss.org/browse/JBIDE-11008 Project: Tools (JBoss Tools) Issue Type: Task Components: JBossAS/Servers Affects Versions: 3.3.0.Beta1 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 3.3.0.CR1 Many plugins have uncaught and unhandled nad unlogged exceptions. This needs to be handled. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
4
0 / 0

[JBoss JIRA] (JBIDE-10550) [UI][Usability] Streamline UI for server editor and all possible options

by Rob Stryker (Created) (JIRA)

[UI][Usability] Streamline UI for server editor and all possible options ------------------------------------------------------------------------ Key: JBIDE-10550 URL: https://issues.jboss.org/browse/JBIDE-10550 Project: Tools (JBoss Tools) Issue Type: Task Components: JBossAS/Servers Affects Versions: 3.3.0.M5 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 3.3.0.Beta1 The Server Editor has often been called "too busy" with unrelated settings populating it in a rather disorganized fashion. Less-often used settings, such as which pollers to use, or manually setting ports, have often been suggested that they be hidden a bit so as not to distract users. With several jiras open for adding additional settings (ex: expose management port? or, for openshift, automatically git-add new files before commit?), simply throwing them into the Server Editor would only serve to clutter it further. A uniform UI with a real design and intuitive location for new settings should be created, with clear outlines for what belongs in the server editor (very little) vs what is a more advanced setting and can be hidden (though still not too far... user should not need to go 'DIG' to find it). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

6
12
0 / 0

[JBoss JIRA] (JBIDE-9830) Option to handle deployment directories manually

by Kevin Formsma (Created) (JIRA)

Option to handle deployment directories manually ------------------------------------------------ Key: JBIDE-9830 URL: https://issues.jboss.org/browse/JBIDE-9830 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS/Servers Affects Versions: 3.3.0.M3 Environment: Eclipse Indigo Release, Windows 7 Reporter: Kevin Formsma Assignee: Rob Stryker Currently, JBoss Tools adds the deployment folder to the scanner list. When using custom deploy folders, an option to disable the automatic deployment of the folder and have the user manually configure the JBoss AS instance to scan the custom directory would be great. This option would by default, not be enabled to preserve existing behavior. The use case for this is my team uses the JBoss AS 4.2 Prefix deployment scanner to deploy items in a predetermined order. When using the custom deploy directory, the Prefix deployment scanner doesn't seem to be used. I'm more than happy to setup the scanner myself, but then the AS tries deploying the items twice. Once for my scanner, and then another for the actions of JBoss Tools. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-9794) Add a CLI batch file feature

by Scott Stark (JIRA)

Add a CLI batch file feature ---------------------------- Key: JBIDE-9794 URL: https://issues.jboss.org/browse/JBIDE-9794 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS/Servers Affects Versions: 3.3.0.M3 Environment: AS7 Reporter: Scott Stark Assignee: Rob Stryker This is a feature request to support a "CLI Batch" file that contains a collection of admin commands that will be run through the cli interface. There will need to be a remote/local notion to support the openshift case of having this file be in the application git repo and applied when pushed vs applied to a local server by invoking the cli tool. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

4
4
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 2012