March 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-2438) include EAP 6.0.1 in JBDS 6.0.1 installer

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-2438?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-2438: -------------------------------- Release Notes Docs Status: Not Yet Documented Affects: Release Notes > include EAP 6.0.1 in JBDS 6.0.1 installer > ----------------------------------------- > > Key: JBDS-2438 > URL: https://issues.jboss.org/browse/JBDS-2438 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 6.0.1.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 6.0.1.GA, 7.0.0.Alpha1 > > Attachments: JBDS2438.patch.txt, JBDS2438.patch2.txt > > > EAP 6.0.1 is out. Time to update the installer to include the latest n' greatest EAP 6. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-10398) OpenShift Express : Can not delete git project

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10398?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-10398: ---------------------------------- Release Notes Docs Status: Not Yet Documented Affects: Release Notes > OpenShift Express : Can not delete git project > ---------------------------------------------- > > Key: JBIDE-10398 > URL: https://issues.jboss.org/browse/JBIDE-10398 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: UpStream > Affects Versions: 3.3.0.M5 > Environment: windows 7 (most likely all windows flavors) > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.0.1.Final > > Attachments: openshift.ogv > > > Whenever I try to physically delete my openshift project from the workspace, I get a popup with the following errors : > {noformat} > Problems encountered while deleting resources. > Could not delete '/hello/.git'. > Problems encountered while deleting resources. > Problems encountered while deleting files. > Could not delete: C:\Users\Fred Bricon\git\hello\.git\objects\pack\pack-10eb864ff7ab3a1edfc8b868c90a743fdee571db.pack. > Could not delete: C:\Users\Fred Bricon\git\hello\.git\objects\pack. > Could not delete: C:\Users\Fred Bricon\git\hello\.git\objects. > Could not delete: C:\Users\Fred Bricon\git\hello\.git. > Could not delete 'C:\Users\Fred Bricon\git\hello'. > {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-8530) Message Driven Bean (EJB3.x) wizard generates incorrect annotattions

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-8530?page=com.atlassian.jira.plugin... ] Denis Golovin updated JBIDE-8530: --------------------------------- Release Notes Docs Status: Not Required > Message Driven Bean (EJB3.x) wizard generates incorrect annotattions > -------------------------------------------------------------------- > > Key: JBIDE-8530 > URL: https://issues.jboss.org/browse/JBIDE-8530 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: ejb3 > Affects Versions: 3.2.0.Final > Reporter: Libor Zoubek > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.0.1.Final > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13699) Confusing web.xml declaration in generated CDI Web Project

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13699?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-13699: ---------------------------------------- This is an upstream issue. We do not generate web.xml. We just extend Dynamic Web Project Wizard. Web.xml is generated by Eclipse Web Tools project. You can see the same issue if you use New Dynamic Web Project wizard. > Confusing web.xml declaration in generated CDI Web Project > ---------------------------------------------------------- > > Key: JBIDE-13699 > URL: https://issues.jboss.org/browse/JBIDE-13699 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: UpStream > Affects Versions: 4.0.0.Final > Environment: JBDS 6.0.0.GA > Reporter: Tomas Remes > Assignee: Alexey Kazakov > > Newly generated CDI Web project contains following web.xml declaration: > {noformat} > <web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xmlns="http://java.sun.com/xml/ns/javaee" xmlns:web="http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" > xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd" > version="3.0"> > {noformat} > I think we would like to use 3.0 declaration and not any mixture. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-12901) Show in File Browser shows error for EAP 5.1.2

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12901?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-12901: ---------------------------------- Release Notes Docs Status: Not Yet Documented Affects: Release Notes > Show in File Browser shows error for EAP 5.1.2 > ---------------------------------------------- > > Key: JBIDE-12901 > URL: https://issues.jboss.org/browse/JBIDE-12901 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS/Servers, UpStream > Affects Versions: 4.0.0.Beta1 > Environment: JBDS 6.0.0.Beta1 B45 > Reporter: Martin Malina > Assignee: Rob Stryker > Labels: upstream > Fix For: 4.0.1.Final, 4.1.0.Alpha1 > > Attachments: ifile-error.png, RemoteSystemExplorer-JBIDE-12901.png > > > When you try to see what's in the deployment folder of a remote EAP 5.1.2 server, you will get an error (but the Remote System explorer will be opened correctly and will show the files). > {code} > Problems occurred when invoking code from plug-in: "org.eclipse.jface". > java.lang.ClassCastException: org.eclipse.core.internal.resources.Folder cannot be cast to org.eclipse.core.resources.IFile > at org.eclipse.rse.internal.files.ui.view.SystemViewRemoteFileAdapter.getLocalResource(SystemViewRemoteFileAdapter.java:632) > at org.eclipse.rse.internal.files.ui.view.SystemViewRemoteFileAdapter.getImageDescriptor(SystemViewRemoteFileAdapter.java:574) > at org.eclipse.rse.ui.view.SystemTableViewProvider.getImage(SystemTableViewProvider.java:236) > at org.eclipse.jface.viewers.DecoratingLabelProvider.getImage(DecoratingLabelProvider.java:85) > at org.eclipse.rse.internal.ui.view.SystemDecoratingLabelProvider.getColumnImage(SystemDecoratingLabelProvider.java:46) > at org.eclipse.jface.viewers.TableColumnViewerLabelProvider.update(TableColumnViewerLabelProvider.java:71) > at org.eclipse.jface.viewers.ViewerColumn.refresh(ViewerColumn.java:152) > at org.eclipse.jface.viewers.AbstractTableViewer.doUpdateItem(AbstractTableViewer.java:399) > at org.eclipse.jface.viewers.StructuredViewer$UpdateItemSafeRunnable.run(StructuredViewer.java:485) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49) > at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) > at org.eclipse.jface.viewers.StructuredViewer.updateItem(StructuredViewer.java:2167) > at org.eclipse.jface.viewers.AbstractTableViewer.createItem(AbstractTableViewer.java:277) > at org.eclipse.jface.viewers.AbstractTableViewer.internalRefreshAll(AbstractTableViewer.java:757) > at org.eclipse.jface.viewers.AbstractTableViewer.internalRefresh(AbstractTableViewer.java:649) > at org.eclipse.jface.viewers.AbstractTableViewer.internalRefresh(AbstractTableViewer.java:636) > at org.eclipse.jface.viewers.AbstractTableViewer$2.run(AbstractTableViewer.java:592) > at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1443) > at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1404) > at org.eclipse.jface.viewers.AbstractTableViewer.inputChanged(AbstractTableViewer.java:590) > at org.eclipse.rse.ui.view.SystemTableView.inputChanged(SystemTableView.java:479) > at org.eclipse.jface.viewers.ContentViewer.setInput(ContentViewer.java:280) > at org.eclipse.jface.viewers.StructuredViewer.setInput(StructuredViewer.java:1690) > at org.eclipse.rse.internal.ui.view.SystemTableViewPart.setInput(SystemTableViewPart.java:1599) > at org.eclipse.rse.internal.ui.view.SystemTableViewPart.setInput(SystemTableViewPart.java:1578) > at org.jboss.ide.eclipse.as.rse.ui.SystemShowInTableAction.run(SystemShowInTableAction.java:77) > at org.jboss.ide.eclipse.as.rse.ui.RSEDeploymentPreferenceUI$2.openExplorer(RSEDeploymentPreferenceUI.java:115) > at org.jboss.tools.as.wst.server.ui.xpl.ExploreActionProvider.runExplore(ExploreActionProvider.java:89) > at org.jboss.tools.as.wst.server.ui.xpl.ExploreActionProvider.runExplore(ExploreActionProvider.java:83) > at org.jboss.tools.as.wst.server.ui.xpl.ExploreActionProvider.access$0(ExploreActionProvider.java:82) > at org.jboss.tools.as.wst.server.ui.xpl.ExploreActionProvider$1.run(ExploreActionProvider.java:74) > at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) > 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.Display.sendEvent(Display.java:4134) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1458) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1481) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1466) > at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1271) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3980) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3619) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1029) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:923) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:588) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:543) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124) > 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:353) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180) > 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:629) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584) > at org.eclipse.equinox.launcher.Main.run(Main.java:1438) > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-12704) Erroneous description in forge console update screen

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12704?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-12704: ---------------------------------- Release Notes Docs Status: Not Required > Erroneous description in forge console update screen > ---------------------------------------------------- > > Key: JBIDE-12704 > URL: https://issues.jboss.org/browse/JBIDE-12704 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: forge, updatesite > Affects Versions: 4.0.0.Alpha2 > Reporter: George Gastaldi > Assignee: Koen Aers > Priority: Trivial > Fix For: 4.0.1.Final, 4.1.0.Alpha1 > > > The current description for Forge Console when selecting to update is: > {panel} > Plugins for using Seam Forge from within Eclipse. > {panel} > It should be: > {panel} > Plugins for using JBoss Forge from within Eclipse. > {panel} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13699) Confusing web.xml declaration in generated CDI Web Project

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13699?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-13699: ----------------------------------- Component/s: UpStream (was: CDI) > Confusing web.xml declaration in generated CDI Web Project > ---------------------------------------------------------- > > Key: JBIDE-13699 > URL: https://issues.jboss.org/browse/JBIDE-13699 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: UpStream > Affects Versions: 4.0.0.Final > Environment: JBDS 6.0.0.GA > Reporter: Tomas Remes > Assignee: Alexey Kazakov > > Newly generated CDI Web project contains following web.xml declaration: > {noformat} > <web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xmlns="http://java.sun.com/xml/ns/javaee" xmlns:web="http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" > xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd" > version="3.0"> > {noformat} > I think we would like to use 3.0 declaration and not any mixture. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13213) Simple adding/removing Project Archives capabilities into project

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13213?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-13213: ---------------------------------- Labels: new_and_noteworthy (was: ) > Simple adding/removing Project Archives capabilities into project > ----------------------------------------------------------------- > > Key: JBIDE-13213 > URL: https://issues.jboss.org/browse/JBIDE-13213 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Archives > Reporter: Vlado Pakan > Assignee: Max Rydahl Andersen > Labels: new_and_noteworthy > Fix For: 4.0.1.Final > > > It would be useful if we have "Configure -> Add/Remove Project Archive support" option. This option would add/remove Project Archive explorer into project in Project Explorer. Now, Project Archive explorer is visible only after creation of archive with Project Archives view. To remove Project Archives explorer now, .packages files has to be deleted. This approach is not much user friendly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13213) Simple adding/removing Project Archives capabilities into project

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13213?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-13213: ---------------------------------- Release Notes Docs Status: Not Yet Documented Affects: Release Notes > Simple adding/removing Project Archives capabilities into project > ----------------------------------------------------------------- > > Key: JBIDE-13213 > URL: https://issues.jboss.org/browse/JBIDE-13213 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Archives > Reporter: Vlado Pakan > Assignee: Max Rydahl Andersen > Labels: new_and_noteworthy > Fix For: 4.0.1.Final > > > It would be useful if we have "Configure -> Add/Remove Project Archive support" option. This option would add/remove Project Archive explorer into project in Project Explorer. Now, Project Archive explorer is visible only after creation of archive with Project Archives view. To remove Project Archives explorer now, .packages files has to be deleted. This approach is not much user friendly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-12961) JMX connection not available for remote EAP 5.1.2

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12961?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-12961: ---------------------------------- Release Notes Docs Status: Not Required > JMX connection not available for remote EAP 5.1.2 > ------------------------------------------------- > > Key: JBIDE-12961 > URL: https://issues.jboss.org/browse/JBIDE-12961 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 4.0.0.Beta1 > Environment: JBDS 6.0.0.Beta1c B58 > Reporter: Martin Malina > Assignee: Martin Malina > Fix For: 4.0.1.Final > > > I am unable to connect to a remote EAP 5.1.2 server in the MBean Explorer. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
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 March 2013