May 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-14395) openshift should enable scaling by default in UI

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14395?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-14395: ---------------------------------------- Fix Version/s: 4.1.0.Beta1 > openshift should enable scaling by default in UI > ------------------------------------------------ > > Key: JBIDE-14395 > URL: https://issues.jboss.org/browse/JBIDE-14395 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Max Rydahl Andersen > Fix For: 4.1.0.Beta1 > > -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-14395) openshift should enable scaling by default in UI

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14395?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-14395: --------------------------------------------- For beta1 if openshift team says it is the expected behavior before 31st May. > openshift should enable scaling by default in UI > ------------------------------------------------ > > Key: JBIDE-14395 > URL: https://issues.jboss.org/browse/JBIDE-14395 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Max Rydahl Andersen > Fix For: 4.1.0.Beta1 > > -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-14343) jenkins password reported in creation dialog and in environment variables dont match

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14343?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-14343: ---------------------------------------- Priority: Critical (was: Major) > jenkins password reported in creation dialog and in environment variables dont match > ------------------------------------------------------------------------------------ > > Key: JBIDE-14343 > URL: https://issues.jboss.org/browse/JBIDE-14343 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.1.0.Beta1 > > Attachments: creation-log.png, creation-log.png, environment-variables.png, environment-variables.png > > > The pw as reported in the creation dialog and in the environment variables dont match (they differ from each other). > This is most likely a WATCHER issue since this is handled by the backend. I have to further investigate though (29.4.2013) -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-14343) jenkins password reported in creation dialog and in environment variables dont match

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14343?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-14343: --------------------------------------------- For Beta1 - ask openshift team if this is expected; and how the user can get admin password if the operation times out. > jenkins password reported in creation dialog and in environment variables dont match > ------------------------------------------------------------------------------------ > > Key: JBIDE-14343 > URL: https://issues.jboss.org/browse/JBIDE-14343 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.1.0.Beta1 > > Attachments: creation-log.png, creation-log.png, environment-variables.png, environment-variables.png > > > The pw as reported in the creation dialog and in the environment variables dont match (they differ from each other). > This is most likely a WATCHER issue since this is handled by the backend. I have to further investigate though (29.4.2013) -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBDS-2537) JBDS70_0318: [Commit] (Dev) (P1) JDK Warning in Installer (JRE is not good enough)

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBDS-2537?page=com.atlassian.jira.plugin.... ] Rob Stryker reassigned JBDS-2537: --------------------------------- Assignee: Denis Golovin (was: Rob Stryker) I've fixed the issues inside jbt with warnings and error checking. I suggest in the installer you add a jdk check of your own and ensure jdk is chosen. > JBDS70_0318: [Commit] (Dev) (P1) JDK Warning in Installer (JRE is not good enough) > ---------------------------------------------------------------------------------- > > Key: JBDS-2537 > URL: https://issues.jboss.org/browse/JBDS-2537 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Requirements > Affects Versions: 7.0.0.GA > Reporter: Jiri Pallich > Assignee: Denis Golovin > Priority: Blocker > Fix For: 7.0.0.Beta2 > > > Help the users that are not sure how to get JDK. Add JRE vs JDK detector at AS launch - JDK is required, getting this installed and configured inside of JBDS/Eclipse is a challenge for the newbie. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13894) 'Tail files...' dialog ignores -n parameter value

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13894?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-13894: --------------------------------------------- Cause: https://github.com/jbosstools/jbosstools-openshift/blob/master/plugins/or... The options are hardcoded. > 'Tail files...' dialog ignores -n parameter value > ------------------------------------------------- > > Key: JBIDE-13894 > URL: https://issues.jboss.org/browse/JBIDE-13894 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.0.x > Reporter: Stefan Bunciak > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.1.0.Beta1 > > Attachments: tail1.png > > > I set -n parameter to 3: > !tail1.png|thumbnail! > but the console output contains much more lines right away: > {code} > Loading.... > ==> jbosseap-6.0/logs/server.log <== > 2013/04/02 07:57:42,044 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016008: Starting weld service for deployment ROOT.war > 2013/04/02 07:57:44,331 INFO [org.jboss.web] (MSC service thread 1-2) JBAS018210: Registering web context: > 2013/04/02 07:57:48,743 INFO [org.jboss.web] (MSC service thread 1-3) JBAS018210: Registering web context: /jboss-as-helloworld-errai > 2013/04/02 07:57:48,933 INFO [org.jboss.as.server] (ServerService Thread Pool -- 35) JBAS018559: Deployed "jboss-as-helloworld-errai.war" > 2013/04/02 07:57:48,934 INFO [org.jboss.as.server] (ServerService Thread Pool -- 35) JBAS018559: Deployed "ROOT.war" > 2013/04/02 07:57:49,138 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.9.25.129:9990/management > 2013/04/02 07:57:49,141 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.9.25.129:9990 > 2013/04/02 07:57:49,141 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.0.1.GA (AS 7.1.3.Final-redhat-4) started in 67688ms - Started 319 of 462 services (140 services are passive or on-demand) > 2013/04/02 08:03:58,941 INFO [org.jboss.resteasy.cdi.CdiInjectorFactory] (http-127.9.25.129/127.9.25.129:8080-4) Found BeanManager at java:comp/BeanManager > 2013/04/02 08:03:59,130 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (http-127.9.25.129/127.9.25.129:8080-4) Deploying javax.ws.rs.core.Application: class org.jboss.tools.example.html5.rest.JaxRsActivator$Proxy$_$$_WeldClientProxy > ==> jbosseap-6.0/logs/boot.log <== > user.name = 515ac573e0b8cd1da6000005 > user.timezone = America/New_York > 07:56:45,930 DEBUG [org.jboss.as.config] VM Arguments: -D[Standalone] -XX:+TieredCompilation -Xmx256m -XX:MaxPermSize=102m -XX:+AggressiveOpts -Dorg.apache.tomcat.util.LOW_MEMORY=true -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dfile.encoding=UTF-8 -Djava.net.preferIPv4Stack=true -Djboss.node.name=binary-pipistiks.rhcloud.com -Djgroups.bind_addr=127.9.25.129 -Dorg.apache.coyote.http11.Http11Protocol.COMPRESSION=on -Dorg.jboss.boot.log.file=/var/lib/openshift/515ac573e0b8cd1da6000005/jbosseap-6.0/jbosseap-6.0/standalone/log/boot.log -Dlogging.configuration=file:/var/lib/openshift/515ac573e0b8cd1da6000005/jbosseap-6.0/jbosseap-6.0/standalone/configuration/logging.properties > 07:56:56,854 WARN [org.jboss.as.server] JBAS015883: No security realm defined for native management service; all access will be unrestricted. > 07:56:56,853 INFO [org.xnio] XNIO Version 3.0.7.GA-redhat-1 > 07:56:57,037 INFO [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http) > 07:56:57,038 WARN [org.jboss.as.server] JBAS015884: No security realm defined for http management service; all access will be unrestricted. > 07:56:56,959 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.7.GA-redhat-1 > 07:56:57,148 INFO [org.jboss.remoting] JBoss Remoting version 3.2.14.GA-redhat-1 > 07:56:57,938 INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers > {code} > I would expect the same behaviour like on linux system - to output just the specified 3 lines... -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13562) Repository is synchronized but adapter states [Started, Republish]

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13562?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-13562: ------------------------------------- state constnats are available in IServer.STATE_XXX or IServer.PUBLISH_STATE_XXX. Both servers and modules may have states (started / stopped / unknown ) or publish states (requires a full, incremental, unknown, or none publish). After a successful publish, you'd mark as NONE. setModuleState(module[], int state); sets the state next to the module (started / stopped, may also be IServer.STATE_UNKNOWN) setModulePublishState(module, IServer.PUBLISH_STATE_FULL or PUBLISH_STATE_INCREMENTAL or PUBLISH_STATE_NONE); (full indicates we still need a full publish, incremental means we require an incremental publish, none indicates the publish is now fully synchronized) setServerPublishState(int) - indicates whether the server itself requires a full / incremental / or no publish setServerState(int) - indicates whether the server is started / stopped / unknown / etc > Repository is synchronized but adapter states [Started, Republish] > ------------------------------------------------------------------ > > Key: JBIDE-13562 > URL: https://issues.jboss.org/browse/JBIDE-13562 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, server > Affects Versions: 4.1.0.Alpha1 > Reporter: Stefan Bunciak > Assignee: Rob Stryker > Fix For: 4.1.0.Beta1 > > Attachments: console.png, server.png > > -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13730) Server adapter state [Republish] although Repository is uptodate

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13730?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-13730: --------------------------------------------- If tracking branch is available, do a dirty check and set the synchronized or need republish. If tracking branch is not available, set state to unknown. > Server adapter state [Republish] although Repository is uptodate > ---------------------------------------------------------------- > > Key: JBIDE-13730 > URL: https://issues.jboss.org/browse/JBIDE-13730 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, server > Affects Versions: 4.1.0.Alpha1 > Reporter: Stefan Bunciak > Assignee: Andre Dietisheim > Fix For: 4.1.0.Beta1 > > Attachments: republishsync.png > > -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13862) Deploying project should be automatically added to OpenShift Server adapter

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13862?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-13862: ---------------------------------------- Priority: Minor (was: Major) > Deploying project should be automatically added to OpenShift Server adapter > --------------------------------------------------------------------------- > > Key: JBIDE-13862 > URL: https://issues.jboss.org/browse/JBIDE-13862 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, server > Affects Versions: 4.1.0.Alpha1 > Reporter: Stefan Bunciak > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.1.0.Beta1 > > Attachments: server.png, server1.png, server2.png > > > Deploying project is automatically added to OpenShift Server adapter after application import: > * after application import contains the deploying project: !server.png|thumbnail! > When created manually via OpenShift Explorer (Application - Create Server Adapter), the deploying project is not automatically added, even though I'm selecting the deploying project: > * !server2.png|thumbnail! *->* !server1.png|thumbnail! -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-14397) Add JRE vs JDK detector at AS launch

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14397?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-14397. --------------------------------- Assignee: Rob Stryker Fix Version/s: 4.1.0.Beta1 Resolution: Done Fixed in a linked issued > Add JRE vs JDK detector at AS launch > ------------------------------------ > > Key: JBIDE-14397 > URL: https://issues.jboss.org/browse/JBIDE-14397 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.1.0.Alpha2 > Reporter: Denis Golovin > Assignee: Rob Stryker > Fix For: 4.1.0.Beta1 > > > JDK is required, getting this installed and configured inside of JBDS/Eclipse is a challenge for the newbie -- 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

13 years

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 May 2013