[JBoss JIRA] (JBDS-4188) Use of help docs causes lucene 5 index errors in console log
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBDS-4188?page=com.atlassian.jira.plugin.... ]
Lukáš Valach closed JBDS-4188.
------------------------------
I also can't reproduce. Closing.
> Use of help docs causes lucene 5 index errors in console log
> ------------------------------------------------------------
>
> Key: JBDS-4188
> URL: https://issues.jboss.org/browse/JBDS-4188
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, rpm, upstream
> Affects Versions: 10.2.0.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Minor
> Fix For: 11.0.0.GA
>
> Attachments: external-window.png
>
>
> As of the latest rpm build (10.2-0.20161117.2130) if you click on the (?) icon in any dialog (eg., Help > About > (?) ) you get a TON of Eclipse Help errors caused by Lucene 5.4.1 trying to read content which I presume was created with Lucene 3.5:
> {code}
> !ENTRY org.eclipse.help.base 4 0 2016-11-17 16:56:06.565
> !MESSAGE Error trying to consume Lucene index from bundle org.eclipse.jst.ws.consumption.ui.doc.user_1.0.700.v201610271000 [429]. Please use an index built with Lucene 5 or higher.
> !ENTRY org.eclipse.help.base 4 0 2016-11-17 16:56:06.610
> !MESSAGE Help index declared, but missing for plugin org.eclipse.dstore.doc.isv.
> !ENTRY org.eclipse.help.base 4 0 2016-11-17 16:56:06.616
> !MESSAGE Help index declared, but missing for plugin org.eclipse.platform.doc.isv.
> !ENTRY org.eclipse.help.base 4 0 2016-11-17 16:56:06.638
> !MESSAGE Error trying to consume Lucene index from bundle org.eclipse.jst.ws.axis2.ui.doc.user_1.0.200.v201610271000 [425]. Please use an index built with Lucene 5 or higher.
> !ENTRY org.eclipse.help.base 4 0 2016-11-17 16:56:06.638
> !MESSAGE Help index declared, but missing for plugin org.eclipse.jdt.doc.user.
> !ENTRY org.eclipse.help.base 4 0 2016-11-17 16:56:06.640
> !MESSAGE Error trying to consume Lucene index from bundle org.eclipse.wst.command.env.doc.user_1.5.400.v201610271000 [455]. Please use an index built with Lucene 5 or higher.
> !ENTRY org.eclipse.help.base 4 0 2016-11-17 16:56:06.675
> !MESSAGE Error trying to consume Lucene index from bundle org.eclipse.wst.dtdeditor.doc.user_1.0.700.v201610271000 [487]. Please use an index built with Lucene 5 or higher.
> !ENTRY org.eclipse.help.base 4 0 2016-11-17 16:56:06.676
> !MESSAGE Help index declared, but missing for plugin org.eclipse.jdt.doc.isv.
> !ENTRY org.eclipse.help.base 4 0 2016-11-17 16:56:06.678
> !MESSAGE Help index declared, but missing for plugin org.eclipse.platform.doc.user.
> !ENTRY org.eclipse.help.base 4 0 2016-11-17 16:56:06.680
> !MESSAGE Error trying to consume Lucene index from bundle org.eclipse.jst.j2ee.doc.user_1.1.400.v201610271000 [392]. Please use an index built with Lucene 5 or higher.
> !ENTRY org.eclipse.help.base 4 0 2016-11-17 16:56:06.687
> !MESSAGE Error trying to consume Lucene index from bundle org.eclipse.wst.xmleditor.doc.user_1.0.700.v201610271000 [554]. Please use an index built with Lucene 5 or higher.
> !ENTRY org.eclipse.help.base 4 0 2016-11-17 16:56:06.697
> !MESSAGE Error trying to consume Lucene index from bundle org.eclipse.wst.xsdeditor.doc.user_1.0.800.v201610271000 [557]. Please use an index built with Lucene 5 or higher.
> !ENTRY org.eclipse.help.base 4 0 2016-11-17 16:56:06.707
> !MESSAGE Error trying to consume Lucene index from bundle org.eclipse.jst.ejb.doc.user_1.1.301.v201610271000 [387]. Please use an index built with Lucene 5 or higher.
> !ENTRY org.eclipse.help.base 4 0 2016-11-17 16:56:06.715
> !MESSAGE Error trying to consume Lucene index from bundle org.eclipse.jst.ws.axis.ui.doc.user_1.1.200.v201610271000 [418]. Please use an index built with Lucene 5 or higher.
> !ENTRY org.eclipse.help.base 4 0 2016-11-17 16:56:06.716
> !MESSAGE Error trying to consume Lucene index from bundle org.eclipse.wst.wsdl.ui.doc.user_1.0.850.v201610271000 [467]. Please use an index built with Lucene 5 or higher.
> !ENTRY org.eclipse.help.base 4 0 2016-11-17 16:56:06.725
> !MESSAGE Error trying to consume Lucene index from bundle org.eclipse.wst.webtools.doc.user_1.0.500.v201610271000 [543]. Please use an index built with Lucene 5 or higher.
> !ENTRY org.eclipse.help.base 4 0 2016-11-17 16:56:06.733
> !MESSAGE Error trying to consume Lucene index from bundle org.eclipse.wst.server.ui.doc.user_1.1.600.v201610271000 [658]. Please use an index built with Lucene 5 or higher.
> !ENTRY org.eclipse.help.base 4 0 2016-11-17 16:56:06.738
> !MESSAGE Help index declared, but missing for plugin org.eclipse.pde.doc.user.
> !ENTRY org.eclipse.help.base 4 0 2016-11-17 16:56:06.745
> !MESSAGE Error trying to consume Lucene index from bundle org.eclipse.jst.ws.doc.user_1.0.700.v201610271000 [439]. Please use an index built with Lucene 5 or higher.
> !ENTRY org.eclipse.help.base 4 0 2016-11-17 16:56:06.747
> !MESSAGE Help index declared, but missing for plugin org.eclipse.rse.doc.isv.
> !ENTRY org.eclipse.help.base 4 0 2016-11-17 16:56:06.749
> !MESSAGE Error trying to consume Lucene index from bundle org.eclipse.wst.wsi.ui.doc.user_1.0.750.v201610271000 [471]. Please use an index built with Lucene 5 or higher.
> !ENTRY org.eclipse.help.base 4 0 2016-11-17 16:56:06.760
> !MESSAGE Error trying to consume Lucene index from bundle org.eclipse.wst.sse.doc.user_1.1.100.v201610271000 [536]. Please use an index built with Lucene 5 or higher.
> !ENTRY org.eclipse.help.base 4 0 2016-11-17 16:56:06.762
> !MESSAGE Error trying to consume Lucene index from bundle org.eclipse.jst.server.ui.doc.user_1.0.600.v201610271000 [649]. Please use an index built with Lucene 5 or higher.
> java.net.URISyntaxException: Illegal character in path at index 56: localhelp:/org.eclipse.mylyn.wikitext.help.ui/help/Mylyn WikiText User Guide.html?lang=en_CA
> at java.net.URI$Parser.fail(URI.java:2848)
> at java.net.URI$Parser.checkChars(URI.java:3021)
> at java.net.URI$Parser.parseHierarchical(URI.java:3105)
> at java.net.URI$Parser.parse(URI.java:3053)
> at java.net.URI.<init>(URI.java:588)
> at java.net.URL.toURI(URL.java:939)
> at org.eclipse.help.internal.base.util.ProxyUtil.getProxy(ProxyUtil.java:57)
> at org.eclipse.help.internal.base.util.ProxyUtil.getConnection(ProxyUtil.java:108)
> at org.eclipse.help.internal.base.util.ProxyUtil.getStream(ProxyUtil.java:124)
> at org.eclipse.help.internal.search.HTMLSearchParticipant.isXHTML(HTMLSearchParticipant.java:108)
> at org.eclipse.help.internal.search.HTMLSearchParticipant.addDocument(HTMLSearchParticipant.java:47)
> at org.eclipse.help.internal.search.SearchIndex.addDocument(SearchIndex.java:248)
> at org.eclipse.help.internal.search.IndexingOperation.addDocuments(IndexingOperation.java:252)
> at org.eclipse.help.internal.search.IndexingOperation.addNewDocuments(IndexingOperation.java:159)
> at org.eclipse.help.internal.search.IndexingOperation.execute(IndexingOperation.java:106)
> at org.eclipse.help.internal.search.LocalSearchManager.updateIndex(LocalSearchManager.java:630)
> at org.eclipse.help.internal.search.LocalSearchManager.ensureIndexUpdated(LocalSearchManager.java:604)
> at org.eclipse.help.internal.search.federated.IndexerJob.run(IndexerJob.java:32)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> java.net.URISyntaxException: Illegal character in path at index 56: localhelp:/org.eclipse.mylyn.wikitext.help.ui/help/Mylyn WikiText User Guide.html?lang=en_CA
> at java.net.URI$Parser.fail(URI.java:2848)
> at java.net.URI$Parser.checkChars(URI.java:3021)
> at java.net.URI$Parser.parseHierarchical(URI.java:3105)
> at java.net.URI$Parser.parse(URI.java:3053)
> at java.net.URI.<init>(URI.java:588)
> at java.net.URL.toURI(URL.java:939)
> at org.eclipse.help.internal.base.util.ProxyUtil.getProxy(ProxyUtil.java:57)
> at org.eclipse.help.internal.base.util.ProxyUtil.getConnection(ProxyUtil.java:108)
> at org.eclipse.help.internal.base.util.ProxyUtil.getStream(ProxyUtil.java:124)
> at org.eclipse.help.search.SearchParticipantXML.addDocument(SearchParticipantXML.java:308)
> at org.eclipse.help.internal.search.HTMLSearchParticipant.addDocument(HTMLSearchParticipant.java:53)
> at org.eclipse.help.internal.search.SearchIndex.addDocument(SearchIndex.java:248)
> at org.eclipse.help.internal.search.IndexingOperation.addDocuments(IndexingOperation.java:252)
> at org.eclipse.help.internal.search.IndexingOperation.addNewDocuments(IndexingOperation.java:159)
> at org.eclipse.help.internal.search.IndexingOperation.execute(IndexingOperation.java:106)
> at org.eclipse.help.internal.search.LocalSearchManager.updateIndex(LocalSearchManager.java:630)
> at org.eclipse.help.internal.search.LocalSearchManager.ensureIndexUpdated(LocalSearchManager.java:604)
> at org.eclipse.help.internal.search.federated.IndexerJob.run(IndexerJob.java:32)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> !ENTRY org.eclipse.help.base 4 4 2016-11-17 16:56:20.057
> !MESSAGE Help documentation could not be indexed completely.
> !SUBENTRY 1 org.eclipse.help.base 4 4 2016-11-17 16:56:20.057
> !MESSAGE Help document /org.eclipse.platform.doc.isv/reference/api/org/eclipse/ui/ide/undo/package-summary.html cannot be opened.
> !SUBENTRY 1 org.eclipse.help.base 4 4 2016-11-17 16:56:20.057
> !MESSAGE Help document /org.eclipse.jdt.doc.isv/reference/api/org/eclipse/jdt/debug/ui/launchConfigurations/package-summary.html cannot be opened.
> !SUBENTRY 1 org.eclipse.help.base 4 4 2016-11-17 16:56:20.057
> !MESSAGE Help document /org.eclipse.platform.doc.isv/reference/api/org/eclipse/ui/activities/package-summary.html cannot be opened.
> !SUBENTRY 1 org.eclipse.help.base 4 4 2016-11-17 16:56:20.057
> !MESSAGE Help document /org.eclipse.jdt.doc.isv/reference/api/org/eclipse/jdt/core/jdom/package-summary.html cannot be opened.
> !SUBENTRY 1 org.eclipse.help.base 4 4 2016-11-17 16:56:20.057
> !MESSAGE Help document /org.eclipse.rse.doc.isv/reference/extension-points/org_eclipse_rse_core_systemTypeProviders.html cannot be opened.
> !SUBENTRY 1 org.eclipse.help.base 4 4 2016-11-17 16:56:20.057
> ...
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 2 months
[JBoss JIRA] (JBDS-4493) Virtualization detection never terminates on powershell version <= 2
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4493?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4493:
--------------------------------
Story Points: 3
Sprint: devex #135 July 2017
> Virtualization detection never terminates on powershell version <= 2
> ---------------------------------------------------------------------
>
> Key: JBDS-4493
> URL: https://issues.jboss.org/browse/JBDS-4493
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 11.0.0.AM2
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Priority: Critical
> Fix For: 11.0.0.GA
>
>
> Follow up on the mail thread about detection not finishing on win 7.
> Namely methods from the Platform class that call powershell commands:
> - isVirtualizationEnabled
> - getHypervisorVersion
> - isHypervisorEnabled
> For some reason when called instead of erroring (since these commands dont work on older powershell) they don't terminate and block the detection.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 2 months
[JBoss JIRA] (JBDS-4493) Virtualization detection never terminates on powershell version <= 2
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4493?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4493:
--------------------------------
Fix Version/s: 11.0.0.GA
> Virtualization detection never terminates on powershell version <= 2
> ---------------------------------------------------------------------
>
> Key: JBDS-4493
> URL: https://issues.jboss.org/browse/JBDS-4493
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 11.0.0.AM2
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Fix For: 11.0.0.GA
>
>
> Follow up on the mail thread about detection not finishing on win 7.
> Namely methods from the Platform class that call powershell commands:
> - isVirtualizationEnabled
> - getHypervisorVersion
> - isHypervisorEnabled
> For some reason when called instead of erroring (since these commands dont work on older powershell) they don't terminate and block the detection.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 2 months
[JBoss JIRA] (JBDS-4493) Virtualization detection never terminates on powershell version <= 2
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4493?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4493:
--------------------------------
Priority: Critical (was: Major)
> Virtualization detection never terminates on powershell version <= 2
> ---------------------------------------------------------------------
>
> Key: JBDS-4493
> URL: https://issues.jboss.org/browse/JBDS-4493
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 11.0.0.AM2
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Priority: Critical
> Fix For: 11.0.0.GA
>
>
> Follow up on the mail thread about detection not finishing on win 7.
> Namely methods from the Platform class that call powershell commands:
> - isVirtualizationEnabled
> - getHypervisorVersion
> - isHypervisorEnabled
> For some reason when called instead of erroring (since these commands dont work on older powershell) they don't terminate and block the detection.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 2 months
[JBoss JIRA] (JBIDE-24796) Starting of CDK 3 Server Adapter with Minishift Home that differs from ~/.minishift prevents OS tooling to create proper connection and links it to default project
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24796?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-24796:
----------------------------------
Attachment: cdk3_sa-manual_correct-mhome.png
> Starting of CDK 3 Server Adapter with Minishift Home that differs from ~/.minishift prevents OS tooling to create proper connection and links it to default project
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24796
> URL: https://issues.jboss.org/browse/JBIDE-24796
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.5.0.Final
> Environment: Fedora
> Reporter: Ondrej Dockal
> Priority: Critical
> Attachments: cdk3_sa-manual_correct-mhome.png, cdk3_sa-manual_wrong-mhome2.png
>
>
> In the first case I would understand that if you change you minishift home (in server editor) and then you start server adapter, you will get some mess... Although, I would like to see a validation of minishift home here. We are checking minishit binary, why not to check minishift home (in this case for existence of the folder). See
> !cdk3_sa-manual_wrong-mhome2.png|thumbnail!
> In the second case comes the bug. Even if I have set MINISHIFT_HOME folder, called setup-cdk that configured everything in that folder and put this folder as Minishift Home, CDK3 Server Adapter is not respecting that location. Or it is maybe OS tooling, not sure here. Solution here would be a check that verifies minishift's home set in CDK server editor corresponds with the one that minishift binary uses, if it is possible (from the side of binary) - but that seems not to be an option here as minishift/cdk stored everything in config that resides in MINISHIFT_HOME or ~/.minishift folder.
> Cc: [~adietish] [~rob.stryker].
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 2 months
[JBoss JIRA] (JBIDE-24796) Starting of CDK 3 Server Adapter with Minishift Home that differs from ~/.minishift prevents OS tooling to create proper connection and links it to default project
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24796?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-24796:
----------------------------------
Description:
In the first case I would understand that if you change you minishift home (in server editor) and then you start server adapter, you will get some mess... Although, I would like to see a validation of minishift home here. We are checking minishit binary, why not to check minishift home (in this case for existence of the folder). See
!cdk3_sa-manual_wrong-mhome2.png|thumbnail!
In the second case comes the bug. Even if I have set MINISHIFT_HOME folder, called setup-cdk that configured everything in that folder and put this folder as Minishift Home, CDK3 Server Adapter is not respecting that location. Or it is maybe OS tooling, not sure here. Solution here would be a check that verifies minishift's home set in CDK server editor corresponds with the one that minishift binary uses, if it is possible (from the side of binary) - but that seems not to be an option here as minishift/cdk stored everything in config that resides in MINISHIFT_HOME or ~/.minishift folder. See
!cdk3_sa-manual_correct-mhome.png|thumbnail!
Cc: [~adietish] [~rob.stryker].
was:
In the first case I would understand that if you change you minishift home (in server editor) and then you start server adapter, you will get some mess... Although, I would like to see a validation of minishift home here. We are checking minishit binary, why not to check minishift home (in this case for existence of the folder). See
!cdk3_sa-manual_wrong-mhome2.png|thumbnail!
In the second case comes the bug. Even if I have set MINISHIFT_HOME folder, called setup-cdk that configured everything in that folder and put this folder as Minishift Home, CDK3 Server Adapter is not respecting that location. Or it is maybe OS tooling, not sure here. Solution here would be a check that verifies minishift's home set in CDK server editor corresponds with the one that minishift binary uses, if it is possible (from the side of binary) - but that seems not to be an option here as minishift/cdk stored everything in config that resides in MINISHIFT_HOME or ~/.minishift folder.
Cc: [~adietish] [~rob.stryker].
> Starting of CDK 3 Server Adapter with Minishift Home that differs from ~/.minishift prevents OS tooling to create proper connection and links it to default project
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24796
> URL: https://issues.jboss.org/browse/JBIDE-24796
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.5.0.Final
> Environment: Fedora
> Reporter: Ondrej Dockal
> Priority: Critical
> Attachments: cdk3_sa-manual_correct-mhome.png, cdk3_sa-manual_wrong-mhome2.png
>
>
> In the first case I would understand that if you change you minishift home (in server editor) and then you start server adapter, you will get some mess... Although, I would like to see a validation of minishift home here. We are checking minishit binary, why not to check minishift home (in this case for existence of the folder). See
> !cdk3_sa-manual_wrong-mhome2.png|thumbnail!
> In the second case comes the bug. Even if I have set MINISHIFT_HOME folder, called setup-cdk that configured everything in that folder and put this folder as Minishift Home, CDK3 Server Adapter is not respecting that location. Or it is maybe OS tooling, not sure here. Solution here would be a check that verifies minishift's home set in CDK server editor corresponds with the one that minishift binary uses, if it is possible (from the side of binary) - but that seems not to be an option here as minishift/cdk stored everything in config that resides in MINISHIFT_HOME or ~/.minishift folder. See
> !cdk3_sa-manual_correct-mhome.png|thumbnail!
> Cc: [~adietish] [~rob.stryker].
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 2 months
[JBoss JIRA] (JBIDE-24796) Starting of CDK 3 Server Adapter with Minishift Home that differs from ~/.minishift prevents OS tooling to create proper connection and links it to default project
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24796?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-24796:
----------------------------------
Description:
In the first case I would understand that if you change you minishift home (in server editor) and then you start server adapter, you will get some mess... Although, I would like to see a validation of minishift home here. We are checking minishit binary, why not to check minishift home (in this case for existence of the folder). See
!cdk3_sa-manual_wrong-mhome2.png|thumbnail!
In the second case comes the bug. Even if I have set MINISHIFT_HOME folder, called setup-cdk that configured everything in that folder and put this folder as Minishift Home, CDK3 Server Adapter is not respecting that location. Or it is maybe OS tooling, not sure here. Solution here would be a check that verifies minishift's home set in CDK server editor corresponds with the one that minishift binary uses, if it is possible (from the side of binary) - but that seems not to be an option here as minishift/cdk stored everything in config that resides in MINISHIFT_HOME or ~/.minishift folder.
Cc: [~adietish] [~rob.stryker].
was:
In the first case I would understand that if you change you minishift home (in server editor) and then you start server adapter, you will get some mess... Although, I would like to see a validation of minishift home here. We are checking minishit binary, why not to check minishift home (in this case for existence of the folder). See
!cdk3_sa-manual_wrong-mhome2.png|thumbnail!
In the second case comes the bug. Even if I have set MINISHIFT_HOME folder, called setup-cdk that configured everything in that folder and put this folder as Minishift Home, CDK3 Server Adapter is not respecting that location. Or it is maybe OS tooling, not sure here. Solution here would be a check that verifies minishift's home set in CDK server editor corresponds with the one that minishift binary uses. If it is possible( from the side of binary)
Cc: [~adietish] [~rob.stryker].
> Starting of CDK 3 Server Adapter with Minishift Home that differs from ~/.minishift prevents OS tooling to create proper connection and links it to default project
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24796
> URL: https://issues.jboss.org/browse/JBIDE-24796
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.5.0.Final
> Environment: Fedora
> Reporter: Ondrej Dockal
> Priority: Critical
> Attachments: cdk3_sa-manual_wrong-mhome2.png
>
>
> In the first case I would understand that if you change you minishift home (in server editor) and then you start server adapter, you will get some mess... Although, I would like to see a validation of minishift home here. We are checking minishit binary, why not to check minishift home (in this case for existence of the folder). See
> !cdk3_sa-manual_wrong-mhome2.png|thumbnail!
> In the second case comes the bug. Even if I have set MINISHIFT_HOME folder, called setup-cdk that configured everything in that folder and put this folder as Minishift Home, CDK3 Server Adapter is not respecting that location. Or it is maybe OS tooling, not sure here. Solution here would be a check that verifies minishift's home set in CDK server editor corresponds with the one that minishift binary uses, if it is possible (from the side of binary) - but that seems not to be an option here as minishift/cdk stored everything in config that resides in MINISHIFT_HOME or ~/.minishift folder.
> Cc: [~adietish] [~rob.stryker].
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 2 months