October 2014 - jbosstools-issues - Jboss List Archives

[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)

10 years, 1 month

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)

10 years, 1 month

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)

10 years, 1 month

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)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-18274) AS7/WildFly8/EAP6 with oracle java 7 fails to start when bound to your hostname

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18274?page=com.atlassian.jira.plugi... ] Martin Malina resolved JBIDE-18274. ----------------------------------- Fix Version/s: 4.2.0.Final (was: 4.3.0.Alpha1) Resolution: Cannot Reproduce Bug I can no longer reproduce this (JBDS 8.0.0.GA + WildFly 8.1). I assume my machine must have been messed up somehow. > AS7/WildFly8/EAP6 with oracle java 7 fails to start when bound to your hostname > ------------------------------------------------------------------------------- > > Key: JBIDE-18274 > URL: https://issues.jboss.org/browse/JBIDE-18274 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.CR1 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.2.0.Final > > Attachments: server-adapter.png, server-editor.png, server-logs.png, server-runtime.png > > > This is a follow up of JBIDE-17935 . > Previously, Rob fixed this: > {quote} > I've surprisingly been able to replicate this and it's a race-condition. I'll need to synchronize some variables in this class here. > {quote} > But in this rare case it still fails for me. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3203) Server runtime not listed to export unless used once

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3203?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3203: ------------------------------------------- I think it is by design but lets check with Rob, [~rob.stryker] care to comment? > Server runtime not listed to export unless used once > ---------------------------------------------------- > > Key: JBDS-3203 > URL: https://issues.jboss.org/browse/JBDS-3203 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: server > Affects Versions: 7.1.1.GA, 8.0.0.GA > Reporter: Mustafa Musaji > Assignee: Rob Stryker > Priority: Minor > > If you add a JBoss Server Runtime to JBDS and then try to export that launch configuration, it doesn't show up in the list of available runtime to export. > You have to start the server at least once before the runtime shows up in the list that is available to export. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3203) Server runtime not listed to export unless used once

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3203?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3203: -------------------------------------- Assignee: Rob Stryker (was: Max Rydahl Andersen) > Server runtime not listed to export unless used once > ---------------------------------------------------- > > Key: JBDS-3203 > URL: https://issues.jboss.org/browse/JBDS-3203 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: server > Affects Versions: 7.1.1.GA, 8.0.0.GA > Reporter: Mustafa Musaji > Assignee: Rob Stryker > Priority: Minor > > If you add a JBoss Server Runtime to JBDS and then try to export that launch configuration, it doesn't show up in the list of available runtime to export. > You have to start the server at least once before the runtime shows up in the list that is available to export. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-18672) cannot run ionic tabs (the default) app with cordovasim

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18672?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-18672: -------------------------------- Fix Version/s: 4.2.1.Final 4.3.0.Alpha1 > cannot run ionic tabs (the default) app with cordovasim > ------------------------------------------------------- > > Key: JBIDE-18672 > URL: https://issues.jboss.org/browse/JBIDE-18672 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.2.0.Final > Environment: Mac OS X, JavaFX > Reporter: Max Rydahl Andersen > Assignee: Ilya Buziuk > Fix For: 4.2.1.Final, 4.3.0.Alpha1 > > > run: > ionic start ionic-demo > import ionic-demo > run as > cordova sim > try use the app, click back. > Two issues: > 1) cordova sim complains about app.appexit not being supported > 2) when trying to click do not show again I get the following in the cordovasim error log: > Outstanding resource locks detected: > ES2 Vram Pool: 51,815,392 used (19.3%), 51,815,392 managed (19.3%), 268,435,456 total > 84 total resources being managed > average resource age is 15.1 frames > 0 resources at maximum supported age (0.0%) > 16 resources marked permanent (19.0%) > 17 resources have had mismatched locks (20.2%) > 17 resources locked (20.2%) > 30 resources contain interesting data (35.7%) > 0 resources disappeared (0.0%) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3203) Server runtime not listed to export unless used once

by Mustafa Musaji (JIRA)

[ https://issues.jboss.org/browse/JBDS-3203?page=com.atlassian.jira.plugin.... ] Mustafa Musaji updated JBDS-3203: --------------------------------- Priority: Minor (was: Major) > Server runtime not listed to export unless used once > ---------------------------------------------------- > > Key: JBDS-3203 > URL: https://issues.jboss.org/browse/JBDS-3203 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: server > Affects Versions: 7.1.1.GA, 8.0.0.GA > Reporter: Mustafa Musaji > Assignee: Max Rydahl Andersen > Priority: Minor > > If you add a JBoss Server Runtime to JBDS and then try to export that launch configuration, it doesn't show up in the list of available runtime to export. > You have to start the server at least once before the runtime shows up in the list that is available to export. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3203) Server runtime not listed to export unless used once

by Mustafa Musaji (JIRA)

Mustafa Musaji created JBDS-3203: ------------------------------------ Summary: Server runtime not listed to export unless used once Key: JBDS-3203 URL: https://issues.jboss.org/browse/JBDS-3203 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: server Affects Versions: 7.1.1.GA, 8.0.0.GA Reporter: Mustafa Musaji Assignee: Max Rydahl Andersen If you add a JBoss Server Runtime to JBDS and then try to export that launch configuration, it doesn't show up in the list of available runtime to export. You have to start the server at least once before the runtime shows up in the list that is available to export. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues October 2014