April 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-7515) Add (optional) start/stop script to the Deploy only server

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-7515?page=com.atlassian.jira.plugin... ] Rob Stryker resolved JBIDE-7515. -------------------------------- Resolution: Done Please open a new issue for this. The ability to add start / stop scripts has been added, and so this jira must be resolved as fixed. If there are smaller bugs with the behavior, they require their own jira entries. > Add (optional) start/stop script to the Deploy only server > ---------------------------------------------------------- > > Key: JBIDE-7515 > URL: https://issues.jboss.org/browse/JBIDE-7515 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Labels: new_and_noteworthy > Fix For: 4.2.0.Beta2 > > Attachments: JBIDE-7515_1.png, JBIDE-7515_2.png, JBIDE-7515_3.png, JBIDE-7515_lc1.png, JBIDE-7515_lc2.png, JBIDE-7515_lc3.png > > > Currently the "Deploy only" server can just "deploy" - I suggest we add support for running a start (and optional) a stop script to let users start/stop what they want. > This would be a nice stop-gap feature for things like AS 7 or other runtimes out in the world until "native" integration is possible. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17211) Inform users which deployment scanner's interval they're setting

by Martin Malina (JIRA)

Martin Malina created JBIDE-17211: ------------------------------------- Summary: Inform users which deployment scanner's interval they're setting Key: JBIDE-17211 URL: https://issues.jboss.org/browse/JBIDE-17211 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: server Affects Versions: 4.2.0.Beta1 Reporter: Martin Malina You asked for a new JIRA in JBIDE-15287 so here you go :) It is possible to change the interval for the custom deployment scanners that the tools add. But the UI doesn't state this, so it seems that in fact we alter the interval even for the default deployment scanner which we don't. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17020) EAP process on remote server is not terminated when you abort a server startup

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17020?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-17020: -------------------------------- Fix Version/s: 4.2.x (was: 4.2.0.Beta2) > EAP process on remote server is not terminated when you abort a server startup > ------------------------------------------------------------------------------ > > Key: JBIDE-17020 > URL: https://issues.jboss.org/browse/JBIDE-17020 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta1 > Environment: JBDS 8.0.0.Beta1a B82 > EAP 6.2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.2.x > > > When you set up a remote server (e.g. eap 6.2) with management (without a runtime, but that shouldn't really matter here) and during startup fail to enter the correct credentials the server is stuck on Starting. If you then press the Stop button twice, the server will be shown as stopped, but in fact the process will still be running on the server. This is a bug - the process should be terminated / killed in this case. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13445) Enable possibility of deployment scanner additions for remote servers

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13445?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-13445: -------------------------------- Fix Version/s: 4.2.x (was: 4.2.0.Beta2) > Enable possibility of deployment scanner additions for remote servers > --------------------------------------------------------------------- > > Key: JBIDE-13445 > URL: https://issues.jboss.org/browse/JBIDE-13445 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.2.x > > > Currently, additions tot he deployment scanners are limited to locally running servers. This is due to a lack of API allowing accurate discovery of what folders need to be added for remote servers, specifically no way for as.core classes to discover what the remote server home is, what the remote configuration folder is, etc. There is a lack of api here, and that will need to be fixed before this issue can work. > Remember: If a remote server is not running with its management ports exposed, do not attempt to add the scanners, as the management connections will fail. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17181) Unhandled loop exception in JMX view using wf8, expose management port

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17181?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-17181: -------------------------------- Fix Version/s: 4.2.x (was: 4.2.0.Beta2) > Unhandled loop exception in JMX view using wf8, expose management port > ---------------------------------------------------------------------- > > Key: JBIDE-17181 > URL: https://issues.jboss.org/browse/JBIDE-17181 > 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.x > > > I was verifying JBIDE-13445. So I set up a remote WildFly 8.0 server using the non-management profile. > Then I wanted to expose management port to test that a custom deployment scanner is actually added. > And once I started the server, I either got plenty of Unhandled loop exceptions, or in another instance JBDS went mad and stopped responding, eating 100 % of CPU. > It turns out that this probably happens when the credentials in server editor are wrong. You are asked for the correct ones on server start, but at that point it's too late to prevent the exceptions. > Note that this applies to both WF 8 and EAP 6.2 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17181) Unhandled loop exception in JMX view using wf8, expose management port

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17181?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-17181: ------------------------------------- Please provide a stacktrace. > Unhandled loop exception in JMX view using wf8, expose management port > ---------------------------------------------------------------------- > > Key: JBIDE-17181 > URL: https://issues.jboss.org/browse/JBIDE-17181 > 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.x > > > I was verifying JBIDE-13445. So I set up a remote WildFly 8.0 server using the non-management profile. > Then I wanted to expose management port to test that a custom deployment scanner is actually added. > And once I started the server, I either got plenty of Unhandled loop exceptions, or in another instance JBDS went mad and stopped responding, eating 100 % of CPU. > It turns out that this probably happens when the credentials in server editor are wrong. You are asked for the correct ones on server start, but at that point it's too late to prevent the exceptions. > Note that this applies to both WF 8 and EAP 6.2 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17181) Unhandled loop exception in JMX view using wf8, expose management port

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17181?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-17181: -------------------------------- Summary: Unhandled loop exception in JMX view using wf8, expose management port (was: Unhandled loop exception when remote server is changed to expose management port) > Unhandled loop exception in JMX view using wf8, expose management port > ---------------------------------------------------------------------- > > Key: JBIDE-17181 > URL: https://issues.jboss.org/browse/JBIDE-17181 > 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.Beta2 > > > I was verifying JBIDE-13445. So I set up a remote WildFly 8.0 server using the non-management profile. > Then I wanted to expose management port to test that a custom deployment scanner is actually added. > And once I started the server, I either got plenty of Unhandled loop exceptions, or in another instance JBDS went mad and stopped responding, eating 100 % of CPU. > It turns out that this probably happens when the credentials in server editor are wrong. You are asked for the correct ones on server start, but at that point it's too late to prevent the exceptions. > Note that this applies to both WF 8 and EAP 6.2 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12821) component.exclusion.patterns doesn't support regex pattern

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12821?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-12821: -------------------------------- Fix Version/s: 4.2.x (was: 4.2.0.Alpha1) > component.exclusion.patterns doesn't support regex pattern > ---------------------------------------------------------- > > Key: JBIDE-12821 > URL: https://issues.jboss.org/browse/JBIDE-12821 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: maven, server > Affects Versions: 3.3.1.Final > Reporter: Sébastien Pinel > Assignee: Rob Stryker > Priority: Critical > Labels: f2f2012 > Fix For: 4.2.x > > Attachments: non-maven-webapp.zip, webapp.zip > > > Using maven-war-plugin, you can use packageIncludes/packageExcludes with a regex (e.g. http://maven.apache.org/plugins/maven-war-plugin/examples/including-exclu...). > With m2e-wtp, the property is correctly added to "org.eclipse.wst.common.component" setting file but JBoss AS tools only support 2 special characters ('*', '?'). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17180) Disable custom deployment settings for remote servers without management port exposed

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17180?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-17180: -------------------------------- Fix Version/s: 4.2.x (was: 4.2.0.Beta2) > Disable custom deployment settings for remote servers without management port exposed > ------------------------------------------------------------------------------------- > > Key: JBIDE-17180 > URL: https://issues.jboss.org/browse/JBIDE-17180 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.2.0.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.2.x > > > JBIDE-13445 added the possibility to use custom deploy dir on remote server. > {quote} > Remember: If a remote server is not running with its management ports exposed, do not attempt to add the scanners, as the management connections will fail. > {quote} > We should disable this option in such case, because right now it just adds confusion - you have a server without management port exposed and not knowing about all the details you change the deployment dir, you will end up with non-working deployment. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17103) No warning/error is shown when detected runtime fails to be added

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17103?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-17103: -------------------------------- Fix Version/s: 4.2.x (was: 4.2.0.Beta2) > No warning/error is shown when detected runtime fails to be added > ----------------------------------------------------------------- > > Key: JBIDE-17103 > URL: https://issues.jboss.org/browse/JBIDE-17103 > 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.x > > > When there is a new version of a runtime, e.g. WildFly 8.1, that is not yet supported by the tooling, runtime detection usually detects it alright, but when you then click OK, the runtime+server are not added. And there is no error anywhere at all - we should fix that. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 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 April 2014