February 2010 - jbosstools-issues

[JBoss JIRA] Created: (JBDS-875) BRMS pluging, deleting file not working

by Jehudi Castro (JIRA)

BRMS pluging, deleting file not working --------------------------------------- Key: JBDS-875 URL: https://jira.jboss.org/jira/browse/JBDS-875 Project: JBoss Developer Studio Issue Type: Bug Reporter: Jehudi Castro see GUVNOR-459 -- 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, 10 months

4
14
0 / 0

[JBoss JIRA] Created: (JBIDE-5878) Archives .packages configuration cannot be used without modifications to build archive with ant inside eclipse

by Denis Golovin (JIRA)

Archives .packages configuration cannot be used without modifications to build archive with ant inside eclipse -------------------------------------------------------------------------------------------------------------- Key: JBIDE-5878 URL: https://jira.jboss.org/jira/browse/JBIDE-5878 Project: Tools (JBoss Tools) Issue Type: Bug Components: Archives Affects Versions: 3.1.0.CR2 Reporter: Denis Golovin Assignee: Rob Stryker By default packages/package@todir attribute is set to /${project-name} and that works only when archive is built by using context menu on Archives View. If you create build.xml and run it by eclipse ant launcher it fails with error like Error adding child node jarName.jar [GenerateArchives] org.jboss.ide.eclipse.archives.core.model.ArchivesModelException: Error adding child node myJar.jar [GenerateArchives] at org.jboss.ide.eclipse.archives.core.model.internal.ArchiveNodeImpl.addChild(ArchiveNodeImpl.java:273) [GenerateArchives] at org.jboss.ide.eclipse.archives.core.util.ModelUtil.fillArchiveModel(ModelUtil.java:216) [GenerateArchives] at org.jboss.ide.eclipse.archives.core.model.ArchivesModel.registerProject(ArchivesModel.java:194) [GenerateArchives] at org.jboss.ide.eclipse.archives.core.model.ArchivesModel.registerProject(ArchivesModel.java:170) [GenerateArchives] at org.jboss.ide.eclipse.archives.core.ant.GenerateArchivesTask.execute(GenerateArchivesTask.java:63) [GenerateArchives] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288) [GenerateArchives] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [GenerateArchives] at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) [GenerateArchives] at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) [GenerateArchives] at java.lang.reflect.Method.invoke(Unknown Source) [GenerateArchives] at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105) [GenerateArchives] at org.apache.tools.ant.Task.perform(Task.java:348) [GenerateArchives] at org.apache.tools.ant.Target.execute(Target.java:357) [GenerateArchives] at org.apache.tools.ant.Target.performTasks(Target.java:385) [GenerateArchives] at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1329) [GenerateArchives] at org.apache.tools.ant.Project.executeTarget(Project.java:1298) [GenerateArchives] at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41) [GenerateArchives] at org.eclipse.ant.internal.ui.antsupport.EclipseDefaultExecutor.executeTargets(EclipseDefaultExecutor.java:32) [GenerateArchives] at org.apache.tools.ant.Project.executeTargets(Project.java:1181) [GenerateArchives] at org.eclipse.ant.internal.ui.antsupport.InternalAntRunner.run(InternalAntRunner.java:423) [GenerateArchives] at org.eclipse.ant.internal.ui.antsupport.InternalAntRunner.main(InternalAntRunner.java:137) -- 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, 10 months

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-5951) jBPM3 runtime from JBDS 2.1.1 workspace is missing when opened in 3.0.0 CR2

by Jiri Peterka (JIRA)

jBPM3 runtime from JBDS 2.1.1 workspace is missing when opened in 3.0.0 CR2 ---------------------------------------------------------------------------- Key: JBIDE-5951 URL: https://jira.jboss.org/jira/browse/JBIDE-5951 Project: Tools (JBoss Tools) Issue Type: Bug Components: Archives, jbpm Affects Versions: 3.1.0.CR2 Environment: JBDS 3.0.0 CR2 184, Linux 32 Reporter: Jiri Peterka Fix For: 3.1.0.GA When workspace with jbpm3 project created in JBDS 2.1.1 GA is opened in JBDS 3.0.0 CR2, there is missin jbpm3 runtime setting. Assumption is jbpm3 runtime setting set in 2.1.1 should be available when opened in 3.0.0. -- 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, 10 months

4
23
0 / 0

[JBoss JIRA] Created: (JBDS-1086) Provide a facade build.xml firl to be able start build without shell script

by Denis Golovin (JIRA)

Provide a facade build.xml firl to be able start build without shell script --------------------------------------------------------------------------- Key: JBDS-1086 URL: https://jira.jboss.org/jira/browse/JBDS-1086 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: Build Affects Versions: 3.0.0.CR2 Reporter: Denis Golovin Assignee: Denis Golovin Fix For: 3.0.0.CR2, LATER Now it is no simple way to start the -- 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, 10 months

1
3
0 / 0

[JBoss JIRA] Created: (JBDS-379) Improve using of eclipse distribution during build

by Denis Golovin (JIRA)

Improve using of eclipse distribution during build -------------------------------------------------- Key: JBDS-379 URL: https://jira.jboss.org/jira/browse/JBDS-379 Project: Developer Studio Issue Type: Task Components: Build Reporter: Denis Golovin Assignee: Denis Golovin 1. Use -configuration key to create configuration folder in temporary build directory, so the same eclipse distribution folder can be used during next build 2. Use the same eclipse distribution on compilation and on testing build phase -- 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, 10 months

2
9
0 / 0

[JBoss JIRA] Created: (JBIDE-4827) Create automated UI functional tests for Hibernate Tools

by Jiri Peterka (JIRA)

Create automated UI functional tests for Hibernate Tools -------------------------------------------------------- Key: JBIDE-4827 URL: https://jira.jboss.org/jira/browse/JBIDE-4827 Project: Tools (JBoss Tools) Issue Type: Task Components: QA Affects Versions: 3.1.0.CR1 Reporter: Jiri Peterka Fix For: 3.0.0.cr1 Create automated UI functional tests for Hibernate Tools. Test cases will be follow manual test cases. -- 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, 10 months

3
10
0 / 0

[JBoss JIRA] Created: (JBIDE-4693) Provide cheat sheets

by Xue Peng (JIRA)

Provide cheat sheets --------------------- Key: JBIDE-4693 URL: https://jira.jboss.org/jira/browse/JBIDE-4693 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: smooks Affects Versions: 3.1.0.M3 Reporter: Xue Peng Assignee: Xue Peng Provide cheat sheets to help the user can easily understand how to use the Smooks configuration editor. -- 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, 10 months

3
8
0 / 0

[JBoss JIRA] Created: (JBIDE-4304) Autoconfigure datasources from JBoss in DTP

by Max Rydahl Andersen (JIRA)

Autoconfigure datasources from JBoss in DTP ------------------------------------------- Key: JBIDE-4304 URL: https://jira.jboss.org/jira/browse/JBIDE-4304 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS Reporter: Max Rydahl Andersen Fix For: 3.1.0.M1, 3.1.0.M2 It would be great if DTP would automatically (or semi-automatically) could be configured to pickup the -ds.xml in a server runtime so users didn't have to set it up. Not sure where in the ui we should have this, a couple of options come to my mind: 1) At AS Server/runtime creation have a checkbox saying "Configure -ds.xml automatically in DTP" and then we will keep DTP informed about the -ds.xml files for it to pick up 2) In DTP's ui have a way to add or maybe only import a -ds.xml and have it preconfigured. The biggest issue will be to know which drivers we should be using for -ds.xml... Things that should be considered: If users changes the -ds.xml how does DTP learn about it ? If the users remove the -ds.xml how does DTP react ? If the users add .? Needs investigation into if DTP have extensions point that allows for this kind of 'monitored' resources to update the connections; or if it is better to simply just have a way to "import" settings from ds.xml's (and then possibly have a manual refresh to pickup changes) Or have both. The usecase for this is to be able to use already existing and newly added -ds.xml files from within Eclipse with minimal setup, i.e. for Seam and Dali projects. (I think this is a duplicate, but couldn't find it ;( -- 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, 10 months

3
10
0 / 0

[JBoss JIRA] Created: (JBIDE-5939) Smooks Handler Config still not linked to Smooks Editor

by Brian Fitzpatrick (JIRA)

Smooks Handler Config still not linked to Smooks Editor ------------------------------------------------------- Key: JBIDE-5939 URL: https://jira.jboss.org/jira/browse/JBIDE-5939 Project: Tools (JBoss Tools) Issue Type: Bug Components: esb Reporter: Brian Fitzpatrick Assignee: Viacheslav Kabanovich Fix For: 3.1.0.CR3, 3.2.next This is a spinoff from JBIDE-5491. The properties Smooks Request Mapper and Smooks Response Mapper are now linked to the Smooks editor, but not Smooks Handler Config. The screen shot attached to JBIDE-5491 shows the issue. Slava, can you please link the Smooks Handler Config property to the Smooks Editor as you've done with the other properties? -- 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, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-5491) Changes for the SOAP Wise Client configuration in the ESB editor

by Brian Fitzpatrick (JIRA)

Changes for the SOAP Wise Client configuration in the ESB editor ---------------------------------------------------------------- Key: JBIDE-5491 URL: https://jira.jboss.org/jira/browse/JBIDE-5491 Project: Tools (JBoss Tools) Issue Type: Bug Components: esb Affects Versions: 3.1.0.GA Reporter: Brian Fitzpatrick Assignee: Viacheslav Kabanovich Fix For: 3.1.0.GA The SOAP Client and SOAP Wise Client configuration panels in the JBoss ESB Editor both say "SOAP Client Action" at the top. Can we change it for the Wise client to "SOAP Wise Client Action"? And these properties -- Smooks Request Mapper, Smooks Response Mapper, and Smooks Handler Config -- should all be linked to the Smooks editor in the same way the SmooksAction's smooks config file property is linked. -- 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, 10 months

6
9
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 February 2010