[JBoss JIRA] (JBIDE-2899) Allow export of server definitions without resetting launch config
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-2899?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen resolved JBIDE-2899.
----------------------------------------
Resolution: Out of Date
Thank you for reporting this issue but this issue have been resolved as out-of-date since it has not had any updates for the last 2+ years (730 days).
If you believe this issue is still relevant and important then please reopen the issue or create a new one mentioning/linking this jira for background information.
Thank you!
> Allow export of server definitions without resetting launch config
> ------------------------------------------------------------------
>
> Key: JBIDE-2899
> URL: https://issues.jboss.org/browse/JBIDE-2899
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 3.0.0.alpha
> Reporter: Gabriele Garuglieri
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: LATER
>
>
> Currently we can export a JBoss Tools server definition using the default WTP server panel.
> There right clicking on the server opens a context menu whose last item is "Properties".
> Clicking it opens a panel where the "Switch Location" button cause the server definition to be exported from workspace metadata to "Servers" project.
> The problem is that doing so resets the launch configuration to the default values loosing any customization the user could have done.
> The "Switch Location" function for JBoss Tools server definition should not loose launch config customizations.
> (This is not strictly related but while you are at it, in the "Export Launch Configurations" panel the "JBoss Application Server Startup Configurations" items are missing the icons).
--
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
12 years, 3 months
[JBoss JIRA] (JBIDE-6247) Bankrupcy history.brl file from Guvnor examples is not opened properly
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-6247?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen resolved JBIDE-6247.
----------------------------------------
Resolution: Out of Date
Thank you for reporting this issue but this issue have been resolved as out-of-date since it has not had any updates for the last 2+ years (730 days).
If you believe this issue is still relevant and important then please reopen the issue or create a new one mentioning/linking this jira for background information.
Thank you!
> Bankrupcy history.brl file from Guvnor examples is not opened properly
> ----------------------------------------------------------------------
>
> Key: JBIDE-6247
> URL: https://issues.jboss.org/browse/JBIDE-6247
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: drools
> Affects Versions: 3.1.x
> Environment: Fedora Linux v.11
> JBossTools-Update-3.1.0.v201004291720R-H72-GA
> Java 1.6Sun JDK
> JBoss EAP 5.0
> Reporter: Vlado Pakan
> Fix For: LATER
>
> Attachments: JBIDE-6247.patch
>
>
> Bankrupcy history.brl file from Guvnor examples is not opened properl
> When trying to open this file JBT display this error:
> Could not open the editor: org.drools.guvnor.client.modeldriven.brl.CompositeFieldConstraint cannot be cast to org.drools.guvnor.client.modeldriven.brl.SingleFieldConstraint
> Error log:
> java.lang.ClassCastException: org.drools.guvnor.client.modeldriven.brl.CompositeFieldConstraint cannot be cast to org.drools.guvnor.client.modeldriven.brl.SingleFieldConstraint
> at org.drools.eclipse.rulebuilder.ui.FactPatternWidget.hasChildren(FactPatternWidget.java:556)
> at org.drools.eclipse.rulebuilder.ui.FactPatternWidget.createConstraintRow(FactPatternWidget.java:333)
> at org.drools.eclipse.rulebuilder.ui.FactPatternWidget.renderSingleFieldConstraint(FactPatternWidget.java:295)
> at org.drools.eclipse.rulebuilder.ui.FactPatternWidget.renderFieldConstraints(FactPatternWidget.java:187)
> at org.drools.eclipse.rulebuilder.ui.FactPatternWidget.addNestedElements(FactPatternWidget.java:270)
> at org.drools.eclipse.rulebuilder.ui.FactPatternWidget.compositeFieldConstraintEditor(FactPatternWidget.java:244)
> at org.drools.eclipse.rulebuilder.ui.FactPatternWidget.renderFieldConstraints(FactPatternWidget.java:194)
> at org.drools.eclipse.rulebuilder.ui.FactPatternWidget.create(FactPatternWidget.java:114)
> at org.drools.eclipse.rulebuilder.ui.FactPatternWidget.<init>(FactPatternWidget.java:80)
> at org.drools.eclipse.rulebuilder.ui.CompositeFactPatternWidget.createFactRows(CompositeFactPatternWidget.java:140)
> at org.drools.eclipse.rulebuilder.ui.CompositeFactPatternWidget.create(CompositeFactPatternWidget.java:77)
> at org.drools.eclipse.rulebuilder.ui.CompositeFactPatternWidget.<init>(CompositeFactPatternWidget.java:53)
> at org.drools.eclipse.rulebuilder.ui.RuleModeller.addCompositeFactPatternWidget(RuleModeller.java:343)
> at org.drools.eclipse.rulebuilder.ui.RuleModeller.redrawLhs(RuleModeller.java:268)
> at org.drools.eclipse.rulebuilder.ui.RuleModeller.reloadLhs(RuleModeller.java:184)
> at org.drools.eclipse.rulebuilder.ui.RuleModeller.reloadWidgets(RuleModeller.java:195)
> at org.drools.eclipse.rulebuilder.editors.BrlPage.setModelXML(BrlPage.java:46)
> at org.drools.eclipse.rulebuilder.editors.RuleEditor.pageChange(RuleEditor.java:274)
> at org.eclipse.ui.part.MultiPageEditorPart.setActivePage(MultiPageEditorPart.java:1076)
> at org.eclipse.ui.forms.editor.FormEditor.setActivePage(FormEditor.java:597)
> at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:361)
> 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.PartPane.setVisible(PartPane.java:313)
> at org.eclipse.ui.internal.presentations.PresentablePart.setVisible(PresentablePart.java:180)
> at org.eclipse.ui.internal.presentations.util.PresentablePartFolder.select(PresentablePartFolder.java:270)
> at org.eclipse.ui.internal.presentations.util.LeftToRightTabOrder.select(LeftToRightTabOrder.java:65)
> at org.eclipse.ui.internal.presentations.util.TabbedStackPresentation.selectPart(TabbedStackPresentation.java:473)
> at org.eclipse.ui.internal.PartStack.refreshPresentationSelection(PartStack.java:1256)
> at org.eclipse.ui.internal.PartStack.setSelection(PartStack.java:1209)
> at org.eclipse.ui.internal.PartStack.showPart(PartStack.java:1608)
> at org.eclipse.ui.internal.PartStack.add(PartStack.java:499)
> at org.eclipse.ui.internal.EditorStack.add(EditorStack.java:103)
> at org.eclipse.ui.internal.PartStack.add(PartStack.java:485)
> at org.eclipse.ui.internal.EditorStack.add(EditorStack.java:112)
> at org.eclipse.ui.internal.EditorSashContainer.addEditor(EditorSashContainer.java:63)
> at org.eclipse.ui.internal.EditorAreaHelper.addToLayout(EditorAreaHelper.java:225)
> at org.eclipse.ui.internal.EditorAreaHelper.addEditor(EditorAreaHelper.java:213)
> at org.eclipse.ui.internal.EditorManager.createEditorTab(EditorManager.java:778)
> at org.eclipse.ui.internal.EditorManager.openEditorFromDescriptor(EditorManager.java:677)
> at org.eclipse.ui.internal.EditorManager.openEditor(EditorManager.java:638)
> at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2854)
> 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:2668)
> at org.guvnor.tools.utils.PlatformUtils.openEditor(PlatformUtils.java:151)
> at org.guvnor.tools.views.RepositoryView.doubleClick(RepositoryView.java:448)
> at org.guvnor.tools.views.RepositoryView.access$4(RepositoryView.java:435)
> at org.guvnor.tools.views.RepositoryView$7.run(RepositoryView.java:405)
> at org.guvnor.tools.views.RepositoryView$9.doubleClick(RepositoryView.java:430)
> at org.eclipse.jface.viewers.StructuredViewer$1.run(StructuredViewer.java:821)
> 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.fireDoubleClick(StructuredViewer.java:819)
> at org.eclipse.jface.viewers.AbstractTreeViewer.handleDoubleSelect(AbstractTreeViewer.java:1419)
> at org.eclipse.jface.viewers.StructuredViewer$4.widgetDefaultSelected(StructuredViewer.java:1195)
> at org.eclipse.jface.util.OpenStrategy.fireDefaultSelectionEvent(OpenStrategy.java:238)
> at org.eclipse.jface.util.OpenStrategy.access$0(OpenStrategy.java:235)
> at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:296)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1176)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3493)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3112)
> 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)
> Steps to reproduce:
> 1. deploy guvnor to server and start server
> 2. open guvnor perspective
> 3. add default guvnor repository connection using Guvnor Repositories view
> 4. right click on newly created Guvnor connection and open Guvnor Console
> 5. choose ok to empty login dialog and click yes to install Guvnor examples
> 6. open <Guvnor connection> > pacakges > mortages >Bankrupcy history.brl file from Guvnor Repositories view. Error is displayed within editor
--
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
12 years, 3 months
[JBoss JIRA] (JBIDE-6117) JBOSS tools native support for code gen in Groovy, and new Groovy seam project
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-6117?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen resolved JBIDE-6117.
----------------------------------------
Resolution: Out of Date
Thank you for reporting this issue but this issue have been resolved as out-of-date since it has not had any updates for the last 2+ years (730 days).
If you believe this issue is still relevant and important then please reopen the issue or create a new one mentioning/linking this jira for background information.
Thank you!
> JBOSS tools native support for code gen in Groovy, and new Groovy seam project
> ------------------------------------------------------------------------------
>
> Key: JBIDE-6117
> URL: https://issues.jboss.org/browse/JBIDE-6117
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: seam2
> Affects Versions: 3.1.0.GA
> Environment: eclipse 3.5 with jboss tools 3.1 GA
> Reporter: William Woodman
> Assignee: Denis Golovin
> Fix For: LATER
>
>
> Trying to use Groovy with Jboss tools and i'm having to hand craft all the files. Essentially i have to generate the types in the IDE, then cut/copy the code back into groovy files and save.
> also have to install groovy IDE files separately and then enable grrovy support fr the project and set the j2ee module dependencies to get the deployed build to work.
> Groovy is actually really nice for the entity builds (so much less clutter) and closure features etc are nice in the language.
> What i'd like is that rather than just jboss tools being flexible to knit groovy in - it should have first class support in the jboss tools.
> I'm using seam so lets lay out thje basic requirement
> 1. future near build of jboss tools to provide install support for groovy. Create seam project and in wizard indicate that that you default code gen to be groovy or java.
> if groovy - inlude the latest groovy all jar in the ejb/war projects and automatically include the J2ee module dependency so that groovy files work when exporting project to server.
> 2. do some integration work with the groovy IDE guys, or duplicate equivalent builders into the JBOSS tools standard download.
> 3. when user selects new entity, form, conversation, etc show the default class gen type (from startup wizard) but let a user overwrite in the wizard (allows mixed mode working - with default for project as set at startup).
> 4. if groovy selected ensure that full debug support included for groovy files.
> This would be a fabulous improvement. At present although i can build a grooy project its very manually intensive and I have to do all the hard work by hand/cut copy etc .
> would be fabulous if jboss tools fully supported this natively.
> Also with seam v3 on the build, ensuring that groovy option is included into weld/seam v3 would be a plus also
--
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
12 years, 3 months
[JBoss JIRA] (JBIDE-3695) We need to add properties to Content Assist from javax.faces.model.DataModel
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-3695?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen resolved JBIDE-3695.
----------------------------------------
Resolution: Out of Date
Thank you for reporting this issue but this issue have been resolved as out-of-date since it has not had any updates for the last 2+ years (730 days).
If you believe this issue is still relevant and important then please reopen the issue or create a new one mentioning/linking this jira for background information.
Thank you!
> We need to add properties to Content Assist from javax.faces.model.DataModel
> ----------------------------------------------------------------------------
>
> Key: JBIDE-3695
> URL: https://issues.jboss.org/browse/JBIDE-3695
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: seam2
> Affects Versions: 3.0.0.CR2
> Reporter: Daniel Azarov
> Assignee: Alexey Kazakov
> Labels: new_and_noteworthy
> Fix For: LATER
>
>
> We need to add next properties: rowAvailable, rowIndex, rowData, wrappedData
> Test case:
> 1. Start Studio
> 2. Select Help->Project Exaples..
> 3. Select Seam DVD Store Example and press Finish button
> 4. Open WebContent/showorders.xhtml
> Assert: There are no error markers for properties from DataModel
--
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
12 years, 3 months
[JBoss JIRA] (JBIDE-8359) VisualEditor throws exception and stays open for file from project that is being closed
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-8359?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen resolved JBIDE-8359.
----------------------------------------
Resolution: Out of Date
Thank you for reporting this issue but this issue have been resolved as out-of-date since it has not had any updates for the last 2+ years (730 days).
If you believe this issue is still relevant and important then please reopen the issue or create a new one mentioning/linking this jira for background information.
Thank you!
> VisualEditor throws exception and stays open for file from project that is being closed
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-8359
> URL: https://issues.jboss.org/browse/JBIDE-8359
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 3.2.0.CR1
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: LATER
>
> Attachments: screenshot79.png, screenshot88.png
>
>
> {noformat}
> Unable to create editor ID org.jboss.tools.jst.jsp.jspeditor.HTMLTextEditor: An unexpected exception was thrown.
> java.lang.NullPointerException
> at org.jboss.tools.jst.jsp.selection.bar.SelectionBar.<init>(SelectionBar.java:113)
> at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditorPart.addPage(JSPMultiPageEditorPart.java:115)
> at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditor.createPagesForVPE(JSPMultiPageEditor.java:489)
> at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditor.createPages(JSPMultiPageEditor.java:411)
> at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditorPart.createPartControl(JSPMultiPageEditorPart.java:164)
> at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:670)
> at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:465)
> at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:595)
> at org.eclipse.ui.internal.PartPane.setVisible(PartPane.java:313)
> at org.eclipse.ui.internal.presentations.PresentablePart.setVisible(PresentablePart.java:180)
> at org.eclipse.ui.internal.presentations.util.PresentablePartFolder.select(PresentablePartFolder.java:270)
> at org.eclipse.ui.internal.presentations.util.LeftToRightTabOrder.select(LeftToRightTabOrder.java:65)
> at org.eclipse.ui.internal.presentations.util.TabbedStackPresentation.selectPart(TabbedStackPresentation.java:473)
> at org.eclipse.ui.internal.PartStack.refreshPresentationSelection(PartStack.java:1254)
> at org.eclipse.ui.internal.PartStack.handleDeferredEvents(PartStack.java:1222)
> at org.eclipse.ui.internal.LayoutPart.deferUpdates(LayoutPart.java:400)
> at org.eclipse.ui.internal.PartSashContainer.handleDeferredEvents(PartSashContainer.java:1409)
> at org.eclipse.ui.internal.LayoutPart.deferUpdates(LayoutPart.java:400)
> at org.eclipse.ui.internal.WorkbenchPage.handleDeferredEvents(WorkbenchPage.java:1420)
> at org.eclipse.ui.internal.WorkbenchPage.deferUpdates(WorkbenchPage.java:1410)
> at org.eclipse.ui.internal.WorkbenchPage.closeEditors(WorkbenchPage.java:1384)
> at org.eclipse.ui.internal.WorkbenchPage.closeEditor(WorkbenchPage.java:1448)
> at org.eclipse.ui.texteditor.AbstractTextEditor$23.run(AbstractTextEditor.java:4156)
> 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:3515)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3164)
> 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:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> 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)
> {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
12 years, 3 months
[JBoss JIRA] (JBIDE-6048) How to show not existed console configuration in combobox?
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-6048?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen resolved JBIDE-6048.
----------------------------------------
Resolution: Out of Date
Thank you for reporting this issue but this issue have been resolved as out-of-date since it has not had any updates for the last 2+ years (730 days).
If you believe this issue is still relevant and important then please reopen the issue or create a new one mentioning/linking this jira for background information.
Thank you!
> How to show not existed console configuration in combobox?
> ----------------------------------------------------------
>
> Key: JBIDE-6048
> URL: https://issues.jboss.org/browse/JBIDE-6048
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: hibernate
> Affects Versions: 3.1.0.CR2
> Reporter: Dmitry Geraskov
> Assignee: Max Rydahl Andersen
> Fix For: 3.3.x
>
>
> If project reffers to not existed console configuration it shown in Hibernte project's properties page as "<None>", but in reveng xml editor shown associated console configuration name. There should be the same behaviour. Which one?
--
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
12 years, 3 months
[JBoss JIRA] (JBIDE-4145) Visio style combo button that visually shows last selection
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-4145?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen resolved JBIDE-4145.
----------------------------------------
Resolution: Out of Date
Thank you for reporting this issue but this issue have been resolved as out-of-date since it has not had any updates for the last 2+ years (730 days).
If you believe this issue is still relevant and important then please reopen the issue or create a new one mentioning/linking this jira for background information.
Thank you!
> Visio style combo button that visually shows last selection
> -----------------------------------------------------------
>
> Key: JBIDE-4145
> URL: https://issues.jboss.org/browse/JBIDE-4145
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: drools
> Reporter: Mark Proctor
> Fix For: LATER
>
>
> While eclipse will remember the last selected action when a combo button entry is selected, it does not update the icon shown on top. In Drools we updated our alignment combo button to work the way Visio does, which is more intuitive, it would be nice to have this built into Eclipse itself.
--
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
12 years, 3 months
[JBoss JIRA] (JBIDE-1984) Provide seam variables to WTP JSF code completion/editor
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-1984?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen resolved JBIDE-1984.
----------------------------------------
Resolution: Out of Date
Thank you for reporting this issue but this issue have been resolved as out-of-date since it has not had any updates for the last 2+ years (730 days).
If you believe this issue is still relevant and important then please reopen the issue or create a new one mentioning/linking this jira for background information.
Thank you!
> Provide seam variables to WTP JSF code completion/editor
> --------------------------------------------------------
>
> Key: JBIDE-1984
> URL: https://issues.jboss.org/browse/JBIDE-1984
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: seam2
> Affects Versions: 2.1.0.beta1
> Reporter: Max Rydahl Andersen
> Assignee: Alexey Kazakov
> Fix For: LATER
>
>
> we should look into implementing a proper JSF variable resolver for eclipse jst.jsf instead of the current one where we just return null_symbol to make it stop "lying" about errors.
--
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
12 years, 3 months
[JBoss JIRA] (JBIDE-4468) UTF-8 support in Properties editor
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-4468?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen resolved JBIDE-4468.
----------------------------------------
Resolution: Out of Date
Thank you for reporting this issue but this issue have been resolved as out-of-date since it has not had any updates for the last 2+ years (730 days).
If you believe this issue is still relevant and important then please reopen the issue or create a new one mentioning/linking this jira for background information.
Thank you!
> UTF-8 support in Properties editor
> ----------------------------------
>
> Key: JBIDE-4468
> URL: https://issues.jboss.org/browse/JBIDE-4468
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: common/jst/core
> Reporter: Krasimir Goutcev
> Fix For: LATER
>
>
> If we create multi language program app, we externalize strings in property file.
> now this file is in format:
> javax.faces.component.UIInput.REQUIRED=\u041C\u043E\u043B\u044F \u0432\u044A\u0432\u0435\u0434\u0435\u0442\u0435 \u0437\u0430\u0434\u044A\u043B\u0436\u0442\u0435\u043B\u043D\u0438\u0442\u0435 \u043F\u043E\u043B\u0435\u0442\u0430\!
> It will be difficult for translator to translate this.
> May be export in simple txt format will be more useful.
--
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
12 years, 3 months
[JBoss JIRA] (JBIDE-508) page.xml param code completion
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-508?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen resolved JBIDE-508.
---------------------------------------
Resolution: Out of Date
Thank you for reporting this issue but this issue have been resolved as out-of-date since it has not had any updates for the last 2+ years (730 days).
If you believe this issue is still relevant and important then please reopen the issue or create a new one mentioning/linking this jira for background information.
Thank you!
> page.xml param code completion
> ------------------------------
>
> Key: JBIDE-508
> URL: https://issues.jboss.org/browse/JBIDE-508
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: seam2
> Reporter: Max Rydahl Andersen
> Assignee: Alexey Kazakov
> Fix For: LATER
>
>
> take param in pages.xml and do codecomplete for it in the related page.
> in s:link, offer code complete for param from pages.xml based on view attribute.
--
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
12 years, 3 months