January 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23707) Explorer: Job that initially loads resources for connection displays "Load Project"

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23707?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-23707: ---------------------------------------- Assignee: Andre Dietisheim > Explorer: Job that initially loads resources for connection displays "Load Project" > ----------------------------------------------------------------------------------- > > Key: JBIDE-23707 > URL: https://issues.jboss.org/browse/JBIDE-23707 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.3.AM1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: explorer, openshift_v3 > Fix For: 4.4.3.AM2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23707) Explorer: Job that initially loads resources for connection displays "Load Project"

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23707?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23707: ------------------------------------- Affects Version/s: 4.4.3.AM1 (was: 4.4.2.AM1) > Explorer: Job that initially loads resources for connection displays "Load Project" > ----------------------------------------------------------------------------------- > > Key: JBIDE-23707 > URL: https://issues.jboss.org/browse/JBIDE-23707 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.3.AM1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: explorer, openshift_v3 > Fix For: 4.4.3.AM2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23707) Explorer: Job that initially loads resources for connection displays "Load Project"

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-23707: ---------------------------------------- Summary: Explorer: Job that initially loads resources for connection displays "Load Project" Key: JBIDE-23707 URL: https://issues.jboss.org/browse/JBIDE-23707 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.4.1.AM3 Reporter: Andre Dietisheim -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23622) Build Log: impossible to get logs once the build pod is completed

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23622?page=com.atlassian.jira.plugi... ] Jan Richter closed JBIDE-23622. ------------------------------- Verified in JBT 4.4.3.AM1 / devstudio 10.3.0.AM1 staged build. > Build Log: impossible to get logs once the build pod is completed > ----------------------------------------------------------------- > > Key: JBIDE-23622 > URL: https://issues.jboss.org/browse/JBIDE-23622 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.Final > Reporter: Marián Labuda > Assignee: Jeff MAURY > Labels: build_log, openshift_v3 > Fix For: 4.4.3.AM1 > > Attachments: cannot-build-log.png, log_build.png > > > When I am trying to get a log of completed build, either via context menu of a pod in tabbed property Pods or via context menu of a build in tabbed property Builds, I get following error dialog > !log_build.png! > There is no error in log. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23463) Properties: Build pod has state of exit code 0 instead of correct status completed

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23463?page=com.atlassian.jira.plugi... ] Jan Richter closed JBIDE-23463. ------------------------------- Verified in JBT 4.4.3.AM1 / devstudio 10.3.0.AM1 staged build. > 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 > Assignee: Andre Dietisheim > Labels: openshift_v3 > Fix For: 4.4.3.AM1 > > Attachments: build-pod-completed.png, 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20529) Master JIRA for XML Validation Problems

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20529?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20529: ------------------------------------- Fix Version/s: 4.4.3.AM2 (was: 4.4.3.AM1) > Master JIRA for XML Validation Problems > --------------------------------------- > > Key: JBIDE-20529 > URL: https://issues.jboss.org/browse/JBIDE-20529 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: project-examples, server > Reporter: Rob Stryker > Labels: xtriage > Fix For: 4.4.3.AM2 > > > This JIRA is meant to be a master container jira for all xml validation issues. These include identifying projects that are enganging in bad xml behavior, projects that point to namespaces or xsd locations that no longer exist, example projects using relative paths for linking to other xsd, and others. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20558) org.jboss.tools.common.validation.JBTValidationException at org.jboss.tools.common.validation.AsYouTypeValidatorManager.

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20558?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20558: ------------------------------------- Fix Version/s: 4.4.3.AM2 (was: 4.4.3.AM1) > org.jboss.tools.common.validation.JBTValidationException at org.jboss.tools.common.validation.AsYouTypeValidatorManager. > ------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20558 > URL: https://issues.jboss.org/browse/JBIDE-20558 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi, common > Affects Versions: 4.3.0.Beta2 > Reporter: The Alchemist > Assignee: Viacheslav Kabanovich > Priority: Minor > Fix For: 4.4.3.AM2 > > > {noformat} > org.jboss.tools.common.validation.JBTValidationException > at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:187) > at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validateJavaElement(AsYouTypeValidatorManager.java:222) > at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validateJavaElement(AsYouTypeValidatorManager.java:217) > at org.jboss.tools.common.validation.java.JavaDirtyRegionProcessor.endProcessing(JavaDirtyRegionProcessor.java:507) > at org.eclipse.wst.sse.ui.internal.reconcile.DirtyRegionProcessor$BackgroundThread.run(DirtyRegionProcessor.java:697) > Caused by: java.lang.NullPointerException > at org.jboss.tools.cdi.core.CDIUtil.collectAdditionalInterceptorBindingDeclaratios(CDIUtil.java:1114) > at org.jboss.tools.cdi.core.CDIUtil.collectAdditionalInterceptorBindingDeclaratios(CDIUtil.java:1118) > at org.jboss.tools.cdi.core.CDIUtil.getAllInterceptorBindingDeclaratios(CDIUtil.java:1110) > at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.hasConflictedInterceptorBindings(CDICoreValidator.java:984) > at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateInterceptorBindings(CDICoreValidator.java:970) > at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateClassBean(CDICoreValidator.java:952) > at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateBean(CDICoreValidator.java:792) > at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateResource(CDICoreValidator.java:641) > at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validate(CDICoreValidator.java:574) > at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:183) > ... 4 more > {noformat} > I wish I could see which class is causing this error... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4170) Remove windows uninstaller from mac distribution

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-4170?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-4170. ----------------------------- > Remove windows uninstaller from mac distribution > ------------------------------------------------ > > Key: JBDS-4170 > URL: https://issues.jboss.org/browse/JBDS-4170 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: platform-installer > Affects Versions: 10.2.0.AM3 > Environment: mac osx > Reporter: Jan Richter > Assignee: Sudhir Verma > Fix For: 10.3.0.AM1 > > > The uninstaller/uninstall.ps1 is getting generated by the mac installer. Remove it or replace with something that runs on mac (like a shell script). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4204) Red Hat JBoss Developer Studio and dialogs do not size correctly under Fedora 25 w/ Wayland

by Supriya Bharadwaj (JIRA)

[ https://issues.jboss.org/browse/JBDS-4204?page=com.atlassian.jira.plugin.... ] Supriya Bharadwaj commented on JBDS-4204: ----------------------------------------- (FYI) Updated 10.2 RNs with the KI added is published on access.redhat.com (https://access.redhat.com/documentation/en/red-hat-jboss-developer-studio...). > Red Hat JBoss Developer Studio and dialogs do not size correctly under Fedora 25 w/ Wayland > ------------------------------------------------------------------------------------------- > > Key: JBDS-4204 > URL: https://issues.jboss.org/browse/JBDS-4204 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: upstream > Affects Versions: 10.1.0.GA > Environment: FC25, wayland > Reporter: cube 00 > Assignee: Supriya Bharadwaj > Labels: upstream > Fix For: 10.3.0.AM1 > > Attachments: jboss1.png, jboss2.png, jboss3.PnG, jbosstools-diagnostics-20161129110614.zip > > > The window either cuts the top off, bottom off or overdraws into space near the window. Dialogs have their OK/Cancel buttons hidden and resizing does not make them appear either. > Appears to be related to Wayland as I [disabled it|https://fedoraproject.org/wiki/Changes/WaylandByDefault] and things are back to normal. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ERT-214) Validate JSON file with JSON Schema [EBZ#494111]

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/ERT-214?page=com.atlassian.jira.plugin.sy... ] Victor Rubezhny resolved ERT-214. --------------------------------- Resolution: Done > Validate JSON file with JSON Schema [EBZ#494111] > ------------------------------------------------ > > Key: ERT-214 > URL: https://issues.jboss.org/browse/ERT-214 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Friendly Jira Robot > Assignee: Victor Rubezhny > Priority: Trivial > Labels: bzira, wst.json > Fix For: Neon.2 (4.6) > > > It's a very big task, but it should be fantastic if WTP Validator could validate JSON file by using JSON Schema. > To do that: > * JSONSchemaDocument should support the full specification of JSON Schema. > * minimal-json should be improved to collect line, column or perhaps we could use IJSONDocument to validate it with JSON Schema. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues January 2017