September 2010 - jbosstools-issues

[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-7225) Teiid Designer admin and preview connections should be based on a configurable runtime.

by John Doyle (JIRA)

Teiid Designer admin and preview connections should be based on a configurable runtime. --------------------------------------------------------------------------------------- Key: JBIDE-7225 URL: https://jira.jboss.org/browse/JBIDE-7225 Project: Tools (JBoss Tools) Issue Type: Bug Components: teiid Affects Versions: 3.2.0.M2 Reporter: John Doyle Assignee: John Doyle The admin and preview connections for Teiid Designer rely on paths that specify plugin + version. Updates to the tooling therefore break existing connections when the version changes. We should instead rely on a user configurable runtime configuration like other JBoss runtimes. -- 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

4
8
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, 5 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, 5 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-7175) testissue for serada/almworks

by Max Andersen (JIRA)

testissue for serada/almworks ----------------------------- Key: JBIDE-7175 URL: https://jira.jboss.org/browse/JBIDE-7175 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Max Andersen Assignee: Igor Sereda Fix For: LATER test for sereda -- 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
16
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, 5 months

1
8
0 / 0

[JBoss JIRA] Created: (JBDS-1308) replace b3 aggregator w/ tycho update site build

by Nick Boldt (JIRA)

replace b3 aggregator w/ tycho update site build ------------------------------------------------ Key: JBDS-1308 URL: https://jira.jboss.org/browse/JBDS-1308 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: Build Affects Versions: 4.0.0.M2, 4.0.0.Beta1 Reporter: Nick Boldt Assignee: Nick Boldt Current implementation of the aggregator in JBDS uberbuilder uses b3, which I've wrapped w/ a bit of Ant to prefetch the update site zips and deduce which features to expose. However, it doesn't work w/ remote update site URLs as input so I'd either have to rewrite the ant wrapper, or trash it in place of the code already working for the JBT aggregator (with a different site.xml if we want to include/exclude different stuff in JBDS vs. JBT). Since that's easier and ultimately moves us forward, not backward, that's the plan. This should ensure that all the stuff currently agg'd into JBDS from external builds (Drools, Teiid, jBPM 3) and the newly inserted ModeShape can all be agg'd in from the same source sites as JBT. -- 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

2
5
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, 5 months

3
11
0 / 0

[JBoss JIRA] Created: (JBIDE-7079) Add support for globalProcessScope and process-scope parameters in EsbActionHandler and EsbNotifier

by Brian Fitzpatrick (JIRA)

Add support for globalProcessScope and process-scope parameters in EsbActionHandler and EsbNotifier --------------------------------------------------------------------------------------------------- Key: JBIDE-7079 URL: https://jira.jboss.org/browse/JBIDE-7079 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: jbpm Affects Versions: 3.2.0.M2 Reporter: Brian Fitzpatrick Assignee: Koen Aers See http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Enterprise_SOA... It should be probably implemented as three-state widget (listbox) called that will contain empty value (default), process and local -- 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

2
3
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 2010