[JBoss JIRA] (JBIDE-24877) CDK 2 detection results in CDK 3 adapter creation
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24877?page=com.atlassian.jira.plugi... ]
Ondrej Dockal edited comment on JBIDE-24877 at 8/24/17 11:03 AM:
-----------------------------------------------------------------
[~mmalina] Thanks Martin! I just wanted to show you guys that it is not just me making some bugs. :)
Anyway, this is so marginal issue, that I can image it very deep in a backlog. It is up to you [~rob.stryker].
was (Author: odockal):
[~mmalina] Thanks Martin! I just wanted to show you guys that I am not lying. :)
Anyway, this is so marginal issue, that I can image it very deep in a backlog. It is up to you [~rob.stryker].
> CDK 2 detection results in CDK 3 adapter creation
> -------------------------------------------------
>
> Key: JBIDE-24877
> URL: https://issues.jboss.org/browse/JBIDE-24877
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.5.1.AM1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.5.1.AM2
>
>
> As described by [~odockal] in JBIDE-24447:
> When you start devstudio and it finds cdk 2 installed inside ../../../cdk/ relative to eclipse's config, it will create a cdk 3 server instead of cdk 2.
> This relative path normally translate to a structure like this:
> $SOME_DIR/devstudio
> $SOME_DIR/cdk/YOUR/CDK/2/SOMEWHERE/INSIDE/HERE
> BUT... this will only happen in a special situation where you have CDK 2 installed where devstudio looks for it (see above) AND you set up the MINISHIFT_HOME env var to point to your CDK 3 home when you start devstudio.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24877) CDK 2 detection results in CDK 3 adapter creation
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24877?page=com.atlassian.jira.plugi... ]
Ondrej Dockal commented on JBIDE-24877:
---------------------------------------
[~mmalina] Thanks Martin! I just wanted to show you guys that I am not lying. :)
Anyway, this is so marginal issue, that I can image it very deep in a backlog. It is up to you [~rob.stryker].
> CDK 2 detection results in CDK 3 adapter creation
> -------------------------------------------------
>
> Key: JBIDE-24877
> URL: https://issues.jboss.org/browse/JBIDE-24877
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.5.1.AM1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.5.1.AM2
>
>
> As described by [~odockal] in JBIDE-24447:
> When you start devstudio and it finds cdk 2 installed inside ../../../cdk/ relative to eclipse's config, it will create a cdk 3 server instead of cdk 2.
> This relative path normally translate to a structure like this:
> $SOME_DIR/devstudio
> $SOME_DIR/cdk/YOUR/CDK/2/SOMEWHERE/INSIDE/HERE
> BUT... this will only happen in a special situation where you have CDK 2 installed where devstudio looks for it (see above) AND you set up the MINISHIFT_HOME env var to point to your CDK 3 home when you start devstudio.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24877) CDK 2 detection results in CDK 3 adapter creation
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24877?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-24877:
---------------------------------------
[~odockal] bugged me long enough so I tried again. He said I needed to have cdk/cdk in the structure to reproduce. I couldn't believe. But it's true. So you need these:
1. You have a structure like this:
./devstudio-whatever - your devstudio install
./cdk/cdk/components/rhel/rhel-ose/Vagrantfile - your vagrant file; i.e. unzip your cdk.zip inside cdk/
2. Start devstudio with MINISHIFT_HOME=dir where dir is where you set up cdk 3 using the same variable (in my case MINISHIFT_HOME=/Users/rasp/minishift_home)
Once I started devstudio, I only had one server - cdk 3. And the minishift home field was set to /Users/rasp/git/cdk-install/cdk - which is the cdk 2 path.
Notice how I needed to have one more cdk directory to reproduce it - if there was just ./cdk/components/rhel/rhel-ose/Vagrantfile it worked fine.
> CDK 2 detection results in CDK 3 adapter creation
> -------------------------------------------------
>
> Key: JBIDE-24877
> URL: https://issues.jboss.org/browse/JBIDE-24877
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.5.1.AM1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.5.1.AM2
>
>
> As described by [~odockal] in JBIDE-24447:
> When you start devstudio and it finds cdk 2 installed inside ../../../cdk/ relative to eclipse's config, it will create a cdk 3 server instead of cdk 2.
> This relative path normally translate to a structure like this:
> $SOME_DIR/devstudio
> $SOME_DIR/cdk/YOUR/CDK/2/SOMEWHERE/INSIDE/HERE
> BUT... this will only happen in a special situation where you have CDK 2 installed where devstudio looks for it (see above) AND you set up the MINISHIFT_HOME env var to point to your CDK 3 home when you start devstudio.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBDS-4513) Align Breadcrumbs in the UI
by Mohit Suman (JIRA)
[ https://issues.jboss.org/browse/JBDS-4513?page=com.atlassian.jira.plugin.... ]
Mohit Suman commented on JBDS-4513:
-----------------------------------
Thanks Catherine for the review. Will merge this issue.
> Align Breadcrumbs in the UI
> ---------------------------
>
> Key: JBDS-4513
> URL: https://issues.jboss.org/browse/JBDS-4513
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Reporter: Mohit Suman
> Assignee: Mohit Suman
> Priority: Minor
> Fix For: 11.1.0.AM1
>
> Attachments: breadcrumb-fix.png
>
>
> The current breadcrumbs start from the corner of the page layout. Making it more centric to the page in accordance to the wizard mode we have in patternfly wizard template.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBDS-4335) Clearly mark third party components available for installation on confirmation page
by Catherine Robson (JIRA)
[ https://issues.jboss.org/browse/JBDS-4335?page=com.atlassian.jira.plugin.... ]
Catherine Robson commented on JBDS-4335:
----------------------------------------
[~dgolovin] I don't agree with this request. Where did this request come from? I don't think that we want to get into visually distinguishing Red Hat from non Red Hat in this context. The purpose of this page is not to show any branding at all about the components that the user is installing, it is meant to be informative about what they are about to put on their computer. The "Red Hat' in front of Red Hat components should be enough IMO to notate Red Hat products in this context since the goal of the page is not to market or teach the users about these components, but rather show them what will be installed.
Adding branding and differentiation will be visual clutter, and might be interpreted as there is a difference in *how* things will install rather than who built them. From a design and UX standpoint, I think that this is a mistake for the installer.
> Clearly mark third party components available for installation on confirmation page
> -----------------------------------------------------------------------------------
>
> Key: JBDS-4335
> URL: https://issues.jboss.org/browse/JBDS-4335
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Affects Versions: 10.4.0.AM1, 10.4.0.GA
> Reporter: Denis Golovin
> Assignee: Mohit Suman
> Labels: ui
> Fix For: 11.1.0.AM1
>
>
> Current UI does not distinguish Red Hat products and third party components available for installation.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months