[JBoss JIRA] (JBDS-4495) Missing CDI features
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBDS-4495?page=com.atlassian.jira.plugin.... ]
Pavol Srna commented on JBDS-4495:
----------------------------------
+1 for both
> 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: Jeff MAURY
> Priority: Blocker
> 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] (JBDS-4495) Missing CDI features
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-4495?page=com.atlassian.jira.plugin.... ]
Martin Malina commented on JBDS-4495:
-------------------------------------
[~nickboldt],
{quote}
we want to keep the deprecated Central connectors for Seam 3, but remove the CDI stuff from inside them?
{quote}
You mean remove the features that we're putting back in? That makes sense. If that's the case, then +1 for both.
> 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: Jeff MAURY
> Priority: Blocker
> 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-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 commented on JBIDE-24796:
---------------------------------------
[~rob.stryker] Sorry for quite complicated description. It was hard to me to understand the issue and found steps to reproduce it. Will try to go to the root cause next time. It was not that obvious before like you and Martin described it above...
> 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 Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBDS-4495?page=com.atlassian.jira.plugin.... ]
Jeff MAURY commented on JBDS-4495:
----------------------------------
+1 for both
> 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: Jeff MAURY
> Priority: Blocker
> 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-24236) Preferences: "automagically" use the oc that's shipped with the cdk3
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24236?page=com.atlassian.jira.plugi... ]
Ondrej Dockal commented on JBIDE-24236:
---------------------------------------
Hi [~rob.stryker], could you please write short description/steps how to verify this. I have done some testing, yet, not sure whether it was all. Thanks!
> Preferences: "automagically" use the oc that's shipped with the cdk3
> --------------------------------------------------------------------
>
> Key: JBIDE-24236
> URL: https://issues.jboss.org/browse/JBIDE-24236
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Labels: oc_binary, openshift_v3
> Fix For: 4.5.0.Final
>
>
> After minishift setup-cdk, the oc command is at %USERPROFILE%\.minishift\cache\oc\v3.4.1.2
> Should our tools help streamline this process for users? I would suggest yes, but needs investigation **how** to do it.
> Another question is, do we need different 'oc' command versions for each openshift connection? Should it really be a workplace setting? Or should it be per-connection?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-24024) Server adapter editor, wizard: better tell me what the settings are for
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24024?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-24024 at 8/8/17 9:39 AM:
------------------------------------------------------------------
[~rhopp] good catch! changing the fix-version.
The link to JBIDE-24184 where this is told to be incorporated in the former was intended to express this. But yes, the fix-version is wrong.
was (Author: adietish):
[~rhopp] good catch! changing the fix-version
> Server adapter editor, wizard: better tell me what the settings are for
> -----------------------------------------------------------------------
>
> Key: JBIDE-24024
> URL: https://issues.jboss.org/browse/JBIDE-24024
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.3.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter_editor, server_adapter_wizard
> Fix For: 4.5.1.AM1
>
> Attachments: image-2017-03-03-11-43-41-941.png, image-2017-03-03-11-44-46-410.png, server-adapter-editor.png, server-adapter-wizard.png
>
>
> A server adapter will publish local files to a pod in OpenShift (via rsync). Our wizard and server adapter editors allows to set the adapter to fullfill this task. The wizard and the editor do a poor job explaining the purpose of those settings though:
> The wizard generically states that it does "file synchronization" but fails to tell "from" where to "where"
> !image-2017-03-03-11-43-41-941.png!
> The editor is even poorer in usability. It wont say anything about file synchronization and even mixes settings for the source and destination:
> !image-2017-03-03-11-44-46-410.png!
> "Source Path" should be right below the "Eclipse Project" since it's providing further details for it. "Pod Deployment Path" should be right below "Resource" (år "Service" in older verisions of this editor" since it provides the path on pods that are identified by "Resource".
> Ideally we'd also add labels "From" and "To" (or similar means to better identify the settings)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-24024) Server adapter editor, wizard: better tell me what the settings are for
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24024?page=com.atlassian.jira.plugi... ]
Andre Dietisheim resolved JBIDE-24024.
--------------------------------------
Resolution: Done
> Server adapter editor, wizard: better tell me what the settings are for
> -----------------------------------------------------------------------
>
> Key: JBIDE-24024
> URL: https://issues.jboss.org/browse/JBIDE-24024
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.3.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter_editor, server_adapter_wizard
> Fix For: 4.5.1.AM1
>
> Attachments: image-2017-03-03-11-43-41-941.png, image-2017-03-03-11-44-46-410.png, server-adapter-editor.png, server-adapter-wizard.png
>
>
> A server adapter will publish local files to a pod in OpenShift (via rsync). Our wizard and server adapter editors allows to set the adapter to fullfill this task. The wizard and the editor do a poor job explaining the purpose of those settings though:
> The wizard generically states that it does "file synchronization" but fails to tell "from" where to "where"
> !image-2017-03-03-11-43-41-941.png!
> The editor is even poorer in usability. It wont say anything about file synchronization and even mixes settings for the source and destination:
> !image-2017-03-03-11-44-46-410.png!
> "Source Path" should be right below the "Eclipse Project" since it's providing further details for it. "Pod Deployment Path" should be right below "Resource" (år "Service" in older verisions of this editor" since it provides the path on pods that are identified by "Resource".
> Ideally we'd also add labels "From" and "To" (or similar means to better identify the settings)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months