July 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-26251) Cannot start OpenShift server adapter in Debug

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26251?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-26251: ---------------------------------- Environment: CDK F28 oc client 3.11 alpha - build from master was: CDK F28 > Cannot start OpenShift server adapter in Debug > ---------------------------------------------- > > Key: JBIDE-26251 > URL: https://issues.jboss.org/browse/JBIDE-26251 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.9.0.AM1 > Environment: CDK > F28 > oc client 3.11 alpha - build from master > Reporter: Josef Kopriva > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.9.0.AM1 > > > {code:java} > eclipse.buildId=12.9.0.AM1-v20180726-1026-B3091 > java.version=1.8.0_181 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Framework arguments: -product com.jboss.devstudio.core.product > Command-line arguments: -data file:/home/jkopriva/devstudio_B3091_testing/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product > org.jboss.tools.openshift.core > Error > Mon Jul 30 12:53:55 CEST 2018 > Could not launch server eap-app (Service) at OpenShift 3 (192.168.42.218) > com.openshift.restclient.OpenShiftException: OpenShiftBinaryCapability process exited: Error: unknown shorthand flag: 'p' in -p > Usage: > oc port-forward TYPE/NAME [LOCAL_PORT:]REMOTE_PORT [...[LOCAL_PORT_N:]REMOTE_PORT_N] [flags] > Examples: > # Listens on ports 5000 and 6000 locally, forwarding data to/from ports 5000 and 6000 in the pod > oc port-forward mypod 5000 6000 > > # Listens on port 8888 locally, forwarding to 5000 in the pod > oc port-forward mypod 8888:5000 > > # Listens on a random port locally, forwarding to 5000 in the pod > oc port-forward mypod :5000 > > # Listens on a random port locally, forwarding to 5000 in the pod > oc port-forward mypod 0:5000 > Options: > --pod-running-timeout=1m0s: The length of time (like 5s, 2m, or 3h, higher than zero) to wait until at least one pod is running > Use "oc options" for a list of global command-line options (applies to all commands). > at com.openshift.internal.restclient.capability.resources.AbstractOpenShiftBinaryCapability.checkProcessIsAlive(AbstractOpenShiftBinaryCapability.java:219) > at com.openshift.internal.restclient.capability.resources.AbstractOpenShiftBinaryCapability.startProcess(AbstractOpenShiftBinaryCapability.java:182) > at com.openshift.internal.restclient.capability.resources.AbstractOpenShiftBinaryCapability.start(AbstractOpenShiftBinaryCapability.java:176) > at com.openshift.internal.restclient.capability.resources.OpenShiftBinaryPortForwarding.forwardPorts(OpenShiftBinaryPortForwarding.java:112) > at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils$1$1.runOCBinary(PortForwardingUtils.java:148) > at org.jboss.tools.openshift.internal.core.ocbinary.OCBinaryOperation.run(OCBinaryOperation.java:29) > at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils$1.visit(PortForwardingUtils.java:150) > at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils$1.visit(PortForwardingUtils.java:1) > at com.openshift.internal.restclient.model.KubernetesResource.accept(KubernetesResource.java:94) > at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils.startPortForwarding(PortForwardingUtils.java:142) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.startPortForwarding(OpenShiftLaunchController.java:366) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController$2.onDebugChange(OpenShiftLaunchController.java:267) > at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.toggleDebugger(OpenShiftDebugMode.java:252) > at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:186) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.updateOpenShift(OpenShiftLaunchController.java:111) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:90) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:859) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:717) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:712) > at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566) > at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502) > at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:60) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26251) Cannot start OpenShift server adapter in Debug

by Josef Kopriva (JIRA)

Josef Kopriva created JBIDE-26251: ------------------------------------- Summary: Cannot start OpenShift server adapter in Debug Key: JBIDE-26251 URL: https://issues.jboss.org/browse/JBIDE-26251 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.9.0.AM1 Environment: CDK F28 Reporter: Josef Kopriva Assignee: Andre Dietisheim Priority: Critical Fix For: 4.9.0.AM1 {code:java} eclipse.buildId=12.9.0.AM1-v20180726-1026-B3091 java.version=1.8.0_181 java.vendor=Oracle Corporation BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US Framework arguments: -product com.jboss.devstudio.core.product Command-line arguments: -data file:/home/jkopriva/devstudio_B3091_testing/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product org.jboss.tools.openshift.core Error Mon Jul 30 12:53:55 CEST 2018 Could not launch server eap-app (Service) at OpenShift 3 (192.168.42.218) com.openshift.restclient.OpenShiftException: OpenShiftBinaryCapability process exited: Error: unknown shorthand flag: 'p' in -p Usage: oc port-forward TYPE/NAME [LOCAL_PORT:]REMOTE_PORT [...[LOCAL_PORT_N:]REMOTE_PORT_N] [flags] Examples: # Listens on ports 5000 and 6000 locally, forwarding data to/from ports 5000 and 6000 in the pod oc port-forward mypod 5000 6000 # Listens on port 8888 locally, forwarding to 5000 in the pod oc port-forward mypod 8888:5000 # Listens on a random port locally, forwarding to 5000 in the pod oc port-forward mypod :5000 # Listens on a random port locally, forwarding to 5000 in the pod oc port-forward mypod 0:5000 Options: --pod-running-timeout=1m0s: The length of time (like 5s, 2m, or 3h, higher than zero) to wait until at least one pod is running Use "oc options" for a list of global command-line options (applies to all commands). at com.openshift.internal.restclient.capability.resources.AbstractOpenShiftBinaryCapability.checkProcessIsAlive(AbstractOpenShiftBinaryCapability.java:219) at com.openshift.internal.restclient.capability.resources.AbstractOpenShiftBinaryCapability.startProcess(AbstractOpenShiftBinaryCapability.java:182) at com.openshift.internal.restclient.capability.resources.AbstractOpenShiftBinaryCapability.start(AbstractOpenShiftBinaryCapability.java:176) at com.openshift.internal.restclient.capability.resources.OpenShiftBinaryPortForwarding.forwardPorts(OpenShiftBinaryPortForwarding.java:112) at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils$1$1.runOCBinary(PortForwardingUtils.java:148) at org.jboss.tools.openshift.internal.core.ocbinary.OCBinaryOperation.run(OCBinaryOperation.java:29) at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils$1.visit(PortForwardingUtils.java:150) at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils$1.visit(PortForwardingUtils.java:1) at com.openshift.internal.restclient.model.KubernetesResource.accept(KubernetesResource.java:94) at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils.startPortForwarding(PortForwardingUtils.java:142) at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.startPortForwarding(OpenShiftLaunchController.java:366) at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController$2.onDebugChange(OpenShiftLaunchController.java:267) at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.toggleDebugger(OpenShiftDebugMode.java:252) at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:186) at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.updateOpenShift(OpenShiftLaunchController.java:111) at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:90) at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:859) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:717) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:712) at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566) at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502) at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:60) {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26236) Create New and Noteworthy for 4.9.0.AM2

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26236?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26236: ------------------------------- Sprint: devex #153 August 2019 > Create New and Noteworthy for 4.9.0.AM2 > --------------------------------------- > > Key: JBIDE-26236 > URL: https://issues.jboss.org/browse/JBIDE-26236 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: website > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 4.9.0.AM2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for all N&N. See subtasks below. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26248) Base New and Noteworthy for 4.9.0.AM2

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26248?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-26248: ---------------------------------- Assignee: Jeff MAURY > Base New and Noteworthy for 4.9.0.AM2 > --------------------------------------------------- > > Key: JBIDE-26248 > URL: https://issues.jboss.org/browse/JBIDE-26248 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: common, foundation, usage > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Labels: task > Fix For: 4.9.0.AM2 > > > Jeff MAURY, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Base JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Base, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Base by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-26236 #comment Create N&N for Base 4.9.0.AM2 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Base for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26248) Base New and Noteworthy for 4.9.0.AM2

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26248?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26248: ------------------------------- Labels: task (was: ) > Base New and Noteworthy for 4.9.0.AM2 > --------------------------------------------------- > > Key: JBIDE-26248 > URL: https://issues.jboss.org/browse/JBIDE-26248 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: common, foundation, usage > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Labels: task > Fix For: 4.9.0.AM2 > > > Jeff MAURY, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Base JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Base, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Base by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-26236 #comment Create N&N for Base 4.9.0.AM2 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Base for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26249) OpenShift New and Noteworthy for 4.9.0.AM2

by Jeff MAURY (JIRA)

Jeff MAURY created JBIDE-26249: ---------------------------------- Summary: OpenShift New and Noteworthy for 4.9.0.AM2 Key: JBIDE-26249 URL: https://issues.jboss.org/browse/JBIDE-26249 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: cdk, openshift Reporter: Jeff MAURY Priority: Critical Fix For: 4.9.0.AM2 Andre Dietisheim, Search for your component's New and Noteworthy issues: Queries: * [Completed OpenShift JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] If no N&N issues are found for OpenShift, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. Document the ones relevant for OpenShift by submitting a pull request against: * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... If your PR's commit comment is of the form... {code}JBIDE-26236 #comment Create N&N for OpenShift 4.9.0.AM2 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. If there is nothing new or noteworthy for OpenShift for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26249) OpenShift New and Noteworthy for 4.9.0.AM2

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26249?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-26249: ---------------------------------- Assignee: Andre Dietisheim > OpenShift New and Noteworthy for 4.9.0.AM2 > --------------------------------------------------- > > Key: JBIDE-26249 > URL: https://issues.jboss.org/browse/JBIDE-26249 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: cdk, openshift > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Priority: Critical > Labels: task > Fix For: 4.9.0.AM2 > > > Andre Dietisheim, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed OpenShift JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for OpenShift, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for OpenShift by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-26236 #comment Create N&N for OpenShift 4.9.0.AM2 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for OpenShift for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26249) OpenShift New and Noteworthy for 4.9.0.AM2

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26249?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26249: ------------------------------- Labels: task (was: ) > OpenShift New and Noteworthy for 4.9.0.AM2 > --------------------------------------------------- > > Key: JBIDE-26249 > URL: https://issues.jboss.org/browse/JBIDE-26249 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: cdk, openshift > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Priority: Critical > Labels: task > Fix For: 4.9.0.AM2 > > > Andre Dietisheim, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed OpenShift JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for OpenShift, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for OpenShift by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-26236 #comment Create N&N for OpenShift 4.9.0.AM2 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for OpenShift for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26250) JSF New and Noteworthy for 4.9.0.AM2

by Jeff MAURY (JIRA)

Jeff MAURY created JBIDE-26250: ---------------------------------- Summary: JSF New and Noteworthy for 4.9.0.AM2 Key: JBIDE-26250 URL: https://issues.jboss.org/browse/JBIDE-26250 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: jsp/jsf/xml/html-source-editing, jsf Reporter: Jeff MAURY Priority: Critical Fix For: 4.9.0.AM2 Jeff MAURY, Search for your component's New and Noteworthy issues: Queries: * [Completed JSF JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] If no N&N issues are found for JSF, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. Document the ones relevant for JSF by submitting a pull request against: * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... If your PR's commit comment is of the form... {code}JBIDE-26236 #comment Create N&N for JSF 4.9.0.AM2 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. If there is nothing new or noteworthy for JSF for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26250) JSF New and Noteworthy for 4.9.0.AM2

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26250?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-26250: ---------------------------------- Assignee: Jeff MAURY > JSF New and Noteworthy for 4.9.0.AM2 > --------------------------------------------------- > > Key: JBIDE-26250 > URL: https://issues.jboss.org/browse/JBIDE-26250 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: jsf, jsp/jsf/xml/html-source-editing > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Labels: task > Fix For: 4.9.0.AM2 > > > Jeff MAURY, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed JSF JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for JSF, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for JSF by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-26236 #comment Create N&N for JSF 4.9.0.AM2 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for JSF for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 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 2018