[JBoss JIRA] Created: (JBDS-350) Tag auto complete in JSF editor partially working
by Andy Gibson (JIRA)
Tag auto complete in JSF editor partially working
-------------------------------------------------
Key: JBDS-350
URL: http://jira.jboss.com/jira/browse/JBDS-350
Project: Developer Studio
Issue Type: Bug
Components: jsf
Affects Versions: 1.1.0.CR1
Environment: Brand new JBDS 1.1 CR1 installation
Reporter: Andy Gibson
Assigned To: Max Rydahl Andersen
The problem happens in editing the source for a xhtml JSF page.
If you type "<h:outputTe" and press ctrl+space to auto complete, the <h:outputText> tag appears as an option for completion. If you select it, it simply puts the element in the source, but doesn't include any attributes. It completes it as :
<h:outputText />
Compare this to JBoss Tools, if you type the same thing and use the auto complete, the IDE completes it as :
<h:outputText value=""></h:outputText value>
with the value="" included and the caret positioned between the two quotes read for typing the value and the EL auto complete box ready to help (see screenshots). Notice also that in the first case, it completes it as a single element, whereas in JBoss Tools it has 2 separate open and close elements.
I can reproduce this on a new project and as I said, this is a fresh installation of JBDS . I have used various versions of JBoss tools, and it has had the tag auto completion for a while (although there was a point where it was broken, that was ages ago).
While it isn't a big deal, when you get used to it being there and it is suddenly missing, you notice it! Let me know if you have problems reproducing it.
Cheers,
Andy Gibson
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 9 months
[JBoss JIRA] Created: (JBIDE-2329) There is a java.lang.IndexOutOfBoundsException if we try use hiperlinks on some EL.
by Alexey Kazakov (JIRA)
There is a java.lang.IndexOutOfBoundsException if we try use hiperlinks on some EL.
-----------------------------------------------------------------------------------
Key: JBIDE-2329
URL: http://jira.jboss.com/jira/browse/JBIDE-2329
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jsp/jsf/xml source editing
Affects Versions: 2.1.1
Reporter: Alexey Kazakov
Assigned To: Victor Rubezhny
Fix For: 3.0.alpha
Try to press Ctrl and move mouse on "contains":
<h:outputText value=" yes" rendered="#{siteUser.groups.contains('user')}"/>
I get a lot of :
java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
at java.util.ArrayList.RangeCheck(ArrayList.java:546)
at java.util.ArrayList.get(ArrayList.java:321)
at org.jboss.tools.seam.text.ext.hyperlink.SeamBeanHyperlinkPartitioner.findJavaElements(SeamBeanHyperlinkPartitioner.java:288)
at org.jboss.tools.seam.text.ext.hyperlink.SeamBeanHyperlinkPartitioner.recognize(SeamBeanHyperlinkPartitioner.java:235)
at org.jboss.tools.common.text.ext.hyperlink.AbstractHyperlinkPartitioner.getChildPartitionType(AbstractHyperlinkPartitioner.java:49)
at org.jboss.tools.common.text.ext.hyperlink.AbstractHyperlinkPartitioner.getChildPartitionType(AbstractHyperlinkPartitioner.java:56)
at org.jboss.tools.common.text.ext.hyperlink.AbstractHyperlinkPartitioner.getChildPartitionType(AbstractHyperlinkPartitioner.java:56)
at org.jboss.tools.common.text.ext.hyperlink.AbstractHyperlinkPartitioner.getChildPartitionType(AbstractHyperlinkPartitioner.java:56)
at org.jboss.tools.common.text.ext.hyperlink.HyperlinkDetector.getPartitionTypes(HyperlinkDetector.java:79)
at org.jboss.tools.common.text.ext.hyperlink.xpl.BaseHyperlinkDetector.getPartitionType(BaseHyperlinkDetector.java:120)
at org.jboss.tools.common.text.ext.hyperlink.xpl.BaseHyperlinkDetector.getHyperlinks(BaseHyperlinkDetector.java:51)
at org.jboss.tools.common.text.ext.hyperlink.xpl.BaseHyperlinkDetector.detectHyperlinks(BaseHyperlinkDetector.java:132)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 9 months
[JBoss JIRA] Created: (JBIDE-2366) Exception appears on opening xhtml file in some case
by Andrei Scherbovich (JIRA)
Exception appears on opening xhtml file in some case
----------------------------------------------------
Key: JBIDE-2366
URL: http://jira.jboss.com/jira/browse/JBIDE-2366
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor
Affects Versions: 3.0.alpha
Environment: JBDS 1.1.0
200806161541-nightly
Reporter: Andrei Scherbovich
Assigned To: Maxim Areshkau
Exception appears on opening xhtml file in some case
Steps:
EXECUTE: Import richfaces-demo-3.2.1.GA project into workspace (http://repository.jboss.com/maven2/org/richfaces/samples/richfaces-demo/3...)
EXECUTE: Open templates/main.xhtml file
FAILURE: java.lang.NumberFormatException: For input string: "100%" appears. VPE doesn't work at all.
java.lang.NumberFormatException: For input string: "100%"
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
at java.lang.Integer.parseInt(Integer.java:456)
at java.lang.Integer.parseInt(Integer.java:497)
at org.jboss.tools.jsf.vpe.richfaces.ComponentUtil.parseWidthHeightValue(ComponentUtil.java:654)
at org.jboss.tools.jsf.vpe.richfaces.template.RichFacesPanelBarTemplate.width(RichFacesPanelBarTemplate.java:138)
at org.jboss.tools.jsf.vpe.richfaces.template.RichFacesPanelBarTemplate.create(RichFacesPanelBarTemplate.java:63)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:427)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:256)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:600)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:494)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:256)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:575)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:490)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:256)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:575)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:490)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:256)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:600)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:494)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:256)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:575)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:490)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:256)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:575)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:490)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:256)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:575)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:490)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:256)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:575)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:490)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:256)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:575)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:490)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:256)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:575)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:490)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:256)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.buildDom(VpeVisualDomBuilder.java:215)
at org.jboss.tools.vpe.editor.VpeController.init(VpeController.java:261)
at org.jboss.tools.vpe.editor.VpeEditorPart$16.load(VpeEditorPart.java:747)
at org.jboss.tools.vpe.editor.mozilla.MozillaEditor.onLoadWindow(MozillaEditor.java:493)
at org.jboss.tools.vpe.editor.mozilla.MozillaEditor.access$2(MozillaEditor.java:488)
at org.jboss.tools.vpe.editor.mozilla.MozillaEditor$4.onLoadWindow(MozillaEditor.java:224)
at org.jboss.tools.vpe.xulrunner.browser.XulRunnerBrowser.onStateChange(XulRunnerBrowser.java:403)
at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2370)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3418)
at org.jboss.tools.vpe.editor.mozilla.MozillaEditor.createPartControl(MozillaEditor.java:271)
at org.jboss.tools.vpe.editor.VpeEditorPart.createVisualEditor(VpeEditorPart.java:753)
at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditor.pageChange(JSPMultiPageEditor.java:212)
at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditor.createPages(JSPMultiPageEditor.java:411)
at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditorPart.createPartControl(JSPMultiPageEditorPart.java:125)
at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:661)
at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:428)
at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:594)
at org.eclipse.ui.internal.EditorReference.getEditor(EditorReference.java:266)
at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2820)
at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2729)
at org.eclipse.ui.internal.WorkbenchPage.access$11(WorkbenchPage.java:2721)
at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2673)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2668)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2652)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2643)
at org.eclipse.ui.ide.IDE.openEditor(IDE.java:646)
at org.eclipse.ui.ide.IDE.openEditor(IDE.java:605)
at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:318)
at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:160)
at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:228)
at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:207)
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:363)
at org.eclipse.jdt.internal.ui.packageview.PackageExplorerPart$5.open(PackageExplorerPart.java:603)
at org.eclipse.jface.viewers.StructuredViewer$2.run(StructuredViewer.java:820)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at org.eclipse.core.runtime.Platform.run(Platform.java:880)
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:818)
at org.eclipse.jface.viewers.StructuredViewer.handleOpen(StructuredViewer.java:1079)
at org.eclipse.jface.viewers.StructuredViewer$6.handleOpen(StructuredViewer.java:1183)
at org.eclipse.jface.util.OpenStrategy.fireOpenEvent(OpenStrategy.java:263)
at org.eclipse.jface.util.OpenStrategy.access$2(OpenStrategy.java:257)
at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:297)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1002)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3821)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3420)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2382)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2198)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:488)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:112)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193)
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:382)
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:585)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
at org.eclipse.equinox.launcher.Main.main(Main.java:1212)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 9 months
[JBoss JIRA] Created: (JBIDE-2333) java.lang.NullPointerException when make openOn on EL w/o atribute.
by Anton Klimkovich (JIRA)
java.lang.NullPointerException when make openOn on EL w/o atribute.
-------------------------------------------------------------------
Key: JBIDE-2333
URL: http://jira.jboss.com/jira/browse/JBIDE-2333
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jsp/jsf/xml source editing
Affects Versions: 2.1.0.GA
Reporter: Anton Klimkovich
EXECUTE: Create seam project
EXECUTE: Open home.xhtml
EXECUTE: Type <h:outputText "#{applicationScope}" />
EXECUTE: Make openOn on applicationScope
FAILURE:
java.lang.NullPointerException
at org.jboss.tools.jsf.text.ext.hyperlink.JSPExprHyperlinkPartitioner.getRegion(JSPExprHyperlinkPartitioner.java:98)
at org.jboss.tools.jsf.text.ext.hyperlink.JSPExprHyperlinkPartitioner.recognize(JSPExprHyperlinkPartitioner.java:141)
at org.jboss.tools.common.text.ext.hyperlink.AbstractHyperlinkPartitioner.getChildPartitionType(AbstractHyperlinkPartitioner.java:49)
at org.jboss.tools.common.text.ext.hyperlink.AbstractHyperlinkPartitioner.getChildPartitionType(AbstractHyperlinkPartitioner.java:56)
at org.jboss.tools.common.text.ext.hyperlink.AbstractHyperlinkPartitioner.getChildPartitionType(AbstractHyperlinkPartitioner.java:56)
at org.jboss.tools.common.text.ext.hyperlink.HyperlinkDetector.getPartitionTypes(HyperlinkDetector.java:79)
at org.jboss.tools.common.text.ext.hyperlink.xpl.BaseHyperlinkDetector.getPartitionType(BaseHyperlinkDetector.java:120)
at org.jboss.tools.common.text.ext.hyperlink.xpl.BaseHyperlinkDetector.getHyperlinks(BaseHyperlinkDetector.java:51)
at org.jboss.tools.common.text.ext.hyperlink.xpl.BaseHyperlinkDetector.detectHyperlinks(BaseHyperlinkDetector.java:132)
at org.eclipse.jface.text.hyperlink.HyperlinkManager.findHyperlinks(HyperlinkManager.java:261)
at org.eclipse.jface.text.hyperlink.HyperlinkManager.mouseMove(HyperlinkManager.java:458)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:198)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3682)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3293)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219)
at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:169)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176)
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:585)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:508)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447)
at org.eclipse.equinox.launcher.Main.run(Main.java:1173)
at org.eclipse.equinox.launcher.Main.main(Main.java:1148)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 9 months
[JBoss JIRA] Created: (RHDS-277) Creating JBoss Seam project (or anyother project actually) in Maven2 compatible directory structure
by Mehmet Salgar (JIRA)
Creating JBoss Seam project (or anyother project actually) in Maven2 compatible directory structure
---------------------------------------------------------------------------------------------------
Key: RHDS-277
URL: http://jira.jboss.com/jira/browse/RHDS-277
Project: Red Hat Developer Studio
Issue Type: Feature Request
Reporter: Mehmet Salgar
Hi,
my request is Red Hat Studio and Maven 2 related.
I think Red Hat Studio should create (or at least give the possibility) for the Jboss Seam projects in a structure that is compatible with a Maven 2 structure.
It is undeniable fact that java programmers are moving toward Maven 2 to manage their depenencies (even JBoss http://in.relation.to/Bloggers/Pete, http://www.michaelyuan.com/blog/2007/10/09/jboss-seam-project-setup-with-..., http://www.jroller.com/wesleyhales/, http://jbossportal.blogspot.com/), in this time it is interesting that an IDE that is developed with Red Hat and JBoss is not supporting directory structure of Maven 2.
With Beta2, I can create a JBoss Seam project and create necessary pom.xml for the web module to be compatible with Maven 2 but with ejb module it is not possible, because maven-ejb-plugin needs ejb-jar.xml (or anything in META-INF) to be in src/main/resources. It is not possible to configure this for any other directory in maven-ejb-plugin.
It is not possible to change the directory structure in RHDS also, it is default ejbModule/META-INF, there must be at least a way to set this to src/main/resources during the project creation.
Same is valid for the web project creation, there I can choose the directory but on a flat level, so it can be src, main but not src/main/java or src/main/webapp.
As I said little bit more compatablity with Maven 2 or little bit more configurablitiy from RHDS would be nice, it would be really stupid not be able to use Maven 2 while it is not RHDS project structure compatible and it would be also stupid not to be able to use RHDS features while it is Maven 2 project structure incompatible......
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 9 months