July 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-12016) OpenShift Wizard - SSH2 Preferences

by Burr Sutter (JIRA)

Burr Sutter created JBIDE-12016: ----------------------------------- Summary: OpenShift Wizard - SSH2 Preferences Key: JBIDE-12016 URL: https://issues.jboss.org/browse/JBIDE-12016 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Reporter: Burr Sutter Assignee: Andre Dietisheim Attachments: Screen Shot 2012-05-25 at 10.57.18 AM.png If the end-user's .ssh directory is empty - we should provide a stronger warning for them - ideally provide a URL to some documentation/video explaining how the user can use Eclipse/JBoss Tools to create their private/public keys - so they can then upload the .pub to OpenShift. At least 10 users failed this test today and had to be "handheld" through the process. What is worse, if the end-user uploads a slightly butchered pub key - the create application phase still works but the git clone fails - with a relatively poor error message - recovery normally means having to go up to the OpenShift console, deleting the poorly created apps - getting the pub key uploaded correctly (deleting the previous one) and starting again. The fact that Eclipse could create the keys was actually unknown by the instructor's of today's class. SSH is still a nightmare for the newbie trying to use OpenShift + JBDS. -- 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
32
0 / 0

[JBoss JIRA] (JBIDE-12134) StackOverflow when importing into existing project

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-12134: ---------------------------------------- Summary: StackOverflow when importing into existing project Key: JBIDE-12134 URL: https://issues.jboss.org/browse/JBIDE-12134 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Andre Dietisheim -- 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
22
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-12230) define groups of components for migration to git

by Nick Boldt (JIRA)

13 years, 6 months

2
3
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-12145) Open twitter in internal browser

by Radim Hopp (JIRA)

Radim Hopp created JBIDE-12145: ---------------------------------- Summary: Open twitter in internal browser Key: JBIDE-12145 URL: https://issues.jboss.org/browse/JBIDE-12145 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: central Affects Versions: 3.3.0.CR1 Environment: JBT 3.3.0.CR1b Id: org.mozilla.xulrunner.gtk.linux.x86_64, Version: 1.9.2.19pre, Location: reference:file:plugins/org.mozilla.xulrunner.gtk.linux.x86_64_1.9.2.19pre/ is present in JBT java version "1.6.0_24" OpenJDK Runtime Environment (IcedTea6 1.11.1) (fedora-65.1.11.1.fc16-x86_64) OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode) Reporter: Radim Hopp Assignee: Snjezana Peco Priority: Minor Fix For: 3.3.1 Since [JBIDE-10072|https://issues.jboss.org/browse/JBIDE-10072] is twitter opened in external browser. But now, I tried to open in internal browser and everything was just fine. May by some change on twitter. Snjezana wrote in comment, that the error only happens whet xulrunner is installed. Id: org.mozilla.xulrunner.gtk.linux.x86_64, Version: 1.9.2.19pre, Location: reference:file:plugins/org.mozilla.xulrunner.gtk.linux.x86_64_1.9.2.19pre/ is present in my installation of JBT Could somebody else try it too? Thanks. -- 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
4
0 / 0

[JBoss JIRA] (JBIDE-12010) provide link to the ssh preferences in the error dialog that pops up if you clonging fails

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-12010: ---------------------------------------- Summary: provide link to the ssh preferences in the error dialog that pops up if you clonging fails Key: JBIDE-12010 URL: https://issues.jboss.org/browse/JBIDE-12010 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 3.3.0.CR1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.4.x Attachments: auth-error-no-key-in-prefs.png When cloning the git repository fails, we provide a specific error text that informs about possible actions to solve the issue. !auth-error-no-key-in-prefs.png! We should provide an error dialog that would have a link to open the ssh preferences. -- 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
3
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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues July 2012