September 2012 - jbosstools-issues

[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-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-11806) Offline Suppert for central - fine tuning

by Radim Hopp (JIRA)

Radim Hopp created JBIDE-11806: ---------------------------------- Summary: Offline Suppert for central - fine tuning Key: JBIDE-11806 URL: https://issues.jboss.org/browse/JBIDE-11806 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: central Affects Versions: 3.3.0.Beta3 Reporter: Radim Hopp Assignee: Snjezana Peco Priority: Minor Fix For: 3.3.0.CR1 Offline support [JBIDE-11192|https://issues.jboss.org/browse/JBIDE-11192] works fine except for two things I noticed: * When trying to create example/quickstart which is not cached (so it won't create), there is still offered readme.md to be opened (which of course doesn't exist) -> errors in Error Log * Would it be possible to put some better text than "java.net.UnknownHostException <hostname>" in tooltip (see screenshot)? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

4
15
0 / 0

[JBoss JIRA] Created: (JBDS-994) Enable ejbql code completion in Seam components.xml (framework:entity-query)

by Joao Paulo Viragine (JIRA)

Enable ejbql code completion in Seam components.xml (framework:entity-query) ---------------------------------------------------------------------------- Key: JBDS-994 URL: https://jira.jboss.org/jira/browse/JBDS-994 Project: JBoss Developer Studio Issue Type: Feature Request Components: seam Reporter: Joao Paulo Viragine Enable ejbql code completion in Seam components.xml as we have in @NamedQuery (http://docs.jboss.org/tools/movies/demos/java_hql_editing_and_validation/...) Eg: <framework:entity-query name="empresas" ejbql="" /> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

3
5
0 / 0

[JBoss JIRA] (JBIDE-12570) what connectorID should we use in Central for m2e-wtp installation via examples?

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-12570: ---------------------------------- Summary: what connectorID should we use in Central for m2e-wtp installation via examples? Key: JBIDE-12570 URL: https://issues.jboss.org/browse/JBIDE-12570 Project: Tools (JBoss Tools) Issue Type: Bug Components: central, maven Affects Versions: 4.0.0.Alpha1 Reporter: Nick Boldt Assignee: Fred Bricon Fix For: 4.0.0.Alpha2 [~fbricon] recently updated central/plugins/org.jboss.tools.central.discovery/plugin.xml to read as follows (in Alpha1 branch): {code} <connectorDescriptor categoryId="org.jboss.tools.central.discovery.maven" groupId="org.jboss.tools.central.discovery.maven.upstream" description="Maven Integration for Web Tools (m2e-wtp)" id="org.maven.ide.eclipse.wtp.feature" kind="task" license="Free, EPL" name="Maven Integration for Web Tools (m2e-wtp)" provider="eclipse.org" siteUrl="http://download.jboss.org/jbosstools/updates/development/juno/central/core/"> <iu id="org.eclipse.m2e.wtp.feature"/> <icon image32="images/m2e_32.gif"> </icon> <overview url="http://www.eclipse.org/m2e-wtp/"> </overview> </connectorDescriptor> {code} However, that means that the m2e-wtp connector includes the new IU, org.eclipse.m2e.wtp.feature, but is still called by its old name, id="org.maven.ide.eclipse.wtp.feature". Should this be changed here and in JBDS Central, too? Can all the examples that might need to install m2e-wtp be updated such that they refer to the new, correct IU name? -- 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
5
0 / 0

[JBoss JIRA] (JBIDE-12598) Central does not open when the Welcome page is active

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-12598: -------------------------------------- Summary: Central does not open when the Welcome page is active Key: JBIDE-12598 URL: https://issues.jboss.org/browse/JBIDE-12598 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 4.0.0.Alpha2 Reporter: Mickael Istria When opening JBoss Central (via menu or toolbar) while Welcome page is active, nothing happens. When opening any other new file or new editor, the editor pops-up on top of the Welcome page. -- 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
4
0 / 0

[JBoss JIRA] (JBIDE-11490) Test Seam tooling with Seam 2.3.Beta

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-11490: ------------------------------------------- Summary: Test Seam tooling with Seam 2.3.Beta Key: JBIDE-11490 URL: https://issues.jboss.org/browse/JBIDE-11490 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam 2 Reporter: Max Rydahl Andersen Assignee: Alexey Kazakov Fix For: 3.3.0.Beta3 Seam 2.3 Beta is out - lets do a quick check to see if we see any issues. Target is AS7/EAP6 Check datasource generation, CRUD generated pages continues to work. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

7
62
0 / 0

[JBoss JIRA] (JBIDE-12748) Add Seam 2.3.0.Final to the downloadable runtimes

by Martin Malina (JIRA)

Martin Malina created JBIDE-12748: ------------------------------------- Summary: Add Seam 2.3.0.Final to the downloadable runtimes Key: JBIDE-12748 URL: https://issues.jboss.org/browse/JBIDE-12748 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: runtime detection Affects Versions: 4.0.0.Alpha2 Reporter: Martin Malina Assignee: Snjezana Peco Fix For: 4.0.0.Beta1 Seam 2.3.0.Final was released a few days ago, see http://www.seamframework.org/Seam2/Downloads We need to add it to the list of downloadable runtimes when you go to Preferences -> JBoss Tools -> JBoss Tools Runtime Detection and click the Download button. I don't know where the runtimes are defined. So please reassign if needed. -- 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
4
0 / 0

[JBoss JIRA] Created: (JBIDE-6018) Improve BPEL refactoring

by Robert (Bob) Brodt (JIRA)

Improve BPEL refactoring ------------------------ Key: JBIDE-6018 URL: https://jira.jboss.org/jira/browse/JBIDE-6018 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: bpm Reporter: Robert (Bob) Brodt Often times I find myself changing the names of variables, port types, partner links, etc. either in the Property sheet or directly on the editor canvas without thinking; what I really wanted to do was refactor the name change and have it propagate through to the WSDL or XSD where the element is defined. It would be simple enough to provide a change listener that prompts you with "Hey, I noticed you changed the name of this <thing> - did you intend to refactor instead?" possibly with a "Don't ask me again!" checkbox. The same functionality should be provided for the WSDL and XSD editor. This would go a long way to better integration within the tooling. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

4
16
0 / 0

[JBoss JIRA] (JBIDE-11855) Mylyn: Cannot connect to https://issues.jboss.org

by Lucia Jelinkova (JIRA)

Lucia Jelinkova created JBIDE-11855: --------------------------------------- Summary: Mylyn: Cannot connect to https://issues.jboss.org Key: JBIDE-11855 URL: https://issues.jboss.org/browse/JBIDE-11855 Project: Tools (JBoss Tools) Issue Type: Bug Components: common/jst/core Affects Versions: 3.3.0.Beta3 Reporter: Lucia Jelinkova Assignee: Alexey Kazakov Fix For: 3.3.0.Beta3 I installed JBT 3.3.0 Beta 3a and Atlassian JIRA connector. When I try to fill in the username and password and validate them In JBoss community task repository (provided by JBT) I get the following error: JIRA RPC services are not enabled. Please contact your JIRA administrator. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

4
10
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 September 2012