April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21602) Sonar build for openshift is failing

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21602?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21602: -------------------------------- Fix Version/s: 4.4.x (was: 4.4.0.Alpha1) > Sonar build for openshift is failing > ------------------------------------ > > Key: JBIDE-21602 > URL: https://issues.jboss.org/browse/JBIDE-21602 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Andre Dietisheim > Assignee: Mickael Istria > Fix For: 4.4.x > > Attachments: sonar-build-output.txt > > > Sonar for openshift is currently failing in our jenkins at https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBo... > I see it complaining in the build about an incompatible bytecode version: > {code} > Caused by: java.lang.UnsupportedClassVersionError: org/eclipse/tycho/core/p2/P2ArtifactRepositoryLayout : Unsupported major.minor version 51.0 > {code} > The full build output is attached [^sonar-build-output.txt] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21191) Aplication wizard: remove workaround for SWT bug where controls only get visible upon resizing dialog

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21191?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21191: -------------------------------- Fix Version/s: 4.4.x (was: 4.4.0.Alpha1) > Aplication wizard: remove workaround for SWT bug where controls only get visible upon resizing dialog > ----------------------------------------------------------------------------------------------------- > > Key: JBIDE-21191 > URL: https://issues.jboss.org/browse/JBIDE-21191 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Beta1, 4.4.0.Alpha1 > Reporter: Andre Dietisheim > Labels: application_wizard, openshift_v3 > Fix For: 4.4.x > > > In JBIDE-21072 we applied a workaround to fix an SWT bug where controls are not visible but appear magically if you resize the dialog: https://bugs.eclipse.org/bugs/show_bug.cgi?id=465280 > We should remove this workaround once the fix makes it to SWT in upstream -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21668) Fix collection setters in ResourcesUIModel

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21668?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-21668: ----------------------------------- Assignee: Viacheslav Kabanovich (was: Jeff Cantrill) > Fix collection setters in ResourcesUIModel > ------------------------------------------ > > Key: JBIDE-21668 > URL: https://issues.jboss.org/browse/JBIDE-21668 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Fix For: 4.4.0.Alpha1 > > > Created as follow up to JBIDE-21590. > Collections setters in ResourcesUIModel, for instance > {code} > public void setBuildConfigs(Collection<IResourceUIModel> buildConfigs) { > firePropertyChange(PROP_BUILD_CONFIGS, resources.get(ResourceKind.BUILD_CONFIG), resources.put(ResourceKind.BUILD_CONFIG, new ArrayList<>(buildConfigs))); > } > {code} > fire incorrect newValue object, because java.util.Map.put(key, value) returns old object associated with the key, not the one just set. > At this moment, this does not create any bugs, because these setters are still not used, all changes go through ResourcesUIModel.add, ResourcesUIModel.remove, ResourcesUIModel.update that have correct notification. But bugs may appear as soon as collection setters are used, so that they better be fixed, for instance this way : > {code} > public void setBuildConfigs(Collection<IResourceUIModel> buildConfigs) { > setResourcesForKind(buildConfigs, ResourceKind.BUILD_CONFIG); > } > private void setResourcesForKind(Collection<IResourceUIModel> list, String kind) { > List<IResourceUIModel> oldList = resources.get(kind); > List<IResourceUIModel> newList = new ArrayList<IResourceUIModel>(list); > resources.put(kind, newList); > firePropertyChange(getProperty(kind), oldList, newList); > } > {code} > and with use of private setResourcesForKind all other setters will remain one-liners. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21668) Fix collection setters in ResourcesUIModel

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21668?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21668: -------------------------------- Issue Type: Task (was: Enhancement) > Fix collection setters in ResourcesUIModel > ------------------------------------------ > > Key: JBIDE-21668 > URL: https://issues.jboss.org/browse/JBIDE-21668 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Fix For: 4.4.0.Alpha1 > > > Created as follow up to JBIDE-21590. > Collections setters in ResourcesUIModel, for instance > {code} > public void setBuildConfigs(Collection<IResourceUIModel> buildConfigs) { > firePropertyChange(PROP_BUILD_CONFIGS, resources.get(ResourceKind.BUILD_CONFIG), resources.put(ResourceKind.BUILD_CONFIG, new ArrayList<>(buildConfigs))); > } > {code} > fire incorrect newValue object, because java.util.Map.put(key, value) returns old object associated with the key, not the one just set. > At this moment, this does not create any bugs, because these setters are still not used, all changes go through ResourcesUIModel.add, ResourcesUIModel.remove, ResourcesUIModel.update that have correct notification. But bugs may appear as soon as collection setters are used, so that they better be fixed, for instance this way : > {code} > public void setBuildConfigs(Collection<IResourceUIModel> buildConfigs) { > setResourcesForKind(buildConfigs, ResourceKind.BUILD_CONFIG); > } > private void setResourcesForKind(Collection<IResourceUIModel> list, String kind) { > List<IResourceUIModel> oldList = resources.get(kind); > List<IResourceUIModel> newList = new ArrayList<IResourceUIModel>(list); > resources.put(kind, newList); > firePropertyChange(getProperty(kind), oldList, newList); > } > {code} > and with use of private setResourcesForKind all other setters will remain one-liners. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21420) Delete more OpenShift projects at once

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21420?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-21420: ----------------------------------- Assignee: Jeff MAURY > Delete more OpenShift projects at once > -------------------------------------- > > Key: JBIDE-21420 > URL: https://issues.jboss.org/browse/JBIDE-21420 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Marián Labuda > Assignee: Jeff MAURY > Labels: explorer, openshift_v3 > Fix For: 4.4.0.Alpha1 > > > It would be nice to remove more projects at once. Currently I can only delete project by project by selecting and choosing delete in its context menu. I would like to select more projects and choose Delete project(s)... in theirs context menu as it is similar for OpenShift 2 domains. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21448) Allow port-forwarding of ports not defined on pod metadata

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21448?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21448: -------------------------------- Fix Version/s: 4.4.x (was: 4.4.0.Alpha1) > Allow port-forwarding of ports not defined on pod metadata > ---------------------------------------------------------- > > Key: JBIDE-21448 > URL: https://issues.jboss.org/browse/JBIDE-21448 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Jiri Pechanec > Fix For: 4.4.x > > > Some of the pods have services that are available via ports that are not defined in pod template. It is useful to have an option to port-forward such ports too. > And example is EAP CLI -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21446) Add way to open remote shell to OpenShift pod

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21446?page=com.atlassian.jira.plugi... ] Fred Bricon closed JBIDE-21446. ------------------------------- Fix Version/s: (was: 4.4.0.Alpha1) Resolution: Duplicate Issue Closing as duplicate of JBIDE-20911 > Add way to open remote shell to OpenShift pod > --------------------------------------------- > > Key: JBIDE-21446 > URL: https://issues.jboss.org/browse/JBIDE-21446 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Tomáš Schlosser > > There is no integration between Remote System Explorer and 'oc rsh', or any other way how to open shell to pod in JBDS. > It would be convenient to have this as a pod context menu entry. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20911) open local terminal with oc already logged in

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20911?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-20911: -------------------------------- Fix Version/s: 4.4.x (was: 4.4.0.Alpha1) > open local terminal with oc already logged in > --------------------------------------------- > > Key: JBIDE-20911 > URL: https://issues.jboss.org/browse/JBIDE-20911 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Max Rydahl Andersen > Fix For: 4.4.x > > > it would be great to have a "Show in > OpenShift CLI" in openshift explorer and on projects that are known to be on openshift that would use local terminal (like: https://v.usetapes.com/ISfR95tJK8) but have `oc login --token=<tokenforlogin> --server=<serverurl>` executed at start. > This would allow users to work with CLI whenever the UI does not have exactly the command needed by user. > * This assumes users have oc in their path > * might need different commands based on what OS (windows vs *nix) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22118) Openshift 3 plugin should support "builder" images

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22118?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-22118: ----------------------------------- Assignee: Jeff Cantrill (was: Fred Bricon) > Openshift 3 plugin should support "builder" images > -------------------------------------------------- > > Key: JBIDE-22118 > URL: https://issues.jboss.org/browse/JBIDE-22118 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Environment: JBoss Developer Studio (Core Features) 9.1.0.GA-v20160403-1700-B477 > Openshift plugin 3.1.0.Final-v20160401-2357-B263 > Reporter: Rafael Benevides > Assignee: Jeff Cantrill > Fix For: 4.4.0.Alpha1 > > Attachments: buildconfig page.png, page_1.png > > > I installed the following image stream: https://raw.githubusercontent.com/jboss-openshift/application-templates/m... > It contains several "builder" images. I would like to use jboss-eap70-openshift:1.3-Beta to build a JavaEE 7 application available at https://github.com/redhat-helloworld-msa/hello . But the Openshift plugin only shows "templates". > Openshift plugin should support "builder" images. These images contain "builder" on their tags. > Ref: Jan-5-2016 discussion: http://etherpad.corp.redhat.com/OpenShiftAndJBossStudio -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21376) Application wizard: should allow to create an app from an image (currently only from template)

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21376?page=com.atlassian.jira.plugi... ] Fred Bricon closed JBIDE-21376. ------------------------------- Resolution: Duplicate Issue Closing as duplicate of JBIDE-22118 > Application wizard: should allow to create an app from an image (currently only from template) > ---------------------------------------------------------------------------------------------- > > Key: JBIDE-21376 > URL: https://issues.jboss.org/browse/JBIDE-21376 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Xavier Coulon > Labels: application_wizard, openshift_v3 > Fix For: 4.4.0.Alpha1 > > Attachments: Screenshot 2015-12-21 16.44.02.png, Screenshot 2015-12-21 16.44.24.png, Screenshot 2015-12-21 18.06.40.png > > > The application wizard in the Eclipse tooling currently only allows to create application from templates. The web console additionally allows creating from images and git source. > One can see the difference when comparing the listing of options in Eclipse vs the listing in the web console (which also includes images): > {quote} > Running OpenShift using our openshift-vagrant box, I can see different proposals between the web console and the Eclipse tooling when adding an application in a project. For example, {{jboss-eap64-openshift:1.1}} is not proposed in the Eclipse tooling. > See attached screenshots. > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 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 April 2016