May 2010 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-6374) NPE after Creating Hibernate Configuration

by Jiri Peterka (JIRA)

NPE after Creating Hibernate Configuration ------------------------------------------ Key: JBIDE-6374 URL: https://jira.jboss.org/browse/JBIDE-6374 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: 3.1.1 Environment: JBDS 3.0.1 GA 80, Linux 64, JDK 1.6 Reporter: Jiri Peterka Assignee: Max Rydahl Andersen Fix For: 3.1.x ERROR: After trying to open configuration editor, it fails with NPE exception (see screenshots and log) REPRODUCIBILITY: LOW -- 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, 7 months

5
20
0 / 0

[JBoss JIRA] Created: (JBIDE-6059) jboss-esb.xml editor and process definition

by Burr Sutter (JIRA)

jboss-esb.xml editor and process definition ------------------------------------------- Key: JBIDE-6059 URL: https://jira.jboss.org/jira/browse/JBIDE-6059 Project: Tools (JBoss Tools) Issue Type: Bug Components: esb Affects Versions: 3.0.0.GA Environment: jbdevstudio-win32-3.0.0.v201002190339M-H173-CR2 Reporter: Burr Sutter The jboss-esb.xml editor produces: <property name="processdefinition" value="bpm5_ESBOrderProcess"/> instead of <property name="process-definition-name" value="bpm5_ESBOrderProcess"/> the first option produces no results - the process is not fired. action name is <action class="org.jboss.soa.esb.services.jbpm.actions.BpmProcessor" name="start_a_new_order_process"> <property name="command" value="StartProcessInstanceCommand"/> -- 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, 7 months

6
17
0 / 0

[JBoss JIRA] Created: (JBIDE-5941) CA not shows proposals for #{cc.attrs.|}

by Maxim Areshkau (JIRA)

CA not shows proposals for #{cc.attrs.|} ---------------------------------------- Key: JBIDE-5941 URL: https://jira.jboss.org/jira/browse/JBIDE-5941 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.0.CR2 Reporter: Maxim Areshkau Assignee: Alexey Kazakov #1 import https://svn.jboss.org/repos/jbosstools/trunk/jsf/tests/org.jboss.tools.js... #2 open page https://svn.jboss.org/repos/jbosstools/trunk/jsf/tests/org.jboss.tools.js... #3 there exist defined attributes for this components via <composite:attribute name="sidebarClass"/> #4 user can reffer to this attributes using following structure #{cc.attrs.headerClass} #5 when we call CA #{cc.attrs.| there no proposals of attributes. I don't know is it expected to work. But if not implemented than change BUG to FR. -- 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, 7 months

5
13
0 / 0

[JBoss JIRA] Created: (JBIDE-5694) support validation/code-completion for JBoss 5.x deployment descriptors

by Erik Mattheis (JIRA)

support validation/code-completion for JBoss 5.x deployment descriptors ----------------------------------------------------------------------- Key: JBIDE-5694 URL: https://jira.jboss.org/jira/browse/JBIDE-5694 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: XML Structured Editor Affects Versions: 3.1.0.CR1 Reporter: Erik Mattheis I've noticed some issues trying to create/edit schema-based deployment descriptors. For instance, with the jboss.xml file below, validation seems to work, but code-completion does not: <?xml version="1.0" encoding="UTF-8"?> <jboss xmlns="http://www.jboss.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss_5_1.xsd" version="5.1"> </jboss> The same goes for the jboss-web.xml file below: <?xml version="1.0" encoding="UTF-8"?> <jboss-web xmlns="http://www.jboss.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-web_5_1.xsd" version="5.1"> </jboss-web> For the following test-ds.xml file, code-completion works but I get a warning about referenced file errors: <?xml version="1.0" encoding="UTF-8"?> <datasources xmlns="http://www.jboss.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ds_5_0.xsd"> </datasources> The *-jboss-beans.xml files for the new microcontainer are also a pain, since there's no public schema document available and the namespaces in the XML are all JBoss URNs. It would be a big help if these had tooling support. -- 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, 7 months

6
25
0 / 0

[JBoss JIRA] Created: (JBIDE-6224) Missing prefix "navigation" in components.xml tree view

by Huojid Grescal (JIRA)

Missing prefix "navigation" in components.xml tree view ------------------------------------------------------- Key: JBIDE-6224 URL: https://jira.jboss.org/jira/browse/JBIDE-6224 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 3.1.0.GA Environment: Windows 7, 64 bits. Eclipse Galileo. Plugin JBoss Tools installed with the update site. Reporter: Huojid Grescal Assignee: Alexey Kazakov I am currently using JBoss Tools on the Seam perspective. I need to use several files for my navigation rules : pages.xml, section1.pages.xml, section2.pages.xml, ... So, I open my components.xml file in "Source" view and add : <navigation:pages> <navigation:resources> <value>/WEB-INF/navigation/pages.xml</value> <value>/WEB-INF/navigation/section1.pages.xml</value> <value>/WEB-INF/navigation/section2.pages.xml</value> </navigation:resources> </navigation:pages> I also add in the "components" tag : xmlns:navigation=http://jboss.com/products/seam/navigation xsi:schemaLocation=http://jboss.com/products/seam/navigation http://jboss.com/products/seam/navigation-2.2.xsd And it works fine. But if I go to the "Tree" view of my components.xml, I have an error which tells me that the "navigation" prefix doesn't exist and that I have to remove it if I want to use the "Tree" view. -- 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, 7 months

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-5947) FAILED: CommonExtAllTests

by Alexey Kazakov (JIRA)

FAILED: CommonExtAllTests -------------------------- Key: JBIDE-5947 URL: https://jira.jboss.org/jira/browse/JBIDE-5947 Project: Tools (JBoss Tools) Issue Type: Bug Components: common, testing Affects Versions: 3.1.0.CR3 Reporter: Alexey Kazakov Assignee: Victor Rubezhny FAILED: CommonExtAllTests Error Message: java.lang.String declaration should be opened Stack Trace: junit.framework.AssertionFailedError: java.lang.String declaration should be opened at org.jboss.tools.common.text.ext.test.OpenOnsTest.testFaceletTaglibTypeOpenOn(OpenOnsTest.java:547) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.extensions.TestSetup.run(TestSetup.java:25) at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:354) at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:206) at org.eclipse.test.UITestApplication$3.run(UITestApplication.java:195) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3468) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3115) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.test.UITestApplication.runApplication(UITestApplication.java:138) at org.eclipse.test.UITestApplication.run(UITestApplication.java:60) at org.eclipse.test.UITestApplication.start(UITestApplication.java:210) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194) 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:368) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514) at org.eclipse.equinox.launcher.Main.run(Main.java:1311) at org.eclipse.equinox.launcher.Main.main(Main.java:1287) at org.eclipse.core.launcher.Main.main(Main.java:34) See jbosstools-nightly-3.1.0.CR3/29 -- 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, 7 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-6088) NPE when opening faces-config.xml

by Krasimir Goutcev (JIRA)

NPE when opening faces-config.xml --------------------------------- Key: JBIDE-6088 URL: https://jira.jboss.org/jira/browse/JBIDE-6088 Project: Tools (JBoss Tools) Issue Type: Bug Environment: Eclipse 3.5.2 Windows Server 2003 x64 JBT 3.1.0.v201003182253N-H80-GA Reporter: Krasimir Goutcev Attachments: .log java.lang.NullPointerException at org.jboss.tools.jsf.ui.editor.edit.LinkEditPart.createFigure(LinkEditPart.java:135) at org.eclipse.gef.editparts.AbstractGraphicalEditPart.getFigure(AbstractGraphicalEditPart.java:452) at org.eclipse.gef.editparts.AbstractConnectionEditPart.activateFigure(AbstractConnectionEditPart.java:95) at org.jboss.tools.jsf.ui.editor.edit.LinkEditPart.activateFigure(LinkEditPart.java:68) at org.eclipse.gef.editparts.AbstractConnectionEditPart.addNotify(AbstractConnectionEditPart.java:102) at org.eclipse.gef.editparts.AbstractConnectionEditPart.setParent(AbstractConnectionEditPart.java:261) at org.eclipse.gef.editparts.AbstractConnectionEditPart.setSource(AbstractConnectionEditPart.java:274) at org.eclipse.gef.editparts.AbstractGraphicalEditPart.addSourceConnection(AbstractGraphicalEditPart.java:252) at org.jboss.tools.jsf.ui.editor.edit.JSFEditPart.refreshSourceConnections(JSFEditPart.java:222) at org.eclipse.gef.editparts.AbstractGraphicalEditPart.refresh(AbstractGraphicalEditPart.java:572) at org.eclipse.gef.editparts.AbstractEditPart.addNotify(AbstractEditPart.java:235) at org.eclipse.gef.editparts.AbstractGraphicalEditPart.addNotify(AbstractGraphicalEditPart.java:219) at org.eclipse.gef.editparts.AbstractEditPart.addChild(AbstractEditPart.java:198) at org.eclipse.gef.editparts.AbstractEditPart.refreshChildren(AbstractEditPart.java:727) at org.eclipse.gef.editparts.AbstractEditPart.refresh(AbstractEditPart.java:677) at org.eclipse.gef.editparts.AbstractGraphicalEditPart.refresh(AbstractGraphicalEditPart.java:571) at org.eclipse.gef.editparts.AbstractEditPart.addNotify(AbstractEditPart.java:235) at org.eclipse.gef.editparts.AbstractGraphicalEditPart.addNotify(AbstractGraphicalEditPart.java:219) at org.eclipse.gef.editparts.AbstractEditPart.addChild(AbstractEditPart.java:198) at org.eclipse.gef.editparts.SimpleRootEditPart.setContents(SimpleRootEditPart.java:101) at org.eclipse.gef.ui.parts.AbstractEditPartViewer.setContents(AbstractEditPartViewer.java:601) at org.eclipse.gef.ui.parts.AbstractEditPartViewer.setContents(AbstractEditPartViewer.java:610) at org.jboss.tools.jsf.ui.editor.JSFEditor.initializeGraphicalViewer(JSFEditor.java:468) at org.jboss.tools.common.gef.GEFEditor.createGraphicalViewer(GEFEditor.java:118) at org.jboss.tools.common.gef.GEFEditor.createPartControl(GEFEditor.java:129) at org.jboss.tools.jsf.ui.editor.FacesConfigGuiEditor.updateGui(FacesConfigGuiEditor.java:94) at org.jboss.tools.common.editor.AbstractSectionEditor.setObject(AbstractSectionEditor.java:96) at org.jboss.tools.jsf.ui.editor.FacesConfigEditor.setNormalMode(FacesConfigEditor.java:106) at org.jboss.tools.common.editor.ObjectMultiPageEditor.initEditors(ObjectMultiPageEditor.java:489) at org.jboss.tools.jsf.ui.editor.FacesConfigEditor.doCreatePages(FacesConfigEditor.java:62) at org.jboss.tools.common.editor.ObjectMultiPageEditor.createPages(ObjectMultiPageEditor.java:237) at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:357) at org.jboss.tools.common.model.ui.editor.EditorPartWrapper.createPartControl(EditorPartWrapper.java:176) at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:662) at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:462) at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:595) at org.eclipse.ui.internal.EditorReference.getEditor(EditorReference.java:286) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2857) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2762) at org.eclipse.ui.internal.WorkbenchPage.access$11(WorkbenchPage.java:2754) at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2705) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2701) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2685) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2676) at org.eclipse.ui.ide.IDE.openEditor(IDE.java:651) at org.eclipse.ui.ide.IDE.openEditor(IDE.java:610) at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:361) at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:168) at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:229) at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:208) at org.eclipse.jdt.ui.actions.SelectionDispatchAction.dispatchRun(SelectionDispatchAction.java:274) at org.eclipse.jdt.ui.actions.SelectionDispatchAction.run(SelectionDispatchAction.java:250) at org.eclipse.jdt.internal.ui.packageview.PackageExplorerActionGroup.handleOpen(PackageExplorerActionGroup.java:373) at org.eclipse.jdt.internal.ui.packageview.PackageExplorerPart$4.open(PackageExplorerPart.java:526) at org.eclipse.ui.OpenAndLinkWithEditorHelper$InternalListener.open(OpenAndLinkWithEditorHelper.java:48) at org.eclipse.jface.viewers.StructuredViewer$2.run(StructuredViewer.java:842) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.runtime.Platform.run(Platform.java:888) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:48) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) at org.eclipse.jface.viewers.StructuredViewer.fireOpen(StructuredViewer.java:840) at org.eclipse.jface.viewers.StructuredViewer.handleOpen(StructuredViewer.java:1101) at org.eclipse.jface.viewers.StructuredViewer$6.handleOpen(StructuredViewer.java:1205) at org.eclipse.jface.util.OpenStrategy.fireOpenEvent(OpenStrategy.java:264) at org.eclipse.jface.util.OpenStrategy.access$2(OpenStrategy.java:258) at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:298) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3910) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3503) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194) 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:368) 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:559) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514) at org.eclipse.equinox.launcher.Main.run(Main.java:1311) at org.eclipse.equinox.launcher.Main.main(Main.java:1287) -- 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, 7 months

5
10
0 / 0

[JBoss JIRA] Created: (JBDS-1118) JBDS 3.0 Seam DB Connection Properties removed

by Gary Lamperillo (JIRA)

JBDS 3.0 Seam DB Connection Properties removed ---------------------------------------------- Key: JBDS-1118 URL: https://jira.jboss.org/jira/browse/JBDS-1118 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Affects Versions: 3.0.0.CR1 Reporter: Gary Lamperillo Attached are 2 screenshots of the JBDS 3.0 CR2 and JBDS 2.1.1 Seam Properties for an EJB Project. In JBDS 3.0 CR2, I no longer see the DB Connection Properties to change, review or test the connection. This is very important. I hope it has been moved somewhere else that I can not find. Please advice. Thanks, Gary -- 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, 7 months

6
30
0 / 0

[JBoss JIRA] Created: (JBDS-1181) "Configure JBoss jBPM Runtime" screen shows URL that points to an invalid page

by Tihomir Surdilovic (JIRA)

"Configure JBoss jBPM Runtime" screen shows URL that points to an invalid page ------------------------------------------------------------------------------- Key: JBDS-1181 URL: https://jira.jboss.org/jira/browse/JBDS-1181 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Affects Versions: 3.0.0.CR1 Reporter: Tihomir Surdilovic See uploaded screenshot, the "Download the JBoss jBPM package if you have non available yet." points to http://www.jboss.org/jbpm/downloads/ which is an invalid url. Please change to point to correct URL ( http://sourceforge.net/projects/jbpm/files/?). Better option also IMO would be if we tell customers to either get the community bits from location X and for supported bits to describe how to get the bits from the Customer Support Portal. -- 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, 7 months

7
16
0 / 0

[JBoss JIRA] Created: (JBIDE-6199) Struts tools fails to install in Eclipse

by db netres (JIRA)

Struts tools fails to install in Eclipse ---------------------------------------- Key: JBIDE-6199 URL: https://jira.jboss.org/jira/browse/JBIDE-6199 Project: Tools (JBoss Tools) Issue Type: Bug Components: struts/shale Affects Versions: 3.0.1.GA Environment: WinXP/Eclipse 3.5.2 Reporter: db netres When installing Struts tools the following error message is returned Cannot complete the install because one or more required items could not be found. Software being installed: Struts Tools 3.0.1.v200910211631N-H194-GA (org.jboss.tools.struts_feature.feature.group 3.0.1.v200910211631N-H194-GA) Missing requirement: Jsp Editor Plug-in 3.0.2.v200910211631N-H194-GA (org.jboss.tools.jst.jsp 3.0.2.v200910211631N-H194-GA) requires 'bundle org.eclipse.wst.javascript.core 0.0.0' but it could not be found Cannot satisfy dependency: From: Struts support for JBoss Visual Page Editor Plug-in 3.0.1.v200910211631N-H194-GA (org.jboss.tools.struts.vpe.struts 3.0.1.v200910211631N-H194-GA) To: bundle org.jboss.tools.vpe 0.0.0 Cannot satisfy dependency: From: Struts Tools 3.0.1.v200910211631N-H194-GA (org.jboss.tools.struts_feature.feature.group 3.0.1.v200910211631N-H194-GA) To: org.jboss.tools.struts.vpe.struts [3.0.1.v200910211631N-H194-GA] Cannot satisfy dependency: From: JBoss Tools RichFaces 3.0.2.v200910211631N-H194-GA (org.jboss.tools.vpe 3.0.2.v200910211631N-H194-GA) To: bundle org.jboss.tools.jst.jsp 0.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, 7 months

4
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 2010