[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 Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24796?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-24796:
-------------------------------------
No problem [~odockal] :D
> 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
> Assignee: Rob Stryker
> 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)
8 years, 8 months
[JBoss JIRA] (JBDS-4495) Missing CDI features
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4495?page=com.atlassian.jira.plugin.... ]
Nick Boldt reassigned JBDS-4495:
--------------------------------
Assignee: Nick Boldt (was: Jeff MAURY)
Resolution: Done
Done as of this morning's green builds.
> Missing CDI features
> --------------------
>
> Key: JBDS-4495
> URL: https://issues.jboss.org/browse/JBDS-4495
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, cdi
> Affects Versions: 11.0.0.GA
> Reporter: Lukáš Valach
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: respin-a
> Fix For: 11.0.0.GA
>
> Attachments: No_CDI_Plugins.png
>
>
> I have installed devstudio-11.0.0.GA-v20170801-0412-B670-installer-standalone.jar and I don't see any CDI functionality. It seems that CDI related plugins wasn't installed.
> Help->About->Installation Detains->Plugins, Search for "CDI", there is nothing.
> !No_CDI_Plugins.png|thumbnail!
> JBoss Tools seems to be ok.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-19715) Refactoring: get rid of "fullSite", stick with "repository"
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19715?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-19715:
-------------------------------
Sprint: devex #116 June 2016, devex #128 February 2017, devex #132 May 2017, devex #136 August 2018 (was: devex #116 June 2016, devex #128 February 2017, devex #132 May 2017)
> Refactoring: get rid of "fullSite", stick with "repository"
> -----------------------------------------------------------
>
> Key: JBIDE-19715
> URL: https://issues.jboss.org/browse/JBIDE-19715
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Affects Versions: 4.3.0.Alpha1
> Reporter: Mickael Istria
> Assignee: Nick Boldt
> Priority: Minor
> Fix For: 4.5.1.AM1
>
>
> Currently, some builds such as aggregate create a "site/target/fullSite" folder, which is aimed at being deployed. However, it would be simpler to populate the site/target/repository folder, so it would be only one directory to move, and the same one for all builds.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months