July 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22855) Editing pod's json - strange behavior

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22855?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22855: ------------------------------------------ [~jcantrill] looks like the server is silently refusing to edit the timestamp. Kinda expected but I think that the server should error? > Editing pod's json - strange behavior > ------------------------------------- > > Key: JBIDE-22855 > URL: https://issues.jboss.org/browse/JBIDE-22855 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM1 > Reporter: Dmitry Bocharov > Priority: Minor > Fix For: 4.4.x > > Attachments: editing_pod_json.webm > > > It's impossible to edit creationTimestamp in pod's json + editing labels causes creation of a new pod: [^editing_pod_json.webm] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22855) Editing pod's json - strange behavior

by Dmitry Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22855?page=com.atlassian.jira.plugi... ] Dmitry Bocharov commented on JBIDE-22855: ----------------------------------------- [~jcantrill], may i ask you to have a look at it. Is it the way it should be or not? > Editing pod's json - strange behavior > ------------------------------------- > > Key: JBIDE-22855 > URL: https://issues.jboss.org/browse/JBIDE-22855 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM1 > Reporter: Dmitry Bocharov > Priority: Minor > Fix For: 4.4.x > > Attachments: editing_pod_json.webm > > > It's impossible to edit creationTimestamp in pod's json + editing labels causes creation of a new pod: [^editing_pod_json.webm] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22855) Editing pod's json - strange behavior

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22855?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22855: ------------------------------------- Priority: Minor (was: Major) > Editing pod's json - strange behavior > ------------------------------------- > > Key: JBIDE-22855 > URL: https://issues.jboss.org/browse/JBIDE-22855 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM1 > Reporter: Dmitry Bocharov > Priority: Minor > Fix For: 4.4.x > > Attachments: editing_pod_json.webm > > > It's impossible to edit creationTimestamp in pod's json + editing labels causes creation of a new pod: [^editing_pod_json.webm] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22855) Editing pod's json - strange behavior

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22855?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22855: ------------------------------------- Fix Version/s: 4.4.x > Editing pod's json - strange behavior > ------------------------------------- > > Key: JBIDE-22855 > URL: https://issues.jboss.org/browse/JBIDE-22855 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM1 > Reporter: Dmitry Bocharov > Priority: Minor > Fix For: 4.4.x > > Attachments: editing_pod_json.webm > > > It's impossible to edit creationTimestamp in pod's json + editing labels causes creation of a new pod: [^editing_pod_json.webm] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22855) Editing pod's json - strange behavior

by Dmitry Bocharov (JIRA)

Dmitry Bocharov created JBIDE-22855: --------------------------------------- Summary: Editing pod's json - strange behavior Key: JBIDE-22855 URL: https://issues.jboss.org/browse/JBIDE-22855 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.4.1.AM1 Reporter: Dmitry Bocharov Attachments: editing_pod_json.webm It's impossible to edit creationTimestamp in pod's json + editing labels causes creation of a new pod: [^editing_pod_json.webm] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22382) Use different icons for EAP server and Red Hat Central

by James Cobb (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22382?page=com.atlassian.jira.plugi... ] James Cobb commented on JBIDE-22382: ------------------------------------ [~fbricon] [~crobson] - I agree that the branding of "Red Hat Central" should reflect the RHD brand. The current background graphics used are from the website branding of jboss.org. Can I please request a full screenshot of the IDE with all of the content for that panel visible? > Use different icons for EAP server and Red Hat Central > ------------------------------------------------------ > > Key: JBIDE-22382 > URL: https://issues.jboss.org/browse/JBIDE-22382 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central, server > Affects Versions: 4.4.0.Alpha2 > Reporter: Marián Labuda > Assignee: Fred Bricon > Priority: Minor > Labels: respin-a > Fix For: 4.4.x > > Attachments: central-rhd-icon.png > > > If there is an EAP server present in Servers view, workbench tool bar contains 2 same icons - Select a default server icon is same as Red Hat Central icon. We should make this explicitly different. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-654) JBDSIS stand-alone installer

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-654?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-654: ---------------------------------- Yes. - thanks Max. > JBDSIS stand-alone installer > ---------------------------- > > Key: JBTIS-654 > URL: https://issues.jboss.org/browse/JBTIS-654 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Affects Versions: 9.0.0.GA > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 9.0.1.GA > > Attachments: Capture.JPG, inst1.png, inst1.png, inst1a.png, inst2.png, inst3.png, inst4.png > > > Establish a stand-alone installer for JBDSIS that will contain JBDS and will enable easier installation of JBDSIS components - specifically Fuse Tooling. This Jira is specifically related to the JBDSIS installer. Other usability issues will be handled in other Jira. > Installation scenario: > {code} > 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) > 2. Download the JBDSIS installer jar. i.e. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.... > 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*.jar` > 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window. > 5. Accept/ respond 'Yes' and restart > 6. Select Window > Perspective > Open Perspective > Fuse Integration > {code} > A prototype installer has already been created - see: > https://github.com/jbosstools/jbosstools-integration-stack/tree/master/de... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22807) Could not install bundle. A bundle is already installed with the name xxx

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22807?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-22807: ---------------------------------- Steps to Reproduce: Machydra job for example: machydra job: jbds10-nightly.freemarker.ui.test. Otherwise: run integration tests with maven commands in command line and pass parameter test.installBase=existing/devstudio/path was:for example: machydra job: jbds10-nightly.freemarker.ui.test. > Could not install bundle. A bundle is already installed with the name xxx > ------------------------------------------------------------------------- > > Key: JBIDE-22807 > URL: https://issues.jboss.org/browse/JBIDE-22807 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: qa > Environment: Fedora 24, x86_64 > devstudio: > Version: 10.0.1.AM2 > Build id: AM2-v20160720-1632-B5674 > OpenJDK Runtime Environment (build 1.8.0_92-b14) > Reporter: Ondrej Dockal > Priority: Critical > Fix For: 4.4.1.AM2 > > > Error log contains errors for each plugin installed in devstudio where tests are run on existing instance of devstudio via mvn command (test is run with parameter test.installBase=path/to/devstudio) > Could not install bundle plugins/org.eclipse.mylyn.commons.net_3.20.0.v20160421-1819.jar A bundle is already installed with the name "org.eclipse.mylyn.c... (Open log entry details for full message). > This imply also for probably all jobs that install devstudio on machines through groovy script and run integration tests. Unless error log is checked in test, this does not mind... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22807) Could not install bundle. A bundle is already installed with the name xxx

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22807?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-22807: ---------------------------------- Fix Version/s: 4.4.1.AM2 > Could not install bundle. A bundle is already installed with the name xxx > ------------------------------------------------------------------------- > > Key: JBIDE-22807 > URL: https://issues.jboss.org/browse/JBIDE-22807 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: qa > Environment: Fedora 24, x86_64 > devstudio: > Version: 10.0.1.AM2 > Build id: AM2-v20160720-1632-B5674 > OpenJDK Runtime Environment (build 1.8.0_92-b14) > Reporter: Ondrej Dockal > Priority: Critical > Fix For: 4.4.1.AM2 > > > Error log contains errors for each plugin installed in devstudio where tests are run on existing instance of devstudio via mvn command (test is run with parameter test.installBase=path/to/devstudio) > Could not install bundle plugins/org.eclipse.mylyn.commons.net_3.20.0.v20160421-1819.jar A bundle is already installed with the name "org.eclipse.mylyn.c... (Open log entry details for full message). > This imply also for probably all jobs that install devstudio on machines through groovy script and run integration tests. Unless error log is checked in test, this does not mind... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22846) Incorrectly referenced artifact are not validated/reported in Source tab in batch editor.

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22846?page=com.atlassian.jira.plugi... ] Ondrej Dockal closed JBIDE-22846. --------------------------------- Fix Version/s: 4.4.1.AM2 Resolution: Cannot Reproduce I could not reproduce this bug anymore, closing. > Incorrectly referenced artifact are not validated/reported in Source tab in batch editor. > ----------------------------------------------------------------------------------------- > > Key: JBIDE-22846 > URL: https://issues.jboss.org/browse/JBIDE-22846 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.4.1.AM2 > Environment: Fedora 24, x86_64, > devstudio: > Version: 10.0.1.AM2 > Build id: AM2-v20160725-1821-B5680 > Build date: 20160725-1821 > Reporter: Ondrej Dockal > Priority: Critical > Fix For: 4.4.1.AM2 > > Attachments: BatchNoValidationSourceTab.png > > > There is no validation of attributes ref or class in source tab of the batch editor. In design and diagram source is seems alright. Also validation of other attributes that reference another artifact are not working. On the other hand, validation of uniqueness of id is working. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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