January 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23463) Properties: Build pod has state of exit code 0 instead of correct status completed

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23463?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23463: ------------------------------------------ PR was merged into opeshift-restclient-java/master. resolving. > Properties: Build pod has state of exit code 0 instead of correct status completed > ---------------------------------------------------------------------------------- > > Key: JBIDE-23463 > URL: https://issues.jboss.org/browse/JBIDE-23463 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM3 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Labels: openshift_v3 > Fix For: 4.4.3.AM1 > > Attachments: build-pod-completed.png, exit-code-0.png > > > When I create a new OpenShift 3 application from a template, there is a running build. Once a build pod is completed, it has status "Completed". But now it Pods tabbed properties it contains status "Exit Code: 0" which is not user friendly and it broke integration tests. > steps: > # EXEC: create an application via a s2i template > # EXEC: in OpenShift explorer: select the connection that you used to create the application and open up the "Properties view" > # EXEC: in Properties: select "Pods" tab. > # ASSERT: a build pod is appearing > # EXEC: wait until the build pod is terminated and then look at its "Status" in the Properties > Pods > Result: > The status for the pod is reported with a "Exit Code: 0" (if successfully terminated, "Exit Code: 1" otherwise) > !exit-code-0.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23463) Properties: Build pod has state of exit code 0 instead of correct status completed

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23463?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23463: ------------------------------------- Attachment: build-pod-completed.png > Properties: Build pod has state of exit code 0 instead of correct status completed > ---------------------------------------------------------------------------------- > > Key: JBIDE-23463 > URL: https://issues.jboss.org/browse/JBIDE-23463 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM3 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Labels: openshift_v3 > Fix For: 4.4.3.AM1 > > Attachments: build-pod-completed.png, exit-code-0.png > > > When I create a new OpenShift 3 application from a template, there is a running build. Once a build pod is completed, it has status "Completed". But now it Pods tabbed properties it contains status "Exit Code: 0" which is not user friendly and it broke integration tests. > steps: > # EXEC: create an application via a s2i template > # EXEC: in OpenShift explorer: select the connection that you used to create the application and open up the "Properties view" > # EXEC: in Properties: select "Pods" tab. > # ASSERT: a build pod is appearing > # EXEC: wait until the build pod is terminated and then look at its "Status" in the Properties > Pods > Result: > The status for the pod is reported with a "Exit Code: 0" (if successfully terminated, "Exit Code: 1" otherwise) > !exit-code-0.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23463) Properties: Build pod has state of exit code 0 instead of correct status completed

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23463?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23463: ------------------------------------------ [~scabanovich] works as expected, the build pod status is now "Completed". Thanks! !build-pod-completed.png! > Properties: Build pod has state of exit code 0 instead of correct status completed > ---------------------------------------------------------------------------------- > > Key: JBIDE-23463 > URL: https://issues.jboss.org/browse/JBIDE-23463 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM3 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Labels: openshift_v3 > Fix For: 4.4.3.AM1 > > Attachments: exit-code-0.png > > > When I create a new OpenShift 3 application from a template, there is a running build. Once a build pod is completed, it has status "Completed". But now it Pods tabbed properties it contains status "Exit Code: 0" which is not user friendly and it broke integration tests. > steps: > # EXEC: create an application via a s2i template > # EXEC: in OpenShift explorer: select the connection that you used to create the application and open up the "Properties view" > # EXEC: in Properties: select "Pods" tab. > # ASSERT: a build pod is appearing > # EXEC: wait until the build pod is terminated and then look at its "Status" in the Properties > Pods > Result: > The status for the pod is reported with a "Exit Code: 0" (if successfully terminated, "Exit Code: 1" otherwise) > !exit-code-0.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4230) JBDS running on Fedora 25 with Wayland makes GUI rendering awful and return "No more handles" every time

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4230?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-4230 at 1/4/17 8:42 AM: ---------------------------------------------------------- Latest snapshot build (devstudio-10.3.0.AM1-v20170103-1259-B6826-installer-standalone.jar) contains a new executable: {code}devstudio-wayland{code} [~rimolive] Can you try that and see if it works for you? Get latest installer from https://devstudio.jboss.com/10.0/snapshots/builds/devstudio.product_maste... was (Author: nickboldt): Latest snapshot build (devstudio-10.3.0.AM1-v20170103-1259-B6826-installer-standalone.jar) contains a new executable: {code}devstudio-wayland{code} [~rimolive] Can you try that and see if it works for you? > JBDS running on Fedora 25 with Wayland makes GUI rendering awful and return "No more handles" every time > -------------------------------------------------------------------------------------------------------- > > Key: JBDS-4230 > URL: https://issues.jboss.org/browse/JBDS-4230 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 10.2.0.GA > Environment: Fedora 25 with Wayland > Reporter: Ricardo Martinelli Oliveira > Assignee: Nick Boldt > Priority: Critical > Fix For: 10.3.0.AM1 > > > Workaround: Add GDK_BACKEND=x11 in devstudio.ini file to force use x11 to run JBDS. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4204) Red Hat JBoss Developer Studio and dialogs do not size correctly under Fedora 25 w/ Wayland

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4204?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4204: ---------------------------------- Solution for devstudio installer is merged and available from latest CI builds. See JBDS-4230 and get latest from https://devstudio.jboss.com/10.0/snapshots/builds/devstudio.product_maste... No progress on rpm solution. > Red Hat JBoss Developer Studio and dialogs do not size correctly under Fedora 25 w/ Wayland > ------------------------------------------------------------------------------------------- > > Key: JBDS-4204 > URL: https://issues.jboss.org/browse/JBDS-4204 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: upstream > Affects Versions: 10.1.0.GA > Environment: FC25, wayland > Reporter: cube 00 > Assignee: Snjezana Peco > Labels: upstream > Fix For: 10.3.0.AM1 > > Attachments: jboss1.png, jboss2.png, jboss3.PnG, jbosstools-diagnostics-20161129110614.zip > > > The window either cuts the top off, bottom off or overdraws into space near the window. Dialogs have their OK/Cancel buttons hidden and resizing does not make them appear either. > Appears to be related to Wayland as I [disabled it|https://fedoraproject.org/wiki/Changes/WaylandByDefault] and things are back to normal. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4204) Red Hat JBoss Developer Studio and dialogs do not size correctly under Fedora 25 w/ Wayland

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4204?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4204: ----------------------------- Summary: Red Hat JBoss Developer Studio and dialogs do not size correctly under Fedora 25 w/ Wayland (was: JBoss IDE and dialogs not sizing correctly under Fedora 25) > Red Hat JBoss Developer Studio and dialogs do not size correctly under Fedora 25 w/ Wayland > ------------------------------------------------------------------------------------------- > > Key: JBDS-4204 > URL: https://issues.jboss.org/browse/JBDS-4204 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: upstream > Affects Versions: 10.1.0.GA > Environment: FC25, wayland > Reporter: cube 00 > Assignee: Snjezana Peco > Labels: upstream > Fix For: 10.3.0.AM1 > > Attachments: jboss1.png, jboss2.png, jboss3.PnG, jbosstools-diagnostics-20161129110614.zip > > > The window either cuts the top off, bottom off or overdraws into space near the window. Dialogs have their OK/Cancel buttons hidden and resizing does not make them appear either. > Appears to be related to Wayland as I [disabled it|https://fedoraproject.org/wiki/Changes/WaylandByDefault] and things are back to normal. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4236) Test of update of devstudio from last stable version to last snapshot doesn't work

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4236?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4236: ---------------------------------- If you're inheriting values from the jbosstools parent pom, then please use TARGET_PLATFORM_VERSION_MAX instead of TARGET_PLATFORM_VERSION_MAXIMUM. Or better yet, don't set tpc.version at all because you're using the version from parent pom so don't need to override using the same value. https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... Also, the latest parent pom version is 4.4.3.AM1-SNAPSHOT. https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml#L7 Should you be using that version instead of 4.4.2.Final ? > Test of update of devstudio from last stable version to last snapshot doesn't work > ---------------------------------------------------------------------------------- > > Key: JBDS-4236 > URL: https://issues.jboss.org/browse/JBDS-4236 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: install-tests > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Labels: integration-test > Fix For: 10.3.0.AM1 > > > Test of update from last stable to last snapshot doesn't work, there is following error in the log: > {code} > Multiple versions of the framework bundle org.eclipse.osgi found > {code} > Jenkins job: > http://machydra.brq.redhat.com:8080/view/Installation%20Jobs/view/DevStud... > Log: > http://machydra.brq.redhat.com:8080/view/Installation%20Jobs/view/DevStud... > It is probably because of inconsistence between bundles/plugins versions, so I tried to change parent from 4.4.2.AM1-SNAPSHOT to 4.4.2.Final-SNAPSHOT which was used in 10.2.0.GA I guess. > Unfortunatelly it has not solved my problem, tycho has been still installing another version of org.eclipse.osgi bundle. So I tried to apply same fix as in JBDS-4077 > Commit: > https://source.jboss.org/changelog/JBossToolsIntegrationTests?cs=2acfada0... > It solved problem with multiple versions of osgi bundle but I got another error during start of devstudio > {code} > !ENTRY org.eclipse.osgi 4 0 2017-01-04 10:40:36.851 > !MESSAGE Application error > !STACK 1 > java.lang.RuntimeException: Application "org.eclipse.tycho.surefire.osgibooter.uitest" could not be found in the registry. > {code} > Whole log > http://machydra.brq.redhat.com:8080/view/Installation%20Jobs/view/DevStud... > Please notice I started job using my fork. > My changes are here > https://github.com/luvalach/jbdevstudio-qa/commit/133ac415ede6a2a9d6758d7... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4236) Test of update of devstudio from last stable version to last snapshot doesn't work

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4236?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4236: ----------------------------- Fix Version/s: 10.3.0.AM1 (was: 10.3.0.AM2) > Test of update of devstudio from last stable version to last snapshot doesn't work > ---------------------------------------------------------------------------------- > > Key: JBDS-4236 > URL: https://issues.jboss.org/browse/JBDS-4236 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: install-tests > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Labels: integration-test > Fix For: 10.3.0.AM1 > > > Test of update from last stable to last snapshot doesn't work, there is following error in the log: > {code} > Multiple versions of the framework bundle org.eclipse.osgi found > {code} > Jenkins job: > http://machydra.brq.redhat.com:8080/view/Installation%20Jobs/view/DevStud... > Log: > http://machydra.brq.redhat.com:8080/view/Installation%20Jobs/view/DevStud... > It is probably because of inconsistence between bundles/plugins versions, so I tried to change parent from 4.4.2.AM1-SNAPSHOT to 4.4.2.Final-SNAPSHOT which was used in 10.2.0.GA I guess. > Unfortunatelly it has not solved my problem, tycho has been still installing another version of org.eclipse.osgi bundle. So I tried to apply same fix as in JBDS-4077 > Commit: > https://source.jboss.org/changelog/JBossToolsIntegrationTests?cs=2acfada0... > It solved problem with multiple versions of osgi bundle but I got another error during start of devstudio > {code} > !ENTRY org.eclipse.osgi 4 0 2017-01-04 10:40:36.851 > !MESSAGE Application error > !STACK 1 > java.lang.RuntimeException: Application "org.eclipse.tycho.surefire.osgibooter.uitest" could not be found in the registry. > {code} > Whole log > http://machydra.brq.redhat.com:8080/view/Installation%20Jobs/view/DevStud... > Please notice I started job using my fork. > My changes are here > https://github.com/luvalach/jbdevstudio-qa/commit/133ac415ede6a2a9d6758d7... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1011) Create UI test for language / dataformats properties

by Lars Heinemann (JIRA)

Lars Heinemann created JBTIS-1011: ------------------------------------- Summary: Create UI test for language / dataformats properties Key: JBTIS-1011 URL: https://issues.jboss.org/browse/JBTIS-1011 Project: JBoss Tools Integration Stack Issue Type: Task Components: Fuse IDE, QE Affects Versions: 10.0.0.Alpha1 Reporter: Lars Heinemann Assignee: Andrej Podhradsky Fix For: 10.0.0.GA If you select a "transform" endpoint in the diagram and set a new expression language the pom.xml should be updated to contain the dependency of the new language if not yet there. Same applies to dataformats (for instance "marshal" endpoints). Whenever you change the dataformat in the properties view to some other data format the dependency for that data format should be added to the pom.xml if its not yet there. Please find more information on this issue in FUSETOOLS-2186. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4236) Test of update of devstudio from last stable version to last snapshot doesn't work

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBDS-4236?page=com.atlassian.jira.plugin.... ] Lukáš Valach commented on JBDS-4236: ------------------------------------ Problem has been solved. It helped to change profile name from "jbds" to "devstudio" and start maven with installBase parameter instead of installPath parameter. I also removed <tpc.version> from pom.xml/project/build/plugins/plugin/tycho-surefire-plugin/configuration/systemProperties and let in only in pom.xml/project/properties. It seems that tpc.version in tycho configuration haven't any effect. > Test of update of devstudio from last stable version to last snapshot doesn't work > ---------------------------------------------------------------------------------- > > Key: JBDS-4236 > URL: https://issues.jboss.org/browse/JBDS-4236 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: install-tests > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Labels: integration-test > Fix For: 10.3.0.AM2 > > > Test of update from last stable to last snapshot doesn't work, there is following error in the log: > {code} > Multiple versions of the framework bundle org.eclipse.osgi found > {code} > Jenkins job: > http://machydra.brq.redhat.com:8080/view/Installation%20Jobs/view/DevStud... > Log: > http://machydra.brq.redhat.com:8080/view/Installation%20Jobs/view/DevStud... > It is probably because of inconsistence between bundles/plugins versions, so I tried to change parent from 4.4.2.AM1-SNAPSHOT to 4.4.2.Final-SNAPSHOT which was used in 10.2.0.GA I guess. > Unfortunatelly it has not solved my problem, tycho has been still installing another version of org.eclipse.osgi bundle. So I tried to apply same fix as in JBDS-4077 > Commit: > https://source.jboss.org/changelog/JBossToolsIntegrationTests?cs=2acfada0... > It solved problem with multiple versions of osgi bundle but I got another error during start of devstudio > {code} > !ENTRY org.eclipse.osgi 4 0 2017-01-04 10:40:36.851 > !MESSAGE Application error > !STACK 1 > java.lang.RuntimeException: Application "org.eclipse.tycho.surefire.osgibooter.uitest" could not be found in the registry. > {code} > Whole log > http://machydra.brq.redhat.com:8080/view/Installation%20Jobs/view/DevStud... > Please notice I started job using my fork. > My changes are here > https://github.com/luvalach/jbdevstudio-qa/commit/133ac415ede6a2a9d6758d7... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 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 January 2017