November 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-23453) Easymport New and Noteworthy for 4.4.2.AM3

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23453?page=com.atlassian.jira.plugi... ] Mickael Istria closed JBIDE-23453. ---------------------------------- Resolution: Rejected Nothing to do. > Easymport New and Noteworthy for 4.4.2.AM3 > --------------------------------------------------- > > Key: JBIDE-23453 > URL: https://issues.jboss.org/browse/JBIDE-23453 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: easymport > Reporter: Jeff MAURY > Assignee: Mickael Istria > Priority: Critical > > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Easymport 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 Easymport, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Easymport 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 'JBIDE-56789 #comment Create N&N for Easymport4.4.2.AM3 #close', 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 Easymport for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23366) replace manual staging cleanup w/ a job

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23366?page=com.atlassian.jira.plugi... ] Lukáš Valach closed JBIDE-23366. -------------------------------- It seems the job works fine. > replace manual staging cleanup w/ a job > --------------------------------------- > > Key: JBIDE-23366 > URL: https://issues.jboss.org/browse/JBIDE-23366 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Affects Versions: 4.4.2.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.AM3 > > > Replace manual cleanup steps in staging guides with a job that can more easily be run to purge content. This will make it easier to iterate: > * to test sshfs-based publishing > * to performance tune the release process (already down from 2h45 of copying files to only 40mins) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23368) Deploy Docker Image: Replication controller does not contain mapped ports from Deploy Image Wizard

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23368?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-23368 at 11/4/16 9:12 AM: ------------------------------------------------------------------- [~mlabuda] yes, I agree and this was my initial impression, too (see https://issues.jboss.org/browse/JBIDE-23352?focusedCommentId=13308084&pag...). This seems to be confirmed by the fact that the web-ui wont allow you to add/remove ports. Web-UI only allows you to chose the routing port. On the ohter hand, offering this ability is giving power to the users and works as long as the users take care to expose those ports on the pod/container. [~jeffmaury] can you reiterate the reasons that made you think that we should allow users to add/remove ports? was (Author: adietish): [~mlabuda] yes, I agree and this was my initial impression, too. This seems to be confirmed by the fact that the web-ui wont allow you to add/remove ports. Web-UI only allows you to chose the routing port. On the ohter hand, offering this ability is giving power to the users and works as long as the users take care to expose those ports on the pod/container. [~jeffmaury] can you reiterate the reasons that made you think that we should allow users to add/remove ports? > Deploy Docker Image: Replication controller does not contain mapped ports from Deploy Image Wizard > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-23368 > URL: https://issues.jboss.org/browse/JBIDE-23368 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.2.AM3 > > > When deploying a docker image via Deploy Docker Wizard to an OpenShift instance, there is a wizard page with mapping of pod ports to service ports. If I add a new port mapping there, it is propagated to a created Service. But created replication controller does not contain those new mappings (results into creating pods without those ports available) > Either way this should be fixed, to also Replication Controller should contain mapped ports, because having a service which has mapped pod ports to service ports but pods itself does not have this port exposes is useless. Or having Add... button does not make sense there, or there is no known use case where it would be useful (existing mapping could be edited but a new one would be useless). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4158) batch.ui.hyperlink.BatchPropertyHyperlinkDetector :: java.lang.NoClassDefFoundError: org/eclipse/jdt/core/JavaModelException

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBDS-4158?page=com.atlassian.jira.plugin.... ] Lukáš Valach closed JBDS-4158. ------------------------------ Verified in 4.4.2.AM3 (rh-eclipse46-devstudio-10.2-0.20161103.1913.el7.x86_64.rpm), I also can't reproduce this issue. > batch.ui.hyperlink.BatchPropertyHyperlinkDetector :: java.lang.NoClassDefFoundError: org/eclipse/jdt/core/JavaModelException > ---------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-4158 > URL: https://issues.jboss.org/browse/JBDS-4158 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: batch, rpm > Affects Versions: 10.2.0.AM3 > Environment: Installed rpm: > {code} > Installed Packages > Name : rh-eclipse46-devstudio > Arch : x86_64 > Epoch : 0 > Version : 10.2 > Release : 0.20161102.2255.el7 > {code} > {code} > $➔ uname -a && java -version > Linux t540p-f24-vm01 4.8.4-200.fc24.x86_64 #1 SMP Tue Oct 25 13:06:04 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux > {code} > {code} > openjdk version "1.8.0_65" > OpenJDK Runtime Environment (build 1.8.0_65-b17) > OpenJDK 64-Bit Server VM (build 25.65-b01, mixed mode) > {code} > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Priority: Blocker > Fix For: 10.2.0.AM3 > > Attachments: batch.ui.hyperlink.error.txt, batch.ui.hyperlink.png > > > Whenever I click on text in a .java file editor in Eclipse, I get this error thrown: > !batch.ui.hyperlink.png|thumbnail! > [^batch.ui.hyperlink.error.txt] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23467) Unnecessary GWT files

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23467?page=com.atlassian.jira.plugi... ] Lukáš Valach updated JBIDE-23467: --------------------------------- Priority: Minor (was: Major) > Unnecessary GWT files > --------------------- > > Key: JBIDE-23467 > URL: https://issues.jboss.org/browse/JBIDE-23467 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, rpm > Affects Versions: 4.4.2.AM3 > Environment: RHEL7 64bit > rh-eclipse46-devstudio-10.2-0.20161103.1913.el7.x86_64.rpm > Reporter: Lukáš Valach > Priority: Minor > > GWT feature and plugin has been removed in [JBIDE-23414|https://issues.jboss.org/browse/JBIDE-23414], but there are still GWT files. > {code} > [lvalach@localhost rh]$ sudo find . -iname '*gwt*' > ./rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/org.jboss.tools.central_2.1.2.v20160922-1945/icons/gwt_background.png > ./rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/org.jboss.tools.central_2.1.2.v20160922-1945/org/jboss/tools/central/wizards/NewGwtProjectWizard.class > {code} > These files are unnecessary I guess. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23414) use Import-Package instead of Require-Bundle for slf4j.api [central]

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23414?page=com.atlassian.jira.plugi... ] Lukáš Valach closed JBIDE-23414. -------------------------------- Verified in 4.4.2.AM3 (rh-eclipse46-devstudio-10.2-0.20161103.1913.el7.x86_64.rpm), plugin has been removed but there are still some GWT files. This problem will be solved in [JBIDE-23467|https://issues.jboss.org/browse/JBIDE-23467]. > use Import-Package instead of Require-Bundle for slf4j.api [central] > -------------------------------------------------------------------- > > Key: JBIDE-23414 > URL: https://issues.jboss.org/browse/JBIDE-23414 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, rpm > Affects Versions: 4.4.2.AM2 > Reporter: Nick Boldt > Assignee: Fred Bricon > Priority: Minor > Fix For: 4.4.2.AM3 > > > Because central use Require-Bundle instead of Import-Package to depend on slf4j.api, this project cannot use the rhel implementation (rh-common-java rpm) version of slf4j.api 1.7.4 .jar when installed via rpm on rhel/fedora. > Here's the line that is causing the problem: > https://github.com/jbosstools/jbosstools-central/blob/fc4bfc7aea223c95b71... > We need to switch to using Import-Package to that *any* implementation of this package, regardless of *Bundle-SymbolicName*, can be used. > More info in JBDS-4136 > See also: > http://stackoverflow.com/questions/13959891/why-do-we-need-imported-packa... > http://stackoverflow.com/questions/1865819/when-should-i-use-import-packa... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23467) Unnecessary GWT files

by Lukáš Valach (JIRA)

Lukáš Valach created JBIDE-23467: ------------------------------------ Summary: Unnecessary GWT files Key: JBIDE-23467 URL: https://issues.jboss.org/browse/JBIDE-23467 Project: Tools (JBoss Tools) Issue Type: Bug Components: central, rpm Affects Versions: 4.4.2.AM3 Environment: RHEL7 64bit rh-eclipse46-devstudio-10.2-0.20161103.1913.el7.x86_64.rpm Reporter: Lukáš Valach GWT feature and plugin has been removed in [JBIDE-23414|https://issues.jboss.org/browse/JBIDE-23414], but there are still GWT files. {code} [lvalach@localhost rh]$ sudo find . -iname '*gwt*' ./rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/org.jboss.tools.central_2.1.2.v20160922-1945/icons/gwt_background.png ./rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/org.jboss.tools.central_2.1.2.v20160922-1945/org/jboss/tools/central/wizards/NewGwtProjectWizard.class {code} These files are unnecessary I guess. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23466) Refactor ConnectionWrapper class for better support of mulithreading

by Dmitrii Bocharov (JIRA)

Dmitrii Bocharov created JBIDE-23466: ---------------------------------------- Summary: Refactor ConnectionWrapper class for better support of mulithreading Key: JBIDE-23466 URL: https://issues.jboss.org/browse/JBIDE-23466 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Reporter: Dmitrii Bocharov Priority: Minor The initial discussion started here: https://github.com/jbosstools/jbosstools-openshift/pull/1359#discussion_r... The problem is that ConnectionWrapper contains a lot of synchronized blocks, that can be bottlenecks. We need to think about using ConcurentHashMap for projects Map or refactor the whole logic of using global variables: projects and resourceCache to make them work synchronously. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23466) Refactor ConnectionWrapper class for better support of mulithreading

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23466?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-23466: ------------------------------------- Priority: Major (was: Minor) > Refactor ConnectionWrapper class for better support of mulithreading > -------------------------------------------------------------------- > > Key: JBIDE-23466 > URL: https://issues.jboss.org/browse/JBIDE-23466 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Reporter: Dmitrii Bocharov > > The initial discussion started here: https://github.com/jbosstools/jbosstools-openshift/pull/1359#discussion_r... > The problem is that ConnectionWrapper contains a lot of synchronized blocks, that can be bottlenecks. We need to think about using ConcurentHashMap for projects Map or refactor the whole logic of using global variables: projects and resourceCache to make them work synchronously. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23368) Deploy Docker Image: Replication controller does not contain mapped ports from Deploy Image Wizard

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23368?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-23368: --------------------------------------- [~jcantrill] I agree with you, we should go with the first proposal of yours. > Deploy Docker Image: Replication controller does not contain mapped ports from Deploy Image Wizard > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-23368 > URL: https://issues.jboss.org/browse/JBIDE-23368 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.2.AM3 > > > When deploying a docker image via Deploy Docker Wizard to an OpenShift instance, there is a wizard page with mapping of pod ports to service ports. If I add a new port mapping there, it is propagated to a created Service. But created replication controller does not contain those new mappings (results into creating pods without those ports available) > Either way this should be fixed, to also Replication Controller should contain mapped ports, because having a service which has mapped pod ports to service ports but pods itself does not have this port exposes is useless. Or having Add... button does not make sense there, or there is no known use case where it would be useful (existing mapping could be edited but a new one would be useless). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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