October 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-12923) OpenShift Explorer throws NPE on user with saved password

by Stefan Bunciak (JIRA)

Stefan Bunciak created JBIDE-12923: -------------------------------------- Summary: OpenShift Explorer throws NPE on user with saved password Key: JBIDE-12923 URL: https://issues.jboss.org/browse/JBIDE-12923 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.0.0.Beta1 Reporter: Stefan Bunciak Assignee: Andre Dietisheim Priority: Blocker Fix For: 4.0.0.Beta1 Attachments: null.png User name in object model gets probably null value. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

3
12
0 / 0

[JBoss JIRA] (JBIDE-12808) JAX-RS builder and validator called twice when a changed file is saved

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-12808: ------------------------------------- Summary: JAX-RS builder and validator called twice when a changed file is saved Key: JBIDE-12808 URL: https://issues.jboss.org/browse/JBIDE-12808 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 4.0.0.Alpha2 Reporter: Xavier Coulon Assignee: Xavier Coulon Fix For: 4.0.0.Beta1 When saving a JAX-RS resource after some changes, the JAX-RS metamodebuilder is called, followed byt the JAX-RS validator which validates the changed file, THEN, the JAX-RS builder is called again, as well as the JAX-RS validator -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
6
0 / 0

[JBoss JIRA] (JBIDE-12877) CLONE - CLONE - CLONE - CLONE - WS Component N&N

by Denis Golovin (JIRA)

Denis Golovin created JBIDE-12877: ------------------------------------- Summary: CLONE - CLONE - CLONE - CLONE - WS Component N&N Key: JBIDE-12877 URL: https://issues.jboss.org/browse/JBIDE-12877 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: Webservices Reporter: Denis Golovin Assignee: Brian Fitzpatrick Fix For: 4.0.0.Alpha2 https://jira.jboss.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=pro... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
2
0 / 0

[JBoss JIRA] (JBIDE-12903) Report the context menu issue to BagZilla: Missing QuickFix context menu within Source pane of VPE for JSF project

by Victor Rubezhny (JIRA)

Victor Rubezhny created JBIDE-12903: --------------------------------------- Summary: Report the context menu issue to BagZilla: Missing QuickFix context menu within Source pane of VPE for JSF project Key: JBIDE-12903 URL: https://issues.jboss.org/browse/JBIDE-12903 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing, UpStream Affects Versions: 4.0.0.Alpha1 Reporter: Victor Rubezhny Assignee: Victor Rubezhny Fix For: 4.0.x The issue jbide-12783 is fixed by a workaround patch that adds the Menu Listener to the Context Menu Manager that cleans the menu items before the final call to MenuManager.update(boolean, boolean) is to be done prior the menu is to be shown. This looks like the reason of the issue is a bug in Eclipse Platform UI. So, we need to report the issue yo BagZilla as well as to send an example to reproduce the issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
5
0 / 0

[JBoss JIRA] (JBIDE-12703) Adding the runtime detection path manually

by Lucia Jelinkova (JIRA)

Lucia Jelinkova created JBIDE-12703: --------------------------------------- Summary: Adding the runtime detection path manually Key: JBIDE-12703 URL: https://issues.jboss.org/browse/JBIDE-12703 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: runtime detection Affects Versions: 4.0.0.Alpha2 Reporter: Lucia Jelinkova Assignee: Snjezana Peco Fix For: 4.0.0.Beta1 While writing my bot tests I need to add a runtime detection path manually (because there's a native window that cannot be operated by bot). There are some issues that I've come across. I am not sure if those are really issues or are intended so I am describing them here: I add the path through the following code while the preferences dialog is open: {code} RuntimeUIActivator.getDefault().getModel().addRuntimePath(new RuntimePath(path)); {code} However, the path is not added to the table, maybe because the table viewer is not refreshed: {code} runtimePathChangeListener = new IRuntimePathChangeListener() { public void changed() { Display.getDefault().asyncExec(new Runnable() { public void run() { if (runtimePathChangeListener != null) { viewer.setInput(RuntimeUIActivator.getRuntimePaths()); } } }); } }; RuntimeUIActivator.getDefault().getModel().addRuntimePathChangeListener(runtimePathChangeListener); {code} There used to be a workaround for this - to close the preferences and open it again. However, when I click the OK button, all runtime paths are taken from the table (not from the model) and stored to the preferences store - since the table has not been refreshed the table is empty and an empty list is stored. {code} @Override public boolean performOk() { RuntimeUIActivator.getDefault().getModel().setRuntimePaths(runtimePaths); RuntimeUIActivator.getDefault().saveRuntimePreferences(); return super.performOk(); } {code} This is even different behavior to the performApply method (I think those methods should have the same result). In this method the paths from model are stored to the preferences store. {code} @Override protected void performApply() { RuntimeUIActivator.getDefault().saveRuntimePreferences(); } {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

3
6
0 / 0

[JBoss JIRA] (JBIDE-12943) Remove all swtbot tests from the original repos

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12943?page=com.atlassian.jira.plugi... ] Martin Malina edited comment on JBIDE-12943 at 10/26/12 5:59 AM: ----------------------------------------------------------------- This is a list of all the tests that we now have in our repo: org.jboss.ide.eclipse.as.ui.bot.test org.jboss.tools.archives.ui.bot.test - https://github.com/jbosstools/jbosstools-server/pull/1 org.jboss.tools.bpel.ui.bot.test - https://github.com/jbosstools/jbosstools-bpel/pull/2 org.jboss.tools.cdi.bot.test org.jboss.tools.cdi.seam3.bot.test org.jboss.tools.jsf.ui.bot.test org.jboss.tools.seam.ui.bot.test org.jboss.tools.struts.ui.bot.test - https://github.com/jbosstools/jbosstools-javaee/pull/2 org.jboss.tools.central.test.ui.bot org.jboss.tools.maven.ui.bot.test - https://github.com/jbosstools/jbosstools-central/pull/2 org.jboss.tools.dummy.ui.bot.test org.jboss.tools.runtime.as.ui.bot.test org.jboss.tools.ui.bot.ext org.jboss.tools.ui.bot.ext.test - https://github.com/jbosstools/jbosstools-base/pull/1 org.jboss.tools.esb.ui.bot.test - https://github.com/jbosstools/jbosstools-esb/pull/2 org.jboss.tools.forge.ui.bot.test - https://github.com/jbosstools/jbosstools-forge/pull/1 org.jboss.tools.freemarker.ui.bot.test - https://github.com/jbosstools/jbosstools-freemarker/pull/1 org.jboss.tools.hibernate.ui.bot.test - https://github.com/jbosstools/jbosstools-hibernate/pull/1 org.jboss.tools.jbpm.ui.bot.test - https://github.com/jbosstools/jbosstools-jbpm/pull/2 org.jboss.tools.jst.ui.bot.test - https://github.com/jbosstools/jbosstools-jst/pull/2 org.jboss.tools.jst.ui.firstrun.bot.test - left in place - we never used it org.jboss.tools.modeshape.rest.ui.bot.test org.teiid.designer.ui.bot.test - no place to remove from - was added separately org.jboss.tools.mylyn.ui.bot.test - no place to remove from - was added separately org.jboss.tools.openshift.ui.bot.test - https://github.com/jbosstools/jbosstools-openshift/pull/2 org.jboss.tools.portlet.ui.bot.test - https://github.com/jbosstools/jbosstools-portlet/pull/2 org.jboss.tools.vpe.ui.bot.test - https://github.com/jbosstools/jbosstools-vpe/pull/1 org.jboss.tools.ws.ui.bot.test - https://github.com/jbosstools/jbosstools-webservices/pull/4 - https://github.com/jbosstools/jbosstools-webservices/pull/5 I hope I didn't miss anything. If I am correct, org.jboss.tools.jst.ui.firstrun.bot.test will stay in place. That means I will remove it from jbosstools-integration-tests repo. was (Author: mmalina): This is a list of all the tests that we now have in our repo: org.jboss.ide.eclipse.as.ui.bot.test org.jboss.tools.archives.ui.bot.test - https://github.com/jbosstools/jbosstools-server/pull/1 org.jboss.tools.bpel.ui.bot.test - https://github.com/jbosstools/jbosstools-bpel/pull/2 org.jboss.tools.cdi.bot.test org.jboss.tools.cdi.seam3.bot.test org.jboss.tools.jsf.ui.bot.test org.jboss.tools.seam.ui.bot.test org.jboss.tools.struts.ui.bot.test - https://github.com/jbosstools/jbosstools-javaee/pull/2 org.jboss.tools.central.test.ui.bot org.jboss.tools.maven.ui.bot.test - https://github.com/jbosstools/jbosstools-central/pull/2 org.jboss.tools.dummy.ui.bot.test org.jboss.tools.runtime.as.ui.bot.test org.jboss.tools.ui.bot.ext org.jboss.tools.ui.bot.ext.test - https://github.com/jbosstools/jbosstools-base/pull/1 org.jboss.tools.esb.ui.bot.test - https://github.com/jbosstools/jbosstools-esb/pull/2 org.jboss.tools.forge.ui.bot.test - https://github.com/jbosstools/jbosstools-forge/pull/1 org.jboss.tools.freemarker.ui.bot.test - https://github.com/jbosstools/jbosstools-freemarker/pull/1 org.jboss.tools.hibernate.ui.bot.test - https://github.com/jbosstools/jbosstools-hibernate/pull/1 org.jboss.tools.jbpm.ui.bot.test - https://github.com/jbosstools/jbosstools-jbpm/pull/2 org.jboss.tools.jst.ui.bot.test - https://github.com/jbosstools/jbosstools-jst/pull/2 org.jboss.tools.jst.ui.firstrun.bot.test - left in place - we never used it org.jboss.tools.modeshape.rest.ui.bot.test org.teiid.designer.ui.bot.test - no place to remove from - was added separately org.jboss.tools.mylyn.ui.bot.test - no place to remove from - was added separately org.jboss.tools.openshift.ui.bot.test - https://github.com/jbosstools/jbosstools-openshift/pull/2 org.jboss.tools.portlet.ui.bot.test - https://github.com/jbosstools/jbosstools-portlet/pull/2 org.jboss.tools.vpe.ui.bot.test - https://github.com/jbosstools/jbosstools-vpe/pull/1 org.jboss.tools.ws.ui.bot.test - https://github.com/jbosstools/jbosstools-webservices/pull/4 I hope I didn't miss anything. If I am correct, org.jboss.tools.jst.ui.firstrun.bot.test will stay in place. That means I will remove it from jbosstools-integration-tests repo. > Remove all swtbot tests from the original repos > ----------------------------------------------- > > Key: JBIDE-12943 > URL: https://issues.jboss.org/browse/JBIDE-12943 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: Build/Releng > Reporter: Martin Malina > Assignee: Martin Malina > > After the migration to git we now have our (QE) repo: > https://github.com/jbosstools/jbosstools-integration-tests > I need to submit pull requests to remove all the tests from the original places, e.g. https://github.com/jbosstools/jbosstools-server/tree/master/as/tests/org.... > Also, the removed tests need to be removed from <modules> in their parent pom. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12943) Remove all swtbot tests from the original repos

by Martin Malina (JIRA)

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12943) Remove all swtbot tests from the original repos

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12943?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-12943: --------------------------------------- I submitted https://github.com/jbosstools/jbosstools-integration-tests/pull/5 for the removal of org.jboss.tools.jst.ui.firstrun.bot.test from the tests repo. > Remove all swtbot tests from the original repos > ----------------------------------------------- > > Key: JBIDE-12943 > URL: https://issues.jboss.org/browse/JBIDE-12943 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: Build/Releng > Reporter: Martin Malina > Assignee: Martin Malina > > After the migration to git we now have our (QE) repo: > https://github.com/jbosstools/jbosstools-integration-tests > I need to submit pull requests to remove all the tests from the original places, e.g. https://github.com/jbosstools/jbosstools-server/tree/master/as/tests/org.... > Also, the removed tests need to be removed from <modules> in their parent pom. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12572) Add server url to conntect-dialog

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-12572: ---------------------------------------- Summary: Add server url to conntect-dialog Key: JBIDE-12572 URL: https://issues.jboss.org/browse/JBIDE-12572 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: openshift Affects Versions: 3.3.0.Final Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 4.0.0.Alpha1 Since there are now different servers available to connect to (liveCD, local install via rpm, PROD, INT, STG etc.), we have to allow the user to define what server he wants to connect to. We'll add a text-field to the connect dialog that is prefilled with the default server. The user may change the url and provide its very own server. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

4
21
0 / 0

[JBoss JIRA] (JBIDE-12876) CLONE - CLONE - CLONE - Visual Editor Component N&N

by Denis Golovin (JIRA)

Denis Golovin created JBIDE-12876: ------------------------------------- Summary: CLONE - CLONE - CLONE - Visual Editor Component N&N Key: JBIDE-12876 URL: https://issues.jboss.org/browse/JBIDE-12876 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: Visual Page Editor core, Visual Page Editor Templates Reporter: Denis Golovin Assignee: Denis Maliarevich Fix For: 4.0.0.Alpha2 [VPE's new_and_noteworthy|https://issues.jboss.org/secure/IssueNavigator.jspa?re...] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

3
5
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 October 2012