[JBoss JIRA] (JBIDE-24236) Preferences: "automagically" use the oc that's shipped with the cdk3
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24236?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-24236:
-------------------------------
Fix Version/s: 4.5.x
(was: 4.5.0.Final)
> 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.x
>
>
> 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, 9 months
[JBoss JIRA] (JBIDE-24503) Properties: Events are hardly useable
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24503?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-24503:
-------------------------------
Fix Version/s: 4.5.x
(was: 4.5.0.Final)
> Properties: Events are hardly useable
> -------------------------------------
>
> Key: JBIDE-24503
> URL: https://issues.jboss.org/browse/JBIDE-24503
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.4.Final
> Reporter: Andre Dietisheim
> Fix For: 4.5.x
>
> Attachments: events-entries.png, image-2017-05-23-22-58-58-587.png
>
>
> steps:
> # EXEC: create some new application (via template or image) so that you have a build and image pulling happening
> # EXEC: select project in OpenShift Explorer and open up "Properties". In "Properties" select "Events" tab. In event entries, select some item (ex. some "Pulling" in "Reason" column), inspect the details that are displayed for it
> Result:
> !events-entries.png!
> Many entries like "Pulling", "Failed Sync", "BackOff" etc. that have larger "Message" and "Source" are hardly useable.
> * If the "Message" is very long, you have to enlarge the "Value" column a lot to be able to read the message.
> * If the "Source" is multi-line, you'll only see the opening "{", the rest is simply not displayed.
> Workaround:
> open web console where the logs are nicely displayed
> !image-2017-05-23-22-58-58-587.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JBIDE-16517) SSL Certificate dialog: need to show to what server we're connecting
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16517?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-16517:
-------------------------------
Fix Version/s: 4.5.x
(was: 4.5.0.Final)
> SSL Certificate dialog: need to show to what server we're connecting
> --------------------------------------------------------------------
>
> Key: JBIDE-16517
> URL: https://issues.jboss.org/browse/JBIDE-16517
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.2.0.Alpha1
> Reporter: Andre Dietisheim
> Labels: connection_wizard, openshift_v2, openshift_v3
> Fix For: 4.5.x
>
> Attachments: certificate-dialog.png
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> The current dialog does not show explicitly to what server we're talking:
> !certificate-dialog.png!
> We should add some text like
> ...untrusted SSL certificate *presented by server <server-url>*
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JBIDE-22815) JavaModelException below AttachSourcesActionDelegate.setActiveEditor (thrown in JavaElement.newJavaModelException)
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22815?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22815:
-------------------------------
Fix Version/s: 4.5.x
(was: 4.5.0.Final)
> JavaModelException below AttachSourcesActionDelegate.setActiveEditor (thrown in JavaElement.newJavaModelException)
> ------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22815
> URL: https://issues.jboss.org/browse/JBIDE-22815
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 4.4.0.Final
> Reporter: Automated Error Reporting Bot
> Assignee: Fred Bricon
> Fix For: 4.5.x
>
>
> The following problem was reported via the automated error reporting:
> Message: HIDDEN
> {noformat}
> org.eclipse.jdt.core.JavaModelException: HIDDEN
> at org.eclipse.jdt.internal.core.JavaElement.newJavaModelException(JavaElement.java:566)
> at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:247)
> at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:579)
> at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:316)
> at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:302)
> at org.eclipse.jdt.internal.core.PackageFragmentRoot.getKind(PackageFragmentRoot.java:486)
> at org.eclipse.jdt.internal.core.PackageFragmentRoot.getSourceAttachmentPath(PackageFragmentRoot.java:600)
> at org.jboss.tools.maven.sourcelookup.ui.actions.AttachSourcesActionDelegate.setActiveEditor(AttachSourcesActionDelegate.java:93)
> at org.eclipse.ui.internal.EditorPluginAction.editorChanged(EditorPluginAction.java:71)
> at org.eclipse.ui.internal.EditorActionBuilder$EditorContribution.editorChanged(EditorActionBuilder.java:80)
> at org.eclipse.ui.internal.EditorActionBuilder$ExternalContributor.setActiveEditor(EditorActionBuilder.java:129)
> at org.eclipse.ui.internal.EditorActionBars.partChanged(EditorActionBars.java:344)
> at org.eclipse.ui.internal.WorkbenchPage.updateActivations(WorkbenchPage.java:302)
> at org.eclipse.ui.internal.WorkbenchPage.access$18(WorkbenchPage.java:284)
> at org.eclipse.ui.internal.WorkbenchPage$E4PartListener.partActivated(WorkbenchPage.java:202)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl$3.run(PartServiceImpl.java:245)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.firePartActivated(PartServiceImpl.java:242)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:711)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:639)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:634)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.showPart(PartServiceImpl.java:1164)
> at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:3252)
> at org.eclipse.ui.internal.WorkbenchPage.access$25(WorkbenchPage.java:3167)
> at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:3149)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3144)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3108)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3098)
> at org.eclipse.ui.ide.IDE.openEditor(IDE.java:541)
> at org.eclipse.ui.ide.IDE.openEditor(IDE.java:500)
> at org.eclipse.ui.internal.ide.handlers.OpenResourceHandler.execute(OpenResourceHandler.java:132)
> at org.eclipse.ui.internal.ide.handlers.OpenResourceHandler.run(OpenResourceHandler.java:187)
> at org.eclipse.ui.internal.handlers.ActionDelegateHandlerProxy.execute(ActionDelegateHandlerProxy.java:299)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
> at sun.reflect.GeneratedMethodAccessor.invoke(null:-1)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> {noformat}
> Bundles:
> | org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.12.0.v20160606-1342 |
> | org.eclipse.dltk.ui | 5.4.0.201602110510 | 5.4.0.201602110510 |
> | org.eclipse.e4.core.di | 1.5.0.v20150421-2214 | 1.6.0.v20160319-0612 |
> | org.eclipse.e4.ui.workbench | 1.3.0.v20150531-1948 | 1.4.0.v20160517-1624 |
> | org.eclipse.e4.ui.workbench.renderers.swt | 0.13.0.v20150901-1347 | 0.14.0.v20160525-0940 |
> | org.eclipse.e4.ui.workbench.swt | 0.13.0.v20150504-0621 | 0.14.0.v20160523-1900 |
> | org.eclipse.jdt.core | 3.11.2.v20160128-0629 | 3.12.0.v20160516-2131 |
> | org.eclipse.jdt.ui | 3.11.2.v20151123-1510 | 3.12.0.v20160525-1829 |
> | org.eclipse.jface | 3.11.0.v20150602-1400 | 3.12.0.v20160518-1929 |
> | org.eclipse.jst.servlet.ui | 1.1.801.v201409042158 | 1.1.801.v201409042158 |
> | org.eclipse.php.ui | 3.7.0.201602121754 | 3.7.0.201602121754 |
> | org.eclipse.search | 3.10.0.v20150318-0856 | 3.10.0.v20150318-0856 |
> | org.eclipse.swt | 3.104.1.v20150825-0743 | 3.105.0.v20160603-0902 |
> | org.eclipse.ui | 3.107.0.v20150507-1945 | 3.108.0.v20160518-1929 |
> | org.eclipse.ui.ide | 3.11.0.v20150825-2158 | 3.12.0.v20160601-1609 |
> | org.eclipse.ui.navigator | 3.6.0.v20150422-0725 | 3.6.100.v20160518-1929 |
> | org.eclipse.ui.views | 3.8.0.v20150422-0725 | 3.8.0.v20150422-0725 |
> | org.jboss.tools.maven.sourcelookup.ui | 1.7.1.Final-v20160401-1059-B103 | 1.8.0.Final-v20160613-2000-B8 |
> Operating Systems:
> | Linux | 3.13.0 | 4.4.0 |
> | MacOSX | 10.11.5 | 10.11.5 |
> | Windows | 6.1.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/5719d0a3e4b04d6a2b...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JBIDE-18131) Split the org.jboss.tools.common.validation plugin in 'core' + 'ui'
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18131?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-18131:
-------------------------------
Fix Version/s: 4.5.x
(was: 4.5.0.Final)
> Split the org.jboss.tools.common.validation plugin in 'core' + 'ui'
> -------------------------------------------------------------------
>
> Key: JBIDE-18131
> URL: https://issues.jboss.org/browse/JBIDE-18131
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: common
> Affects Versions: 4.2.0.Beta3
> Reporter: Xavier Coulon
> Assignee: Jeff MAURY
> Fix For: 4.5.x
>
>
> IMHO, it would make sense to split the {{org.jboss.tools.common.validation}} plugin in two separate ones: {{core}} + {{ui}}:
> - the {{core}} part would deal with performing the validation (based on the WST Validation Framework)
> - the {{ui}} part would deal for the preference pages and configuration.
> ATM, the CDI validation is performed in the {{org.jboss.tools.cdi.core}} plugin, but this drags a log of _.ui_ dependencies, which is somehow wrong.
> OTOH, the JAX-RS validation is performed in the {{org.jboss.tools.ws.jaxrs.ui}} plugin to avoid having _*.ui_ dependencies in the {{org.jboss.tools.ws.jaxrs.core}} plugin, but this is somehow wrong, too (I had to move the {{marker}} declaration in the {{org.jboss.tools.ws.jaxrs.core}} plugin to be able to remove all markers when the JAX-RS support is removed from a project, whatever the way it is removed (nature, facet, etc.)
> Can we discuss about that change for JBoss Tools 4.3 ?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months