August 2010 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-6652) Implement ModeShape capability/activity to enable/disable ModeShape functionality

by Brian Fitzpatrick (JIRA)

Implement ModeShape capability/activity to enable/disable ModeShape functionality --------------------------------------------------------------------------------- Key: JBIDE-6652 URL: https://jira.jboss.org/browse/JBIDE-6652 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: modeshape Affects Versions: 3.2.0.M1 Reporter: Brian Fitzpatrick Assignee: Dan Florian Fix For: 3.2.x As we discussed on the phone, the use of Capabilities/Activities in Eclipse might be a good way to handle the "Always On" aspect of the ModeShape menus in JBoss Tools. For some reason, this functionality is labeled as "Capabilities" in Eclipse Preferences, but the actual extension point is "org.eclipse.ui.activities" and called Activities in the API documentation. Go figure. That said, it's very simple to implement. I'll attach a patch with the suggested tweaks to plugin.xml and plugin.properties. But this should address Max's issues with the ModeShape menus appearing on all folders and files and be easy to add to the documentation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

3
10
0 / 0

[JBoss JIRA] Created: (JBIDE-6654) Rename ModeShape Servers view to avoid further confusion with overloaded term "server"

by Brian Fitzpatrick (JIRA)

Rename ModeShape Servers view to avoid further confusion with overloaded term "server" -------------------------------------------------------------------------------------- Key: JBIDE-6654 URL: https://jira.jboss.org/browse/JBIDE-6654 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: modeshape Affects Versions: 3.2.0.M1 Reporter: Brian Fitzpatrick Assignee: Dan Florian Fix For: 3.2.x The ModeShape Servers view provides one more overloaded use of the word "Server". Perhaps do what was done for the Teiid Designer's server view and simply call it "ModeShape"? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-6628) [Designer] Provide Teiid driver in a plug-in wrapper to save the user the step of creating a DTP Driver Definition

by Brian Fitzpatrick (JIRA)

[Designer] Provide Teiid driver in a plug-in wrapper to save the user the step of creating a DTP Driver Definition ------------------------------------------------------------------------------------------------------------------ Key: JBIDE-6628 URL: https://jira.jboss.org/browse/JBIDE-6628 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: teiid Affects Versions: 3.2.0.M1 Reporter: Brian Fitzpatrick Assignee: Barry LaFond Fix For: 3.2.x For the Teiid driver... Is it possible to wrap the driver jar in a plug-in and automatically set it up? Or set up multiple versions (7.0, 7.1, etc.)? Though it's server-dependent, we should be able to control that enough to simplify life for the user and auto-configure a driver instance. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-5134) Quick fix for "Seam Runtime ${name} does not exist" error marker

by Denis Golovin (JIRA)

Quick fix for "Seam Runtime ${name} does not exist" error marker ---------------------------------------------------------------- Key: JBIDE-5134 URL: https://jira.jboss.org/jira/browse/JBIDE-5134 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Seam Affects Versions: 3.1.0.CR1 Reporter: Denis Golovin Assignee: Denis Golovin Fix For: 3.1.0.CR1 It shows new Seam Runtime wizard. Seam wizard fields filled with default walues: 1. Runtime name (editable in case there is runtime with this name but different version) 2. Version should be locked to version used in seam project settings. After wizard finished it should re-validate seam project configuration. -- 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

15 years, 5 months

4
10
0 / 0

[JBoss JIRA] Created: (JBIDE-6246) .scenario files from Guvnor examples are not opened properly

by Vlado Pakan (JIRA)

.scenario files from Guvnor examples are not opened properly ------------------------------------------------------------ Key: JBIDE-6246 URL: https://jira.jboss.org/jira/browse/JBIDE-6246 Project: Tools (JBoss Tools) Issue Type: Bug Components: drools Affects Versions: 3.1.x Environment: Fedora Linux v.11 JBossTools-Update-3.1.0.v201004291720R-H72-GA Java 1.6Sun JDK JBoss EAP 5.0 Reporter: Vlado Pakan Assignee: Kris Verlaenen .dsl files from Guvnor Repository examples are opened as read-only but it's possible to modified them via .dsl file editor in JBT. When trying to save this read-only file JBT display this error: Save Failed org.guvnor.tools.utils.StringInput cannot be cast to org.eclipse.ui.part.FileEditorInput It should not be possible to modify read-only .dsl file. Steps to reproduce: 1. deploy guvnor to server and start server 2. open guvnor perspective 3. add default guvnor repository connection using Guvnor Repositories view 4. right click on newly created Guvnor connection and open Guvnor Console 5. choose ok to empty login dialog and click yes to install Guvnor examples 6. open <Guvnor connection> > pacakges > mortages > ApplicantDsl.dsl file from Guvnor Repositories view 7. select first expresion in opened ApplicantDsl.dsl file and click on edit button 8. click on OK button in Edit Language Mappiing dialog. It's not necessary to make any changes. 9. Choose save for ApplicantDsl.dsl file and error mentioned above is displayed -- 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

15 years, 5 months

4
9
0 / 0

[JBoss JIRA] Created: (JBIDE-6872) Quick Fix for "Component class does not contain setter for property" error marker

by Daniel Azarov (JIRA)

Quick Fix for "Component class does not contain setter for property" error marker --------------------------------------------------------------------------------- Key: JBIDE-6872 URL: https://jira.jboss.org/browse/JBIDE-6872 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: Seam Affects Versions: 3.2.0.M2 Reporter: Daniel Azarov Assignee: Daniel Azarov Fix For: 3.2.x Quick Fix should offer to create setter method and getter method (if there is no getter and user wants it) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

2
5
0 / 0

[JBoss JIRA] Created: (JBIDE-2265) bottomup generation should not have Generate WSDL enabled by default

by Max Rydahl Andersen (JIRA)

bottomup generation should not have Generate WSDL enabled by default --------------------------------------------------------------------- Key: JBIDE-2265 URL: http://jira.jboss.com/jira/browse/JBIDE-2265 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Reporter: Max Rydahl Andersen -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

3
5
0 / 0

[JBoss JIRA] Created: (JBDS-486) improve mechanism for running local builds, including per-module building rather than FULL JBDS/JBT builds

by Nick Boldt (JIRA)

improve mechanism for running local builds, including per-module building rather than FULL JBDS/JBT builds ---------------------------------------------------------------------------------------------------------- Key: JBDS-486 URL: https://jira.jboss.org/jira/browse/JBDS-486 Project: Developer Studio Issue Type: Feature Request Components: Build Reporter: Nick Boldt Assignee: Nick Boldt -- 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

15 years, 6 months

1
8
0 / 0

[JBoss JIRA] Created: (JBDS-857) Installer build should not depend on bundle.eclipse step or on creation of *-ALL-*.zip files

by Nick Boldt (JIRA)

Installer build should not depend on bundle.eclipse step or on creation of *-ALL-*.zip files -------------------------------------------------------------------------------------------- Key: JBDS-857 URL: https://jira.jboss.org/jira/browse/JBDS-857 Project: JBoss Developer Studio Issue Type: Bug Affects Versions: 3.0.0.M4 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 3.0.0.M4 bundle.eclipse is basically and empty method call, but there's a lot of leftover properties being set related to it which should be removed. Also, the ALL zips are still created and used to produce the installer jars, then deleted while the build results page is being created. We should switch the installer from "unpack a zip" to "use p2 to install a from the update zip" . If done correctly, we may even end up with ONE installer instead of 4, saving a ton of bandwidth and simplifying deployment to diverse hardware. -- 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

15 years, 6 months

3
11
0 / 0

[JBoss JIRA] Created: (JBIDE-2419) can not get runtime location from project target runtime with eclipse 3.4

by Denny Xu (JIRA)

can not get runtime location from project target runtime with eclipse 3.4 ------------------------------------------------------------------------- Key: JBIDE-2419 URL: http://jira.jboss.com/jira/browse/JBIDE-2419 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.0.0.alpha Reporter: Denny Xu Assigned To: Denny Xu -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

2
6
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 August 2010