November 2017 - jbosstools-issues

[JBoss JIRA] (JBDS-3806) Installer - reduce footer height to reveal more content

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3806?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3806: -------------------------------- Fix Version/s: 11.2.0.AM1 (was: 11.x) > Installer - reduce footer height to reveal more content > ------------------------------------------------------- > > Key: JBDS-3806 > URL: https://issues.jboss.org/browse/JBDS-3806 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.Beta2 > Reporter: Joshua Wilson > Assignee: Denis Golovin > Labels: ui > Fix For: 11.2.0.AM1 > > Attachments: confirm.png > > > The footer on the confirm page would look better if it cut into the display of one of the components to be installed. Also, remove the transparency. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3797) Installer: temporary files are not removed when window is closed

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3797?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3797: -------------------------------- Labels: (was: havoc) > Installer: temporary files are not removed when window is closed > ---------------------------------------------------------------- > > Key: JBDS-3797 > URL: https://issues.jboss.org/browse/JBDS-3797 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer, upstream > Reporter: Pavol Pitonak > Assignee: Denis Golovin > Fix For: 11.x > > > # download installer exe > # run DeveloperPlatformInstaller*.exe > # when installer's window opens, close the window > # look into _C:\Users\yourusername\AppData\Local\Temp_ > result: > Temp folder contains several files and directories with name starting *7zS*, with total size of about *1.7GB*, when you open start the installer multiple times, it appears multiple times in Temp -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3863) Platform Installer Hung after CDK install failed, no way to cancel, no info on error.

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3863?page=com.atlassian.jira.plugin.... ] Denis Golovin resolved JBDS-3863. --------------------------------- Resolution: Done Resolved with JBDS-3631: 1. 'Cancel' button added 2. 'Open log' button added > Platform Installer Hung after CDK install failed, no way to cancel, no info on error. > -------------------------------------------------------------------------------------- > > Key: JBDS-3863 > URL: https://issues.jboss.org/browse/JBDS-3863 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 1.1.0.GA, 9.1.0.Beta1 > Environment: Windows 7/64 bit. > (Some components of previous manual CDK install on the system). > Also Windows 10/64. > Reporter: Robert Terzi > Assignee: Denis Golovin > Labels: ui > Fix For: 11.2.0.AM1 > > Attachments: box-add-fail-1.1.0-ga.txt, install.log, jbds-install-log-win7-error.txt > > > Using the platform installer, CDK installation failed, progress shown as 99%. At this point the installer was hung. > Note: > * CDK install progress said Failed, with progress stuck at 99%. > * There is no way to cancel out of the install. > * There was no pop-up about error messages. > * No indication of where to look for error messages/logs etc.was provided. > * CDK was previously installed manually. However, the installer window didn't say a previous CDK installation was detected, but the log does show it deleted the previous cdkv2 box. > From the log it looks like the box add command failed. When originally reported it might have been due to disk space, but it's not clear/obvious from the log. As of DevSuite 1.1.0 GA, the problems still exists if the vagrant box add command fails. Note: I've verified this isn't related to disk space and is a Vagrant problem. > Note: after killing the installer and trying the `vagrant box add` command copied from the log file manually in Cygwin bash the box add command succeeded. The test system had 5-15 GB of free space between the installation started. > Full log attached, excerpt here. > Tue, 26 Apr 2016 18:05:38 GMT-INFO: cdk - Move C:\Users\rct\AppData\Local\Temp\7zSC53C.tmp\rhel-vagrant-virtualbox.box to c:\sw\rhjbds\cdk\boxes\rhel-vagrant-virtualbox.box > Tue, 26 Apr 2016 18:05:43 GMT-INFO: cdk - Move C:\Users\rct\AppData\Local\Temp\7zSC53C.tmp\rhel-vagrant-virtualbox.box to c:\sw\rhjbds\cdk\boxes\rhel-vagrant-virtualbox.box SUCCESS > Tue, 26 Apr 2016 18:05:43 GMT-INFO: cdk - Move C:\Users\rct\AppData\Local\Temp\7zSC53C.tmp\pscp.exe to c:\sw\rhjbds\cdk\bin\pscp.exe > Tue, 26 Apr 2016 18:05:43 GMT-INFO: cdk - Move C:\Users\rct\AppData\Local\Temp\7zSC53C.tmp\pscp.exe to c:\sw\rhjbds\cdk\bin\pscp.exe SUCCESS > Tue, 26 Apr 2016 18:05:43 GMT-INFO: cdk - Write C:\Users\rct\AppData\Local\Temp\set-pscp-path.ps1 > Tue, 26 Apr 2016 18:05:43 GMT-INFO: cdk - Write C:\Users\rct\AppData\Local\Temp\set-pscp-path.ps1 SUCCESS > Tue, 26 Apr 2016 18:05:43 GMT-INFO: cdk - Write c:\sw\rhjbds\cdk\components\rhel\rhel-ose\.cdk > Tue, 26 Apr 2016 18:05:43 GMT-INFO: cdk - Write c:\sw\rhjbds\cdk\components\rhel\rhel-ose\.cdk SUCCESS > Tue, 26 Apr 2016 18:05:43 GMT-INFO: cdk - Execute powershell -ExecutionPolicy,ByPass,-File,C:\Users\rct\AppData\Local\Temp\set-pscp-path.ps1 > Tue, 26 Apr 2016 18:05:44 GMT-INFO: cdk - Execute powershell -ExecutionPolicy,ByPass,-File,C:\Users\rct\AppData\Local\Temp\set-pscp-path.ps1 SUCCESS > Tue, 26 Apr 2016 18:05:44 GMT-INFO: cdk - postVagrantSetup called > Tue, 26 Apr 2016 18:05:44 GMT-INFO: cdk - Execute command vagrant plugin install "c:\sw\rhjbds\cdk\plugins\vagrant-registration-1.2.1.gem" > Tue, 26 Apr 2016 18:05:44 GMT-INFO: cdk - Execute options { > "env": { > "path": "C:\\HashiCorp\\Vagrant\\bin;C:\\Program Files\\Oracle\\VirtualBox\\;" > } > } > Tue, 26 Apr 2016 18:05:55 GMT-INFO: cdk - Installing the 'c:\sw\rhjbds\cdk\plugins\vagrant-registration-1.2.1.gem' plugin. This can take a few minutes... > Installed the plugin 'vagrant-registration (1.2.1)'! > Tue, 26 Apr 2016 18:05:55 GMT-INFO: cdk - Execute vagrant plugin install "c:\sw\rhjbds\cdk\plugins\vagrant-registration-1.2.1.gem" SUCCESS > Tue, 26 Apr 2016 18:05:55 GMT-INFO: cdk - Execute command vagrant box remove cdkv2 -f > Tue, 26 Apr 2016 18:05:55 GMT-INFO: cdk - Execute options { > "env": { > "path": "C:\\HashiCorp\\Vagrant\\bin;C:\\Program Files\\Oracle\\VirtualBox\\;" > } > } > Tue, 26 Apr 2016 18:06:02 GMT-INFO: cdk - Removing box 'cdkv2' (v0) with provider 'virtualbox'... > Tue, 26 Apr 2016 18:06:02 GMT-INFO: cdk - Execute vagrant box remove cdkv2 -f SUCCESS > Tue, 26 Apr 2016 18:06:02 GMT-INFO: cdk - Execute command vagrant box add --name cdkv2 "c:\sw\rhjbds\cdk\boxes\rhel-vagrant-virtualbox.box" > Tue, 26 Apr 2016 18:06:02 GMT-INFO: cdk - Execute options { > "env": { > "path": "C:\\HashiCorp\\Vagrant\\bin;C:\\Program Files\\Oracle\\VirtualBox\\;" > } > } > Tue, 26 Apr 2016 18:06:10 GMT-ERROR: cdk - Error: Command failed: vagrant box add --name cdkv2 "c:\sw\rhjbds\cdk\boxes\rhel-vagrant-virtualbox.box" > The box failed to unpackage properly. Please verify that the box > file you're trying to add is not corrupted and try again. The > output from attempting to unpackage (if any): > x box.ovf > x Vagrantfile > x vagrant-virtualbox-box.vmdk: Write failed > x metadata.json > bsdtar.EXE: Error exit delayed from previous errors. > Tue, 26 Apr 2016 18:06:10 GMT-ERROR: cdk - The box failed to unpackage properly. Please verify that the box > file you're trying to add is not corrupted and try again. The > output from attempting to unpackage (if any): > x box.ovf > x Vagrantfile > x vagrant-virtualbox-box.vmdk: Write failed > x metadata.json > bsdtar.EXE: Error exit delayed from previous errors. > Tue, 26 Apr 2016 18:06:10 GMT-ERROR: cdk failed to install: Error: Command failed: vagrant box add --name cdkv2 "c:\sw\rhjbds\cdk\boxes\rhel-vagrant-virtualbox.box" > The box failed to unpackage properly. Please verify that the box > file you're trying to add is not corrupted and try again. The > output from attempting to unpackage (if any): > x box.ovf > x Vagrantfile > x vagrant-virtualbox-box.vmdk: Write failed > x metadata.json > bsdtar.EXE: Error exit delayed from previous errors. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3863) Platform Installer Hung after CDK install failed, no way to cancel, no info on error.

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3863?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3863: -------------------------------- Fix Version/s: 11.2.0.AM1 (was: 11.x) > Platform Installer Hung after CDK install failed, no way to cancel, no info on error. > -------------------------------------------------------------------------------------- > > Key: JBDS-3863 > URL: https://issues.jboss.org/browse/JBDS-3863 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 1.1.0.GA, 9.1.0.Beta1 > Environment: Windows 7/64 bit. > (Some components of previous manual CDK install on the system). > Also Windows 10/64. > Reporter: Robert Terzi > Assignee: Denis Golovin > Labels: ui > Fix For: 11.2.0.AM1 > > Attachments: box-add-fail-1.1.0-ga.txt, install.log, jbds-install-log-win7-error.txt > > > Using the platform installer, CDK installation failed, progress shown as 99%. At this point the installer was hung. > Note: > * CDK install progress said Failed, with progress stuck at 99%. > * There is no way to cancel out of the install. > * There was no pop-up about error messages. > * No indication of where to look for error messages/logs etc.was provided. > * CDK was previously installed manually. However, the installer window didn't say a previous CDK installation was detected, but the log does show it deleted the previous cdkv2 box. > From the log it looks like the box add command failed. When originally reported it might have been due to disk space, but it's not clear/obvious from the log. As of DevSuite 1.1.0 GA, the problems still exists if the vagrant box add command fails. Note: I've verified this isn't related to disk space and is a Vagrant problem. > Note: after killing the installer and trying the `vagrant box add` command copied from the log file manually in Cygwin bash the box add command succeeded. The test system had 5-15 GB of free space between the installation started. > Full log attached, excerpt here. > Tue, 26 Apr 2016 18:05:38 GMT-INFO: cdk - Move C:\Users\rct\AppData\Local\Temp\7zSC53C.tmp\rhel-vagrant-virtualbox.box to c:\sw\rhjbds\cdk\boxes\rhel-vagrant-virtualbox.box > Tue, 26 Apr 2016 18:05:43 GMT-INFO: cdk - Move C:\Users\rct\AppData\Local\Temp\7zSC53C.tmp\rhel-vagrant-virtualbox.box to c:\sw\rhjbds\cdk\boxes\rhel-vagrant-virtualbox.box SUCCESS > Tue, 26 Apr 2016 18:05:43 GMT-INFO: cdk - Move C:\Users\rct\AppData\Local\Temp\7zSC53C.tmp\pscp.exe to c:\sw\rhjbds\cdk\bin\pscp.exe > Tue, 26 Apr 2016 18:05:43 GMT-INFO: cdk - Move C:\Users\rct\AppData\Local\Temp\7zSC53C.tmp\pscp.exe to c:\sw\rhjbds\cdk\bin\pscp.exe SUCCESS > Tue, 26 Apr 2016 18:05:43 GMT-INFO: cdk - Write C:\Users\rct\AppData\Local\Temp\set-pscp-path.ps1 > Tue, 26 Apr 2016 18:05:43 GMT-INFO: cdk - Write C:\Users\rct\AppData\Local\Temp\set-pscp-path.ps1 SUCCESS > Tue, 26 Apr 2016 18:05:43 GMT-INFO: cdk - Write c:\sw\rhjbds\cdk\components\rhel\rhel-ose\.cdk > Tue, 26 Apr 2016 18:05:43 GMT-INFO: cdk - Write c:\sw\rhjbds\cdk\components\rhel\rhel-ose\.cdk SUCCESS > Tue, 26 Apr 2016 18:05:43 GMT-INFO: cdk - Execute powershell -ExecutionPolicy,ByPass,-File,C:\Users\rct\AppData\Local\Temp\set-pscp-path.ps1 > Tue, 26 Apr 2016 18:05:44 GMT-INFO: cdk - Execute powershell -ExecutionPolicy,ByPass,-File,C:\Users\rct\AppData\Local\Temp\set-pscp-path.ps1 SUCCESS > Tue, 26 Apr 2016 18:05:44 GMT-INFO: cdk - postVagrantSetup called > Tue, 26 Apr 2016 18:05:44 GMT-INFO: cdk - Execute command vagrant plugin install "c:\sw\rhjbds\cdk\plugins\vagrant-registration-1.2.1.gem" > Tue, 26 Apr 2016 18:05:44 GMT-INFO: cdk - Execute options { > "env": { > "path": "C:\\HashiCorp\\Vagrant\\bin;C:\\Program Files\\Oracle\\VirtualBox\\;" > } > } > Tue, 26 Apr 2016 18:05:55 GMT-INFO: cdk - Installing the 'c:\sw\rhjbds\cdk\plugins\vagrant-registration-1.2.1.gem' plugin. This can take a few minutes... > Installed the plugin 'vagrant-registration (1.2.1)'! > Tue, 26 Apr 2016 18:05:55 GMT-INFO: cdk - Execute vagrant plugin install "c:\sw\rhjbds\cdk\plugins\vagrant-registration-1.2.1.gem" SUCCESS > Tue, 26 Apr 2016 18:05:55 GMT-INFO: cdk - Execute command vagrant box remove cdkv2 -f > Tue, 26 Apr 2016 18:05:55 GMT-INFO: cdk - Execute options { > "env": { > "path": "C:\\HashiCorp\\Vagrant\\bin;C:\\Program Files\\Oracle\\VirtualBox\\;" > } > } > Tue, 26 Apr 2016 18:06:02 GMT-INFO: cdk - Removing box 'cdkv2' (v0) with provider 'virtualbox'... > Tue, 26 Apr 2016 18:06:02 GMT-INFO: cdk - Execute vagrant box remove cdkv2 -f SUCCESS > Tue, 26 Apr 2016 18:06:02 GMT-INFO: cdk - Execute command vagrant box add --name cdkv2 "c:\sw\rhjbds\cdk\boxes\rhel-vagrant-virtualbox.box" > Tue, 26 Apr 2016 18:06:02 GMT-INFO: cdk - Execute options { > "env": { > "path": "C:\\HashiCorp\\Vagrant\\bin;C:\\Program Files\\Oracle\\VirtualBox\\;" > } > } > Tue, 26 Apr 2016 18:06:10 GMT-ERROR: cdk - Error: Command failed: vagrant box add --name cdkv2 "c:\sw\rhjbds\cdk\boxes\rhel-vagrant-virtualbox.box" > The box failed to unpackage properly. Please verify that the box > file you're trying to add is not corrupted and try again. The > output from attempting to unpackage (if any): > x box.ovf > x Vagrantfile > x vagrant-virtualbox-box.vmdk: Write failed > x metadata.json > bsdtar.EXE: Error exit delayed from previous errors. > Tue, 26 Apr 2016 18:06:10 GMT-ERROR: cdk - The box failed to unpackage properly. Please verify that the box > file you're trying to add is not corrupted and try again. The > output from attempting to unpackage (if any): > x box.ovf > x Vagrantfile > x vagrant-virtualbox-box.vmdk: Write failed > x metadata.json > bsdtar.EXE: Error exit delayed from previous errors. > Tue, 26 Apr 2016 18:06:10 GMT-ERROR: cdk failed to install: Error: Command failed: vagrant box add --name cdkv2 "c:\sw\rhjbds\cdk\boxes\rhel-vagrant-virtualbox.box" > The box failed to unpackage properly. Please verify that the box > file you're trying to add is not corrupted and try again. The > output from attempting to unpackage (if any): > x box.ovf > x Vagrantfile > x vagrant-virtualbox-box.vmdk: Write failed > x metadata.json > bsdtar.EXE: Error exit delayed from previous errors. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4016) Add Readme.txt(.md) in the root of devsuite installation with references to all included projects

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4016?page=com.atlassian.jira.plugin.... ] Denis Golovin closed JBDS-4016. ------------------------------- Fix Version/s: 11.2.0.AM1 (was: 11.x) Resolution: Won't Fix > Add Readme.txt(.md) in the root of devsuite installation with references to all included projects > ------------------------------------------------------------------------------------------------- > > Key: JBDS-4016 > URL: https://issues.jboss.org/browse/JBDS-4016 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: platform-installer > Affects Versions: 10.1.0.GA > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 11.2.0.AM1 > > > This file should be generated during build based on info in platform specific requirements*.json -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4623) Jboss Fuse tooling design issue with routes imported from other xml

by ravi narayanan (JIRA)

[ https://issues.jboss.org/browse/JBDS-4623?page=com.atlassian.jira.plugin.... ] ravi narayanan updated JBDS-4623: --------------------------------- Summary: Jboss Fuse tooling design issue with routes imported from other xml (was: Jboss Fuse tooling issue with routes imported from other xml) > Jboss Fuse tooling design issue with routes imported from other xml > ------------------------------------------------------------------- > > Key: JBDS-4623 > URL: https://issues.jboss.org/browse/JBDS-4623 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: fusetools > Affects Versions: 10.4.0.GA, 11.1.0.GA > Environment: Dev > Reporter: ravi narayanan > Attachments: Camelcontext.JPG, RouteContextSource.JPG, Routecontext.JPG > > > Hello, > I am using Jboss developer studio Version: 10.4.0.GA.I have imported Routes From Other XML Files using the in the main camel-context.xml and defining the routes in a seperate xml file inside .Iam able to see the design view of the xml defined in camel-context.xml in fuse tooling.But iam not able to see the design view of the routeContext xml it is blank in design view, but the source has the xml. > i have raised the same in SO as well. > https://stackoverflow.com/questions/47178405/jboss-fuse-tooling-issue-wit... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4623) Jboss Fuse tooling issue with routes imported from other xml

by ravi narayanan (JIRA)

[ https://issues.jboss.org/browse/JBDS-4623?page=com.atlassian.jira.plugin.... ] ravi narayanan updated JBDS-4623: --------------------------------- Attachment: Camelcontext.JPG > Jboss Fuse tooling issue with routes imported from other xml > ------------------------------------------------------------ > > Key: JBDS-4623 > URL: https://issues.jboss.org/browse/JBDS-4623 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: fusetools > Affects Versions: 10.4.0.GA, 11.1.0.GA > Environment: Dev > Reporter: ravi narayanan > Attachments: Camelcontext.JPG, RouteContextSource.JPG, Routecontext.JPG > > > Hello, > I am using Jboss developer studio Version: 10.4.0.GA.I have imported Routes From Other XML Files using the in the main camel-context.xml and defining the routes in a seperate xml file inside .Iam able to see the design view of the xml defined in camel-context.xml in fuse tooling.But iam not able to see the design view of the routeContext xml it is blank in design view, but the source has the xml. > i have raised the same in SO as well. > https://stackoverflow.com/questions/47178405/jboss-fuse-tooling-issue-wit... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4623) Jboss Fuse tooling issue with routes imported from other xml

by ravi narayanan (JIRA)

[ https://issues.jboss.org/browse/JBDS-4623?page=com.atlassian.jira.plugin.... ] ravi narayanan updated JBDS-4623: --------------------------------- Attachment: RouteContextSource.JPG > Jboss Fuse tooling issue with routes imported from other xml > ------------------------------------------------------------ > > Key: JBDS-4623 > URL: https://issues.jboss.org/browse/JBDS-4623 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: fusetools > Affects Versions: 10.4.0.GA, 11.1.0.GA > Environment: Dev > Reporter: ravi narayanan > Attachments: RouteContextSource.JPG, Routecontext.JPG > > > Hello, > I am using Jboss developer studio Version: 10.4.0.GA.I have imported Routes From Other XML Files using the in the main camel-context.xml and defining the routes in a seperate xml file inside .Iam able to see the design view of the xml defined in camel-context.xml in fuse tooling.But iam not able to see the design view of the routeContext xml it is blank in design view, but the source has the xml. > i have raised the same in SO as well. > https://stackoverflow.com/questions/47178405/jboss-fuse-tooling-issue-wit... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4623) Jboss Fuse tooling issue with routes imported from other xml

by ravi narayanan (JIRA)

[ https://issues.jboss.org/browse/JBDS-4623?page=com.atlassian.jira.plugin.... ] ravi narayanan updated JBDS-4623: --------------------------------- Attachment: Routecontext.JPG > Jboss Fuse tooling issue with routes imported from other xml > ------------------------------------------------------------ > > Key: JBDS-4623 > URL: https://issues.jboss.org/browse/JBDS-4623 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: fusetools > Affects Versions: 10.4.0.GA, 11.1.0.GA > Environment: Dev > Reporter: ravi narayanan > Attachments: Routecontext.JPG > > > Hello, > I am using Jboss developer studio Version: 10.4.0.GA.I have imported Routes From Other XML Files using the in the main camel-context.xml and defining the routes in a seperate xml file inside .Iam able to see the design view of the xml defined in camel-context.xml in fuse tooling.But iam not able to see the design view of the routeContext xml it is blank in design view, but the source has the xml. > i have raised the same in SO as well. > https://stackoverflow.com/questions/47178405/jboss-fuse-tooling-issue-wit... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4623) Jboss Fuse tooling issue with routes imported from other xml

by ravi narayanan (JIRA)

ravi narayanan created JBDS-4623: ------------------------------------ Summary: Jboss Fuse tooling issue with routes imported from other xml Key: JBDS-4623 URL: https://issues.jboss.org/browse/JBDS-4623 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: fusetools Affects Versions: 11.1.0.GA, 10.4.0.GA Environment: Dev Reporter: ravi narayanan Hello, I am using Jboss developer studio Version: 10.4.0.GA.I have imported Routes From Other XML Files using the in the main camel-context.xml and defining the routes in a seperate xml file inside .Iam able to see the design view of the xml defined in camel-context.xml in fuse tooling.But iam not able to see the design view of the routeContext xml it is blank in design view, but the source has the xml. i have raised the same in SO as well. https://stackoverflow.com/questions/47178405/jboss-fuse-tooling-issue-wit... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 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 November 2017