May 2011 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBDS-1656) Recognize and define Drools Runtime from SOA-P standalone product

by Vlado Pakan (JIRA)

Recognize and define Drools Runtime from SOA-P standalone product ----------------------------------------------------------------- Key: JBDS-1656 URL: https://issues.jboss.org/browse/JBDS-1656 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: installer Affects Versions: 4.1.0.M1 Reporter: Vlado Pakan When searching for runtimes during installation SOA-P Standalone is properly recognized as SOA-P-STD Runtime but contained Drools Runtime is not added to defined Drools Runtimes when installed JBDS is run. Doesn't work with these SOA-P Standalone versions 5.0.2, 5.1.0, 4.3.CP.04. JDBS should automatically detect Drools Runtime within SOA-P Stadnalone product during installation and define it for later use. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

6
5
0 / 0

[JBoss JIRA] Created: (JBIDE-8271) Help text for CDI filed conent assist proposal contains unnecessary text with weird symbols in header and doesn't contains any text in case of missing javadoc

by Denis Golovin (JIRA)

Help text for CDI filed conent assist proposal contains unnecessary text with weird symbols in header and doesn't contains any text in case of missing javadoc -------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-8271 URL: https://issues.jboss.org/browse/JBIDE-8271 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299) Affects Versions: 3.2.0.CR1 Reporter: Denis Golovin Assignee: Alexey Kazakov Fix For: 3.3.0.M1 Attachments: screenshot58.png Help for selected proposal should contain text from javadoc or state that javadoc comment cannot be found for setter and getted methods if present -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

5
15
0 / 0

[JBoss JIRA] Created: (JBIDE-5436) Code assist for JSF functions in EL.

by Alexey Kazakov (JIRA)

Code assist for JSF functions in EL. ------------------------------------ Key: JBIDE-5436 URL: https://jira.jboss.org/jira/browse/JBIDE-5436 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JSF, jsp/jsf/xml source editing Reporter: Alexey Kazakov Assignee: Victor Rubezhny Fix For: 3.2.next For example: #{rich:clientId('id')} #{rich:element('id')} #{rich:component('id')} #{rich:findComponent('id')} -- 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

14 years, 10 months

3
7
0 / 0

[JBoss JIRA] Created: (JBIDE-8820) Code Assist doesn't work properly for .drl file

by Vlado Pakan (JIRA)

Code Assist doesn't work properly for .drl file ----------------------------------------------- Key: JBIDE-8820 URL: https://issues.jboss.org/browse/JBIDE-8820 Project: Tools (JBoss Tools) Issue Type: Bug Components: drools Affects Versions: 3.2.1.M1 Environment: Linux 32bit, java sun jdk 1.6_24, jbdevstudio-product-linux-gtk-4.1.0.v201104171649R-H346-M1 Reporter: Vlado Pakan Assignee: Kris Verlaenen 1. Create a new Drools project: File -> New -> Other -> Drools Project Choose Name, click Next Check all options Choose Drools Runtime, click Finish 2. Open sample.drl file 3. Invoke Code Assist bellow line with import statement. It works. Context menu with available statements is displayed 4. Invoke Code Assist at the beginning of line with m : Message( status ... . No context menu is displayed It's was working in JBDS 4.0.0.GA version. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

5
9
0 / 0

[JBoss JIRA] Created: (JBIDE-9031) Deploying EAR with a module having a sub-module in its component descriptor deploys erroneous ear.

by Andre Dietisheim (JIRA)

Deploying EAR with a module having a sub-module in its component descriptor deploys erroneous ear. -------------------------------------------------------------------------------------------------- Key: JBIDE-9031 URL: https://issues.jboss.org/browse/JBIDE-9031 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.2.0.Final Environment: Tested with Eclipse Indigo Release 20110319-2305 with latest nightly build trunk of JBoss Tools. Deploying on a JBoss 4.2 server. Reporter: Andre Dietisheim Assignee: Rob Stryker Priority: Critical Fix For: 3.2.1.CR1, 3.3.0.M2 Attachments: error-renaming-archive.png, recursive-projects.zip h3.Context: For some reasons I have to deploy an EAR webapp with (in its libs) a jar containing itself another jar. h3.Environment: For this I have a first Java project with the following component descriptor: {code:xml} <?xml version="1.0" encoding="UTF-8"?> <project-modules id="moduleCoreId" project-version="1.5.0"> <wb-module deploy-name="project1"> <wb-resource deploy-path="/" source-path="/src/main/java"/> </wb-module> </project-modules> {code} Then, the second Java project has the component descriptor: {code:xml} <?xml version="1.0" encoding="UTF-8"?> <project-modules id="moduleCoreId" project-version="1.5.0"> <wb-module deploy-name="project2"> <wb-resource deploy-path="/" source-path="/src/main/java"/> <dependent-module archiveName="project1.jar" deploy-path="/lib" handle="module:/resource/project1/project1"> <dependency-type>uses</dependency-type> </dependent-module> </wb-module> </project-modules> {code} Then, in Eclipse when exporting the *project2* as a *Module Archive*, I obtain a .jar file featuring both classes from *project2* and a *lib* folder with the project1 compiled jar. Now, in the ear project I have the following lines in the component descriptor: {code:xml} <dependent-module archiveName=" project1.jar" deploy-path="/lib" handle="module:/resource/ project1/ project1"> <dependency-type>uses</dependency-type> </dependent-module> <dependent-module archiveName=" project2.jar" deploy-path="/lib" handle="module:/resource/ project2/ project2"> <dependency-type>uses</dependency-type> </dependent-module> {code} (The EAR needs the 2 jars as well) h3.Problem: Then, when deployed into my *JBoss 4.2 Runtime* server in Eclipse, I got the following error: {code} Error renaming C:\DEV\jboss\server\default\tmp\jbosstoolsTemp\tmp7021855122707247750.jar to C:\DEV\jboss\server\default\deploy\EAR_Project.ear\lib\project2.jar\lib\project1.jar {code} !error-renaming-archive.png! After some research, I think an exception is thrown at *org.jboss.ide.eclipse.as.core.server.xpl.PublishCopyUtil.LocalCopyCallback.moveTempFile(File, File)* during the safe rename. However, when I look to the error message I got the feeling that the publishing process want to copy the tmp jar file into a folder called "C:\DEV\jboss\server\default\deploy\EAR_Project.ear\lib\project2.jar\lib\" which can not work because "C:\DEV\jboss\server\default\deploy\EAR_Project.ear\lib\project2.jar" is a file. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (JBIDE-6656) Split out ModeShape documentation into separate plug-in

by Brian Fitzpatrick (JIRA)

Split out ModeShape documentation into separate plug-in ------------------------------------------------------- Key: JBIDE-6656 URL: https://jira.jboss.org/browse/JBIDE-6656 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 Would recommend splitting out the documentation bits into a separate plug-in so that they are more easily accessed by the documentation team. Easier for them to tweak a doc plug-in separate from the rest of the code to avoid any accidental code changes. -- 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

14 years, 10 months

4
7
0 / 0

[JBoss JIRA] Created: (JBIDE-8951) pom.xml and manifest.mf versions must align

by Nick Boldt (JIRA)

pom.xml and manifest.mf versions must align ------------------------------------------- Key: JBIDE-8951 URL: https://issues.jboss.org/browse/JBIDE-8951 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel Affects Versions: 3.2.1.CR1 Reporter: Nick Boldt Assignee: Robert (Bob) Brodt Priority: Blocker Fix For: 3.2.1.CR1 When you bump a plugin's pom.xml, you must also bump its MANIFEST.MF (or feature.xml): [ERROR] Failed to execute goal org.sonatype.tycho:maven-osgi-packaging-plugin:0.10.0:validate-version (default-validate-version) on project org.jboss.tools.bpel.tests.feature: Unqualified OSGi version 1.1.0.qualifier must match unqualified Maven version 1.1.1-SNAPSHOT for SNAPSHOT builds -> [Help 1] http://hudson.qa.jboss.com/hudson/view/DevStudio_Stable_Branch/job/jbosst... If it's unclear what needs to be changed, run this script in some directory containing plugins/features: http://anonsvn.jboss.org/repos/jbosstools/trunk/build/util/checkPOMvsMani... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-8918) Recognize and define Drools Runtime from SOA-P standalone product

by Vlado Pakan (JIRA)

Recognize and define Drools Runtime from SOA-P standalone product ----------------------------------------------------------------- Key: JBIDE-8918 URL: https://issues.jboss.org/browse/JBIDE-8918 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: runtimes Affects Versions: 3.2.1.M1 Reporter: Vlado Pakan Assignee: Snjezana Peco When searching for runtimes (Menu Window > Preferences > JBoss Tools > JBoss Tools Runtimes) Standalone SOA-P is properly recognized as SOA-P-STD Runtime but contained Drools Runtime is not added to defined Drools Runtimes. Doesn't work with these SOA-P Standalone versions 5.0.2, 5.1.0, 4.3.CP.04. JBT should automatically detect Drools Runtime within SOA-P standalone product and define it for later use. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

4
6
0 / 0

[JBoss JIRA] Created: (JBIDE-8543) StringIndexOutOfBoundsException in Export DDL wizard

by Pavol Srna (JIRA)

StringIndexOutOfBoundsException in Export DDL wizard ---------------------------------------------------- Key: JBIDE-8543 URL: https://issues.jboss.org/browse/JBIDE-8543 Project: Tools (JBoss Tools) Issue Type: Bug Components: teiid Affects Versions: 3.2.0.Final Environment: JBDS 4.0.GA, linux 32bit Reporter: Pavol Srna Fix For: 3.2.1 Exception Stack Trace: java.lang.StringIndexOutOfBoundsException: String index out of range: -1 at java.lang.String.charAt(String.java:686) at com.metamatrix.modeler.internal.ui.wizards.ExportDdlWizard.fileModified(ExportDdlWizard.java:584) at com.metamatrix.modeler.internal.ui.wizards.ExportDdlWizard$18.modifyText(ExportDdlWizard.java:465) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:173) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3540) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3161) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.ui.internal.handlers.WizardHandler$Export.executeHandler(WizardHandler.java:98) at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:274) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:293) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169) at org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:241) at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3540) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3161) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574) at org.eclipse.equinox.launcher.Main.run(Main.java:1407) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-8190) RSE Panel in New Server Wizard has wrong layout on Win7.

by Dominik Pospisil (JIRA)

RSE Panel in New Server Wizard has wrong layout on Win7. -------------------------------------------------------- Key: JBIDE-8190 URL: https://issues.jboss.org/browse/JBIDE-8190 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.2.0.CR1 Reporter: Dominik Pospisil Assignee: Rob Stryker RSE Panel in New Server Wizard has wrong layout on Win7. Both New Host and Browse button are not visible even if the whole dialog is expanded. Note that everything is fine on linux / gtk platform. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

5
7
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 May 2011