[JBoss JIRA] (JBIDE-19183) Constant AssertionFailedExceptions from FreeMarker Editor
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19183?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-19183:
---------------------------------------
Could you attach at least one template example?
Thanks
> Constant AssertionFailedExceptions from FreeMarker Editor
> ---------------------------------------------------------
>
> Key: JBIDE-19183
> URL: https://issues.jboss.org/browse/JBIDE-19183
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: freemarker
> Environment: Eclipse 4.4.1
> Linux
> Reporter: Eric Sirianni
>
> I get constant "assertion failed" errors in the freemarker editor. The error is associated with the following stack trace in my eclipse log:
> {noformat}
> !ENTRY org.eclipse.ui 4 0 2015-02-06 12:28:37.974
> !MESSAGE Unhandled event loop exception
> !STACK 0
> org.eclipse.core.runtime.AssertionFailedException: assertion failed:
> at org.eclipse.core.runtime.Assert.isTrue(Assert.java:110)
> at org.eclipse.core.runtime.Assert.isTrue(Assert.java:96)
> at org.eclipse.jface.text.Position.setLength(Position.java:185)
> at org.eclipse.jface.text.rules.FastPartitioner.computePartitioning(FastPartitioner.java:634)
> at org.eclipse.jface.text.AbstractDocument.computePartitioning(AbstractDocument.java:1430)
> at org.eclipse.jface.text.TextUtilities.computePartitioning(TextUtilities.java:431)
> at org.eclipse.jface.text.presentation.PresentationReconciler.createPresentation(PresentationReconciler.java:451)
> at org.eclipse.jface.text.presentation.PresentationReconciler.processDamage(PresentationReconciler.java:569)
> at org.eclipse.jface.text.presentation.PresentationReconciler.access$3(PresentationReconciler.java:567)
> at org.eclipse.jface.text.presentation.PresentationReconciler$InternalListener.textChanged(PresentationReconciler.java:227)
> at org.eclipse.jface.text.TextViewer.updateTextListeners(TextViewer.java:2830)
> at org.eclipse.jface.text.TextViewer.invalidateTextPresentation(TextViewer.java:3501)
> at org.jboss.ide.eclipse.freemarker.editor.Editor.resetRange(Editor.java:282)
> at org.jboss.ide.eclipse.freemarker.editor.Editor.highlightRelatedRegions(Editor.java:257)
> at org.jboss.ide.eclipse.freemarker.editor.Editor.handleCursorPositionChanged(Editor.java:174)
> at org.jboss.ide.eclipse.freemarker.editor.Editor.mouseUp(Editor.java:200)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:220)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4454)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3799)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3409)
> {noformat}
> This happens across multiple FreeMarker templates, all with very basic syntax.
> I am using version 1.4.1.Final of the FreeMarker plugin.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19219) Install Grinder doesn't support Oomph popups
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19219?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-19219:
---------------------------------------
public static final String PROP_SETUP_SKIP = "oomph.setup.skip";
public static final String PROP_SETUP_QUESTIONNAIRE_SKIP = "oomph.setup.questionnaire.skip";
> Install Grinder doesn't support Oomph popups
> --------------------------------------------
>
> Key: JBIDE-19219
> URL: https://issues.jboss.org/browse/JBIDE-19219
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, qa
> Affects Versions: 4.3.0.Alpha1
> Reporter: Mickael Istria
> Assignee: Mickael Istria
>
> With the introduction of Oomph, install-grinder now faces many popups and pages that it doesn't know how to deal with.
> Either we have to rework it to support Oomph, or we have to find a way to disable Oomph.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-18676) HTML5 Palette throws exceptions when editing external file
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18676?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-18676:
-----------------------------------------------
PR is sent https://github.com/jbosstools/jbosstools-jst/pull/466
> HTML5 Palette throws exceptions when editing external file
> -----------------------------------------------------------
>
> Key: JBIDE-18676
> URL: https://issues.jboss.org/browse/JBIDE-18676
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.2.0.CR2
> Reporter: Alexey Kazakov
> Assignee: Viacheslav Kabanovich
> Priority: Minor
> Fix For: 4.3.0.Alpha2
>
>
> 1. Open any HTML file outside workspace via File->Open File...
> 2. Edit the file (HTML5 Palette should be opened):
> {code}
> java.lang.ArrayIndexOutOfBoundsException: 0
> at org.jboss.tools.common.model.ui.views.palette.PaletteContents.changed(PaletteContents.java:55)
> at org.jboss.tools.common.model.ui.views.palette.PaletteContents.update(PaletteContents.java:47)
> at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.PagePaletteContents.update(PagePaletteContents.java:57)
> at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.PalettePageImpl$DocumentListener.documentChanged(PalettePageImpl.java:86)
> at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument._fireDocumentChanged(BasicStructuredDocument.java:460)
> at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.fireStructuredDocumentEvent(BasicStructuredDocument.java:1184)
> at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.internalReplaceText(BasicStructuredDocument.java:1964)
> at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replaceText(BasicStructuredDocument.java:2423)
> at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replaceText(BasicStructuredDocument.java:2408)
> at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.access$2(JobSafeStructuredDocument.java:1)
> at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument$3.run(JobSafeStructuredDocument.java:141)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.wst.sse.ui.EditorExecutionContext.execute(EditorExecutionContext.java:149)
> at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.replaceText(JobSafeStructuredDocument.java:144)
> at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replace(BasicStructuredDocument.java:2368)
> at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.access$0(JobSafeStructuredDocument.java:1)
> at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument$1.run(JobSafeStructuredDocument.java:103)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.wst.sse.ui.EditorExecutionContext.execute(EditorExecutionContext.java:149)
> at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.replace(JobSafeStructuredDocument.java:106)
> at org.eclipse.jface.text.projection.ProjectionTextStore.replace(ProjectionTextStore.java:111)
> at org.eclipse.jface.text.AbstractDocument.replace(AbstractDocument.java:1184)
> at org.eclipse.jface.text.AbstractDocument.replace(AbstractDocument.java:1210)
> at org.eclipse.jface.text.projection.ProjectionDocument.replace(ProjectionDocument.java:629)
> at org.eclipse.jface.text.DefaultDocumentAdapter.replaceTextRange(DefaultDocumentAdapter.java:248)
> at org.eclipse.swt.custom.StyledText.modifyContent(StyledText.java:7268)
> at org.eclipse.swt.custom.StyledText.sendKeyEvent(StyledText.java:8111)
> at org.eclipse.swt.custom.StyledText.doContent(StyledText.java:2481)
> at org.eclipse.swt.custom.StyledText.handleKey(StyledText.java:5955)
> at org.eclipse.swt.custom.StyledText.handleKeyDown(StyledText.java:5986)
> at org.eclipse.swt.custom.StyledText$7.handleEvent(StyledText.java:5663)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4486)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1412)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1397)
> at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1424)
> at org.eclipse.swt.widgets.Widget.gtk_key_press_event(Widget.java:824)
> at org.eclipse.swt.widgets.Control.gtk_key_press_event(Control.java:3269)
> at org.eclipse.swt.widgets.Composite.gtk_key_press_event(Composite.java:777)
> at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:2098)
> at org.eclipse.swt.widgets.Control.windowProc(Control.java:5510)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:4700)
> at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method)
> at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:9074)
> at org.eclipse.swt.widgets.Display.eventProc(Display.java:1253)
> at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method)
> at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:2473)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3439)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236)
> 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:606)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
> {code}
> 3. Drop any item from the palette. Press Finish on the wizard:
> {code}
> java.lang.NullPointerException
> at org.jboss.tools.jst.web.ui.internal.preferences.js.PreferredJSLibVersions.saveLibPreference(PreferredJSLibVersions.java:270)
> at org.jboss.tools.jst.angularjs.internal.ionic.palette.wizard.NewIonicWidgetWizard.doPerformFinish(NewIonicWidgetWizard.java:82)
> at org.jboss.tools.jst.web.ui.palette.html.wizard.AbstractNewHTMLWidgetWizard$1.run(AbstractNewHTMLWidgetWizard.java:124)
> at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:466)
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:374)
> at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1059)
> at org.jboss.tools.jst.web.ui.palette.html.wizard.AbstractNewHTMLWidgetWizard.performFinish(AbstractNewHTMLWidgetWizard.java:128)
> at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:853)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:438)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4486)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3831)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3441)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:832)
> at org.eclipse.jface.window.Window.open(Window.java:808)
> at org.jboss.tools.common.model.ui.editors.dnd.DefaultDropCommand.execute(DefaultDropCommand.java:125)
> at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.JSPTextEditor$3.run(JSPTextEditor.java:746)
> at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.JSPTextEditor.runDropCommand(JSPTextEditor.java:765)
> at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.JSPMultiPageEditor.runDropCommand(JSPMultiPageEditor.java:867)
> 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:606)
> at org.jboss.tools.common.model.ui.views.palette.PaletteCreator.dropIntoEditor(PaletteCreator.java:187)
> at org.jboss.tools.common.model.ui.views.palette.PaletteCreator.insertIntoEditor(PaletteCreator.java:141)
> at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.PalettePageImpl.insertIntoEditor(PalettePageImpl.java:128)
> at org.jboss.tools.jst.web.ui.palette.PaletteViewer.insertIntoEditor(PaletteViewer.java:72)
> at org.jboss.tools.jst.web.ui.palette.PaletteViewer.setActiveTool(PaletteViewer.java:67)
> at org.jboss.tools.jst.web.ui.palette.xpl.MobileToolEntryEditPart$2.actionPerformed(MobileToolEntryEditPart.java:398)
> at org.eclipse.draw2d.Clickable.fireActionPerformed(Clickable.java:206)
> at org.eclipse.draw2d.Clickable$1.actionPerformed(Clickable.java:175)
> at org.eclipse.draw2d.ButtonModel.fireActionPerformed(ButtonModel.java:140)
> at org.eclipse.draw2d.ToggleModel.fireActionPerformed(ToggleModel.java:27)
> at org.eclipse.draw2d.ButtonModel$DefaultFiringBehavior.released(ButtonModel.java:506)
> at org.eclipse.draw2d.ButtonModel.fireReleased(ButtonModel.java:179)
> at org.eclipse.draw2d.ButtonModel.setPressed(ButtonModel.java:466)
> at org.jboss.tools.jst.web.ui.palette.xpl.MobileToolEntryEditPart$GTKToggleButtonTracker.handleButtonUp(MobileToolEntryEditPart.java:143)
> at org.eclipse.gef.tools.AbstractTool.mouseUp(AbstractTool.java:1200)
> at org.eclipse.gef.tools.SelectionTool.mouseUp(SelectionTool.java:574)
> at org.eclipse.gef.EditDomain.mouseUp(EditDomain.java:301)
> at org.eclipse.gef.ui.parts.DomainEventDispatcher.dispatchMouseReleased(DomainEventDispatcher.java:380)
> at org.eclipse.draw2d.LightweightSystem$EventHandler.mouseUp(LightweightSystem.java:548)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:220)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4486)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3831)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3441)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236)
> 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:606)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-18188) HTML5 Palette: filter to show only palette groups for which libraries are defined on the page
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18188?page=com.atlassian.jira.plugi... ]
Alexey Kazakov resolved JBIDE-18188.
------------------------------------
Resolution: Done
> HTML5 Palette: filter to show only palette groups for which libraries are defined on the page
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-18188
> URL: https://issues.jboss.org/browse/JBIDE-18188
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.3.x
> Reporter: Daniel Azarov
> Assignee: Daniel Azarov
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Alpha1
>
> Attachments: Filter1.png, Filter2.png
>
>
> *Test case 1:*
> 1. Open empty html file in Visual Page Editor and make sure button "Show only palette groups for which libraries are defined on the page" is not selected
> {code}
> {code}
> ASSERT:
> Follow palette groups visible on HTML 5 Palette:
> 1. Ionic 1.0
> 2. jQuery Mobile 1.4
> 3. HTML 5.0
> 2. Press the button "Show only palette groups for which libraries are defined on the page"
> ASSERT:
> No Palette groups are visible in HTML 5 Palette
> *Test case 2:*
> 1. Open follow html file in Visual Page Editor and make sure button "Show only palette groups for which libraries are defined on the page" is not selected
> {code:html}
> <!DOCTYPE html>
> <html>
> <head>
> <meta name="viewport" content="width=device-width, initial-scale=1">
> <link rel="stylesheet" href="http://code.ionicframework.com/1.0.0-beta.13/css/ionic.css" />
> <script src="http://code.ionicframework.com/1.0.0-beta.13/js/ionic.bundle.js"></script>
> <meta charset="UTF-8">
> <title>Insert title here</title>
> </head>
> <body>
> </body>
> </html>
> {code}
> ASSERT:
> Follow palette groups visible on HTML 5 Palette:
> 1. Ionic 1.0
> 2. jQuery Mobile 1.4
> 3. HTML 5.0
> 2. Press the button "Show only palette groups for which libraries are defined on the page"
> ASSERT:
> Follow palette groups visible on HTML 5 Palette:
> 1. Ionic 1.0
> 2. HTML 5.0
> *Test case 3:*
> 1. Open follow html file in Visual Page Editor and make sure button "Show only palette groups for which libraries are defined on the page" is not selected
> {code:html}
> <!DOCTYPE html>
> <html>
> <head>
> <meta name="viewport" content="width=device-width, initial-scale=1">
> <link rel="stylesheet" href="http://code.jquery.com/mobile/1.4.4/jquery.mobile-1.4.4.min.css" />
> <script src="http://code.jquery.com/jquery-2.0.3.min.js"></script>
> <script src="http://code.jquery.com/mobile/1.4.4/jquery.mobile-1.4.4.min.js"></script>
> <meta charset="UTF-8">
> <title>Insert title here</title>
> </head>
> <body>
> </body>
> </html>
> {code}
> ASSERT:
> Follow palette groups visible on HTML 5 Palette:
> 1. Ionic 1.0
> 2. jQuery Mobile 1.4
> 3. HTML 5.0
> 2. Press the button "Show only palette groups for which libraries are defined on the page"
> ASSERT:
> Follow palette groups visible on HTML 5 Palette:
> 1. jQuery Mobile 1.4
> 2. HTML 5.0
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-18188) HTML5 Palette: filter to show only palette groups for which libraries are defined on the page
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18188?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-18188:
----------------------------------------
[~vpakan] make sure you have org.jboss.tools.jst.angularjs.feature installed. The Ionic palette is a part of our angularJS feature. Anyway this issue (if it's an issue) is a separate one. The filter is in Alpha1 and please open a new issue for remaining problems.
> HTML5 Palette: filter to show only palette groups for which libraries are defined on the page
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-18188
> URL: https://issues.jboss.org/browse/JBIDE-18188
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.3.x
> Reporter: Daniel Azarov
> Assignee: Daniel Azarov
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Alpha1
>
> Attachments: Filter1.png, Filter2.png
>
>
> *Test case 1:*
> 1. Open empty html file in Visual Page Editor and make sure button "Show only palette groups for which libraries are defined on the page" is not selected
> {code}
> {code}
> ASSERT:
> Follow palette groups visible on HTML 5 Palette:
> 1. Ionic 1.0
> 2. jQuery Mobile 1.4
> 3. HTML 5.0
> 2. Press the button "Show only palette groups for which libraries are defined on the page"
> ASSERT:
> No Palette groups are visible in HTML 5 Palette
> *Test case 2:*
> 1. Open follow html file in Visual Page Editor and make sure button "Show only palette groups for which libraries are defined on the page" is not selected
> {code:html}
> <!DOCTYPE html>
> <html>
> <head>
> <meta name="viewport" content="width=device-width, initial-scale=1">
> <link rel="stylesheet" href="http://code.ionicframework.com/1.0.0-beta.13/css/ionic.css" />
> <script src="http://code.ionicframework.com/1.0.0-beta.13/js/ionic.bundle.js"></script>
> <meta charset="UTF-8">
> <title>Insert title here</title>
> </head>
> <body>
> </body>
> </html>
> {code}
> ASSERT:
> Follow palette groups visible on HTML 5 Palette:
> 1. Ionic 1.0
> 2. jQuery Mobile 1.4
> 3. HTML 5.0
> 2. Press the button "Show only palette groups for which libraries are defined on the page"
> ASSERT:
> Follow palette groups visible on HTML 5 Palette:
> 1. Ionic 1.0
> 2. HTML 5.0
> *Test case 3:*
> 1. Open follow html file in Visual Page Editor and make sure button "Show only palette groups for which libraries are defined on the page" is not selected
> {code:html}
> <!DOCTYPE html>
> <html>
> <head>
> <meta name="viewport" content="width=device-width, initial-scale=1">
> <link rel="stylesheet" href="http://code.jquery.com/mobile/1.4.4/jquery.mobile-1.4.4.min.css" />
> <script src="http://code.jquery.com/jquery-2.0.3.min.js"></script>
> <script src="http://code.jquery.com/mobile/1.4.4/jquery.mobile-1.4.4.min.js"></script>
> <meta charset="UTF-8">
> <title>Insert title here</title>
> </head>
> <body>
> </body>
> </html>
> {code}
> ASSERT:
> Follow palette groups visible on HTML 5 Palette:
> 1. Ionic 1.0
> 2. jQuery Mobile 1.4
> 3. HTML 5.0
> 2. Press the button "Show only palette groups for which libraries are defined on the page"
> ASSERT:
> Follow palette groups visible on HTML 5 Palette:
> 1. jQuery Mobile 1.4
> 2. HTML 5.0
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBDS-3258) Docker Tooling (Advanced Integration)
by Burr Sutter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3258?page=com.atlassian.jira.plugin.... ]
Burr Sutter commented on JBDS-3258:
-----------------------------------
It is certainly possible that we can merge these jiras and my learning has grown over the last couple of months - I will attempt to "rewrite" them via this comment:
0) assumes boot2docker has been dowloaded and installed - if the end-user has not yet downloaded and installed boot2docker, then we assume the end-user has remote Docker Daemon and will need to point to a URL for the Docker Daemon running on another machine on the network. I do not believe the Docker Daemon has much in the way of security but we will need to consider that when talking to a remote docker
1) boot2docker init - handled by boot2docker - end-user will be responsible for running this themselves outside of the IDE
2) boot2docker up - handled by boot2docker - end-user will be responsible for running this themselves outside of the IDE
3) boot2docker ip run by the end-user manually, outside of JBDS. The end-user is responsible for making note of this ip address has he/she will need it to run tests of his/her web apps. boot2docker currently provides a start.sh that works on Mac and Windows that handles "init", "up" and "ip" and on Windows it also issues a "ssh" so that the end-user is dropped into the boot2docker-vm shell. Basically this shell (command prompt) will be open in the background IF the end-user is running a local copy of Docker (via boot2docker).
4) I, the Java developer, need to browse a docker registry (either DockerHub or private registry), identify the image that I wish to have local and download (docker pull) for that image+tag.
5) docker ps - allows me to see all the currently running containers
6) docker rm - allows me to remove (may require a stop/kill) a particular running container
7) docker images - allows me to see all the available (on the particular docker daemon) docker images
8) docker rmi - allows me to remove a particular image (provides an error if there is still a container associated with the image)
9) docker pull - allows me to pull a docker image from the previously designated docker registry (local, public, private)
10) docker run -it -p 8080:8080 -p 9990:9990 --link mysqldb:mydatabaseserver centos/wildfly
assumes we have a way to let the end-user see the logs
11) docker run -p 8080:8080 -p 9990:9990 --link mysqldb:mydatabaseserver centos/wildfly -d
12) if run with -d, then we need to support "docker logs container_id"
13) I can then deploy my .war or .ear to the running app server
14) I can restart the running app server in debug mode and run the debugger
15) I can undeploy and redeploy my .war or .ear
16) I can stop/restart the running, embedded app server
17) I can then commit (docker commit)
18) then I can publish my changes (docker push) to the previously configured registrry
19) also, I can use "docker build" with a previously created Dockerfile and "docker push" its output
> Docker Tooling (Advanced Integration)
> -------------------------------------
>
> Key: JBDS-3258
> URL: https://issues.jboss.org/browse/JBDS-3258
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: openshift, requirements
> Reporter: Burr Sutter
> Assignee: Xavier Coulon
>
> Once significant delta between the "basic" and advanced scenarios is that here I wish to custom craft my own docker images instead of using an existing one - where my custom crafted image includes my .war or .ear.
> In addition to the basic integrations of pull, run, stop, commit and push
> boot2docker init
> boot2docker up
> boot2docker down
> boot2docker ip
> docker run -d
> docker ps
> docker rm
> docker rmi
> docker build
> End-user steps:
> 0) assumes boot2docker has been dowloaded and installed
> 1) boot2docker init : required to to insure boot2docker-vm is properly initialized
> 2) boot2docker up : starts the VirtualBox boot2docker-vm
> 3) boot2docker ip : returns the IP address - this will be vital when it comes to testing - it would need to be integrated with our Run - As on Docker capability.
> 4) docker run -i -t -p 80:8080 jboss/wildfly -d : the -d means detached, I may need to run N containers simultaneously
> 5) docker ps : allows me to see all my currently running containers
> 6) docker rm : allows me to kill a currently running container
> 7) docker rmi : allows me to remove a local image
> 8) docker build : assumes that I have crafted a Dockerfile - this will create the local image - with my .war or .ear embedded
> 9) docker run : this new created image
> The docker build scenario can be triggered via a Maven plugin
> The docker build scenario can also be triggered via an Eclipse menu option (like a Maven install)
> We need to figure out the file-system layout so that the Dockerfile and the maven project are all nicely checked into git/svn. So that Jenkins can pick up this repository and perform an automated "docker build" (post Maven install) and then run all the appropriate unit, integration and functional tests.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months