June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22448) TP p2diff generation fails build when TP version changes

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22448?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-22448: ----------------------------------- Story Points: 2 (was: 6) > TP p2diff generation fails build when TP version changes > -------------------------------------------------------- > > Key: JBIDE-22448 > URL: https://issues.jboss.org/browse/JBIDE-22448 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: target-platform > Affects Versions: 4.4.0.Alpha2 > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.4.0.Alpha3 > > > Add support for skipping p2diff generation when there's no previous site against which to diff, eg., when upversioning or releasing from snapshot to release in Nexus. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22159) Docker image is empty after selecting it from Image search wizard

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22159?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22159: ------------------------------------------ works for me, thx! merged into master > Docker image is empty after selecting it from Image search wizard > ----------------------------------------------------------------- > > Key: JBIDE-22159 > URL: https://issues.jboss.org/browse/JBIDE-22159 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Viacheslav Kabanovich > Fix For: 4.4.0.Alpha3 > > > As discovered in https://github.com/jbosstools/jbosstools-openshift/pull/1106#issuecomment..., provided you have a docker and an OpenShift connection: > - In OpenShift Explorer, select the Deploy Image menu > - select the docker connection > - type a docker image name already pulled in the docker daemon > - delete it and click the search... button > - select the same docker image as previously typed > - once the search wizard closes, the docker Image name field is still empty. > See http://screencast.com/t/iTJX7SjB > As per [~scabanovich]: > {quote} > it is possible that validator does not let empty string to model, so model remains with valid previous value. Then, when you select that same value in the dialog, model is notified, but it already has that value and it does not notify ui because it did not change > {quote} > and his fix proposal: > {quote} > before calling setImageName(newValue) check if it has the same value, then call setImageName(""); and only after this check and adjustment call setImageName(newValue). > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3574) CDK username pulldown field is not tall enough (screenshot attached)

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3574?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-3574: ------------------------------- Priority: Minor (was: Major) > CDK username pulldown field is not tall enough (screenshot attached) > -------------------------------------------------------------------- > > Key: JBDS-3574 > URL: https://issues.jboss.org/browse/JBDS-3574 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: runtime > Affects Versions: 9.1.0.Beta1 > Environment: Version: 9.1.0.Beta1 > Build id: Beta1-v20151210-1215-B180 > Build date: 20151210-1215 > Reporter: Len DiMaggio > Assignee: Rob Stryker > Priority: Minor > Fix For: 10.0.0.Alpha3 > > Attachments: 10_Alpha1.png, Dec_10_username.png, Fedora.png, RHEL7.png > > > See attached screenshot. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3574) CDK username pulldown field is not tall enough (screenshot attached)

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3574?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-3574: ------------------------------- Attachment: Fedora.png RHEL7.png > CDK username pulldown field is not tall enough (screenshot attached) > -------------------------------------------------------------------- > > Key: JBDS-3574 > URL: https://issues.jboss.org/browse/JBDS-3574 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: runtime > Affects Versions: 9.1.0.Beta1 > Environment: Version: 9.1.0.Beta1 > Build id: Beta1-v20151210-1215-B180 > Build date: 20151210-1215 > Reporter: Len DiMaggio > Assignee: Rob Stryker > Fix For: 10.0.0.Alpha3 > > Attachments: 10_Alpha1.png, Dec_10_username.png, Fedora.png, RHEL7.png > > > See attached screenshot. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22459) Figure out impact of adding EAP 7 to DCP and what changes DCP has that might affect Central

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22459?page=com.atlassian.jira.plugi... ] Len DiMaggio commented on JBIDE-22459: -------------------------------------- For Dev Studio 10 users: The eap7 QS will show up (should be online by now) and eap6 ones should be gone (Same thing should be seen for Dev Studio 9 users) > Figure out impact of adding EAP 7 to DCP and what changes DCP has that might affect Central > ------------------------------------------------------------------------------------------- > > Key: JBIDE-22459 > URL: https://issues.jboss.org/browse/JBIDE-22459 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: central > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Blocker > > ~1 year ago we made Central use DCP for querying the quickstart list to let users start easily with the examples/quickstrats. > In the context of EAP 7 coming out there are new quickstarts. > In a perfect world the following have happend: > EAP 7 Quickstarts added to DCP > Central in both devstudio 9 and 10 can see both EAP 6 and EAP 7 quickstarts > What seem to have happened instead is: > if EAP 7 quickstarts are added to DCP EAP 6 quickstarts are no longer available > DCP has changed its format/approach and not sure what the impact of this is > (can devstudio 9 still work ? must devstudio 10 change ? will we ever have multiple version support ?) > This bug is to gather the facts and figure out what we do about them. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22434) Properties not showing whole Docker image ID

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22434?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-22434: ---------------------------------- Fix Version/s: 4.4.0.Alpha3 > Properties not showing whole Docker image ID > -------------------------------------------- > > Key: JBIDE-22434 > URL: https://issues.jboss.org/browse/JBIDE-22434 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker > Affects Versions: 4.4.0.Alpha2 > Environment: Version: 10.0.0.Alpha1 > Build id: Alpha1-v20160525-0422-B5425 > Build date: 20160525-0422 > Reporter: Josef Kopriva > Assignee: Jeff Johnston > Fix For: 4.4.0.Alpha3 > > Attachments: Dockerfile, Docker_Image_ID.png > > > Image ID in properties tab is not complete, but Parent ID is complete. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22241) OpenShift Explorer: Cascade resource deletion

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22241?page=com.atlassian.jira.plugi... ] Jeff Cantrill edited comment on JBIDE-22241 at 6/1/16 10:46 AM: ---------------------------------------------------------------- I would defer this issue until https://github.com/kubernetes/kubernetes/issues/19054 merges which will move cascade delete to the server instead of requiring us to duplicate all the logic. {{<kargakis> jcantril: for deploymentconfigs? <kargakis> jcantril: or in general how to implement a reaper? * rhcarvalho has quit (Remote host closed the connection) * goern has quit (Quit: done for now) <jcantril> kargakis, if i run 'oc delete <resource> cascade'... * goern (~goern(a)aftr-37-201-171-241.unity-media.net) has joined <jcantril> kargakis, we hope to provide similiar logic in the jbosstools openshift tooling <kargakis> jcantril: each reapable resource has to implement its own logic * cdaley (~cdaley@2605:a000:160e:80c6:1202:b5ff:fe80:27c1) has joined <kargakis> jcantril: https://github.com/kubernetes/kubernetes/blob/master/pkg/kubectl/stop.go * claytonc has quit (Read error: Connection reset by peer) <kargakis> jcantril: all the upstream implementations <jcantril> kargakis, does that mean then.... that cascade is a delete flag and the api server interprets it accordingly? * claytonc (~claytonc(a)75-130-183-34.static.hlrg.nc.charter.com) has joined * ChanServ gives channel operator status to claytonc <jcantril> kargakis, its just a flag to the request? <kargakis> jcantril: oc delete can understand if <resource> is reapable or not <kargakis> jcantril: if <resource> is reapable, then the related reaper will be used <jcantril> kargakis, i dont wish to duplicate the reapable logic... just to explicitly ask the cluster to cascade delete <kargakis> jcantril: and all calls happen client-side <kargakis> jcantril: cascade deletion is moving to the server upstream * rhcarvalho (Rodolfo@nat/redhat/x-fcpoagpuinftkvls) has joined <kargakis> jcantril: but it's still not there * rlourenc has quit (Quit: Leaving) * openshift-dev468 has quit (Quit: Page closed) <jcantril> kargakis, so in order for me to cascade now....i would have to impl logic that... for each kind ....reimpl what that particular type manages and delete those resources <kargakis> jcantril: https://github.com/kubernetes/kubernetes/issues/19054 <kargakis> jcantril: yes, right now for each resource you would have to duplicate the api calls that happen in oc}} was (Author: jcantrill): I would defer this issue until https://github.com/kubernetes/kubernetes/issues/19054 merges which will move cascade delete to the server instead of requiring us to duplicate all the logic. > OpenShift Explorer: Cascade resource deletion > --------------------------------------------- > > Key: JBIDE-22241 > URL: https://issues.jboss.org/browse/JBIDE-22241 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Assignee: Jeff MAURY > Labels: explorer, openshift_v3, ux > Fix For: 4.4.0.Alpha3 > > > It would be nice to have a possibility to allow cascading deletion, deletion of related resource/resource managed by the resource which is about to be deleted. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22241) OpenShift Explorer: Cascade resource deletion

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22241?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-22241: --------------------------------------- I would defer this issue until https://github.com/kubernetes/kubernetes/issues/19054 merges which will move cascade delete to the server instead of requiring us to duplicate all the logic. > OpenShift Explorer: Cascade resource deletion > --------------------------------------------- > > Key: JBIDE-22241 > URL: https://issues.jboss.org/browse/JBIDE-22241 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Assignee: Jeff MAURY > Labels: explorer, openshift_v3, ux > Fix For: 4.4.0.Alpha3 > > > It would be nice to have a possibility to allow cascading deletion, deletion of related resource/resource managed by the resource which is about to be deleted. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22444) Client: release and use a final artifact of openshift-restclient-java

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22444?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22444: ------------------------------------- Priority: Blocker (was: Major) > Client: release and use a final artifact of openshift-restclient-java > --------------------------------------------------------------------- > > Key: JBIDE-22444 > URL: https://issues.jboss.org/browse/JBIDE-22444 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.0.Alpha3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Blocker > Fix For: 4.4.0.Alpha3 > > > 4.4.0.Alpha2 is using openshift-restclient-java 4.0.4-SNAPSHOT. We should release a final version of the client and use it in the next milestone. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20729) Investigate ProcessInformationStore for its uses and whether it can be replaced

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20729?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-20729. --------------------------------- I verified this with latest JBoss Tools 4.4.0.Alpha3 from master, on Windows 10 with Oracle JDK 1.8. I ran Eclipse using "eclipse -consoleLog" from command line, then downloaded and installed WildFly 9.0.2 and then right-clicked the server. The error from JBIDE-20754 was not shown in the console (as was seen previously). > Investigate ProcessInformationStore for its uses and whether it can be replaced > ------------------------------------------------------------------------------- > > Key: JBIDE-20729 > URL: https://issues.jboss.org/browse/JBIDE-20729 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.CR1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.0.Alpha1 > > > https://issues.jboss.org/browse/JBIDE-20510 was opened for a small bug regarding spaces on windows, but it revealed to me that the java8 I have installed there lacks a jps command. This means we need to revisit whether or not the ProcessInformationSotre is the proper solution for what it is doing, or if we can replace it with the debug code in jbt-base. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 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 June 2016