[JBoss JIRA] (JBDS-4131) Can't import example project after RPM installation on RHEL 7
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4131?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4131:
-----------------------------
Attachment: devstudio10.2.wtf.png
devstudio10.2.wtf2.png
After re-adding a number of missing dependencies [1] devstudio now starts up... but I ran the HTML5 Project quickstart and got this not-so-helpful error:
!devstudio10.2.wtf.png|thumbnail!
Digging deeper, it's a NPE in importProject:
{code}
java.lang.NullPointerException
at org.jboss.tools.maven.project.examples.ImportMavenArchetypeProjectExampleDelegate.importProject(ImportMavenArchetypeProjectExampleDelegate.java:57)
at org.jboss.tools.maven.project.examples.AbstractImportMavenExample.importProject(AbstractImportMavenExample.java:36)
at org.jboss.tools.project.examples.wizard.NewProjectExamplesJob.runInWorkspace(NewProjectExamplesJob.java:90)
at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
{code}
!devstudio10.2.wtf2.png|thumbnail!
> Can't import example project after RPM installation on RHEL 7
> -------------------------------------------------------------
>
> Key: JBDS-4131
> URL: https://issues.jboss.org/browse/JBDS-4131
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, rpm
> Affects Versions: 10.2.0.AM3
> Environment: RHEL Server 7.2.
> Reporter: Lukáš Valach
> Fix For: 10.2.0.AM3
>
> Attachments: DevstudiErrorLog.txt, devstudio10.2.wtf.png, devstudio10.2.wtf2.png, import_wizard.png, rh-eclipse46-devstudio.repo
>
>
> During the test of RPM installation on RHEL 7 I noticed that I can't import HTML5 example project from central. Only the window with message "Refreshing project examples" appear for a while and then nothing happens.
> There is one warning and many errors in Error Log View.
> Error log export: [^DevstudiErrorLog.txt]
> I also tried to import project from file system, but there isn't the "Existing Maven Project" option in the import wizard. [^import_wizard.png]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23403) As a user I need to be able to inspect the state of my EAP deployments
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-23403:
----------------------------------------
Summary: As a user I need to be able to inspect the state of my EAP deployments
Key: JBIDE-23403
URL: https://issues.jboss.org/browse/JBIDE-23403
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Affects Versions: 4.4.2.AM2
Reporter: Andre Dietisheim
Assignee: Rob Stryker
The web console for eap was disabled in the eap image that we have in OpenShift. It's therefore not possible for users to inspect the state of their deployment.
The only there is to do such thing is to inspect jolokia informations. There is no such tooling in Eclipse yet. Furthermore the url to access those is non-obvious as one can see [herehttp://developers.redhat.com/blog/2016/03/30/jolokia-jvm-monitoring-i...]. I therefore suggest that we should provide help/tooling that allows users to easily access and manipulate those informations.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBDS-4134) missing require-bundles in rpm install
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4134?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4134:
----------------------------------
Same list, minus versions:
{code}
com.google.guava
javax.servlet
org.eclipse.cdt.core.native
org.eclipse.jetty.websocket.server
org.eclipse.jetty.websocket.servlet
org.eclipse.m2e.core
org.eclipse.m2e.core.ui
org.eclipse.m2e.discovery
org.eclipse.m2e.editor.xml
org.eclipse.m2e.jdt
org.eclipse.m2e.profiles.core
org.eclipse.m2e.wtp
org.eclipse.rse.core
org.eclipse.rse.ui
org.eclipse.tm.terminal.connector.local
org.jboss.tools.browsersim.ui
org.jboss.tools.forge.core
org.jboss.tools.livereload.core
org.jboss.tools.maven.core
org.jboss.tools.maven.sourcelookup.core
org.jboss.tools.maven.ui
org.jboss.tools.openshift.common.ui
org.jboss.tools.openshift.ui
org.sonatype.m2e.mavenarchiver
{code}
> missing require-bundles in rpm install
> --------------------------------------
>
> Key: JBDS-4134
> URL: https://issues.jboss.org/browse/JBDS-4134
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Sub-task
> Components: build, rpm
> Affects Versions: 10.2.0.AM2
> Reporter: Nick Boldt
> Fix For: 10.2.0.AM3
>
> Attachments: unresolved-requirements.txt
>
>
> Digested from the log attached to JBDS-3141, here's a list of all the missing require-bundles as reported by Eclipse on startup of the rh-eclipse46-devstudio install. See attached.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23402) [WATCHER] Explorer: can "Deploy Latest" even if the build failed
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23402?page=com.atlassian.jira.plugi... ]
Jeff Cantrill commented on JBIDE-23402:
---------------------------------------
This does appear to be a feature request/bug in OpenShift. I would redirect this question to https://github.com/openshift/origin
> [WATCHER] Explorer: can "Deploy Latest" even if the build failed
> ----------------------------------------------------------------
>
> Key: JBIDE-23402
> URL: https://issues.jboss.org/browse/JBIDE-23402
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, upstream
> Affects Versions: 4.4.2.AM2
> Reporter: Andre Dietisheim
> Fix For: 4.4.x
>
> Attachments: JBIDE-23402-a.png, JBIDE-23402-b.png
>
>
> When right-clicking on an application, we can select "Deploy Latest". This will start both a build and a deploy pod. The deploy pod will wait for the build pod to complete.
> In this case, due to github being unavailable, the build pod will fail very quickly. The deploy pod will then continue waiting up to 10 minutes even though what it is waiting for has already failed. This 10 minutes is wasted. It should fail quickly.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23402) Explorer: can "Deploy Latest" even if the build failed
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23402?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-23402:
------------------------------------------
[~jcantrill] This looks like something that we should pass along to openshift-dev, agree?
> Explorer: can "Deploy Latest" even if the build failed
> ------------------------------------------------------
>
> Key: JBIDE-23402
> URL: https://issues.jboss.org/browse/JBIDE-23402
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, upstream
> Affects Versions: 4.4.2.AM2
> Reporter: Andre Dietisheim
> Fix For: 4.4.x
>
> Attachments: JBIDE-23402-a.png, JBIDE-23402-b.png
>
>
> When right-clicking on an application, we can select "Deploy Latest". This will start both a build and a deploy pod. The deploy pod will wait for the build pod to complete.
> In this case, due to github being unavailable, the build pod will fail very quickly. The deploy pod will then continue waiting up to 10 minutes even though what it is waiting for has already failed. This 10 minutes is wasted. It should fail quickly.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23402) [Upstream] Explorer: can "Deploy Latest" even if the build failed
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23402?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23402:
-------------------------------------
Summary: [Upstream] Explorer: can "Deploy Latest" even if the build failed (was: Explorer: can "Deploy Latest" even if the build failed)
> [Upstream] Explorer: can "Deploy Latest" even if the build failed
> -----------------------------------------------------------------
>
> Key: JBIDE-23402
> URL: https://issues.jboss.org/browse/JBIDE-23402
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, upstream
> Affects Versions: 4.4.2.AM2
> Reporter: Andre Dietisheim
> Fix For: 4.4.x
>
> Attachments: JBIDE-23402-a.png, JBIDE-23402-b.png
>
>
> When right-clicking on an application, we can select "Deploy Latest". This will start both a build and a deploy pod. The deploy pod will wait for the build pod to complete.
> In this case, due to github being unavailable, the build pod will fail very quickly. The deploy pod will then continue waiting up to 10 minutes even though what it is waiting for has already failed. This 10 minutes is wasted. It should fail quickly.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23402) [Upstream] Explorer: can "Deploy Latest" even if the build failed
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23402?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23402:
-------------------------------------
Fix Version/s: 4.4.x
> [Upstream] Explorer: can "Deploy Latest" even if the build failed
> -----------------------------------------------------------------
>
> Key: JBIDE-23402
> URL: https://issues.jboss.org/browse/JBIDE-23402
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, upstream
> Affects Versions: 4.4.2.AM2
> Reporter: Andre Dietisheim
> Fix For: 4.4.x
>
> Attachments: JBIDE-23402-a.png, JBIDE-23402-b.png
>
>
> When right-clicking on an application, we can select "Deploy Latest". This will start both a build and a deploy pod. The deploy pod will wait for the build pod to complete.
> In this case, due to github being unavailable, the build pod will fail very quickly. The deploy pod will then continue waiting up to 10 minutes even though what it is waiting for has already failed. This 10 minutes is wasted. It should fail quickly.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23402) [WATCHER] Explorer: can "Deploy Latest" even if the build failed
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23402?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23402:
-------------------------------------
Summary: [WATCHER] Explorer: can "Deploy Latest" even if the build failed (was: [Upstream] Explorer: can "Deploy Latest" even if the build failed)
> [WATCHER] Explorer: can "Deploy Latest" even if the build failed
> ----------------------------------------------------------------
>
> Key: JBIDE-23402
> URL: https://issues.jboss.org/browse/JBIDE-23402
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, upstream
> Affects Versions: 4.4.2.AM2
> Reporter: Andre Dietisheim
> Fix For: 4.4.x
>
> Attachments: JBIDE-23402-a.png, JBIDE-23402-b.png
>
>
> When right-clicking on an application, we can select "Deploy Latest". This will start both a build and a deploy pod. The deploy pod will wait for the build pod to complete.
> In this case, due to github being unavailable, the build pod will fail very quickly. The deploy pod will then continue waiting up to 10 minutes even though what it is waiting for has already failed. This 10 minutes is wasted. It should fail quickly.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23402) Explorer: can "Deploy Latest" even if the build failed
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23402?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-23402:
--------------------------------
Description:
When right-clicking on an application, we can select "Deploy Latest". This will start both a build and a deploy pod. The deploy pod will wait for the build pod to complete.
In this case, due to github being unavailable, the build pod will fail very quickly. The deploy pod will then continue waiting up to 10 minutes even though what it is waiting for has already failed. This 10 minutes is wasted. It should fail quickly.
was:I can have a deploy pod is waiting for a build pod that already failed
> Explorer: can "Deploy Latest" even if the build failed
> ------------------------------------------------------
>
> Key: JBIDE-23402
> URL: https://issues.jboss.org/browse/JBIDE-23402
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, upstream
> Affects Versions: 4.4.2.AM2
> Reporter: Andre Dietisheim
> Attachments: JBIDE-23402-a.png, JBIDE-23402-b.png
>
>
> When right-clicking on an application, we can select "Deploy Latest". This will start both a build and a deploy pod. The deploy pod will wait for the build pod to complete.
> In this case, due to github being unavailable, the build pod will fail very quickly. The deploy pod will then continue waiting up to 10 minutes even though what it is waiting for has already failed. This 10 minutes is wasted. It should fail quickly.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months