July 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-816) Cannot install SwitchYard tooling from EA zip file in offline mode

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-816?page=com.atlassian.jira.plugin.... ] Paul Leacu reassigned JBTIS-816: -------------------------------- Assignee: Paul Leacu > Cannot install SwitchYard tooling from EA zip file in offline mode > ------------------------------------------------------------------ > > Key: JBTIS-816 > URL: https://issues.jboss.org/browse/JBTIS-816 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 9.0.1.CR3 > Environment: JBDS 9.1.0.GA + devstudio-integration-stack-9.0.1.CR3-earlyaccess.zip > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > > Cannot install SwitchYard tooling from EA zip file in offline mode due to missing > * org.eclipse.zest.core 1.5.100 (required by fuse tooling) > * org.eclipse.emf.compare.feature.group 2.1.0 (required by switchayrd tooling) > * org.eclipse.bpel.feature.feature.group [1.0.2,2.0.0) (required by switchyard bpel tooling) > All features mentioned above are available in devstudio-integration-stack-9.0.1.CR3.zip. So, to install all features in offline mode we need both zip files. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22817) Add Events support to Properties view

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22817?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22817: ------------------------------- Fix Version/s: 4.4.1.AM3 Labels: explorer new_and_noteworthy openshift_v3 (was: ) > Add Events support to Properties view > ------------------------------------- > > Key: JBIDE-22817 > URL: https://issues.jboss.org/browse/JBIDE-22817 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.1.AM1 > Reporter: Fred Bricon > Assignee: Jeff Cantrill > Labels: explorer, new_and_noteworthy, openshift_v3 > Fix For: 4.4.1.AM3 > > > The web console has an Events tab that lists all events for all resources. We could add the same to the Properties view. > Later, we could add support for events per resources, but that requires more work how to layout more infos. That'll be the subject of another issue -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22644) Unable to perform oc binary actions because of insecure flag

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22644?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22644: ------------------------------------------ [~jcantrill] https://github.com/openshift/openshift-restclient-java/pull/180 was merged, is this now fixed and can be resolved or is there more work to be done? > Unable to perform oc binary actions because of insecure flag > ------------------------------------------------------------ > > Key: JBIDE-22644 > URL: https://issues.jboss.org/browse/JBIDE-22644 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > > Trying to retrieve pod logs or any oc binary action results in warning of: > specifying a root certificates file with the insecure flag is not allowed > Per deads openshift dev "...it means that your kubeconfig file has a CA set, but you're trying to connect insecurely" > Persumably this requires us to make sure KUBECONFIG env var is not set when executing oc binary commands. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22644) Unable to perform oc binary actions because of insecure flag

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22644?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-22644 at 7/27/16 8:56 AM: ------------------------------------------------------------------- [~jcantrill] [#180|https://github.com/openshift/openshift-restclient-java/pull/180] was merged, is this now fixed and can be resolved or is there more work to be done? was (Author: adietish): [~jcantrill] https://github.com/openshift/openshift-restclient-java/pull/180 was merged, is this now fixed and can be resolved or is there more work to be done? > Unable to perform oc binary actions because of insecure flag > ------------------------------------------------------------ > > Key: JBIDE-22644 > URL: https://issues.jboss.org/browse/JBIDE-22644 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > > Trying to retrieve pod logs or any oc binary action results in warning of: > specifying a root certificates file with the insecure flag is not allowed > Per deads openshift dev "...it means that your kubeconfig file has a CA set, but you're trying to connect insecurely" > Persumably this requires us to make sure KUBECONFIG env var is not set when executing oc binary commands. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-123) [content assist] Template demarcation not documented [EBZ#489371]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-123?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan resolved ERT-123. ------------------------------ Resolution: Done > [content assist] Template demarcation not documented [EBZ#489371] > ----------------------------------------------------------------- > > Key: ERT-123 > URL: https://issues.jboss.org/browse/ERT-123 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Labels: General, bzira > > There appears to be some distinction between two different kinds of content assist templates. The two different kinds of templates are separated into two different files, 'default-templates.xml' and 'default-codetemplates.xml'. Both files use different context, and as such different context types. This affects the way that resolvers work on these templates. > I can't seem to find any documentation on this logic, and can't figure it out on my own. > What is the distinction? Why are templates given the contexts that they currently have? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-50) JavaScript Debugger integration tests for chromium based browsers [EBZ#486074]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-50?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-50: ---------------------------- Story Points: 20 > JavaScript Debugger integration tests for chromium based browsers [EBZ#486074] > ------------------------------------------------------------------------------ > > Key: ERT-50 > URL: https://issues.jboss.org/browse/ERT-50 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Max Rydahl Andersen > Labels: Debug, bzira > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-51) JavaScript Debugger integration tests for node.js [EBZ#486075]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-51?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-51: ---------------------------- Sprint: devex #118 July 2016 > JavaScript Debugger integration tests for node.js [EBZ#486075] > -------------------------------------------------------------- > > Key: ERT-51 > URL: https://issues.jboss.org/browse/ERT-51 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Max Rydahl Andersen > Assignee: Pavol Srna > Labels: Debug, bzira > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-109) Validation required for WebKit Protocol launch configuration [EBZ#487910]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-109?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan updated ERT-109: ----------------------------- Story Points: 5 > Validation required for WebKit Protocol launch configuration [EBZ#487910] > ------------------------------------------------------------------------- > > Key: ERT-109 > URL: https://issues.jboss.org/browse/ERT-109 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Labels: Debug, bzira > > WIP Backend must be selected before launching WebKit Debugger or it will throw exception below: > java.lang.RuntimeException: Missing 'wip backend' parameter in launch config > at org.eclipse.wst.jsdt.chromium.debug.ui.launcher.WipLaunchType.createConnectionToRemote(WipLaunchType.java:32) > at org.eclipse.wst.jsdt.chromium.debug.ui.launcher.LaunchTypeBase.launch(LaunchTypeBase.java:66) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) > at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039) > at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-51) JavaScript Debugger integration tests for node.js [EBZ#486075]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-51?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-51: ---------------------------- Story Points: 20 > JavaScript Debugger integration tests for node.js [EBZ#486075] > -------------------------------------------------------------- > > Key: ERT-51 > URL: https://issues.jboss.org/browse/ERT-51 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Max Rydahl Andersen > Assignee: Pavol Srna > Labels: Debug, bzira > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-3) Investigate defining browsers / runtimes to use for debugging [EBZ#359436]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-3?page=com.atlassian.jira.plugin.syst... ] Gorkem Ercan resolved ERT-3. ---------------------------- Resolution: Done > Investigate defining browsers / runtimes to use for debugging [EBZ#359436] > -------------------------------------------------------------------------- > > Key: ERT-3 > URL: https://issues.jboss.org/browse/ERT-3 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Max Rydahl Andersen > Priority: Trivial > Labels: 3.8_M6, Debug, bzira > Fix For: Neon (4.6) M6 > > > Akin to JDT's notion of an installed JRE (EE), we should investigate being able to define browsers (Firefox et. al.) and runtimes (node.js, Rhino, etc) that can be used to run / debug with. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 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 2016