October 2010 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (TOOLSDOC-118) JBDS40_051 Memory and system requirements for different configurations and operating systems

by Isaac Rooskov (JIRA)

JBDS40_051 Memory and system requirements for different configurations and operating systems -------------------------------------------------------------------------------------------- Key: TOOLSDOC-118 URL: https://jira.jboss.org/browse/TOOLSDOC-118 Project: Documentation for JBoss Tools/Developer Studio Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Reporter: Isaac Rooskov Assignee: Isaac Rooskov Priority: Blocker Tracker for this issue. Status: Committed -- 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, 2 months

2
5
0 / 0

[JBoss JIRA] Created: (JBIDE-2708) Implement webbeans validation rules

by Max Rydahl Andersen (JIRA)

Implement webbeans validation rules ----------------------------------- Key: JBIDE-2708 URL: https://jira.jboss.org/jira/browse/JBIDE-2708 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: webbeans Reporter: Max Rydahl Andersen Fix For: LATER See webbeans ref impl for static check* methods. Unittests has tests.broken which we can use as inspiration for tests. -- 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, 2 months

4
14
0 / 0

[JBoss JIRA] Created: (JBDS-1382) No obvious icon is present to launch JBDS after installation on Mac

by John Verhaeg (JIRA)

No obvious icon is present to launch JBDS after installation on Mac ------------------------------------------------------------------- Key: JBDS-1382 URL: https://jira.jboss.org/browse/JBDS-1382 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: installer Affects Versions: 4.0.0.Beta1 Environment: Mac OS X 10.6 (Snow Leopard) w/ Cocoa Reporter: John Verhaeg After installation, I get the jbdevstudio folder, but nothing in it but other folders and a readme that talks about "clicking on the installed icon in your program menu or desktop" that doesn't exist. Just browsing for something to launch, my first inclination was to look in the studio subfolder, and only after discovering there's nothing appropriate there, and knowing, as a developer for Teiid Designer, that dev studio is an Eclipse application, did I deduce that I must have to launch the eclipse application under the eclipse subfolder. This definitely isn't intuitive, and especially wouldn't be for those new to dev studio and/or Eclipse. I'd want to see an app icon directly in my Applications folder, not even within the jbdevstudio folder. -- 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, 2 months

5
10
0 / 0

[JBoss JIRA] Created: (JBIDE-6575) CDI deployment problems validation.

by Alexey Kazakov (JIRA)

CDI deployment problems validation. ----------------------------------- Key: JBIDE-6575 URL: https://jira.jboss.org/browse/JBIDE-6575 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: cdi (jsr-299) Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.2.x Such as: 5.2.1. Unsatisfied and ambiguous dependencies - If an unsatisfied or unresolvable ambiguous dependency exists, the container automatically detects the problem and treats it as a deployment problem. 5.2.4. Primitive types and null values - if an injection point of primitive type resolves to a bean that may have null values, such as a producer method with a non-primitive return type or a producer field with a non-primitive type, the container automatically detects the problem and treats it as a deployment problem. ... -- 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, 2 months

2
9
0 / 0

[JBoss JIRA] Created: (JBIDE-6581) org.jboss.tools.ws.creation.core.test takes more than 15 mins to run - break into smaller pieces?

by Nick Boldt (JIRA)

org.jboss.tools.ws.creation.core.test takes more than 15 mins to run - break into smaller pieces? ------------------------------------------------------------------------------------------------- Key: JBIDE-6581 URL: https://jira.jboss.org/browse/JBIDE-6581 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.2.0.M1 Reporter: Nick Boldt Assignee: Brian Fitzpatrick [ERROR] Failed to execute goal org.sonatype.tycho:maven-osgi-test-plugin:0.9.0:test (default-test) on project org.jboss.tools.ws.creation.core.test: Error while executing platform: Error while executing external command, process killed. Process timeout out after 900 seconds -> [Help 2] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.sonatype.tycho:maven-osgi-test-plugin:0.9.0:test (default-test) on project org.jboss.tools.ws.creation.core.test: Error while executing platform at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:141) Does this test need more time? can it be broken into smaller pieces? -- 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, 2 months

6
33
0 / 0

[JBoss JIRA] Created: (JBIDE-6214) Support project example with no Eclipse metadata, only pom.xml, in zip

by Pete Muir (JIRA)

Support project example with no Eclipse metadata, only pom.xml, in zip ---------------------------------------------------------------------- Key: JBIDE-6214 URL: https://jira.jboss.org/jira/browse/JBIDE-6214 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: project-examples Reporter: Pete Muir Assignee: Snjezana Peco If projects want to incorporate producing project examples into their release process, they are likely not to have any valid eclipse metadata available for the example when using Maven. -- 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, 2 months

7
20
0 / 0

[JBoss JIRA] Created: (JBIDE-7371) create tests for deltacloud client

by Andre Dietisheim (JIRA)

create tests for deltacloud client ---------------------------------- Key: JBIDE-7371 URL: https://jira.jboss.org/browse/JBIDE-7371 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: deltacloud Affects Versions: 3.2.0.Beta1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.2.0.Beta2 We need tests for deltacloud client -- 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, 2 months

2
17
0 / 0

[JBoss JIRA] Created: (JBIDE-7294) Names of cloud servers are confusing

by Pete Muir (JIRA)

Names of cloud servers are confusing ------------------------------------ Key: JBIDE-7294 URL: https://jira.jboss.org/browse/JBIDE-7294 Project: Tools (JBoss Tools) Issue Type: Bug Components: deltacloud, JBossAS Affects Versions: 3.2.0.M2 Reporter: Pete Muir Currently the name is something like <image name> [<instance id>] which is somewhat confusing, as the it makes it look like the it's the image you are starting, not something on the 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, 2 months

5
9
0 / 0

[JBoss JIRA] Created: (JBIDE-6382) Add the "Add Richfaces Libraries from Seam distribution" option for EPP

by Snjezana Peco (JIRA)

Add the "Add Richfaces Libraries from Seam distribution" option for EPP ------------------------------------------------------------------------ Key: JBIDE-6382 URL: https://jira.jboss.org/browse/JBIDE-6382 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Portal/GateIn Affects Versions: 3.1.0.GA Reporter: Snjezana Peco Assignee: Snjezana Peco Fix For: 3.2.next -- 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, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-6902) WrappedException during Undo action in Smooks Editor

by Jiri Peterka (JIRA)

WrappedException during Undo action in Smooks Editor ---------------------------------------------------- Key: JBIDE-6902 URL: https://jira.jboss.org/browse/JBIDE-6902 Project: Tools (JBoss Tools) Issue Type: Bug Components: smooks Affects Versions: 3.2.0.M2 Environment: JBT Version: 3.2.0.v20100820-1242-H295-M2 Reporter: Jiri Peterka Assignee: John Graham Attachments: smooks-mess.png Steps: 1. Create XML->Java Mapping in Smooks Editor 2. Add some beans 3. Delete these beans 4. Do several undo operations ERROR1: Exception ERROR2: Diagram Mess (see attached screenshot) ERROR3: Corrupted Diagram can't be deleted (because it doesn't exist) -> WORKAROUND: Save and close & reopen !ENTRY org.eclipse.emf.common 2 0 2010-08-24 14:32:35.085 !MESSAGE An exception was ignored during command execution !STACK 0 org.eclipse.emf.common.util.WrappedException: An exception was ignored during command execution at org.eclipse.emf.common.command.BasicCommandStack.handleError(BasicCommandStack.java:287) at org.eclipse.emf.common.command.BasicCommandStack.execute(BasicCommandStack.java:118) at org.jboss.tools.smooks.gef.tree.command.GEFAdapterCommand.execute(GEFAdapterCommand.java:214) at org.eclipse.gef.commands.CompoundCommand.execute(CompoundCommand.java:111) at org.eclipse.gef.commands.CompoundCommand.execute(CompoundCommand.java:111) at org.eclipse.gef.commands.CommandStack.execute(CommandStack.java:197) at org.jboss.tools.smooks.graphical.editors.SmooksGraphicalEditorPart$1.execute(SmooksGraphicalEditorPart.java:163) at org.eclipse.gef.ui.actions.WorkbenchPartAction.execute(WorkbenchPartAction.java:83) at org.eclipse.gef.ui.actions.DeleteAction.run(DeleteAction.java:133) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.jface.commands.ActionHandler.execute(ActionHandler.java:119) 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.keys.WorkbenchKeyboard.executeCommand(WorkbenchKeyboard.java:468) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.press(WorkbenchKeyboard.java:786) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.processKeyEvent(WorkbenchKeyboard.java:885) at org.eclipse.ui.internal.keys.OutOfOrderListener.handleEvent(OutOfOrderListener.java:76) 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.Widget.sendEvent(Widget.java:1282) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1267) at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1294) at org.eclipse.swt.widgets.Widget.gtk_key_press_event(Widget.java:730) at org.eclipse.swt.widgets.Control.gtk_key_press_event(Control.java:2839) at org.eclipse.swt.widgets.Composite.gtk_key_press_event(Composite.java:734) at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:1743) at org.eclipse.swt.widgets.Control.windowProc(Control.java:4794) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4372) at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method) at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:8163) at org.eclipse.swt.widgets.Display.eventProc(Display.java:1239) at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method) at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:2224) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3169) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2629) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2593) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2427) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:670) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:663) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115) at org.eclipse.swtbot.eclipse.core.UITestApplication.start(UITestApplication.java:54) 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) at org.eclipse.equinox.launcher.Main.main(Main.java:1383) Caused by: java.lang.IndexOutOfBoundsException: index=-1, size=0 at org.eclipse.emf.ecore.util.BasicFeatureMap.remove(BasicFeatureMap.java:1821) at org.eclipse.emf.ecore.util.FeatureMapUtil$FeatureEList.remove(FeatureMapUtil.java:841) at org.eclipse.emf.edit.command.RemoveCommand.doExecute(RemoveCommand.java:327) at org.eclipse.emf.edit.command.AbstractOverrideableCommand.execute(AbstractOverrideableCommand.java:131) at org.eclipse.emf.common.command.CommandWrapper.execute(CommandWrapper.java:180) at org.eclipse.emf.common.command.BasicCommandStack.execute(BasicCommandStack.java:84) ... 55 more -- 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, 2 months

3
21
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 October 2010