[JBoss JIRA] (JBDS-4109) virtualbox detection does not work on Mac OS X
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-4109?page=com.atlassian.jira.plugin.... ]
Jan Richter closed JBDS-4109.
-----------------------------
This looks suspiciously similar to JBDS-4090. Closing since the detection works in master now.
> virtualbox detection does not work on Mac OS X
> ----------------------------------------------
>
> Key: JBDS-4109
> URL: https://issues.jboss.org/browse/JBDS-4109
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 10.1.0.AM2
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 10.2.0.AM2
>
>
> Detection does not work on mac because first steps assume it is windows, where detection done using environment variable and produces path to VirtualBox installation folder. Under mac it goes different way and uses 'which virtualbox'. It returns path to actual executable file(s) not folder.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23350) Deploy Docker Wizard: Prompt to enter credentials contains Finish button
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23350?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-23350:
----------------------------------
Labels: deploy_docker_wizard openshift_v3 (was: )
> Deploy Docker Wizard: Prompt to enter credentials contains Finish button
> ------------------------------------------------------------------------
>
> Key: JBIDE-23350
> URL: https://issues.jboss.org/browse/JBIDE-23350
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.AM2
> Reporter: Marián Labuda
> Labels: deploy_docker_wizard, openshift_v3
>
> When opening Deploy Image to OpenShift wizard from context menu of a docker image and there was no OpenShift connection selected, OpenShift connection wizard is shown with Finish button, although connection is active (connected). There should be opened the Deploy Image to OpenShift with the connection wizard page and it should have next button.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23350) Deploy Docker Wizard: Prompt to enter credentials contains Finish button
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-23350:
-------------------------------------
Summary: Deploy Docker Wizard: Prompt to enter credentials contains Finish button
Key: JBIDE-23350
URL: https://issues.jboss.org/browse/JBIDE-23350
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.4.2.AM2
Reporter: Marián Labuda
When opening Deploy Image to OpenShift wizard from context menu of a docker image and there was no OpenShift connection selected, OpenShift connection wizard is shown with Finish button, although connection is active (connected). There should be opened the Deploy Image to OpenShift with the connection wizard page and it should have next button.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBDS-3731) Installer - Failure to install a component does not halt the installer's progress bar
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3731?page=com.atlassian.jira.plugin.... ]
Jan Richter closed JBDS-3731.
-----------------------------
> Installer - Failure to install a component does not halt the installer's progress bar
> -------------------------------------------------------------------------------------
>
> Key: JBDS-3731
> URL: https://issues.jboss.org/browse/JBDS-3731
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.CR1
> Environment: Windows10
> Reporter: Len DiMaggio
> Assignee: Denis Golovin
> Labels: havoc
> Fix For: 10.2.0.AM2
>
> Attachments: Screenshot (20).png, Screenshot (24).png
>
>
> See the attached screenshots - when the bug described in JBDS-3722 was encountered, the virtualbox installation status bar continued to proceed, even though the installation of the affected component had stopped. This will be confusing to the user.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-22347) NullPointerException in JdtUtils.resolveTypeArguments
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22347?page=com.atlassian.jira.plugi... ]
Jan Richter closed JBIDE-22347.
-------------------------------
Closing, should it happen again in a new version, aeri should reopen this.
> NullPointerException in JdtUtils.resolveTypeArguments
> -----------------------------------------------------
>
> Key: JBIDE-22347
> URL: https://issues.jboss.org/browse/JBIDE-22347
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.3.1.Final
> Reporter: Automated Error Reporting Bot
> Assignee: Xavier Coulon
> Fix For: 4.4.2.AM2
>
>
> The following problem was reported via the automated error reporting:
> Message: Failed to (re)build the JAX-RS metamodel for projet assist-web-war
> {noformat}
> java.lang.NullPointerException: null
> at org.jboss.tools.ws.jaxrs.core.jdt.JdtUtils.resolveTypeArguments(JdtUtils.java:1009)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsProvider$Builder.getProvidedKinds(JaxrsProvider.java:264)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsProvider$Builder.build(JaxrsProvider.java:210)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsProvider$Builder.build(JaxrsProvider.java:180)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsElementFactory.internalCreateElements(JaxrsElementFactory.java:147)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsElementFactory.createElements(JaxrsElementFactory.java:75)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.processJavaElement(JaxrsMetamodel.java:628)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.processResourceChange(JaxrsMetamodel.java:608)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.processProject(JaxrsMetamodel.java:506)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.ResourceChangedBuildJob.run(ResourceChangedBuildJob.java:70)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
> Bundles:
> | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.7.0.v20150330-2103 |
> | org.jboss.tools.ws.jaxrs.core | 1.8.1.Final-v20160331-0952-B76 | 1.8.1.Final-v20160331-0952-B76 |
> Operating Systems:
> | Windows | 6.1.0 | 6.1.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/5720efc5e4b0a54983...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-22896) JavaModelException below JdtUtils.findDeclaringNode (thrown in JavaElement.newNotPresentException)
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22896?page=com.atlassian.jira.plugi... ]
Jan Richter closed JBIDE-22896.
-------------------------------
Problem set to reopen the issue should it happen again in a new version and closing.
> JavaModelException below JdtUtils.findDeclaringNode (thrown in JavaElement.newNotPresentException)
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22896
> URL: https://issues.jboss.org/browse/JBIDE-22896
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.3.1.Final
> Reporter: Automated Error Reporting Bot
> Assignee: Xavier Coulon
> Fix For: 4.4.2.AM2
>
>
> The following problem was reported via the automated error reporting:
> Message: Failed to build or refresh the JAX-RS metamodel
> {noformat}
> org.eclipse.jdt.core.JavaModelException: submt(HttpServletRequest, int) [in PublicWS [in [Working copy] PublicWS.java [in be.fromprison.ws.endpoints [in src/main/java [in from-prison]]]]] does not exist
> at org.eclipse.jdt.internal.core.JavaElement.newNotPresentException(JavaElement.java:556)
> at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:590)
> 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.SourceRefElement.getSourceRange(SourceRefElement.java:218)
> at org.jboss.tools.ws.jaxrs.core.jdt.JdtUtils.findDeclaringNode(JdtUtils.java:494)
> at org.jboss.tools.ws.jaxrs.core.jdt.JdtUtils.resolveAllAnnotations(JdtUtils.java:373)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsResourceMethod$Builder.buildInResource(JaxrsResourceMethod.java:153)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsElementFactory.createElements(JaxrsElementFactory.java:211)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsElementFactory.createElements(JaxrsElementFactory.java:65)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.processJavaElementChange(JaxrsMetamodel.java:420)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.processJavaElementChange(JaxrsMetamodel.java:392)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementChangedBuildJob.run(JavaElementChangedBuildJob.java:73)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
> Bundles:
> | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.8.0.v20160509-0411 |
> | org.eclipse.jdt.core | 3.11.0.xx-201604081629-e45 | 3.12.0.v_OTDT_r250_201606070956 |
> | org.eclipse.wst.sse.ui | 1.3.401.v201510130005 | 1.3.500.v201605120129 |
> | org.jboss.tools.common.validation | 3.7.1.Final-v20160408-2358-B112 | 3.8.0.Final-v20160610-1533-B7 |
> | org.jboss.tools.ws.jaxrs.core | 1.8.1.Final-v20160331-0952-B76 | 1.9.1.v20160608-0648 |
> | org.jboss.tools.ws.jaxrs.ui | 1.8.1.Final-v20160331-0952-B76 | 1.9.0.Final-v20160610-0003-B1 |
> Operating Systems:
> | Linux | 3.10.0.13 | 4.6.3.fc24 |
> | MacOSX | 10.11.3 | 10.11.6 |
> | 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/571dd2b8e4b08bd809...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months