October 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-18687) Display standalone.xml config file in 'Filesets' node of an OpenShift server

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18687?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-18687: ------------------------------------- Fix Version/s: 4.2.1.Final 4.3.x > Display standalone.xml config file in 'Filesets' node of an OpenShift server > ----------------------------------------------------------------------------- > > Key: JBIDE-18687 > URL: https://issues.jboss.org/browse/JBIDE-18687 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift, server > Affects Versions: 4.2.0.Final > Reporter: Xavier Coulon > Fix For: 4.2.1.Final, 4.3.x > > Attachments: Screenshot 2014-10-22 14.35.04.png > > > If I want to edit/review the standalone.xml config file associated with the WildFly/EAP/AS server running on OpenShift, I need to customize the Project Explorer view to reveal the {{.* resources}}, then go to {{.openshift>configuration>standalone.xml}}. > It would be much easier if this file was accessible from the Servers view, as with any local WildFly/EAP/AS server. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18687) Display standalone.xml config file in 'Filesets' node of an OpenShift server

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18687?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-18687: ------------------------------------- Component/s: server > Display standalone.xml config file in 'Filesets' node of an OpenShift server > ----------------------------------------------------------------------------- > > Key: JBIDE-18687 > URL: https://issues.jboss.org/browse/JBIDE-18687 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift, server > Affects Versions: 4.2.0.Final > Reporter: Xavier Coulon > Attachments: Screenshot 2014-10-22 14.35.04.png > > > If I want to edit/review the standalone.xml config file associated with the WildFly/EAP/AS server running on OpenShift, I need to customize the Project Explorer view to reveal the {{.* resources}}, then go to {{.openshift>configuration>standalone.xml}}. > It would be much easier if this file was accessible from the Servers view, as with any local WildFly/EAP/AS server. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18595) Investigate why we seem to not be affected by https://bugs.eclipse.org/bugs/show_bug.cgi?id=445122

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18595?page=com.atlassian.jira.plugi... ] Len DiMaggio updated JBIDE-18595: --------------------------------- Fix Version/s: 4.2.1.Final Affects Version/s: 4.2.0.Final > Investigate why we seem to not be affected by https://bugs.eclipse.org/bugs/show_bug.cgi?id=445122 > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-18595 > URL: https://issues.jboss.org/browse/JBIDE-18595 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, target-platform > Affects Versions: 4.2.0.Final > Reporter: Max Rydahl Andersen > Assignee: Len DiMaggio > Fix For: 4.2.1.Final > > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=445122 is a pretty serious bug causing havoc into any plugins that try to iterate properties as pure strings since equinox for reasons beyond me now stores non-string objects into system properties breaking the contract. > Are we not using a recent enough SR1 or are we just not bundling/using the SR1 plugins that triggers the error ? (1 is m2e logging) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18663) Overlapping text boxes on tool.org documentation page

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18663?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18663: ------------------------------------ Also tried Windows 8: {code} Chrome 38.0.2125.111 (Official Build 290379) m -- Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/38.0.2125.111 Safari/537.36 Firefox 28.0 -- Build identifier: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:28.0) Gecko/20100101 Firefox/28.0 {code} And Fedora 20: {code} Chrome 34.0.1847.116 (Official Build 260972) -- Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/34.0.1847.116 Safari/537.36 Firefox 32.0 -- Build identifier: Mozilla/5.0 (X11; Linux x86_64; rv:32.0) Gecko/20100101 Firefox/32.0 Midori 0.5.8 Fedora 20: Linux t540p-fc20-vm01 3.16.3-200.fc20.x86_64 #1 SMP Wed Sep 17 22:34:21 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux {code} Cannot reproduce. Was this on OSX? > Overlapping text boxes on tool.org documentation page > ----------------------------------------------------- > > Key: JBIDE-18663 > URL: https://issues.jboss.org/browse/JBIDE-18663 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: website > Affects Versions: 4.2.0.CR2 > Reporter: Michelle Murray > Assignee: Xavier Coulon > Fix For: 4.2.x > > Attachments: toolsorg.png > > > http://tools.jboss.org/documentation/ > How Tos, etc. text boxes are overlapping page header > !toolsorg.png! -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18663) Overlapping text boxes on tool.org documentation page

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18663?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18663: ------------------------------------ [~mmurray] on which OS and browser version are you seeing this? I just checked Firefox, Midori and Chrome on Fedora 18 and it's fine here. {code} Chrome 31.0.1650.63 Firefox 26.0 - Mozilla/5.0 (X11; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0 Midori 0.4.7 Fedora 18: Linux thunk 3.11.10-100.fc18.x86_64 #1 SMP Mon Dec 2 20:28:38 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux {code} > Overlapping text boxes on tool.org documentation page > ----------------------------------------------------- > > Key: JBIDE-18663 > URL: https://issues.jboss.org/browse/JBIDE-18663 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: website > Affects Versions: 4.2.0.CR2 > Reporter: Michelle Murray > Assignee: Xavier Coulon > Fix For: 4.2.x > > Attachments: toolsorg.png > > > http://tools.jboss.org/documentation/ > How Tos, etc. text boxes are overlapping page header > !toolsorg.png! -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18663) Overlapping text boxes on tool.org documentation page

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18663?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18663: ------------------------------- Assignee: Xavier Coulon > Overlapping text boxes on tool.org documentation page > ----------------------------------------------------- > > Key: JBIDE-18663 > URL: https://issues.jboss.org/browse/JBIDE-18663 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: website > Affects Versions: 4.2.0.CR2 > Reporter: Michelle Murray > Assignee: Xavier Coulon > Attachments: toolsorg.png > > > http://tools.jboss.org/documentation/ > How Tos, etc. text boxes are overlapping page header > !toolsorg.png! -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18663) Overlapping text boxes on tool.org documentation page

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18663?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18663: ------------------------------- Fix Version/s: 4.2.x > Overlapping text boxes on tool.org documentation page > ----------------------------------------------------- > > Key: JBIDE-18663 > URL: https://issues.jboss.org/browse/JBIDE-18663 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: website > Affects Versions: 4.2.0.CR2 > Reporter: Michelle Murray > Assignee: Xavier Coulon > Fix For: 4.2.x > > Attachments: toolsorg.png > > > http://tools.jboss.org/documentation/ > How Tos, etc. text boxes are overlapping page header > !toolsorg.png! -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17212) Server process is not killed if shutdown script fails or is empty with Deploy-only server adapter

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17212?page=com.atlassian.jira.plugi... ] Martin Malina resolved JBIDE-17212. ----------------------------------- Fix Version/s: 4.2.0.Final (was: 4.2.x) Resolution: Cannot Reproduce Bug I tried this now and it works (JBDS 8.0.0.GA). Here's what I did: Deploy-only server Startup script: "read" Shutdown script: <empty> As expected, first attempt to stop the server failed and second attempt killed the process and the server was then marked as Stopped. > Server process is not killed if shutdown script fails or is empty with Deploy-only server adapter > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-17212 > URL: https://issues.jboss.org/browse/JBIDE-17212 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.2.0.Final > > > As you said in JBIDE-7515, when you specify startup and shutdown scripts with a deploy-only server, the server process should be killed if the shutdown script fails. But that is not the case. > From JBIDE-7515: > {quote} > I left the shutdown script empty. > You said that if the shutdown script fails, the process ID will be killed. Maybe technically an empty command does not fail, but I believe in this case the running java process should still be killed and it isn't. > In fact, it doesn't work even if I put something that will fail there, e.g. "exit 1". > {quote} > The shutdown should default to process kill even if the shutdown script is empty. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-351) Create automated test for complex SOAP binding settings

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBTIS-351: --------------------------------------- Summary: Create automated test for complex SOAP binding settings Key: JBTIS-351 URL: https://issues.jboss.org/browse/JBTIS-351 Project: JBoss Tools Integration Stack Issue Type: Task Components: QE Affects Versions: 4.2.0.Beta1 Reporter: Andrej Podhradsky Assignee: Andrej Podhradsky See SWITCHYARD-2195 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18294) In runtime detection of EAP 5, when you uncheck the EAP server in the results, the seam runtime is still added

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18294?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-18294: --------------------------------------- I tend to disagree on this one - if the EAP item is collapsed (so you don't see the nested Seam runtime) and you uncheck the item, it is reasonable to expect that the checkbox applies to the item and everything hidden inside. But since this only really applies to EAP 5.x which is old, and does not apply to EAP 6.x, I'm fine with leaving it as it is. > In runtime detection of EAP 5, when you uncheck the EAP server in the results, the seam runtime is still added > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18294 > URL: https://issues.jboss.org/browse/JBIDE-18294 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection, seam2 > Affects Versions: 4.2.0.CR1 > Reporter: Martin Malina > Assignee: Snjezana Peco > Priority: Minor > Fix For: 4.2.1.Final > > > This is a followup of JBIDE-17630 which contained two issues and one is still outstanding: > When you search for runtimes and EAP 5.x (including seam) is found, by default the entry is collapsed and you can expand it to see the seam runtime included with the eap server. > If you uncheck the eap server, the seam runtime beneath will still be checked. This can be confusing. I believe checking/unchecking the eap server should affect the seam runtime as well. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
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 October 2014