July 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23576) Integration tests global refactoring: org.jboss.tools.cdk.ui.bot.test

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23576?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-23576: ------------------------------------- [~jeffmaury] Can you elaborate a bit here as to what needs to happen? > Integration tests global refactoring: org.jboss.tools.cdk.ui.bot.test > --------------------------------------------------------------------- > > Key: JBIDE-23576 > URL: https://issues.jboss.org/browse/JBIDE-23576 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: cdk > Affects Versions: 4.4.2.Final > Reporter: Jeff MAURY > Assignee: Rob Stryker > Labels: cdk, integration, integration_tests > Fix For: 4.5.0.Final > > > Maven command: > {code} > mvn clean verify -Dtest.module=org.jboss.tools.cdk.ui.bot.test -DskipTests=false > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24379) javaee tests failing for linux, windows and osx

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24379?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24379: ------------------------------- Attachment: jst.ui.test.log > javaee tests failing for linux, windows and osx > ----------------------------------------------- > > Key: JBIDE-24379 > URL: https://issues.jboss.org/browse/JBIDE-24379 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch, jsf, seam2 > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Dmitrii Bocharov > Priority: Blocker > Fix For: 4.5.0.Final > > Attachments: javaee-test-failures.png, javaee-test-failures_last_pass_jan26.png, javaee-tests-failing.png, javaee-tests-failing_latest_status_jul5_842am_build269.png, jst.ui.test.log > > > JavaEE tests have been failing for months. > Please investigate. > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23576) Integration tests global refactoring: org.jboss.tools.cdk.ui.bot.test

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23576?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-23576: -------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM2) > Integration tests global refactoring: org.jboss.tools.cdk.ui.bot.test > --------------------------------------------------------------------- > > Key: JBIDE-23576 > URL: https://issues.jboss.org/browse/JBIDE-23576 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: cdk > Affects Versions: 4.4.2.Final > Reporter: Jeff MAURY > Assignee: Rob Stryker > Labels: cdk, integration, integration_tests > Fix For: 4.5.0.Final > > > Maven command: > {code} > mvn clean verify -Dtest.module=org.jboss.tools.cdk.ui.bot.test -DskipTests=false > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24682) Reflect changes in minishift's version command

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24682?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-24682: ------------------------------------- Escalating this issue. [~odockal] Really good catch. Thanks for being so on-the-ball here. Output of 'minishift version' was (and is) expected to follow a consistent format at the bare minimum. Previous expectations (and current, until changed) are a stream suitable to fed into a Properties object. Any change from this expected output is an API breakage as far as we see it. However, what's worse is that the current output is 100% inconsistent: minishift v1.2.0+001371f CDK Version:3.0.0-13072017-1 Notice how the CDK line includes a colon, and can be fed into properties format, but the minishift line has no colon, and breaks our reader. Any attempt to parse this manually will fail, unless I'm coding a parser specifically geared for today's output and nothing else. I've pinged [~hardy.ferentschik] to see where and how to escalate this for a prompt solution. > Reflect changes in minishift's version command > ---------------------------------------------- > > Key: JBIDE-24682 > URL: https://issues.jboss.org/browse/JBIDE-24682 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.5.0.Final > Reporter: Ondrej Dockal > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.5.0.Final > > > Due to changes in upstream project the 'minishift version' command returns different lines. > CDK result from http://cdk-builds.usersys.redhat.com/builds/weekly/19-Jun-2017.cdk-3.0.0-... build: > {code} > Minishift version: 1.0.0+4f8cb6d > CDK Version: 3.0.0-2 > {code} > vs. > CDK result from nightly http://cdk-builds.usersys.redhat.com/builds/nightly/13-Jul-2017 build: > {code} > minishift v1.2.0+001371f > CDK Version:3.0.0-13072017-1 > {code} > And this change results in error while creating CDK 3 server adapter with newer CDK nightly build as it ends with "Unknown error while checking minishift version" as we expect the string to contains "Minishift Version". > We should get in touch with cdk team to check whether they plan to change the output 'CDK Version' to something else as well, in case we are going to distinguish between minishift and cdk. If we accept in CDK 3 server adapter both cdk and minishift binary maybe we should create a CDK jira that would ask for changing output from 'minishift version' from 'CDK Version: X.X.X' to 'cdk vX.X.X'. I do not know if we plan to do so, it is just an idea... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24682) Reflect changes in minishift's version command

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24682?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-24682: ----------------------------------- Assignee: Rob Stryker > Reflect changes in minishift's version command > ---------------------------------------------- > > Key: JBIDE-24682 > URL: https://issues.jboss.org/browse/JBIDE-24682 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.5.0.Final > Reporter: Ondrej Dockal > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.5.0.Final > > > Due to changes in upstream project the 'minishift version' command returns different lines. > CDK result from http://cdk-builds.usersys.redhat.com/builds/weekly/19-Jun-2017.cdk-3.0.0-... build: > {code} > Minishift version: 1.0.0+4f8cb6d > CDK Version: 3.0.0-2 > {code} > vs. > CDK result from nightly http://cdk-builds.usersys.redhat.com/builds/nightly/13-Jul-2017 build: > {code} > minishift v1.2.0+001371f > CDK Version:3.0.0-13072017-1 > {code} > And this change results in error while creating CDK 3 server adapter with newer CDK nightly build as it ends with "Unknown error while checking minishift version" as we expect the string to contains "Minishift Version". > We should get in touch with cdk team to check whether they plan to change the output 'CDK Version' to something else as well, in case we are going to distinguish between minishift and cdk. If we accept in CDK 3 server adapter both cdk and minishift binary maybe we should create a CDK jira that would ask for changing output from 'minishift version' from 'CDK Version: X.X.X' to 'cdk vX.X.X'. I do not know if we plan to do so, it is just an idea... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24682) Reflect changes in minishift's version command

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24682?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-24682: -------------------------------- Priority: Blocker (was: Critical) > Reflect changes in minishift's version command > ---------------------------------------------- > > Key: JBIDE-24682 > URL: https://issues.jboss.org/browse/JBIDE-24682 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.5.0.Final > Reporter: Ondrej Dockal > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.5.0.Final > > > Due to changes in upstream project the 'minishift version' command returns different lines. > CDK result from http://cdk-builds.usersys.redhat.com/builds/weekly/19-Jun-2017.cdk-3.0.0-... build: > {code} > Minishift version: 1.0.0+4f8cb6d > CDK Version: 3.0.0-2 > {code} > vs. > CDK result from nightly http://cdk-builds.usersys.redhat.com/builds/nightly/13-Jul-2017 build: > {code} > minishift v1.2.0+001371f > CDK Version:3.0.0-13072017-1 > {code} > And this change results in error while creating CDK 3 server adapter with newer CDK nightly build as it ends with "Unknown error while checking minishift version" as we expect the string to contains "Minishift Version". > We should get in touch with cdk team to check whether they plan to change the output 'CDK Version' to something else as well, in case we are going to distinguish between minishift and cdk. If we accept in CDK 3 server adapter both cdk and minishift binary maybe we should create a CDK jira that would ask for changing output from 'minishift version' from 'CDK Version: X.X.X' to 'cdk vX.X.X'. I do not know if we plan to do so, it is just an idea... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4460) Devsuite registry entry has hardcoded version to 1.4.0

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4460?page=com.atlassian.jira.plugin.... ] Denis Golovin reassigned JBDS-4460: ----------------------------------- Assignee: Denis Golovin > Devsuite registry entry has hardcoded version to 1.4.0 > ------------------------------------------------------ > > Key: JBDS-4460 > URL: https://issues.jboss.org/browse/JBDS-4460 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 11.0.0.AM2 > Environment: windows > Reporter: Jan Richter > Assignee: Denis Golovin > > Red Hat Development Suite entry in windows apps still shows as version 1.4.0.GA -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4438) Detect free space available on disk for Windows

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4438?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-4438: ------------------------------------- We obviously lost freespace attribute along the way > Detect free space available on disk for Windows > ----------------------------------------------- > > Key: JBDS-4438 > URL: https://issues.jboss.org/browse/JBDS-4438 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 11.0.0.AM1 > Environment: Windows > Reporter: Denis Golovin > Assignee: Sudhir Verma > Fix For: 11.0.0.AM2 > > > DevSuite Installer should check if target disk has enough free space to continue installation. Before implementing UI for that platform.js module should have corresponding method to get the actual number. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4438) Detect free space available on disk for Windows

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4438?page=com.atlassian.jira.plugin.... ] Denis Golovin reassigned JBDS-4438: ----------------------------------- Assignee: Denis Golovin (was: Sudhir Verma) > Detect free space available on disk for Windows > ----------------------------------------------- > > Key: JBDS-4438 > URL: https://issues.jboss.org/browse/JBDS-4438 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 11.0.0.AM1 > Environment: Windows > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 11.0.0.AM2 > > > DevSuite Installer should check if target disk has enough free space to continue installation. Before implementing UI for that platform.js module should have corresponding method to get the actual number. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24617) Docker New and Noteworthy for 4.5.0.AM2

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24617?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-24617. ------------------------------ > Docker New and Noteworthy for 4.5.0.AM2 > --------------------------------------------------- > > Key: JBIDE-24617 > URL: https://issues.jboss.org/browse/JBIDE-24617 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: docker > Reporter: Jeff MAURY > Assignee: Jeff Johnston > Priority: Critical > Fix For: 4.5.0.AM2 > > > Jeff Johnston, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Docker 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 Docker, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Docker 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... {code}JBIDE-24614 #comment Create N&N for Docker 4.5.0.AM2 #close{code}... 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 Docker for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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