October 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (ERT-441) Cannot export native app [EBZ#506551]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-441: --------------------------------------- Summary: Cannot export native app [EBZ#506551] Key: ERT-441 URL: https://issues.jboss.org/browse/ERT-441 Project: Eclipse Release Train Issue Type: Task Components: Thym Reporter: Friendly Jira Robot Fix For: Neon (4.6) Created attachment 265051 screen.png Error code 65 for command: xcodebuild with args: -xcconfig,/Users/psrna/data/workspaces/10_2-am3_01/test.hyb.app/platforms/ios/cordova/build-debug.xcconfig,-project,test hyb app.xcodeproj,-target,test hyb app,-configuration,Debug,-destination,platform=iOS,build,CONFIGURATION_BUILD_DIR=/Users/psrna/data/workspaces/10_2-am3_01/test.hyb.app/platforms/ios/build/device,SHARED_PRECOMPS_DIR=/Users/psrna/data/workspaces/10_2-am3_01/test.hyb.app/platforms/ios/build/sharedpch -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-958) Create test for RHBPMS-4334

by Jozef Marko (JIRA)

Jozef Marko created JBTIS-958: --------------------------------- Summary: Create test for RHBPMS-4334 Key: JBTIS-958 URL: https://issues.jboss.org/browse/JBTIS-958 Project: JBoss Tools Integration Stack Issue Type: Task Components: BPMN2, QE Affects Versions: 4.4.0.Alpha1 Reporter: Jozef Marko Assignee: Jozef Marko Create test, that will verify if the error event created in business central can be saved after import into bpmn2 modeler. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4059) unresolved shared libraries when installing rh-eclipse46-devstudio rpm

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBDS-4059?page=com.atlassian.jira.plugin.... ] Pavol Srna closed JBDS-4059. ---------------------------- All other problems tracked under https://issues.jboss.org/browse/JBDS-3984. Closing. > unresolved shared libraries when installing rh-eclipse46-devstudio rpm > ---------------------------------------------------------------------- > > Key: JBDS-4059 > URL: https://issues.jboss.org/browse/JBDS-4059 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, rpm > Reporter: Pavol Srna > Assignee: Nick Boldt > Fix For: 10.2.0.AM3 > > > [~vkadlcik] has run some rpm sanity tests. The findings can be seen here: http://nest.test.redhat.com/mnt/qa/scratch/bkr-hv03-guest19/2016:24366/tp... > [~nickboldt] can you please investigate? Thanks! -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-948) Runtime is not detected if the Devstudio was installed using the InstallConfigRecord.xml

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-948?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky edited comment on JBTIS-948 at 10/26/16 5:10 AM: ------------------------------------------------------------------- I've found the issue JBDS-4075 (The installation config doesn't work in Devstudio 10.1.0.GA) which could be related to this one. EDIT: issue JBDS-4075 is the one you have found in your first comment. was (Author: apodhrad): I've found the issue JBDS-4075 (The installation config doesn't work in Devstudio 10.1.0.GA) which could be related to this one. > Runtime is not detected if the Devstudio was installed using the InstallConfigRecord.xml > ---------------------------------------------------------------------------------------- > > Key: JBTIS-948 > URL: https://issues.jboss.org/browse/JBTIS-948 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 10.0.0.CR1 > Environment: devstudio-integration-stack-rt-10.0.0.CR1-standalone-installer.jar > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > > Runtime is not detected if the Devstudio was installed using the InstallConfigRecord.xml. It seems that the folder for runtime detection is set to {{<user>/jboss-runtimes}}. > The above folder can be found at Preferences > JBoss Tools > JBoss Runtime Detection -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-948) Runtime is not detected if the Devstudio was installed using the InstallConfigRecord.xml

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-948?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky commented on JBTIS-948: ----------------------------------------- But this issue looks a bit different. The installation proceeds without any problem and the fuse runtime is in the folder 'devstudio'. So the only one problem is that the runtime detector is not set. > Runtime is not detected if the Devstudio was installed using the InstallConfigRecord.xml > ---------------------------------------------------------------------------------------- > > Key: JBTIS-948 > URL: https://issues.jboss.org/browse/JBTIS-948 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 10.0.0.CR1 > Environment: devstudio-integration-stack-rt-10.0.0.CR1-standalone-installer.jar > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > > Runtime is not detected if the Devstudio was installed using the InstallConfigRecord.xml. It seems that the folder for runtime detection is set to {{<user>/jboss-runtimes}}. > The above folder can be found at Preferences > JBoss Tools > JBoss Runtime Detection -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-948) Runtime is not detected if the Devstudio was installed using the InstallConfigRecord.xml

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-948?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky commented on JBTIS-948: ----------------------------------------- I've found the issue JBDS-4075 (The installation config doesn't work in Devstudio 10.1.0.GA) which could be related to this one. > Runtime is not detected if the Devstudio was installed using the InstallConfigRecord.xml > ---------------------------------------------------------------------------------------- > > Key: JBTIS-948 > URL: https://issues.jboss.org/browse/JBTIS-948 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 10.0.0.CR1 > Environment: devstudio-integration-stack-rt-10.0.0.CR1-standalone-installer.jar > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > > Runtime is not detected if the Devstudio was installed using the InstallConfigRecord.xml. It seems that the folder for runtime detection is set to {{<user>/jboss-runtimes}}. > The above folder can be found at Preferences > JBoss Tools > JBoss Runtime Detection -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23030) Scaling a service changes the wrong deployment

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23030?page=com.atlassian.jira.plugi... ] Radim Hopp commented on JBIDE-23030: ------------------------------------ I'll take a look right after lunch ;-) > Scaling a service changes the wrong deployment > ---------------------------------------------- > > Key: JBIDE-23030 > URL: https://issues.jboss.org/browse/JBIDE-23030 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Fred Bricon > Assignee: Jeff Cantrill > Priority: Critical > Fix For: 4.4.2.AM3 > > Attachments: scale-to-shows-old-rc.ogv > > > In openshift explorer, when scaling a service that has 2 deployments, it deploys pod from the oldest deployment instead of the latest. Eventually, these pods are killed by openshift. > The workaround is to open the properties view and issue a scale command on a deployment directly. > However, because scaling is such a front-and-center feature from the explorer, I believe it's critical we fix it ASAP > (copied from JBIDE-23412) > The following steps can be seen in the following screencast: > [^scale-to-shows-old-rc.ogv] > # ASSERT: have an app running (ex. nodejs-example) > # ASSERT: In OpenShift Explorer: make sure it has at least 1 pod: pick "Scale To" in the context menu of the service. Dialog shows that there's at least 1 pod currently > # ASSERT: in OpenShift Explorer: there 1 pod shown as child to the service. > # ASSERT: in Properties view, pick "Deployments" tab and see that there's at least 1 deployment (aka replication controller) > # EXEC: in OpenShift explorer: select Service pick "Deploy Latest" > # ASSERT: in Properties view: "Deployments" now shows 2 Deployments > # ASSERT: in OpenShift Explorer you now see 2 children/pods > # EXEC: in OpenShift Explorer: pick "Scale To..." in the context menu of the service > Result: > The current number of pods is shown as 0. > !replicas-0.png! > But it's very sure that this is not true. Behind the scenes a new replication controller was created which deployed a new pod: > !rc2-replicas-1.png! > The old replication controller was turned to have 0 pods. The "Scale To" dialog shows the number of replcas for the old replication controller. > !rc-1-replicas-0.png! -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-954) Fuse: Fix all automated tests for 9.0.0

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBTIS-954?page=com.atlassian.jira.plugin.... ] Tomáš Sedmík updated JBTIS-954: ------------------------------- Original Estimate: 1 day Remaining Estimate: 1 day > Fuse: Fix all automated tests for 9.0.0 > --------------------------------------- > > Key: JBTIS-954 > URL: https://issues.jboss.org/browse/JBTIS-954 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: Fuse IDE, QE > Affects Versions: 4.4.0.Alpha1 > Reporter: Tomáš Sedmík > Assignee: Tomáš Sedmík > Priority: Blocker > Fix For: 4.4.0.Final > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Some tests end with errors (for example _CamelEditorTest_) -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-946) Fix few tests according to changes in TD 10.0.2

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBTIS-946?page=com.atlassian.jira.plugin.... ] Tomáš Sedmík closed JBTIS-946. ------------------------------ Resolution: Done PR was pushed to master, jbtis-4.3.x and jbtis-4.4.x branches > Fix few tests according to changes in TD 10.0.2 > ----------------------------------------------- > > Key: JBTIS-946 > URL: https://issues.jboss.org/browse/JBTIS-946 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: QE, teiid > Affects Versions: 4.3.2.Final > Reporter: Matus Makovy > Assignee: Matus Makovy > Fix For: 4.3.3.Final > > -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-943) SY - Do no use direct API for deleting projects in tests

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBTIS-943?page=com.atlassian.jira.plugin.... ] Tomáš Sedmík closed JBTIS-943. ------------------------------ Resolution: Done PR was pushed to master and jbtis-4.4.x branches > SY - Do no use direct API for deleting projects in tests > -------------------------------------------------------- > > Key: JBTIS-943 > URL: https://issues.jboss.org/browse/JBTIS-943 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: QE, switchyard > Affects Versions: 4.4.0.Alpha1 > Reporter: Andrej Podhradsky > Assignee: Andrej Podhradsky > Fix For: 4.4.0.Final > > -- This message was sent by Atlassian JIRA (v7.2.2#72004)

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