[JBoss JIRA] (JBTIS-909) Update SAP tests so that we can specify the Camel version
by Andrej Podhradsky (JIRA)
Andrej Podhradsky created JBTIS-909:
---------------------------------------
Summary: Update SAP tests so that we can specify the Camel version
Key: JBTIS-909
URL: https://issues.jboss.org/browse/JBTIS-909
Project: JBoss Tools Integration Stack
Issue Type: Task
Components: Fuse IDE, QE
Affects Versions: 4.3.2.CR1
Reporter: Andrej Podhradsky
Assignee: Andrej Podhradsky
Fix For: 4.3.2.CR1
Update SAP tests so that we can specify the Camel version. Currently, it takes the default version which is 2.17.3 for which there is no the appropriated sap version.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-23210) application is not created in the selected project
by Peng Li (JIRA)
Peng Li created JBIDE-23210:
-------------------------------
Summary: application is not created in the selected project
Key: JBIDE-23210
URL: https://issues.jboss.org/browse/JBIDE-23210
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.4.1.Final
Environment: # openshift version
openshift v3.2.1.15
kubernetes v1.2.0-36-g4a3f9c5
etcd 2.2.5
Reporter: Peng Li
Attachments: Screenshot from 2016-09-22 15-58-02.png, Screenshot from 2016-09-22 16-00-12.png
When I have multiple projects in the list, I choose to create application in a project, it's always created in the first project in the list.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBTIS-908) Fuse: Test availability of all supported Camel versions
by Tomáš Sedmík (JIRA)
Tomáš Sedmík created JBTIS-908:
----------------------------------
Summary: Fuse: Test availability of all supported Camel versions
Key: JBTIS-908
URL: https://issues.jboss.org/browse/JBTIS-908
Project: JBoss Tools Integration Stack
Issue Type: Task
Components: Fuse IDE, QE
Affects Versions: 4.3.1.Final
Reporter: Tomáš Sedmík
Assignee: Tomáš Sedmík
Fix For: 4.3.2.CR1
Check whether all supported Camel versions are available in _New Fuse Integration Project_ wizard.
Use _plugins/org.jboss.tools.fuse.reddeer/src/org/jboss/tools/fuse/reddeer/SupportedVersions.java_
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBDS-3838) Cannot install CDK. Installer prompts to setup VAGRANT_HOME if there is space in path and then it ignores it and fails
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3838?page=com.atlassian.jira.plugin.... ]
Jan Richter commented on JBDS-3838:
-----------------------------------
The workaround works reliably if you follow the instructions the installer gives you if VAGRANT_HOME is not in use.
But there is an issue (which I just discovered while re-checking the workflow) - the contents of VAGRANT_HOME are not validated at all (JBDS-4058). The installer only checks for the existence of the variable, so unless the user actually uses a valid path without spaces, the installation will inevitably fail.
There is also an issue with CDK, which seems to prevent it from running when the user has space in their name anyway (CDK-11).
As for the detailed steps:
- go to "Environment Variables" settings ( Control Panel -> System and Security -> System -> Advanced System Settings -> Environment Variables | or just use the start menu and search for "environment variables")
- under "User variables for $username" select "New..."
- Variable name: VAGRANT_HOME
- Variable value: a valid path without spaces
- keep clicking OK as long as there are windows that have the button
- start up the installer and now you should be able to continue
> Cannot install CDK. Installer prompts to setup VAGRANT_HOME if there is space in path and then it ignores it and fails
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3838
> URL: https://issues.jboss.org/browse/JBDS-3838
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.CR1
> Reporter: Pavol Srna
> Assignee: Denis Golovin
> Priority: Blocker
> Labels: havoc
> Fix For: 10.0.0.Alpha1
>
> Attachments: install.log, vagrant.log, vbox.log
>
>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBDS-4058) Installer does not validate VAGRANT_HOME when used
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-4058?page=com.atlassian.jira.plugin.... ]
Jan Richter reassigned JBDS-4058:
---------------------------------
Assignee: Denis Golovin
> Installer does not validate VAGRANT_HOME when used
> --------------------------------------------------
>
> Key: JBDS-4058
> URL: https://issues.jboss.org/browse/JBDS-4058
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 10.1.0.GA
> Reporter: Jan Richter
> Assignee: Denis Golovin
>
> As per JBDS-3838, we require users with space in their name to use VAGRANT_HOME environment variable. The problem is, the installer will let you proceed without validating the variable contents.
> Something like "x:\this definitely has no spaces\" will allow the user to proceed with installation, which inevitably fails. We need to validate if the path stored in the variable is valid, that the selected drive actually exists, and that there are no spaces.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBDS-4058) Installer does not validate VAGRANT_HOME when used
by Jan Richter (JIRA)
Jan Richter created JBDS-4058:
---------------------------------
Summary: Installer does not validate VAGRANT_HOME when used
Key: JBDS-4058
URL: https://issues.jboss.org/browse/JBDS-4058
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Bug
Components: platform-installer
Affects Versions: 10.1.0.GA
Reporter: Jan Richter
As per JBDS-3838, we require users with space in their name to use VAGRANT_HOME environment variable. The problem is, the installer will let you proceed without validating the variable contents.
Something like "x:\this definitely has no spaces\" will allow the user to proceed with installation, which inevitably fails. We need to validate if the path stored in the variable is valid, that the selected drive actually exists, and that there are no spaces.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBDS-4057) cdk fails, online install
by Misha Ali (JIRA)
[ https://issues.jboss.org/browse/JBDS-4057?page=com.atlassian.jira.plugin.... ]
Misha Ali updated JBDS-4057:
----------------------------
Affects Version/s: 10.1.0.GA
> cdk fails, online install
> -------------------------
>
> Key: JBDS-4057
> URL: https://issues.jboss.org/browse/JBDS-4057
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 10.1.0.GA
> Reporter: Misha Ali
>
> I'm testing the online installer on a win 8 VM. The username is administrator, so we shouldn't face the space in the user name issue.
> I've run the online installer thrice now and every component has installed, but CDK fails with no useful error message or log. I don't know if this can be replicated, but I will add the VM I'm using in an internal comment for testing.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBDS-4057) cdk fails, online install
by Misha Ali (JIRA)
Misha Ali created JBDS-4057:
-------------------------------
Summary: cdk fails, online install
Key: JBDS-4057
URL: https://issues.jboss.org/browse/JBDS-4057
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Bug
Reporter: Misha Ali
I'm testing the online installer on a win 8 VM. The username is administrator, so we shouldn't face the space in the user name issue.
I've run the online installer thrice now and every component has installed, but CDK fails with no useful error message or log. I don't know if this can be replicated, but I will add the VM I'm using in an internal comment for testing.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months