August 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-838) Unable to add nested <when> in Camel - Blueprint

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-838?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBTIS-838: ---------------------------------- Moved to Integration Stack (JBTIS) and assigned to Paul as FYI. > Unable to add nested <when> in Camel - Blueprint > ------------------------------------------------ > > Key: JBTIS-838 > URL: https://issues.jboss.org/browse/JBTIS-838 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Affects Versions: 8.0.0.GA, 9.0.0.GA > Reporter: Abel BOUCHAMA > Assignee: Paul Leacu > Fix For: 9.0.0.GA > > > When we add <when> condition in existing <when> block in blueprint.xml source view, and we save it. If we go after to design view and come back after to source view, the new block <when> disappear. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-838) Unable to add nested <when> in Camel - Blueprint

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-838?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBTIS-838: ----------------------------- Project: JBoss Tools Integration Stack (was: Red Hat JBoss Developer Studio (devstudio)) Key: JBTIS-838 (was: JBDS-4006) Workflow: GIT Pull Request workflow (was: CDW v1) Docs QE Status: (was: NEW) Affects Version/s: 9.0.0.GA 8.0.0.GA (was: 8.0.0.GA) > Unable to add nested <when> in Camel - Blueprint > ------------------------------------------------ > > Key: JBTIS-838 > URL: https://issues.jboss.org/browse/JBTIS-838 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Affects Versions: 9.0.0.GA, 8.0.0.GA > Reporter: Abel BOUCHAMA > > When we add <when> condition in existing <when> block in blueprint.xml source view, and we save it. If we go after to design view and come back after to source view, the new block <when> disappear. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23019) Integration tests: have them running automatically, continuously

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-23019: ---------------------------------------- Summary: Integration tests: have them running automatically, continuously Key: JBIDE-23019 URL: https://issues.jboss.org/browse/JBIDE-23019 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 4.4.1.AM3 Reporter: Andre Dietisheim Fix For: 4.5.x The integration tests suite is very lenghty to run and should thus be run in a continuous manner on our CI. There are several pain-points currently: - there's no dedicated OS instance to run them against - tests are not stable - etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-837) JBTIS Target Platform - Neon - sync with JBT 4.4.1.AM3

by Paul Leacu (JIRA)

Paul Leacu created JBTIS-837: -------------------------------- Summary: JBTIS Target Platform - Neon - sync with JBT 4.4.1.AM3 Key: JBTIS-837 URL: https://issues.jboss.org/browse/JBTIS-837 Project: JBoss Tools Integration Stack Issue Type: Feature Request Components: target-platform Affects Versions: 4.4.0.Alpha1-TP Reporter: Paul Leacu Assignee: Paul Leacu Sync w/ 4.4.1.AM3 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-834) JBTIS Target Platform - Mars - add swtbot.ide feature dependency for Fuse/SY

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-834?page=com.atlassian.jira.plugin.... ] Paul Leacu closed JBTIS-834. ---------------------------- Resolution: Rejected This works ok in Neon and we don't want to respin the Mars TP from .Final this late. > JBTIS Target Platform - Mars - add swtbot.ide feature dependency for Fuse/SY > ---------------------------------------------------------------------------- > > Key: JBTIS-834 > URL: https://issues.jboss.org/browse/JBTIS-834 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: target-platform > Affects Versions: 4.3.2.Final-TP > Reporter: Paul Leacu > Assignee: Paul Leacu > > *Reason:* IS dependency for Fuse/SY > *Project page/sources:* > *Version:* 4.3.3 > *License and owner:* EPL > *Original p2 repo:* > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/swtbot/2.3.0/ > *Include Sources:* Yes > *Affected JBoss Tools components:* Integration Stack > *Include in JBDS:* Yes JBDSIS > *Type of dependency:* testing|central-only|distribution > *List of bundles added/removed:* > {code} > > org.eclipse.swtbot.eclipse.spy [2.3.0.201506081302] > > org.eclipse.swtbot.generator.jdt [2.3.0.201506081302] > > org.eclipse.swtbot.ide.feature.group [2.3.0.201506081302] > > org.eclipse.swtbot.ide.feature.jar [2.3.0.201506081302] > > org.eclipse.swtbot.generator.rules.workbench [2.3.0.201506081302] > > org.eclipse.swtbot.generator [2.3.0.201506081302] > > org.eclipse.swtbot.generator.feature.feature.jar [2.3.0.201506081302] > > org.eclipse.swtbot.generator.ui [2.3.0.201506081302] > > org.eclipse.swtbot.eclipse.ui [2.3.0.201506081302] > > org.eclipse.swtbot.generator.feature.feature.group [2.3.0.201506081302] > === Summary === > file:///home/pleacu/git-clone/jbosstools-integration-stack/target-platform/target/target-platform.target.repo contains 10 unique IUs > {code} > The JBT core TP dependencies are: > http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-834) JBTIS Target Platform - Mars - add swtbot.ide feature dependency for Fuse/SY

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-834?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-834: ---------------------------------- So - given this works ok on Neon - I'll close this issue and leave the TP (which is already at .Fina) alone - if we are all in agreement. [~bfitzpat] [~apodhrad] > JBTIS Target Platform - Mars - add swtbot.ide feature dependency for Fuse/SY > ---------------------------------------------------------------------------- > > Key: JBTIS-834 > URL: https://issues.jboss.org/browse/JBTIS-834 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: target-platform > Affects Versions: 4.3.2.Final-TP > Reporter: Paul Leacu > Assignee: Paul Leacu > > *Reason:* IS dependency for Fuse/SY > *Project page/sources:* > *Version:* 4.3.3 > *License and owner:* EPL > *Original p2 repo:* > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/swtbot/2.3.0/ > *Include Sources:* Yes > *Affected JBoss Tools components:* Integration Stack > *Include in JBDS:* Yes JBDSIS > *Type of dependency:* testing|central-only|distribution > *List of bundles added/removed:* > {code} > > org.eclipse.swtbot.eclipse.spy [2.3.0.201506081302] > > org.eclipse.swtbot.generator.jdt [2.3.0.201506081302] > > org.eclipse.swtbot.ide.feature.group [2.3.0.201506081302] > > org.eclipse.swtbot.ide.feature.jar [2.3.0.201506081302] > > org.eclipse.swtbot.generator.rules.workbench [2.3.0.201506081302] > > org.eclipse.swtbot.generator [2.3.0.201506081302] > > org.eclipse.swtbot.generator.feature.feature.jar [2.3.0.201506081302] > > org.eclipse.swtbot.generator.ui [2.3.0.201506081302] > > org.eclipse.swtbot.eclipse.ui [2.3.0.201506081302] > > org.eclipse.swtbot.generator.feature.feature.group [2.3.0.201506081302] > === Summary === > file:///home/pleacu/git-clone/jbosstools-integration-stack/target-platform/target/target-platform.target.repo contains 10 unique IUs > {code} > The JBT core TP dependencies are: > http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-834) JBTIS Target Platform - Mars - add swtbot.ide feature dependency for Fuse/SY

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBTIS-834?page=com.atlassian.jira.plugin.... ] Brian Fitzpatrick commented on JBTIS-834: ----------------------------------------- This came up for a few reasons and it should probably be rejected after all. 1) The Mars TP already includes parts of the SWTBot framework but not all of it. I ran into an issue where I was unable to install the rest of it on a local workbench because of an issue somewhere up the update site chain with a missing dependency. It gets most of the way through the install and then fails with: {code} An error occurred while collecting items to be installed session context was:(profile=C__jee-mars-29-SEP-2015_eclipse, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). No repository found containing: osgi.bundle,org.apache.commons.io,2.4.0 {code} 2) We are attempting to do more testing on the development side, ensuring that we aren't breaking functionality as we add it so I am attempting to resurrect the SWTbot tests that I wrote for SwitchYard a while back. In order to run them, I need (1) to work. Ultimately this is not enough of a reason to include the remaining SWTBot bits in the TP but I am out of ideas of how to resolve the problems otherwise. It installs just fine on a Neon-based workbench btw so this is purely a Mars issue. Hopefully that clarifies things a bit. > JBTIS Target Platform - Mars - add swtbot.ide feature dependency for Fuse/SY > ---------------------------------------------------------------------------- > > Key: JBTIS-834 > URL: https://issues.jboss.org/browse/JBTIS-834 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: target-platform > Affects Versions: 4.3.2.Final-TP > Reporter: Paul Leacu > Assignee: Paul Leacu > > *Reason:* IS dependency for Fuse/SY > *Project page/sources:* > *Version:* 4.3.3 > *License and owner:* EPL > *Original p2 repo:* > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/swtbot/2.3.0/ > *Include Sources:* Yes > *Affected JBoss Tools components:* Integration Stack > *Include in JBDS:* Yes JBDSIS > *Type of dependency:* testing|central-only|distribution > *List of bundles added/removed:* > {code} > > org.eclipse.swtbot.eclipse.spy [2.3.0.201506081302] > > org.eclipse.swtbot.generator.jdt [2.3.0.201506081302] > > org.eclipse.swtbot.ide.feature.group [2.3.0.201506081302] > > org.eclipse.swtbot.ide.feature.jar [2.3.0.201506081302] > > org.eclipse.swtbot.generator.rules.workbench [2.3.0.201506081302] > > org.eclipse.swtbot.generator [2.3.0.201506081302] > > org.eclipse.swtbot.generator.feature.feature.jar [2.3.0.201506081302] > > org.eclipse.swtbot.generator.ui [2.3.0.201506081302] > > org.eclipse.swtbot.eclipse.ui [2.3.0.201506081302] > > org.eclipse.swtbot.generator.feature.feature.group [2.3.0.201506081302] > === Summary === > file:///home/pleacu/git-clone/jbosstools-integration-stack/target-platform/target/target-platform.target.repo contains 10 unique IUs > {code} > The JBT core TP dependencies are: > http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22992) OpenShift tools use wrong rest client bits

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22992?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22992: ------------------------------------------ I just checked the latest builds. Even though they fail complaining about not being able to build the cdk server source feature, artifacts are built and they contain the latest client lib (5.0.0-RC1) > OpenShift tools use wrong rest client bits > ------------------------------------------ > > Key: JBIDE-22992 > URL: https://issues.jboss.org/browse/JBIDE-22992 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, openshift > Affects Versions: 4.4.1.AM3 > Environment: eclipse.buildId=10.1.0.AM3-v20160810-0441-B5735 > java.version=1.8.0_101 > java.vendor=Oracle Corporation > BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US > Framework arguments: -product com.jboss.devstudio.core.product > Command-line arguments: -os win32 -ws win32 -arch x86_64 -product com.jboss.devstudio.core.product > Reporter: Denis Golovin > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.4.1.Final > > Attachments: IU-unchanged-not-published.png, openshift-client-IU-new-timestamp.png, openshift-client-IU.png > > > An internal error occurred during: "Loading service-manager to configure additional frameworks that CDK depends on.".{code}java.lang.NoSuchMethodError: com.openshift.restclient.ClientBuilder.withMaxRequests(I)Lcom/openshift/restclient/ClientBuilder; > at org.jboss.tools.openshift.core.connection.ConnectionFactory.create(ConnectionFactory.java:53) > at org.jboss.tools.openshift.core.connection.ConnectionFactory.create(ConnectionFactory.java:1) > at org.jboss.tools.openshift.cdk.server.core.internal.listeners.CDKOpenshiftUtility.createOpenshiftConnection(CDKOpenshiftUtility.java:77) > at org.jboss.tools.openshift.cdk.server.core.internal.listeners.CDKOpenshiftUtility.createOpenshiftConnection(CDKOpenshiftUtility.java:55) > at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ConfigureDependentFrameworksListener.configureOpenshift(ConfigureDependentFrameworksListener.java:91) > at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ConfigureDependentFrameworksListener.configureFrameworks(ConfigureDependentFrameworksListener.java:56) > at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ConfigureDependentFrameworksListener$1.run(ConfigureDependentFrameworksListener.java:44) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55){code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22965) CDK tools should work behind proxy

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22965?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-22965: ------------------------------------- Description: Proxy support has been added in CDK vagrant box and in vagrant-registration plugin. We should make sure our CDK tooling supports it too. Eclipse Proxy Testing link: https://mojo.redhat.com/docs/DOC-989982 was: Proxy support has been added in CDK vagrant box and in vagrant-registration plugin. We should make sure our CDK tooling supports it too. > CDK tools should work behind proxy > ---------------------------------- > > Key: JBIDE-22965 > URL: https://issues.jboss.org/browse/JBIDE-22965 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Reporter: Alexey Kazakov > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.4.1.Final > > > Proxy support has been added in CDK vagrant box and in vagrant-registration plugin. > We should make sure our CDK tooling supports it too. > Eclipse Proxy Testing link: https://mojo.redhat.com/docs/DOC-989982 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3627) Installer needs to help move past lack of t/c signing

by David Hladky (JIRA)

[ https://issues.jboss.org/browse/JBDS-3627?page=com.atlassian.jira.plugin.... ] David Hladky commented on JBDS-3627: ------------------------------------ Hi, thanks, sorry, I overlooked it. You are right about the behaviour and it is not correct one. The reason why this happens is Keycloak refuses the credentials with following message: dhladky+error: java.io.IOException: Bad status: 400 response: {"error_description":"Account is not fully set up","error":"invalid_grant"} at ...... This behaviour started in June this year due to Keycloak started to manage the permissions during the user login. Vlastimil added "required actions" and since then the logic is broken. I created RHDENG-750 .The logic of how the service is supposed to be working is as described earlier. I will look into it when I return from vacation. > Installer needs to help move past lack of t/c signing > ----------------------------------------------------- > > Key: JBDS-3627 > URL: https://issues.jboss.org/browse/JBDS-3627 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Reporter: Joshua Wilson > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.1.0.AM3 > > Attachments: Installer-not-signed-tc.PNG > > > DevSuite installer uses "REST services in JBoss Download Manager" explained here https://mojo.redhat.com/docs/DOC-940689. > DevSuite Intsaller follows the explanation for tc-accepted entry point [code is here|https://github.com/redhat-developer-tooling/developer-platform-insta...]. It uses file from previous CDK release (published in cdn and available through download manager) to do verification: > 1. that provided credentials are valid; > 2. that required T&C's are signed. > There are two major use cases for developers installing DevSuite using Installer: > 1. Direct download - when developer sign in to developers.redhat.com and download installer himeslf; > 2. Shared installer - when someone share installer with developers without account. > There two kind of users involved in those scenarios above: > 1. New users that must go through registration process; > 2. Registered users. > *Direct download* > For new ones registration process is really simple now. After creating RHD account and downloading installer there is no additional steps to get through installation. > For already registered users there could be problems related to T&C's and authentication reported here https://issues.jboss.org/browse/RHDENG-579. > So far there are two kind of problems: > 1. Users can login and download DevSuite installer, but cannot use the same credentials to install; > 2. Users that can login in to developers.redhat.com and get request to sign additional T&C's but credentials for the same user in DevSuite Installer reported as invalid when REST tc-accepted entry point is used > *Shared Download* > In this scenario new users without account can press Register link, then go through registration process in browser return back to installer and use new account credentials for installation. > Registered users could need to sign additional T&C's if missing and would be good to show external link to do so. Current entry point tc-accepted does not provide any hints where missing T&C's could be signed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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