[JBoss JIRA] (JBIDE-23637) AERI report: NPE in CDKRuntimeDetector.exists
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23637?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-23637:
-------------------------------------
Seems to be caused by a server in an existing workspace where the new install does not have support for some old server type.
An example would be an installation that previously had a wonka server type, a new install that does not have wonka-tools.
> AERI report: NPE in CDKRuntimeDetector.exists
> ---------------------------------------------
>
> Key: JBIDE-23637
> URL: https://issues.jboss.org/browse/JBIDE-23637
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.5.0.AM1
> Reporter: Dmitrii Bocharov
>
> https://aer.ctrlflow.com/redhat/reporters#!/problems/584af47be4b0c53b1227...
> {noformat}
> at org.jboss.tools.openshift.cdk.server.core.internal.detection.CDKRuntimeDetector.exists(CDKRuntimeDetector.java:106)
>
> at org.jboss.tools.openshift.cdk.server.core.internal.detection.CDKRuntimeDetector.initializeRuntime(CDKRuntimeDetector.java:55)
>
> at org.jboss.tools.runtime.core.internal.RuntimeDetector.initializeRuntime(RuntimeDetector.java:149)
>
> at org.jboss.tools.runtime.core.util.RuntimeInitializerUtil.initializeRuntimes(RuntimeInitializerUtil.java:56)
>
> at org.jboss.tools.runtime.core.util.RuntimeInitializerUtil.initializeRuntimesFromFolder(RuntimeInitializerUtil.java:36)
>
> at org.jboss.tools.runtime.ui.internal.startup.JBossRuntimeStartup.initializeCDKRuntimes(JBossRuntimeStartup.java:78)
>
> at org.jboss.tools.runtime.ui.internal.startup.JBossRuntimeStartup.initializeRuntimes(JBossRuntimeStartup.java:53)
>
> at org.jboss.tools.runtime.ui.internal.startup.RuntimeScanner$1.run(RuntimeScanner.java:79)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 6 months
[JBoss JIRA] (JBIDE-23658) Hibernate console configuration wizard problems - and no way to get specifics
by Jesper Skov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23658?page=com.atlassian.jira.plugi... ]
Jesper Skov commented on JBIDE-23658:
-------------------------------------
Yes.
But it will take me some time to make - tomorrow.
I would like to be able to provide a stack trace - or a log warning/info whatever - that hints at the problem.
Can you tell me how to get some output from the plugin in eclipse?
As per above, the only documentation for how to do this does not work.
> Hibernate console configuration wizard problems - and no way to get specifics
> -----------------------------------------------------------------------------
>
> Key: JBIDE-23658
> URL: https://issues.jboss.org/browse/JBIDE-23658
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.4.2.Final
> Environment: Neon.1 and Neon.2, Windows 7, targeting Oracle
> Reporter: Jesper Skov
> Assignee: Koen Aers
>
> Creating a Hibernate Console Configuration using the wizard fails for most of our projects.
> All the feedback we have is the text in red: "Could not create JPA based Configuration"
> I would have liked to qualify this problem report with some more information. But there is no problems reported in the eclipse log.
> I have tried enabling debugging, as per http://docs.jboss.org/tools/latest/en/hibernatetools/html/plugins.html#de..., without getting any output to the Eclipse Error console, or to the hibernate log file.
> We wonder if maybe the plugin/perspective is just dead (or dying).
> The plugin documentation has snapshots from 2010/2011, and the JBossTools documentation itself (http://docs.jboss.org/tools/latest/) was not updated since 4.1.0/2013.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 6 months
[JBoss JIRA] (JBDS-4229) If updating CDK installation error reported
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4229?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-4229:
-------------------------------------
[~jeffmaury] Installer removes existing box first, then installs new one. What does it say in log? Could you attach it ti the issue?
> If updating CDK installation error reported
> -------------------------------------------
>
> Key: JBDS-4229
> URL: https://issues.jboss.org/browse/JBDS-4229
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 10.2.0.GA
> Reporter: Jeff MAURY
> Labels: cdk, installer
> Fix For: 10.3.0.GA
>
>
> If you install DevSuite on a system where a previous version already exists, then an error is reported during the CDK installation but no explanation is given. User has to go to the install log and detect that the cdkv2 box is already there
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 6 months
[JBoss JIRA] (JBIDE-23136) Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23136?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-23136:
-------------------------------------
Sprint: devex #123 November 2016, devex #125 December 2017 (was: devex #123 November 2016)
> Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-23136
> URL: https://issues.jboss.org/browse/JBIDE-23136
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.Final
> Reporter: Marián Labuda
> Assignee: Dmitrii Bocharov
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.4.3.AM1
>
> Attachments: eap64-basic-s2i-new-app-from-cli-1.png, eap64-basic-s2i-new-app-from-jbosstools-1.png, local-docker-images-after-pull-1.png
>
>
> I have a docker connection to local docker daemon and a CDK docker connection. I am pushing an image from a docker connection to CDK registry via Deploy Image to OpenShift wizard. Push of an image pass, but it results into an image with no tag, see:
> 172.30.192.49:5000/msa/msa <none> 238200ae067d 4 months ago 1.05 GB
> Such images are not shown in docker explorer under a docker connection because of upstream bug ERT-411
> Steps to reproduce:
> - have a project with a file named {{Dockerfile}} with the following content (1 line):
> {code}
> FROM fedora:latest
> {code}
> - Select the file in the project explorer, then {{Run As > Docker Image Build}}. Use the CDK connection and give it a name (eg: {{username/fedora}})
> - Select the image in the Docker Explorer view, then {{Deploy to OpenShift}}.
> - In the wizard, select the option to push the image to the registry (add a dummy port if needed)
> - once the operation completed, there's an unexpected image named like {{172.30.164.33:5000/<project>/fedora}} in the output of the {{docker images}} command (in CLI)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 6 months
[JBoss JIRA] (JBIDE-23658) Hibernate console configuration wizard problems - and no way to get specifics
by Jesper Skov (JIRA)
Jesper Skov created JBIDE-23658:
-----------------------------------
Summary: Hibernate console configuration wizard problems - and no way to get specifics
Key: JBIDE-23658
URL: https://issues.jboss.org/browse/JBIDE-23658
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: hibernate
Affects Versions: 4.4.2.Final
Environment: Neon.1 and Neon.2, Windows 7, targeting Oracle
Reporter: Jesper Skov
Creating a Hibernate Console Configuration using the wizard fails for most of our projects.
All the feedback we have is the text in red: "Could not create JPA based Configuration"
I would have liked to qualify this problem report with some more information. But there is no problems reported in the eclipse log.
I have tried enabling debugging, as per http://docs.jboss.org/tools/latest/en/hibernatetools/html/plugins.html#de..., without getting any output to the Eclipse Error console, or to the hibernate log file.
We wonder if maybe the plugin/perspective is just dead (or dying).
The plugin documentation has snapshots from 2010/2011, and the JBossTools documentation itself (http://docs.jboss.org/tools/latest/) was not updated since 4.1.0/2013.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 6 months