[JBoss JIRA] (JBIDE-24447) Look for minishift configuration in MINISHIFT_HOME
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24447?page=com.atlassian.jira.plugi... ]
Ondrej Dockal edited comment on JBIDE-24447 at 8/2/17 9:59 AM:
---------------------------------------------------------------
I have tested this features on devstudio:
Version: 11.0.0.GA
Build id: GA-v20170731-0116-B659
What I got...
When I start devstudio with clean workspace, no runtime detection dialog is shown (Searcing new runtimes...) and when I open Servers View, I can see there is a CDK 3 server adapter! (It is called "Container Development Environment 3") and when I open the adapter, I have Minishift Home set to path that can be seen in pic (not important): !cdk2_x_RD.png|thumbnail!. What is important here is the thing that it is my old CDK 2.x folder with cdk.zip file unzipped and other stuff like vagrant box file, etc... (ls -all gives me no 'cdk' file that would contains runtime detection information which would clarify why it is was detected). So, is it place for reporting new issue? I must say this situation might be result of me having installed multiple milestones of devstudios that I tested during past months or changes I made to environment, etc. Also, If I rename the cdk folder to something else, It starts working as can be read below.
But, If I delete that adapter that was magically added via Runtime Detection on fresh start and restart the IDE, I got: !cdk3_minishift_home.png|thumbnail! which lead to cdk runtime file that was set via MINSIHFT_HOME env. var. So it is working in this case.
was (Author: odockal):
I have tested this features on devstudio:
Version: 11.0.0.GA
Build id: GA-v20170731-0116-B659
What I got...
When I start devstudio with clean workspace, no runtime detection dialog is shown (Searcing new runtimes...) and when I open Servers View, I can see there is a CDK 3 server adapter! (It is called "Container Development Environment 3") and when I open the adapter, I have Minishift Home set to path that can be seen in pic (not important): !cdk2_x_RD.png|thumbnail!. What is important here is the thing that it is my old CDK 2.x folder with cdk.zip file unzipped and other stuff like vagrant box file, etc... (ls -all gives me no 'cdk' file that would contains runtime detection information which would clarify why it is was detected). So, is it place for reporting new issue? I must say this situation might be result of me having installed multiple milestones of devstudios that I tested during past months or changes I made to environment, etc. Also, If I rename the cdk folder to something else, It starts working as can be read below.
But, If I delete that adapter that was magically added via Runtime Detection on fresh start and restart the IDE, I got: !cdk3_minishift_home.png|thumbnail! which lead to cdk runtime file that was set via MINSIHFT_HOME env. var. So it is working in this case.
> Look for minishift configuration in MINISHIFT_HOME
> --------------------------------------------------
>
> Key: JBIDE-24447
> URL: https://issues.jboss.org/browse/JBIDE-24447
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: runtime-detection
> Affects Versions: 4.4.4.Final
> Reporter: Jan Richter
> Assignee: Rob Stryker
> Fix For: 4.5.0.AM1
>
> Attachments: cdk2_x_RD.png, cdk3_minishift_home.png
>
>
> One can use the MINISHIFT_HOME variable to save minishift configuration somewhere else than in ~/.minishift
> It would be nice if runtime detection looked there if the variable is configured.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 11 months
[JBoss JIRA] (JBIDE-24447) Look for minishift configuration in MINISHIFT_HOME
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24447?page=com.atlassian.jira.plugi... ]
Ondrej Dockal commented on JBIDE-24447:
---------------------------------------
I have tested this features on devstudio:
Version: 11.0.0.GA
Build id: GA-v20170731-0116-B659
What I got...
When I start devstudio with clean workspace, no runtime detection dialog is shown (Searcing new runtimes...) and when I open Servers View, I can see there is a CDK 3 server adapter! (It is called "Container Development Environment 3") and when I open the adapter, I have Minishift Home set to path that can be seen in pic (not important): !cdk2_x_RD.png|thumbnail!. What is important here is the thing that it is my old CDK 2.x folder with cdk.zip file unzipped and other stuff like vagrant box file, etc... (ls -all gives me no 'cdk' file that would contains runtime detection information which would clarify why it is was detected). So, is it place for reporting new issue? I must say this situation might be result of me having installed multiple milestones of devstudios that I tested during past months or changes I made to environment, etc. Also, If I rename the cdk folder to something else, It starts working as can be read below.
But, If I delete that adapter that was magically added via Runtime Detection on fresh start and restart the IDE, I got: !cdk3_minishift_home.png|thumbnail! which lead to cdk runtime file that was set via MINSIHFT_HOME env. var. So it is working in this case.
> Look for minishift configuration in MINISHIFT_HOME
> --------------------------------------------------
>
> Key: JBIDE-24447
> URL: https://issues.jboss.org/browse/JBIDE-24447
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: runtime-detection
> Affects Versions: 4.4.4.Final
> Reporter: Jan Richter
> Assignee: Rob Stryker
> Fix For: 4.5.0.AM1
>
> Attachments: cdk2_x_RD.png, cdk3_minishift_home.png
>
>
> One can use the MINISHIFT_HOME variable to save minishift configuration somewhere else than in ~/.minishift
> It would be nice if runtime detection looked there if the variable is configured.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 11 months
[JBoss JIRA] (JBIDE-24789) Find a way to avoid freeze of master for several days
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24789?page=com.atlassian.jira.plugi... ]
Aurélien Pupier commented on JBIDE-24789:
-----------------------------------------
If it is fully automated I don't really see an overhead. What are the not automated parts?
> Find a way to avoid freeze of master for several days
> -----------------------------------------------------
>
> Key: JBIDE-24789
> URL: https://issues.jboss.org/browse/JBIDE-24789
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build
> Affects Versions: 4.5.0.Final
> Reporter: Aurélien Pupier
>
> Currently, for each milestone, final release, the master branch is frozen for several days which is decreasing productivity and increase risk at the end of code freeze (as everybody wants to merge a lot of PRs at the same time)
> it would be nice to find a way to avoid the freeze on the master branch.
> Proposal:
> - create a branch for each milestone/release:
> -- it allows to continue working on master
> -- it allows to provide blocker/critical fix if needed on the branch
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 11 months
[JBoss JIRA] (JBIDE-24790) Connection wizard: "Override 'oc' location" text box does not expand when dialog is horizontally expanded
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24790?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-24790:
-------------------------------------
Summary: Connection wizard: "Override 'oc' location" text box does not expand when dialog is horizontally expanded (was: Connection wizard: oc override text box does not expand when dialog is horizontally expanded)
> Connection wizard: "Override 'oc' location" text box does not expand when dialog is horizontally expanded
> ---------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24790
> URL: https://issues.jboss.org/browse/JBIDE-24790
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.0.Final
> Reporter: Jeff MAURY
> Assignee: Andre Dietisheim
> Priority: Minor
> Labels: connection_wizard, openshift_v3
> Fix For: 4.5.0.Final
>
>
> When the connection editor is horizontally expanded, the override oc text box keep the same size and is not expanded (as opposed to the registry url and template namespace text boxes)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 11 months
[JBoss JIRA] (JBIDE-24790) Connection wizard: oc override text box does not expand when dialog is horizontally expanded
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24790?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-24790:
-------------------------------------
Summary: Connection wizard: oc override text box does not expand when dialog is horizontally expanded (was: oc override text box does not expand when dialog is horizontally expanded)
> Connection wizard: oc override text box does not expand when dialog is horizontally expanded
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-24790
> URL: https://issues.jboss.org/browse/JBIDE-24790
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.0.Final
> Reporter: Jeff MAURY
> Assignee: Andre Dietisheim
> Priority: Minor
> Fix For: 4.5.0.Final
>
>
> When the connection editor is horizontally expanded, the override oc text box keep the same size and is not expanded (as opposed to the registry url and template namespace text boxes)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 11 months
[JBoss JIRA] (JBTIS-1151) Section 508 - VPAT Compatibility
by Bob Davis (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1151?page=com.atlassian.jira.plugin... ]
Bob Davis commented on JBTIS-1151:
----------------------------------
I should add -
"I believe it should just be a documentation requirement for release" - assuming that the LOE and associated costs are justified by the benefit we gain from it.
If this is added expense and effort that will result in no change in usage of DevSuite by governmental agencies and won't drive infrastructure/middleware sales, then it's probably not worth the effort.
Bob
> Section 508 - VPAT Compatibility
> --------------------------------
>
> Key: JBTIS-1151
> URL: https://issues.jboss.org/browse/JBTIS-1151
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: distribution
> Affects Versions: 10.3.0.GA
> Environment:
> Reporter: Wagner Queiroz
> Assignee: Paul Leacu
> Priority: Minor
>
> Provide Section 508 - VPAT compliance Integration Stack product if possible in a next GA release.
> Ref: https://mojo.redhat.com/docs/DOC-28860
> Some useful info before going to a formal evaluation:
> https://mojo.redhat.com/docs/DOC-175787
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 11 months