October 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-942) Add regression test for FUSETOOLS-2177

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBTIS-942?page=com.atlassian.jira.plugin.... ] Tomáš Sedmík closed JBTIS-942. ------------------------------ Resolution: Out of Date closing as out of date issue > Add regression test for FUSETOOLS-2177 > -------------------------------------- > > Key: JBTIS-942 > URL: https://issues.jboss.org/browse/JBTIS-942 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: Fuse IDE, QE > Affects Versions: 4.4.0.Final > Reporter: Tomáš Sedmík > Assignee: Tomáš Sedmík > Fix For: 4.4.3.Final > > > see https://issues.jboss.org/browse/FUSETOOLS-2177 for details -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-813) create a regression test for FUSETOOLS-1788

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBTIS-813?page=com.atlassian.jira.plugin.... ] Tomáš Sedmík closed JBTIS-813. ------------------------------ Resolution: Out of Date closing as out of date issue > create a regression test for FUSETOOLS-1788 > ------------------------------------------- > > Key: JBTIS-813 > URL: https://issues.jboss.org/browse/JBTIS-813 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: Fuse IDE, QE > Affects Versions: 4.3.1.Final > Reporter: Tomáš Sedmík > Assignee: Tomáš Sedmík > Fix For: 4.3.1.Final > > > see https://issues.jboss.org/browse/FUSETOOLS-1788 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-740) Fuse: Add tests for Remote operations

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBTIS-740?page=com.atlassian.jira.plugin.... ] Tomáš Sedmík closed JBTIS-740. ------------------------------ Resolution: Won't Do Won't Do at the moment. Feel free to reopen this issue. > Fuse: Add tests for Remote operations > ------------------------------------- > > Key: JBTIS-740 > URL: https://issues.jboss.org/browse/JBTIS-740 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: Fuse IDE, QE > Affects Versions: 4.3.0.Final > Reporter: Tomáš Sedmík > Assignee: Tomáš Sedmík > Priority: Critical > Fix For: 4.3.1.Final > > > * connect to remote JBoss Fuse server via JMX Navigator > * try edit routes > * try tracing > * try ActiveMQ operations -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4591) Can't install com.redhat.fabric8analytics.lsp.eclipse from RH Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4591?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4591: ---------------------------------- Caused by JBIDE-24897 - work in progress there and an incomplete fix in parent pom & jbt aggregation site. > Can't install com.redhat.fabric8analytics.lsp.eclipse from RH Central > --------------------------------------------------------------------- > > Key: JBDS-4591 > URL: https://issues.jboss.org/browse/JBDS-4591 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: central, central-update > Affects Versions: 11.1.0.GA > Environment: * RHEL7 > * rh-eclipse47-devstudio-11.1-0.20171019.0637.el7.x86_64.rpm > Reporter: Lukáš Valach > Assignee: Nick Boldt > Fix For: 11.1.0.GA > > > It is not possible to install "Fabric8 Analytics Language Server Integration" from RH Central. Feature group *com.redhat.fabric8analytics.lsp.eclipse.feature.feature.group* isn't in update site. > {code} > Problems occurred while performing installation: The following connectors are not available: Fabric8 Analytics Language Server Integration (id=com.redhat.fabric8analytics.lsp.eclipse.feature.feature.group, site=https://devstudio.redhat.com/11/snapshots/updates/discovery.earlyacc...) > The following connectors are not available: Fabric8 Analytics Language Server Integration (id=com.redhat.fabric8analytics.lsp.eclipse.feature.feature.group, site=https://devstudio.redhat.com/11/snapshots/updates/discovery.earlyacc...) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-635) Add regression test for FUSETOOLS-1474

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBTIS-635?page=com.atlassian.jira.plugin.... ] Tomáš Sedmík closed JBTIS-635. ------------------------------ Resolution: Won't Do Data Transformer in Fuse Tooling will be replaced. > Add regression test for FUSETOOLS-1474 > -------------------------------------- > > Key: JBTIS-635 > URL: https://issues.jboss.org/browse/JBTIS-635 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: Fuse IDE, QE > Affects Versions: 4.0.0 > Reporter: Tomáš Sedmík > Assignee: Tomáš Sedmík > Fix For: 4.3.0.Final > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > SSIA > + classes from other projects should be inaccessible -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1177) Unknown category when specifying discovery url for Integration Stack EA

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1177?page=com.atlassian.jira.plugin... ] Andrej Podhradsky commented on JBTIS-1177: ------------------------------------------ The same error occurs with Devstudio 11.1.0.AM3 > Unknown category when specifying discovery url for Integration Stack EA > ----------------------------------------------------------------------- > > Key: JBTIS-1177 > URL: https://issues.jboss.org/browse/JBTIS-1177 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 11.1.0.Beta1 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Fix For: 11.1.0.Beta1 > > > {code} > Unknown category 'com.jboss.jbds.discovery.certification.supported.earlyaccess' referenced by connector 'jboss.integration-stack.ea.bundle.ds' declared in com.jboss.jbds.central.discovery.integration_stack.earlyaccess_11.1.0.Beta1_v20171012_1209_B62.jar_5518145992839178562.jar > {code} > I use Devstudio 11.1.0.GA-v20171017-1040-B1391 with the following lines in devstudio.ini > {code} > -Djboss.discovery.directory.url=https://devstudio.redhat.com/11/staging/updates/integration-stack/discovery/11.1.0.Beta1/devstudio-directory.xml > -Djboss.discovery.site.integration-stack.url=https://devstudio.redhat.com/11/staging/updates/integration-stack/discovery/11.1.0.Beta1 > -Djboss.discovery.earlyaccess.site.integration-stack.url=https://devstudio.redhat.com/11/staging/updates/integration-stack/discovery/11.1.0.Beta1/earlyaccess > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25274) Inconsistent licenses in org.jboss.ide.eclipse.freemarker

by Timo Leser (JIRA)

Timo Leser created JBIDE-25274: ---------------------------------- Summary: Inconsistent licenses in org.jboss.ide.eclipse.freemarker Key: JBIDE-25274 URL: https://issues.jboss.org/browse/JBIDE-25274 Project: Tools (JBoss Tools) Issue Type: Bug Components: freemarker Affects Versions: 4.5.1.AM3, 4.5.0.Final, 4.4.4.Final Reporter: Timo Leser Attachments: files_with_epl_header.txt A couple of source files in org.jboss.ide.eclipse.freemarker_1.5.3 contain EPL headers while the plugin itself is, according to its License.txt, under LGPL. Problem is still present in in JBoss Tools 4.5.0. The freemaker plugin that was present in JBoss Tools 4.3.1 did not have this inconsistency. See attachment for list of files with EPL headers. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25273) Edit resource limits wizard: memory limit is erroneously shown as "MiB" where it should be "bytes"

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25273?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-25273: ------------------------------------------ Turns out that the reason for this is in the openshift-restclient-java library. The following json {code} "requests":{ "memory":"5" } {code} is parsed as {code} "requests" => {"memory" => "5Mi"} {code} where it should be *"5"* and not *"5Mi"*. > Edit resource limits wizard: memory limit is erroneously shown as "MiB" where it should be "bytes" > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-25273 > URL: https://issues.jboss.org/browse/JBIDE-25273 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.1.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: edit_resource_limits_wizard, openshift_v3 > Fix For: 4.5.1.Final > > Attachments: edit-resource-limits-memory-limit-units.png > > > steps: > # ASSERT: make sure that you have an application with a service and replication controller running in OpenShift (ex. create an app with the nodejs-mongo-persistent template) > # ASSERT: make sure that your memory request limit is in bytes: > # EXEC: in OpenShift explorer, select your project > # EXEC: in "Properties" view, select "Deployments" tab and select the last entry > # EXEC: pick "Edit" in the context menu to it > # ASSERT: replication controller is opened in the editor > # EXEC: search (Ctrl+F) "limits" and make sure it has an entry for memory limits that has no unit > {code} > "resources" : { > "limits" : {"memory" : "512"}, > }, > {code} > # EXEC: in OpenShift Explorer: select the service for your application and pick "Edit Resource Limits..." in the context menu > # ASSERT: Edit resource limits wizard shows up > Result: > Memory > Limits show *MiB* as unit > !edit-resource-limits-memory-limit-units.png! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25273) Edit resource limits wizard: memory limit is erroneously shown as "MiB" where it should be "bytes"

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25273?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-25273: ---------------------------------------- Assignee: Andre Dietisheim > Edit resource limits wizard: memory limit is erroneously shown as "MiB" where it should be "bytes" > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-25273 > URL: https://issues.jboss.org/browse/JBIDE-25273 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.1.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: edit_resource_limits_wizard, openshift_v3 > Fix For: 4.5.1.Final > > Attachments: edit-resource-limits-memory-limit-units.png > > > steps: > # ASSERT: make sure that you have an application with a service and replication controller running in OpenShift (ex. create an app with the nodejs-mongo-persistent template) > # ASSERT: make sure that your memory request limit is in bytes: > # EXEC: in OpenShift explorer, select your project > # EXEC: in "Properties" view, select "Deployments" tab and select the last entry > # EXEC: pick "Edit" in the context menu to it > # ASSERT: replication controller is opened in the editor > # EXEC: search (Ctrl+F) "limits" and make sure it has an entry for memory limits that has no unit > {code} > "resources" : { > "limits" : {"memory" : "512"}, > }, > {code} > # EXEC: in OpenShift Explorer: select the service for your application and pick "Edit Resource Limits..." in the context menu > # ASSERT: Edit resource limits wizard shows up > Result: > Memory > Limits show *MiB* as unit > !edit-resource-limits-memory-limit-units.png! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25091) Edit resource limits wizard: Duplicate value "MiB" in Memory Limit & Request

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25091?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-25091 at 10/20/17 8:28 AM: -------------------------------------------------------------------- [~jeffmaury] here's the PR for this change: https://github.com/jbosstools/jbosstools-openshift/pull/1598/files I discovered a parsing error in the client library that would parse {code} "requests":{ "memory":"5" } {code} as {code} "requests" => {"memory" => "5Mi"} {code} where it should be *"5"* and not *"5Mi"*. I'll filed a separate jira for this: JBIDE-25273 was (Author: adietish): [~jeffmaury] here's the PR for this change: https://github.com/jbosstools/jbosstools-openshift/pull/1598/files I discovered a parsing error in the client library that would parse {code} "requests":{ "memory":"5" } {code} as {code} "requests" => {"memory" => "5Mi"} {code} where it should be *"5"* and not *"5Mi"*. I'll file a separate jira for this. > Edit resource limits wizard: Duplicate value "MiB" in Memory Limit & Request > ---------------------------------------------------------------------------- > > Key: JBIDE-25091 > URL: https://issues.jboss.org/browse/JBIDE-25091 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.1.AM2 > Reporter: Josef Kopriva > Priority: Minor > Labels: edit_resource_limits_wizard, openshift_v3 > Fix For: 4.5.x > > Attachments: edit-resource-limits.png, image-2017-09-22-13-02-35-216.png, request-resource-limit-combo.png, resource-limits-web-console.png > > > When editing memory settings in dialog "Edit resource limits", there is a duplicate value MiB in the Combos for Memory > "Request" and Memory > "Limit": > !edit-resource-limits.png! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 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 October 2017