[JBoss JIRA] (JBIDE-17032) Ability to configure jQuery / jQuery Mobile versions injected by Palette
by Vineet Reynolds (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17032?page=com.atlassian.jira.plugi... ]
Vineet Reynolds commented on JBIDE-17032:
-----------------------------------------
I think hardcoding versions is safe, for the default versions. But, if we can fetch info about new version releases, that would be good if we can get it right. Getting the latest version of jQuery Core correctly would be important.
For minor version updates to jQM, I've noted that the team does not change the major version numbers for jQuery support; patch updates to jQuery are accepted. So, hypothetically, in the future, jQueryMobile 1.4.3 will work against jQuery 1.8 - 1.10.3 / 2.0.4 (where all three - jQM 1.4.3, and jQ 1.10.3 / 2.0.4 are unreleased at the moment), because jQM 1.4 was tested on jQuery 1.8-1.10/2.0).
A pattern search for 1.4.* and 2.0.* would therefore be fine for now. But it would be even better if we can store this info on a server, have JBDS access it and update itself correctly. We can therefore control what versions are supported in JBDS; I know it is fairly impossible that a minor or patch update should break JBDS, so treat this as a conservative answer.
And yes, it is better to use the latest versions unless the user changes his choice.
> Ability to configure jQuery / jQuery Mobile versions injected by Palette
> ------------------------------------------------------------------------
>
> Key: JBIDE-17032
> URL: https://issues.jboss.org/browse/JBIDE-17032
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Reporter: Alexey Kazakov
> Assignee: Viacheslav Kabanovich
> Priority: Critical
> Labels: new_and_noteworthy
> Fix For: 4.2.0.Beta2
>
> Attachments: 2014-04-25 17.02.bmml, 2014-04-25 17.02.bmml, 2014-04-25 17.02.png, css.gif, JS-CSSWizBan.png, js.png, lib.png, NextPage.bmml, NextPage.bmml, NextPage.bmml, NextPage.png, Preferences.bmml, Preferences.png, SeparateDialog.bmml, SeparateDialog.png
>
>
> Currently the following versions are injected for JQM 1.4:
> {code}
> <script src="http://code.jquery.com/jquery-1.10.2.min.js"></script>
> <script src="http://code.jquery.com/mobile/1.4.2/jquery.mobile-1.4.2.min.js"></script>
> {code}
> And for JQM 1.3:
> {code}
> <script src="http://code.jquery.com/jquery-1.9.1.min.js"></script>
> <script src="http://code.jquery.com/mobile/1.3.2/jquery.mobile-1.3.2.min.js"></script>
> {code}
> It would be good if we have a place where users can configure what versions of JQ and JQM they want to inject.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (JBIDE-17032) Ability to configure jQuery / jQuery Mobile versions injected by Palette
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17032?page=com.atlassian.jira.plugi... ]
Daniel Azarov updated JBIDE-17032:
----------------------------------
Attachment: JS-CSSWizBan.png
> Ability to configure jQuery / jQuery Mobile versions injected by Palette
> ------------------------------------------------------------------------
>
> Key: JBIDE-17032
> URL: https://issues.jboss.org/browse/JBIDE-17032
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Reporter: Alexey Kazakov
> Assignee: Viacheslav Kabanovich
> Priority: Critical
> Labels: new_and_noteworthy
> Fix For: 4.2.0.Beta2
>
> Attachments: 2014-04-25 17.02.bmml, 2014-04-25 17.02.bmml, 2014-04-25 17.02.png, css.gif, JS-CSSWizBan.png, js.png, lib.png, NextPage.bmml, NextPage.bmml, NextPage.bmml, NextPage.png, Preferences.bmml, Preferences.png, SeparateDialog.bmml, SeparateDialog.png
>
>
> Currently the following versions are injected for JQM 1.4:
> {code}
> <script src="http://code.jquery.com/jquery-1.10.2.min.js"></script>
> <script src="http://code.jquery.com/mobile/1.4.2/jquery.mobile-1.4.2.min.js"></script>
> {code}
> And for JQM 1.3:
> {code}
> <script src="http://code.jquery.com/jquery-1.9.1.min.js"></script>
> <script src="http://code.jquery.com/mobile/1.3.2/jquery.mobile-1.3.2.min.js"></script>
> {code}
> It would be good if we have a place where users can configure what versions of JQ and JQM they want to inject.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (JBIDE-16540) IStructuredDocumentRegion management failed when generating Page from Palette
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16540?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-16540:
-----------------------------------
Fix Version/s: 4.2.x
(was: 4.2.0.Beta2)
> IStructuredDocumentRegion management failed when generating Page from Palette
> -----------------------------------------------------------------------------
>
> Key: JBIDE-16540
> URL: https://issues.jboss.org/browse/JBIDE-16540
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.2.0.Alpha2
> Reporter: Lucia Jelinkova
> Assignee: Daniel Azarov
> Priority: Minor
> Fix For: 4.2.x
>
> Attachments: .log, screencast.ogv
>
>
> When creating a Page on html page, the following exception is written to error log:
> {code}org.eclipse.wst.xml.core.internal.document.StructuredDocumentRegionManagementException: IStructuredDocumentRegion management failed.
> at org.eclipse.wst.xml.core.internal.document.XMLModelParser.removeStructuredDocumentRegion(XMLModelParser.java:2265)
> at org.eclipse.wst.xml.core.internal.document.XMLModelParser.removeStructuredDocumentRegion(XMLModelParser.java:2288)
> at org.eclipse.wst.xml.core.internal.document.XMLModelParser.replaceStructuredDocumentRegions(XMLModelParser.java:2339)
> at org.eclipse.wst.xml.core.internal.document.DOMModelImpl.nodesReplaced(DOMModelImpl.java:737)
> at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument._fireEvent(BasicStructuredDocument.java:600)
> at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.fireStructuredDocumentEvent(BasicStructuredDocument.java:1198)
> at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.internalReplaceText(BasicStructuredDocument.java:1979)
> 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.jboss.tools.jst.web.ui.internal.editor.jspeditor.dnd.MobilePaletteInsertHelper.writeBuffer(MobilePaletteInsertHelper.java:124)
> at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.dnd.MobilePaletteInsertHelper.insertNode(MobilePaletteInsertHelper.java:150)
> at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.dnd.MobilePaletteInsertHelper.insertJsCss(MobilePaletteInsertHelper.java:381)
> at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.dnd.MobilePaletteInsertHelper.modify(MobilePaletteInsertHelper.java:103)
> at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.dnd.MobilePaletteInsertHelper.isMobile(MobilePaletteInsertHelper.java:86)
> at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.dnd.JSPPaletteInsertHelper.modify(JSPPaletteInsertHelper.java:45)
> at org.jboss.tools.common.model.ui.views.palette.PaletteInsertHelper.insertIntoEditor(PaletteInsertHelper.java:121)
> at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.dnd.FileDropCommand.run(FileDropCommand.java:67)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2333)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2315)
> at org.jboss.tools.common.model.ui.editors.dnd.DefaultDropCommand.execute(DefaultDropCommand.java:133)
> at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.dnd.PaletteDropCommand.execute(PaletteDropCommand.java:117)
> at org.jboss.tools.jst.web.ui.palette.html.wizard.AbstractNewHTMLWidgetWizard.doPerformFinish(AbstractNewHTMLWidgetWizard.java:94)
> at org.jboss.tools.jst.web.ui.palette.html.jquery.wizard.NewJQueryWidgetWizard.doPerformFinish(NewJQueryWidgetWizard.java:106)
> at org.jboss.tools.jst.web.ui.palette.html.wizard.AbstractNewHTMLWidgetWizard$1.run(AbstractNewHTMLWidgetWizard.java:78)
> at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:465)
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:373)
> at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1055)
> at org.jboss.tools.jst.web.ui.palette.html.wizard.AbstractNewHTMLWidgetWizard.performFinish(AbstractNewHTMLWidgetWizard.java:82)
> at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:851)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:437)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:633)
> 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:4423)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3771)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3391)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:827)
> at org.eclipse.jface.window.Window.open(Window.java:803)
> at org.jboss.tools.common.model.ui.editors.dnd.DefaultDropCommand.execute(DefaultDropCommand.java:110)
> at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.JSPTextEditor$3.run(JSPTextEditor.java:740)
> at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.JSPTextEditor.runDropCommand(JSPTextEditor.java:759)
> at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.JSPMultiPageEditor.runDropCommand(JSPMultiPageEditor.java:864)
> 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:622)
> 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:393)
> 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:142)
> 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:4423)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3771)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3391)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1122)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1006)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:146)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:615)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:566)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:125)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:109)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:80)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:372)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:226)
> 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:622)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (JBIDE-17240) downloadruntimes verifying credentials should not follow redirects
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17240?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-17240.
---------------------------------
Assignee: Rob Stryker
Fix Version/s: 4.2.0.Beta2
Resolution: Done
The workflow no longer uses redirect requests.
> downloadruntimes verifying credentials should not follow redirects
> ------------------------------------------------------------------
>
> Key: JBIDE-17240
> URL: https://issues.jboss.org/browse/JBIDE-17240
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.2.0.Beta1
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.2.0.Beta2
>
>
> This is a weird bug, but I need a jira, so here goes.
> First, this bug is not actually replicatable in jbosstools. IT is only replicatable in fuseide. When validating credentials in downloadruntime, we setFollowRedirects to true, when it should be false.
> Magically, though, eap still functions properly (no idea why) while the url to download a fuse runtime fails with status 200 (as it should)
> Status 200 means 'ok' and status 302 means 'temporarily moved'. The 200 is coming because it is following the 302 redirect to the next url, and getting a 200 status.
> However, why EAP gets the 302 status directly, while the fuse url follows the redirect, i have no idea. It would seem to me that the eap should also follow the 302 redirect and return a 200 status, but it doesn't.
> Either way, the fix is to set follow redirect to false. Then works for all runtimes.
> Please test that eap6.x downloads properly after this is marked as resolved.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (JBIDE-17240) downloadruntimes verifying credentials should not follow redirects
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-17240:
-----------------------------------
Summary: downloadruntimes verifying credentials should not follow redirects
Key: JBIDE-17240
URL: https://issues.jboss.org/browse/JBIDE-17240
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: runtime-detection
Affects Versions: 4.2.0.Beta1
Reporter: Rob Stryker
This is a weird bug, but I need a jira, so here goes.
First, this bug is not actually replicatable in jbosstools. IT is only replicatable in fuseide. When validating credentials in downloadruntime, we setFollowRedirects to true, when it should be false.
Magically, though, eap still functions properly (no idea why) while the url to download a fuse runtime fails with status 200 (as it should)
Status 200 means 'ok' and status 302 means 'temporarily moved'. The 200 is coming because it is following the 302 redirect to the next url, and getting a 200 status.
However, why EAP gets the 302 status directly, while the fuse url follows the redirect, i have no idea. It would seem to me that the eap should also follow the 302 redirect and return a 200 status, but it doesn't.
Either way, the fix is to set follow redirect to false. Then works for all runtimes.
Please test that eap6.x downloads properly after this is marked as resolved.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (JBIDE-15897) Server Adapter Context Menu: make all relevant OpenShift Explorer actions available from Server Adapter
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15897?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-15897:
-------------------------------------
Affects: Documentation (Ref Guide, User Guide, etc.),User Experience (was: Documentation (Ref Guide, User Guide, etc.))
> Server Adapter Context Menu: make all relevant OpenShift Explorer actions available from Server Adapter
> -------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-15897
> URL: https://issues.jboss.org/browse/JBIDE-15897
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.2.0.Final
> Reporter: Max Rydahl Andersen
> Assignee: Max Rydahl Andersen
> Labels: server_adapter
> Fix For: 4.2.0.Beta2
>
> Attachments: explorer-context-menu.png, explorer-context-menu.png, server-adapter-context-menu.png, server-adapter-context-menu.png
>
> Original Estimate: 1 day
> Time Spent: 2 days
> Remaining Estimate: 0 minutes
>
> JBIDE-11841 was done earlier but only added the missing actions - when new actions are added we tend to forget to add them.
> Explorer:
> !explorer-context-menu.png!
> Server adapter:
> !server-adapter-context-menu.png!
> We should make it so these actions (when relevant) gets added to both places (openshift explorer / server adapter) and optimally also available in an OpenShift context menu on a project.
> Meaning you don't have to navigate to explorer view constantly.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (JBIDE-15897) Server Adapter Context Menu: make all relevant OpenShift Explorer actions available from Server Adapter
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15897?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-15897 at 5/7/14 12:49 PM:
-------------------------------------------------------------------
we're missing the following in the server context menu:
- Import Application (not shown if the project already exists)
- Edit Embedded Cartidges
- Application Details
the following dont make a lot of sense:
- Delete Application (if we delete the application, we'd have to delete the adapter too. An adapter without it's application is useless)
- Refresh
was (Author: adietish):
we're missing the following in the server context menu:
- Import Application (not shown if the project already exists)
- Edit Embedded Cartidges
- Application Details
- Refresh
the following dont make a lot of sense:
- Delete Application (if we delete the application, we'd have to delete the adapter too. An adapter without it's application is useless)
> Server Adapter Context Menu: make all relevant OpenShift Explorer actions available from Server Adapter
> -------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-15897
> URL: https://issues.jboss.org/browse/JBIDE-15897
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.2.0.Final
> Reporter: Max Rydahl Andersen
> Assignee: Max Rydahl Andersen
> Labels: server_adapter
> Fix For: 4.2.0.Beta2
>
> Attachments: explorer-context-menu.png, explorer-context-menu.png, server-adapter-context-menu.png, server-adapter-context-menu.png
>
> Original Estimate: 1 day
> Time Spent: 2 days
> Remaining Estimate: 0 minutes
>
> JBIDE-11841 was done earlier but only added the missing actions - when new actions are added we tend to forget to add them.
> Explorer:
> !explorer-context-menu.png!
> Server adapter:
> !server-adapter-context-menu.png!
> We should make it so these actions (when relevant) gets added to both places (openshift explorer / server adapter) and optimally also available in an OpenShift context menu on a project.
> Meaning you don't have to navigate to explorer view constantly.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (JBDS-2793) Align JDF and WFK quickstarts/examples/tutorials with a project layout that works with eclipse tooling
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2793?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-2793:
-------------------------------------------
assign to [~vineet.reynolds] to validate this approach will work for JDF/WFK team.
One concern raised was that using Eclipse link folders would be portable for end users, but cordova-cli used by QE could not validate it headless (would need manual/swtbot testing via eclipse for examples)
> Align JDF and WFK quickstarts/examples/tutorials with a project layout that works with eclipse tooling
> ------------------------------------------------------------------------------------------------------
>
> Key: JBDS-2793
> URL: https://issues.jboss.org/browse/JBDS-2793
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: aerogear-hybrid
> Reporter: Max Rydahl Andersen
> Assignee: Vineet Reynolds
> Attachments: directoryStructure.tiff
>
>
> wfk/jdf has or will get quickstarts/tutorials that works with cordova.
> Needs to sync up with them on what we support/dont support.
> Current suggestion is that the cordova app should be *separate* from the webapp, not "mixed" in.
> With a structure like:
> TicketMonster/
> www/config.xml
> plugins
> .project
> platforms
> ios
> android
> it can build both with cordova-cli and the eclipse tools (eclipse will ignore platforms directory)
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (JBDS-2793) Align JDF and WFK quickstarts/examples/tutorials with a project layout that works with eclipse tooling
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2793?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen updated JBDS-2793:
--------------------------------------
Assignee: Vineet Reynolds (was: Max Rydahl Andersen)
> Align JDF and WFK quickstarts/examples/tutorials with a project layout that works with eclipse tooling
> ------------------------------------------------------------------------------------------------------
>
> Key: JBDS-2793
> URL: https://issues.jboss.org/browse/JBDS-2793
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: aerogear-hybrid
> Reporter: Max Rydahl Andersen
> Assignee: Vineet Reynolds
> Attachments: directoryStructure.tiff
>
>
> wfk/jdf has or will get quickstarts/tutorials that works with cordova.
> Needs to sync up with them on what we support/dont support.
> Current suggestion is that the cordova app should be *separate* from the webapp, not "mixed" in.
> With a structure like:
> TicketMonster/
> www/config.xml
> plugins
> .project
> platforms
> ios
> android
> it can build both with cordova-cli and the eclipse tools (eclipse will ignore platforms directory)
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months