July 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20397) [origin_intservice_59]Port forward to local used port

by Chunyun Chen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20397?page=com.atlassian.jira.plugi... ] Chunyun Chen updated JBIDE-20397: --------------------------------- Steps to Reproduce: 1. EXEC: make sure the port 8080 is used at local host 2. ASSERT: [chunchen@F17-CCY daily]$ ps -ef |grep jenkins jenkins 971 1 0 Jul27 ? 00:02:14 /etc/alternatives/java -Dcom.sun.akuma.Daemon=daemonized -Djava.awt.headless=true -DJENKINS_HOME=/var/lib/jenkins -jar /usr/lib/jenkins/jenkins.war --logfile=/var/log/jenkins/jenkins.log --webroot=/var/cache/jenkins/war --daemon --httpPort=8080 --ajp13Port=8009 --debug=5 --handlerCountMax=100 --handlerCountMaxIdle=20 3: EXEC:select a pod which will try to use local port 8080 -> right click 'Port Forwarding'->click 'Start All' 4. ASSERT: got below status: Name Local Port Remote Port Status 8080 8080 Started was: 1. EXEC: make sure the port 8080 is used at local host 2. ASSERT: [chunchen@F17-CCY daily]$ ps -ef |grep jenkins jenkins 971 1 0 Jul27 ? 00:02:14 /etc/alternatives/java -Dcom.sun.akuma.Daemon=daemonized -Djava.awt.headless=true -DJENKINS_HOME=/var/lib/jenkins -jar /usr/lib/jenkins/jenkins.war --logfile=/var/log/jenkins/jenkins.log --webroot=/var/cache/jenkins/war --daemon --httpPort=8080 --ajp13Port=8009 --debug=5 --handlerCountMax=100 --handlerCountMaxIdle=20 3: EXEC:select a pod which will try to use local port 8080 ->right click 'Port Forwarding'->click 'Start All' 4. ASSERT: got below status: Name Local Port Remote Port Status 8080 8080 Started > [origin_intservice_59]Port forward to local used port > ----------------------------------------------------- > > Key: JBIDE-20397 > URL: https://issues.jboss.org/browse/JBIDE-20397 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Environment: 3.0.0.CR1-v20150728-1708-B905 > Reporter: Chunyun Chen > Labels: application_wizard, openshift_v3 > > Port forward successfully even if the relevant local port is used by other process. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20397) [origin_intservice_59]Port forward to local used port

by Chunyun Chen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20397?page=com.atlassian.jira.plugi... ] Chunyun Chen updated JBIDE-20397: --------------------------------- Steps to Reproduce: 1. EXEC: make sure the port 8080 is used at local host 2. ASSERT: [chunchen@F17-CCY daily]$ ps -ef |grep jenkins jenkins 971 1 0 Jul27 ? 00:02:14 /etc/alternatives/java -Dcom.sun.akuma.Daemon=daemonized -Djava.awt.headless=true -DJENKINS_HOME=/var/lib/jenkins -jar /usr/lib/jenkins/jenkins.war --logfile=/var/log/jenkins/jenkins.log --webroot=/var/cache/jenkins/war --daemon --httpPort=8080 --ajp13Port=8009 --debug=5 --handlerCountMax=100 --handlerCountMaxIdle=20 3: EXEC:select a pod which will try to use local port 8080 --> right click 'Port Forwarding' -->click 'Start All' 4. ASSERT: got below status: Name Local Port Remote Port Status 8080 8080 Started was: 1. EXEC: make sure the port 8080 is used at local host 2. ASSERT: [chunchen@F17-CCY daily]$ ps -ef |grep jenkins jenkins 971 1 0 Jul27 ? 00:02:14 /etc/alternatives/java -Dcom.sun.akuma.Daemon=daemonized -Djava.awt.headless=true -DJENKINS_HOME=/var/lib/jenkins -jar /usr/lib/jenkins/jenkins.war --logfile=/var/log/jenkins/jenkins.log --webroot=/var/cache/jenkins/war --daemon --httpPort=8080 --ajp13Port=8009 --debug=5 --handlerCountMax=100 --handlerCountMaxIdle=20 3: EXEC:select a pod which will try to use local port 8080 -> right click 'Port Forwarding'->click 'Start All' 4. ASSERT: got below status: Name Local Port Remote Port Status 8080 8080 Started > [origin_intservice_59]Port forward to local used port > ----------------------------------------------------- > > Key: JBIDE-20397 > URL: https://issues.jboss.org/browse/JBIDE-20397 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Environment: 3.0.0.CR1-v20150728-1708-B905 > Reporter: Chunyun Chen > Labels: application_wizard, openshift_v3 > > Port forward successfully even if the relevant local port is used by other process. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20397) [origin_intservice_59]Port forward to local used port

by Chunyun Chen (JIRA)

Chunyun Chen created JBIDE-20397: ------------------------------------ Summary: [origin_intservice_59]Port forward to local used port Key: JBIDE-20397 URL: https://issues.jboss.org/browse/JBIDE-20397 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.0.CR1 Environment: 3.0.0.CR1-v20150728-1708-B905 Reporter: Chunyun Chen Port forward successfully even if the relevant local port is used by other process. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20244) server New and Noteworthy for 4.3.0.Beta2

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20244?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-20244. --------------------------------- OK, I was just checking. Thanks. Closing now. > server New and Noteworthy for 4.3.0.Beta2 > ----------------------------------------- > > Key: JBIDE-20244 > URL: https://issues.jboss.org/browse/JBIDE-20244 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: archives, jmx, server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.3.0.Beta2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If server is not listed here check if there are issues that should be added and add them. > Document the ones relevant for server by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3454) Mobile Hybrid Project not opening on the emulator

by Supriya Bharadwaj (JIRA)

[ https://issues.jboss.org/browse/JBDS-3454?page=com.atlassian.jira.plugin.... ] Supriya Bharadwaj updated JBDS-3454: ------------------------------------ Attachment: error_project29july.log Hi [~gercan], attached is the error log. Thanks - supriya > Mobile Hybrid Project not opening on the emulator > ------------------------------------------------- > > Key: JBDS-3454 > URL: https://issues.jboss.org/browse/JBDS-3454 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 9.0.0.Alpha2 > Reporter: Supriya Bharadwaj > Assignee: Gorkem Ercan > Priority: Minor > Attachments: error_project29july.log > > > I am trying to create a Mobile Hybrid project using the Mobile Hybrid Project wizard in JBoss Central. After its creation, the project does not open on the emulator. Also, if I export the project and try installing the apk file on a mobile android platform I get an "Application not installed" message. On certain environments (JBDS 9.0.0Alpha2 on RHEL 7) while trying to export the project it throws a "not an android project" error. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20129) Application wizard: Allow users to edit template parameters by double clicking

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20129?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-20129: ----------------------------------- Assignee: Andre Dietisheim (was: Fred Bricon) > Application wizard: Allow users to edit template parameters by double clicking > ------------------------------------------------------------------------------ > > Key: JBIDE-20129 > URL: https://issues.jboss.org/browse/JBIDE-20129 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: application_wizard, openshift_v3 > Fix For: 4.3.0.CR1 > > Attachments: edit-template-parameters.png > > > Steps: > # EXEC: launch v3 application wizard, select a template and get to page 2 > # EXEC: try to edit template parameters. > Result: > !edit-template-parameters.png! > You can only edit parameters by selecting them then and then hitting "Edit". > It would be handy if we could allow the user to edit via double-clicking onto items -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20370) When an Openshift project is created, make sure the Openshift Explorer is displayed

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20370?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-20370: ----------------------------------- Assignee: Fred Bricon (was: Jeff Cantrill) Resolution: Done Applied in master > When an Openshift project is created, make sure the Openshift Explorer is displayed > ------------------------------------------------------------------------------------ > > Key: JBIDE-20370 > URL: https://issues.jboss.org/browse/JBIDE-20370 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Fred Bricon > Assignee: Fred Bricon > Labels: application_wizard, openshift_v3 > Fix For: 4.3.0.CR1 > > > If I try to create a new Application on OpenShift v3, it'll create a Project first, then an application from a template on that project. Nothing shows up in Eclipse once I'm done, this is utterly confusing. At the very least, at the end, the OpenShift Explorer should be displayed, to let me know *something* happened. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20370) When an Openshift project is created, make sure the Openshift Explorer is displayed

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20370?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-20370: --------------------------------------- [~fbricon] LGTM. Merge to your hearts content. > When an Openshift project is created, make sure the Openshift Explorer is displayed > ------------------------------------------------------------------------------------ > > Key: JBIDE-20370 > URL: https://issues.jboss.org/browse/JBIDE-20370 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Fred Bricon > Assignee: Jeff Cantrill > Labels: application_wizard, openshift_v3 > Fix For: 4.3.0.CR1 > > > If I try to create a new Application on OpenShift v3, it'll create a Project first, then an application from a template on that project. Nothing shows up in Eclipse once I'm done, this is utterly confusing. At the very least, at the end, the OpenShift Explorer should be displayed, to let me know *something* happened. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3495) JBDS 9.0.0.beta is preconfigured with an Eclipse Docker tooling site

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3495?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3495: ---------------------------------- [~fbricon] [~dgolovin] this PR didn't work. Any idea how we can engage p2.inf processes LATER ? Need to cause the site to be removed, but there's p2.inf instructions for the docker.feature which is ADDING the site at the same time. Help? > JBDS 9.0.0.beta is preconfigured with an Eclipse Docker tooling site > -------------------------------------------------------------------- > > Key: JBDS-3495 > URL: https://issues.jboss.org/browse/JBDS-3495 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: updatesite > Affects Versions: 9.0.0.Beta2 > Reporter: Len DiMaggio > Assignee: Nick Boldt > Fix For: 9.0.0.CR1 > > Attachments: DockerTooling.png > > > See attached screenshot - JBDS 9.0.0.beta2 is preconfigured with this update site: > http://download.eclipse.org/linuxtools/updates-docker-nightly -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3494) JBDS 9.0.0.beta2 - is preconfigured without an update site

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3494?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-3494 at 7/28/15 9:03 PM: ----------------------------------------------------------- PR to add update site to BYOE feature: https://github.com/jbdevstudio/jbdevstudio-product/pull/327 [~dgolovin] [~fbricon] please review. was (Author: nickboldt): PR to add update site to BYOE feature: https://github.com/jbdevstudio/jbdevstudio-product/pull/327 > JBDS 9.0.0.beta2 - is preconfigured without an update site > ----------------------------------------------------------- > > Key: JBDS-3494 > URL: https://issues.jboss.org/browse/JBDS-3494 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: updatesite > Affects Versions: 9.0.0.Beta2 > Reporter: Len DiMaggio > Assignee: Nick Boldt > Fix For: 9.0.0.CR1 > > Attachments: JBDS_update.png > > > Seeing this in JBDS 9.0.0.beta2.respin-b: > There are no update sites configured - see attached screenshot. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 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 July 2015