[JBoss JIRA] (JBIDE-23463) Properties: Build pod has state of exit code 0 instead of correct status completed
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23463?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23463:
-------------------------------------
Fix Version/s: 4.4.2.Final
(was: 4.4.x)
> Properties: Build pod has state of exit code 0 instead of correct status completed
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-23463
> URL: https://issues.jboss.org/browse/JBIDE-23463
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.AM3
> Reporter: Marián Labuda
> Labels: openshift_v3
> Fix For: 4.4.2.Final
>
> Attachments: exit-code-0.png
>
>
> When I create a new OpenShift 3 application from a template, there is a running build. Once a build pod is completed, it has status "Completed". But now it Pods tabbed properties it contains status "Exit Code: 0" which is not user friendly and it broke integration tests.
> steps:
> # EXEC: create an application via a s2i template
> # EXEC: in OpenShift explorer: select the connection that you used to create the application and open up the "Properties view"
> # EXEC: in Properties: select "Pods" tab.
> # ASSERT: a build pod is appearing
> # EXEC: wait until the build pod is terminated and then look at its "Status" in the Properties > Pods
> Result:
> The status for the pod is reported with a "Exit Code: 0" (if successfully terminated, "Exit Code: 1" otherwise)
> !exit-code-0.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBDS-4157) Validation doesn't work - NoClassDefFoundError: jdk/nashorn/internal/runtime/ECMAException
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBDS-4157?page=com.atlassian.jira.plugin.... ]
Lukáš Valach closed JBDS-4157.
------------------------------
Resolution: Duplicate
Can't reproduce ECMAException with new/clean project.
Validation still don't works though ECMAException does not appear. Thus I have to admit this may be caused by JBDS-4133.
So closing as duplicity.
> Validation doesn't work - NoClassDefFoundError: jdk/nashorn/internal/runtime/ECMAException
> ------------------------------------------------------------------------------------------
>
> Key: JBDS-4157
> URL: https://issues.jboss.org/browse/JBDS-4157
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: rpm, webservices
> Affects Versions: 10.2.0.AM3
> Environment: RHEL7, 64bit
> Reporter: Lukáš Valach
> Assignee: Lukáš Valach
> Fix For: 10.2.0.GA
>
> Attachments: eclipse_log_ECMAException.txt, ECMAException_import_as_maven_project_20161107.png, jboss-as-kitchensink-html5-mobile.zip, nope.png, rh-eclipse46-devstudio10.2.log.20161107-1117.txt
>
>
> I notice that devstudio isn't able to validate rest service class. There is following error in the log.
> {code}
> !ENTRY org.eclipse.core.jobs 4 2 2016-11-03 11:52:21.836
> !MESSAGE An internal error occurred during: "Validating jboss-as-kitchensink-html5-mobile".
> !STACK 0
> java.lang.NoClassDefFoundError: jdk/nashorn/internal/runtime/ECMAException
> at org.eclipse.wst.jsdt.core.dom.ASTParser.internalCreateAST(ASTParser.java:903)
> at org.eclipse.wst.jsdt.core.dom.ASTParser.createAST(ASTParser.java:673)
> at org.eclipse.wst.jsdt.internal.core.validation.JavaScriptValidator.validate(JavaScriptValidator.java:62)
> at org.eclipse.wst.validation.Validator$V2.validate(Validator.java:1159)
> at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:704)
> at org.eclipse.wst.validation.internal.ValManager$1.visit(ValManager.java:665)
> at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:810)
> at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:669)
> at org.eclipse.wst.validation.internal.ValBuilderJob$Visitor.visit(ValBuilderJob.java:299)
> at org.eclipse.core.internal.resources.Resource$2.visit(Resource.java:120)
> at org.eclipse.core.internal.resources.Resource$1.visitElement(Resource.java:84)
> at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:82)
> at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:87)
> at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:87)
> at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:87)
> at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:87)
> at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:87)
> at org.eclipse.core.internal.watson.ElementTreeIterator.iterate(ElementTreeIterator.java:129)
> at org.eclipse.core.internal.resources.Resource.accept(Resource.java:94)
> at org.eclipse.core.internal.resources.Resource.accept(Resource.java:52)
> at org.eclipse.core.internal.resources.Resource.accept(Resource.java:117)
> at org.eclipse.core.internal.resources.Resource.accept(Resource.java:105)
> at org.eclipse.wst.validation.internal.ValBuilderJob.fullBuild(ValBuilderJob.java:219)
> at org.eclipse.wst.validation.internal.ValBuilderJob.run(ValBuilderJob.java:178)
> at org.eclipse.wst.validation.internal.ValBuilderJob.runInWorkspace(ValBuilderJob.java:126)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: java.lang.ClassNotFoundException: jdk.nashorn.internal.runtime.ECMAException cannot be found by org.eclipse.wst.jsdt.core_2.0.0.v201610121400
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:461)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:372)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:364)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 27 more
> {code}
> There are also errors like this
> {code}
> java.lang.NoClassDefFoundError: org/apache/lucene/analysis/standard/StandardAnalyzer
> {code}
> I know that lucene is known issue but what about ECMAException?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBDS-4169) Integrate OpenShift Server Adapter in Servers view
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBDS-4169?page=com.atlassian.jira.plugin.... ]
Andre Dietisheim updated JBDS-4169:
-----------------------------------
Labels: openshift_v3 server_adapter (was: )
> Integrate OpenShift Server Adapter in Servers view
> --------------------------------------------------
>
> Key: JBDS-4169
> URL: https://issues.jboss.org/browse/JBDS-4169
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 10.1.0.GA
> Reporter: Aurélien Pupier
> Assignee: Jeff MAURY
> Labels: openshift_v3, server_adapter
> Fix For: 10.2.0.AM3
>
>
> it is currently in a dedicated view.
> It is then hard to find for people used to JBDS and other servers.
> I personally wasn't able to find this specific view by myself, I was trying to add/remove application on the CDK server adapter.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBDS-4169) Integrate OpenShift Server Adapter in Servers view
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBDS-4169?page=com.atlassian.jira.plugin.... ]
Andre Dietisheim updated JBDS-4169:
-----------------------------------
Fix Version/s: 10.2.0.AM3
> Integrate OpenShift Server Adapter in Servers view
> --------------------------------------------------
>
> Key: JBDS-4169
> URL: https://issues.jboss.org/browse/JBDS-4169
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 10.1.0.GA
> Reporter: Aurélien Pupier
> Assignee: Jeff MAURY
> Labels: openshift_v3, server_adapter
> Fix For: 10.2.0.AM3
>
>
> it is currently in a dedicated view.
> It is then hard to find for people used to JBDS and other servers.
> I personally wasn't able to find this specific view by myself, I was trying to add/remove application on the CDK server adapter.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months