June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22436) Intermittent NullPointerException upon opening helloworld, kitchensink cheat sheets in JBDS

by Nikoleta Žiaková (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22436?page=com.atlassian.jira.plugi... ] Nikoleta Žiaková commented on JBIDE-22436: ------------------------------------------ I was able to reproduce this problem on Fedora 20 with GNOME. I got exactly the same stack trace as [~mjurc] attached. It happens with fresh install of quickstarts (unzip EAP 7.0.0.GA QS zip). Trying afterwards with the same QS install succeeds without error. > Intermittent NullPointerException upon opening helloworld, kitchensink cheat sheets in JBDS > ------------------------------------------------------------------------------------------- > > Key: JBIDE-22436 > URL: https://issues.jboss.org/browse/JBIDE-22436 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples, upstream > Affects Versions: 4.3.1.Final > Reporter: Michal Jurc > Assignee: Snjezana Peco > Fix For: 4.4.x > > Attachments: helloworld-cheatsheet.xml, JBIDE-22436-9.1-helloworld.log, kitchensink-cheatsheet.xml, org.jboss.tools.cheatsheet.test.zip > > > After finishing the import of {{helloworld}} and {{kitchensink}} quickstarts, the user is prompted whether the cheat sheet for the project should be opened. Upon opening it, JBDS 9.0 and 9.1 produces the following error message: > {quote}An error has occurred. See error log for more details. > java.lang.NullPointerException{quote} > The detailed error log produces the same message. > The quickstarts and their cheat sheets work even after the prompt with NullPointerException message. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22509) Red Hat Central: Update default project example icon to the Red Hat Developer icon

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22509?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-22509. ------------------------------ Verified in JBDS 10.0.0.GA-v20160603-0010-B5505. Closing. > Red Hat Central: Update default project example icon to the Red Hat Developer icon > ---------------------------------------------------------------------------------- > > Key: JBIDE-22509 > URL: https://issues.jboss.org/browse/JBIDE-22509 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central > Affects Versions: 4.4.0.Alpha2 > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.4.0.Final > > Attachments: icon-default.png > > > Default JBoss Dev icon doesn't look good in > !http://content.screencast.com/users/fbricon/folders/Jing/media/4da3bbc7-85b4-4c41-b6ff-5f9d1688bbde/00000433.png|width=900! > We should use the sexier Red Hat Developper icon instead: !icon-default.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3852) Mock installer model to allow running installer fast without installing anything

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3852?page=com.atlassian.jira.plugin.... ] Jan Richter updated JBDS-3852: ------------------------------ Fix Version/s: LATER (was: 10.0.0.GA) > Mock installer model to allow running installer fast without installing anything > -------------------------------------------------------------------------------- > > Key: JBDS-3852 > URL: https://issues.jboss.org/browse/JBDS-3852 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Task > Components: platform-installer > Affects Versions: 10.0.0.Alpha1 > Reporter: Denis Golovin > Assignee: Jan Richter > Labels: Havoc > Fix For: LATER > > > Would be good for demonstrations and UI development -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22473) Environment Var Wizard: Cannot remove env vars

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22473?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-22473: ----------------------------------------------- [~adietish], please take a look at the pull request for UI https://github.com/jbosstools/jbosstools-openshift/pull/1211 Any environment var can be deleted or renamed. The result of rename is shown as the sum of the deleted original var and added new var. A deleted original var is shown in the table in italic with text decoration '[deleted]'. User can restore it in one of the following ways: 1) select and push Restore, 2) select and push Edit, set value and finish, 3) Push Add, enter the same key (it is not prohibited since the var is marked deleted) and finish, 4) Rename another var to its name. All these operations are consistent and show user which original vars are deleted/modified and which new are added. The option to delete/rename original vars is implemented only for 'Manage Environment Variables' wizard. Other wizards are not affected. > Environment Var Wizard: Cannot remove env vars > ---------------------------------------------- > > Key: JBIDE-22473 > URL: https://issues.jboss.org/browse/JBIDE-22473 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Viacheslav Kabanovich > Labels: env_var_wizard, openshift_v3 > Fix For: 4.4.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22473) Environment Var Wizard: Cannot remove env vars

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22473?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich updated JBIDE-22473: ------------------------------------------ Git Pull Request: https://github.com/openshift/openshift-restclient-java/pull/169, https://github.com/jbosstools/jbosstools-openshift/pull/1211 (was: https://github.com/openshift/openshift-restclient-java/pull/169) > Environment Var Wizard: Cannot remove env vars > ---------------------------------------------- > > Key: JBIDE-22473 > URL: https://issues.jboss.org/browse/JBIDE-22473 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Viacheslav Kabanovich > Labels: env_var_wizard, openshift_v3 > Fix For: 4.4.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22477) For JBIDE 4.4.0.Final: Prepare for Final/GA

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22477?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22477: ------------------------------------ Reopened webservices and livereload because wrong parent pom reference in master branch. > For JBIDE 4.4.0.Final: Prepare for Final/GA > ------------------------------------------- > > Key: JBIDE-22477 > URL: https://issues.jboss.org/browse/JBIDE-22477 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.4.0.Final > > > For JBIDE 4.4.0.Final: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.0.Final or 10.0.0.GA > [Unresolved JIRAs with fixVersion = 4.4.0.Final, 10.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...] > 1. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.0.Final-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.0.Final-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.0.Final-SNAPSHOT{color}* in your *{color:orange}jbosstools-4.4.x{color}* branch > 2. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.x{color}* branch; > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.4.x > git push origin jbosstools-4.4.x > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.0.Final-SNAPSHOT{color}* in your *{color:blue}master{color}* branch (we'll move to 4.5.0.Alpha1 later!) > * *{color:blue}4.4.0.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.x{color}* branch > 3. Ensure you've *built your code* using the latest target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0) > {code} > mvn clean verify -Dtpc.version=4.60.0.Final-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > 5. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] > See also: JBDS-3920 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22507) Debugging: cannot debug kitchensink, no breakpoint is being hit

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22507?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22507: ----------------------------------- Priority: Major (was: Blocker) > Debugging: cannot debug kitchensink, no breakpoint is being hit > --------------------------------------------------------------- > > Key: JBIDE-22507 > URL: https://issues.jboss.org/browse/JBIDE-22507 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, server > Affects Versions: 4.4.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Labels: debug, openshift_v3 > Fix For: 4.4.1.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22477) For JBIDE 4.4.0.Final: Prepare for Final/GA

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22477?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-22477. ---------------------------------- Resolution: Done > For JBIDE 4.4.0.Final: Prepare for Final/GA > ------------------------------------------- > > Key: JBIDE-22477 > URL: https://issues.jboss.org/browse/JBIDE-22477 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.4.0.Final > > > For JBIDE 4.4.0.Final: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.0.Final or 10.0.0.GA > [Unresolved JIRAs with fixVersion = 4.4.0.Final, 10.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...] > 1. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.0.Final-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.0.Final-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.0.Final-SNAPSHOT{color}* in your *{color:orange}jbosstools-4.4.x{color}* branch > 2. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.x{color}* branch; > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.4.x > git push origin jbosstools-4.4.x > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.0.Final-SNAPSHOT{color}* in your *{color:blue}master{color}* branch (we'll move to 4.5.0.Alpha1 later!) > * *{color:blue}4.4.0.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.x{color}* branch > 3. Ensure you've *built your code* using the latest target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0) > {code} > mvn clean verify -Dtpc.version=4.60.0.Final-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > 5. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] > See also: JBDS-3920 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18951) jboss-web_8_0.xsd in AS XML catalog reported as "containing errors" by Luna

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18951?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-18951: ------------------------------------- [~mmalina] did you correct the URL? I believe the errors you're showing there are due to the schema not being found, because you're using a schemaLocation that does not exist. > jboss-web_8_0.xsd in AS XML catalog reported as "containing errors" by Luna > --------------------------------------------------------------------------- > > Key: JBIDE-18951 > URL: https://issues.jboss.org/browse/JBIDE-18951 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, upstream > Affects Versions: 4.2.0.Final > Environment: W7 Pro SP1 > eclipse.buildId=4.4.1.M20140925-0400 > org.jboss.tools.as.catalog (3.0.0.Final-v20141016-1911-B95) "JBoss AS XML Catalog Entries" > Reporter: Jordan Glassman > Assignee: Rob Stryker > Fix For: 4.4.1.Alpha1 > > Attachments: Capture4.PNG, xsd-details.png > > > In a jboss-web.xml file, a namespace declaration like: > {code} <jboss-web xmlns="http://www.jboss.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-web_8_0.xsd" version="8.0" > >{code} > Gives eclipse error: > {quote}Referenced file contains errors (jar:file:/C:/eclipse/plugins/org.jboss.tools.as.catalog_3.0.0.Final-v20141016-1911-B95.jar!/schema/xsd/jboss-web_8_0.xsd). > For more information, right click on the message in the Problems View and select "Show Details..."{quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18951) jboss-web_8_0.xsd in AS XML catalog reported as "containing errors" by Luna

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18951?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-18951: -------------------------------- Fix Version/s: 4.4.1.Alpha1 > jboss-web_8_0.xsd in AS XML catalog reported as "containing errors" by Luna > --------------------------------------------------------------------------- > > Key: JBIDE-18951 > URL: https://issues.jboss.org/browse/JBIDE-18951 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, upstream > Affects Versions: 4.2.0.Final > Environment: W7 Pro SP1 > eclipse.buildId=4.4.1.M20140925-0400 > org.jboss.tools.as.catalog (3.0.0.Final-v20141016-1911-B95) "JBoss AS XML Catalog Entries" > Reporter: Jordan Glassman > Assignee: Rob Stryker > Fix For: 4.4.1.Alpha1 > > Attachments: Capture4.PNG, xsd-details.png > > > In a jboss-web.xml file, a namespace declaration like: > {code} <jboss-web xmlns="http://www.jboss.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-web_8_0.xsd" version="8.0" > >{code} > Gives eclipse error: > {quote}Referenced file contains errors (jar:file:/C:/eclipse/plugins/org.jboss.tools.as.catalog_3.0.0.Final-v20141016-1911-B95.jar!/schema/xsd/jboss-web_8_0.xsd). > For more information, right click on the message in the Problems View and select "Show Details..."{quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 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 June 2016