[JBoss JIRA] (JBDS-3138) Central has Beta2 content - causing bugs/mismatches for cordova/aerogear tooling
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3138?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3138:
-----------------------------
Attachment: jbds8-cr1-central-site-contains-Beta2-bits.png
Looks like the CR1 site does include Beta2 bits. Which is odd because the Beta3 site contains Beta3 bits. Investigating...
> Central has Beta2 content - causing bugs/mismatches for cordova/aerogear tooling
> --------------------------------------------------------------------------------
>
> Key: JBDS-3138
> URL: https://issues.jboss.org/browse/JBDS-3138
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: browsersim, discovery, updatesite
> Reporter: Burr Sutter
> Assignee: Konstantin Marmalyukov
> Priority: Blocker
> Labels: respin-a
> Fix For: 8.0.0.CR1
>
> Attachments: JBDS3138.png, jbds8-cr1-central-site-contains-Beta2-bits.png, Screenshot 2014-08-31 13.53.05.png
>
>
> Fresh installation of JBDS 8 CR1
> Hybrid tools installed by clicking on Hybrid Mobile Project in JBoss Central.
> I did receive a warning during the installation
> http://screencast.com/t/cz8fiK8SD
> CordovaSim is missing
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-16714) Embed wizard, Application wizard: Embed same cartridge with different version should show warning
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16714?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-16714:
------------------------------------------
with the move to a backend in OpenShift v3 with a new REST interface this will most likely become obsolte.
> Embed wizard, Application wizard: Embed same cartridge with different version should show warning
> -------------------------------------------------------------------------------------------------
>
> Key: JBIDE-16714
> URL: https://issues.jboss.org/browse/JBIDE-16714
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.2.0.Alpha2
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Priority: Minor
> Labels: application_wizard, embed_wizard
> Fix For: 4.2.x
>
>
> Nowadays, when on OpenShift Online are available multiple cartridges differentiated only by version (e.g. PostgreSQL 8.4 and 9.2) there should be some kind of warning about embedding both (what could happen accidentally or by ignorance...).
> How it works now? If user choose 2 cartridges of the same type, then just the first one is embedded and while trying to embed second cartridge user get error that application has already embedded that kind of cartridge (that they cannot coexist).
> I suggest to have similar dialog as in embedding e.g. Jenkins cartridge to application without having Jenkins Application (server) etc.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-17423) BrowserSim is not opening source code of opened web page
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17423?page=com.atlassian.jira.plugi... ]
Vlado Pakan closed JBIDE-17423.
-------------------------------
Verified with JBDS 8.0.0.CR1-v20140831-0335-B201
> BrowserSim is not opening source code of opened web page
> --------------------------------------------------------
>
> Key: JBIDE-17423
> URL: https://issues.jboss.org/browse/JBIDE-17423
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 4.2.0.Beta2
> Environment: JBDS 8.0.0.Beta2-v20140525-2146-B104
> Reporter: Vlado Pakan
> Assignee: Konstantin Marmalyukov
> Priority: Blocker
> Fix For: 4.2.0.CR1
>
>
> 1. Open BrowserSim
> 2. Open page www.github.com in BrowserSim
> 3. Choose View Page Source from BrowserSim context menu
> ERROR: No source code displayed in JBDS just error message in VPE and Error Log view
> {noformat}
> java.lang.ClassCastException: org.jboss.tools.vpe.browsersim.eclipse.callbacks.StringInput cannot be cast to org.eclipse.ui.IFileEditorInput
> at org.jboss.tools.vpe.preview.editor.VpeEditorPartFactory.createVisualEditor(VpeEditorPartFactory.java:35)
> at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.JSPMultiPageEditor.createPagesForVPE(JSPMultiPageEditor.java:589)
> at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.JSPMultiPageEditor.createPages(JSPMultiPageEditor.java:506)
> at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:362)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.createPartControl(CompatibilityPart.java:140)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityEditor.createPartControl(CompatibilityEditor.java:99)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.create(CompatibilityPart.java:321)
> at sun.reflect.GeneratedMethodAccessor143.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55)
> at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:888)
> at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:869)
> at org.eclipse.e4.core.internal.di.InjectorImpl.inject(InjectorImpl.java:120)
> at org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:337)
> at org.eclipse.e4.core.internal.di.InjectorImpl.make(InjectorImpl.java:258)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.make(ContextInjectionFactory.java:162)
> at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.createFromBundle(ReflectionContributionFactory.java:104)
> at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.doCreate(ReflectionContributionFactory.java:73)
> at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.create(ReflectionContributionFactory.java:55)
> at org.eclipse.e4.ui.workbench.renderers.swt.ContributedPartRenderer.createWidget(ContributedPartRenderer.java:127)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createWidget(PartRenderingEngine.java:984)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:663)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:767)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$2(PartRenderingEngine.java:738)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$7.run(PartRenderingEngine.java:732)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:716)
> at org.eclipse.e4.ui.workbench.renderers.swt.StackRenderer.showTab(StackRenderer.java:1250)
> at org.eclipse.e4.ui.workbench.renderers.swt.LazyStackRenderer$1.handleEvent(LazyStackRenderer.java:66)
> at org.eclipse.e4.ui.services.internal.events.UIEventHandler$1.run(UIEventHandler.java:40)
> at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:187)
> at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:156)
> at org.eclipse.swt.widgets.Display.syncExec(Display.java:4598)
> at org.eclipse.e4.ui.internal.workbench.swt.E4Application$1.syncExec(E4Application.java:207)
> at org.eclipse.e4.ui.services.internal.events.UIEventHandler.handleEvent(UIEventHandler.java:36)
> at org.eclipse.equinox.internal.event.EventHandlerWrapper.handleEvent(EventHandlerWrapper.java:197)
> at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:197)
> at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
> at org.eclipse.equinox.internal.event.EventAdminImpl.dispatchEvent(EventAdminImpl.java:135)
> at org.eclipse.equinox.internal.event.EventAdminImpl.sendEvent(EventAdminImpl.java:78)
> at org.eclipse.equinox.internal.event.EventComponent.sendEvent(EventComponent.java:39)
> at org.eclipse.e4.ui.services.internal.events.EventBroker.send(EventBroker.java:81)
> at org.eclipse.e4.ui.internal.workbench.UIEventPublisher.notifyChanged(UIEventPublisher.java:59)
> at org.eclipse.emf.common.notify.impl.BasicNotifierImpl.eNotify(BasicNotifierImpl.java:374)
> at org.eclipse.e4.ui.model.application.ui.impl.ElementContainerImpl.setSelectedElement(ElementContainerImpl.java:171)
> at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.showElementInWindow(ModelServiceImpl.java:479)
> at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.bringToTop(ModelServiceImpl.java:445)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.delegateBringToTop(PartServiceImpl.java:692)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.showPart(PartServiceImpl.java:1123)
> at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:3127)
> at org.eclipse.ui.internal.WorkbenchPage.access$23(WorkbenchPage.java:3049)
> at org.eclipse.ui.internal.WorkbenchPage$9.run(WorkbenchPage.java:3031)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3026)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2990)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2971)
> at org.jboss.tools.vpe.browsersim.eclipse.callbacks.ViewSourceCallback.openInMemoryHtmlEditor(ViewSourceCallback.java:100)
> at org.jboss.tools.vpe.browsersim.eclipse.callbacks.ViewSourceCallback.access$0(ViewSourceCallback.java:83)
> at org.jboss.tools.vpe.browsersim.eclipse.callbacks.ViewSourceCallback$1.run(ViewSourceCallback.java:75)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3781)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3419)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1152)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1033)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:635)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:578)
> 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:379)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:233)
> 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)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-16720) Server Adapter: Allow easier access to openshift operations from jboss servers
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16720?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-16720:
-------------------------------------
Summary: Server Adapter: Allow easier access to openshift operations from jboss servers (was: Allow easier access to openshift operations from jboss servers)
> Server Adapter: Allow easier access to openshift operations from jboss servers
> ------------------------------------------------------------------------------
>
> Key: JBIDE-16720
> URL: https://issues.jboss.org/browse/JBIDE-16720
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift, server
> Affects Versions: 4.1.1.Final
> Reporter: Mark Drilling
> Fix For: 4.2.x
>
>
> We currently have a couple issues with connecting to an OpenShift Data Virtualization instance from the tooling. I'm aware that issues are being addressed for future release, others I'm not sure. This is intended to help guide your development to accommodate this use case.
> Our expected usage with Data Virtualization is a bit different than some others. With DV we expect to deploy via a DV cartridge to OpenShift, then connect to the OpenShift DV instance as a remote server. We typically would not deploy using git push.
> Currently, we connect to an OpenShift DV instance like this:
> 1) Deploy DV cartridge via OpenShift web console.
> 2) Port forward from command line using rhc port-forward
> 3) Set up EAP server instance in the tooling, mark as externally managed and start it. From there we can connect to the DV instance and continue with modeling and deployments in Teiid Designer perspective
> The issues we observed:
> 1) Creation of the OpenShift 'server' forces a git repo to be copied locally. We'd like to simply create the 'OpenShift server' without cloning the repo.
> 2) Can't deploy our downloadable cartridge from the wizard. I believe OpenShift is now (or will soon) allow downloadable carts to be registered, so this problem should be solved as the cart will show up in the cartridge list.
> Our current method of connecting is ok for now, but a simpler usage of the OpenShift server adapter would allow us to more easily manage the instance (e.g. port-forward without going to the command line, viewing logs, etc.)
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18147) Port forwarding, Environment Variables: Port forwarding cause tearing down the session
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18147?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-18147:
-------------------------------------
Summary: Port forwarding, Environment Variables: Port forwarding cause tearing down the session (was: Port forwarding cause tearing down the session)
> Port forwarding, Environment Variables: Port forwarding cause tearing down the session
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-18147
> URL: https://issues.jboss.org/browse/JBIDE-18147
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.CR1
> Reporter: Marián Labuda
> Fix For: 4.2.0.CR2
>
>
> After starting and stopping port forwarding there happens something wrong with session / ssh calling. I found it in Environment variables shell after creating env. variable and clicking on Refresh button. Following error has shown in log and environment variable from table was not removed, although it should be (Refresh button update local environment variables to environment variable of an existing OpenShift application).
> {code}
> com.openshift.client.OpenShiftSSHOperationException: Failed to execute remote ssh command "eap"
> at com.openshift.internal.client.ApplicationResource.sshExecCmd(ApplicationResource.java:871)
> at com.openshift.internal.client.ApplicationResource.loadPorts(ApplicationResource.java:840)
> at com.openshift.internal.client.ApplicationResource.refresh(ApplicationResource.java:614)
> at org.jboss.tools.openshift.express.internal.ui.wizard.environment.EditEnvironmentVariablesWizardModel.refreshEnvironmentVariables(EditEnvironmentVariablesWizardModel.java:35)
> at org.jboss.tools.openshift.express.internal.ui.wizard.environment.EnvironmentVariablesWizardPage$RefreshEnvironmentVariablesJob.doRun(EnvironmentVariablesWizardPage.java:292)
> at org.jboss.tools.openshift.express.internal.ui.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> Caused by: com.jcraft.jsch.JSchException: session is down
> at com.jcraft.jsch.Session.openChannel(Session.java:843)
> at com.openshift.internal.client.ApplicationResource.sshExecCmd(ApplicationResource.java:865)
> ... 6 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBDS-3130) [RFE] Add tooling to manage openshift databases
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBDS-3130?page=com.atlassian.jira.plugin.... ]
Andre Dietisheim updated JBDS-3130:
-----------------------------------
Fix Version/s: 9.0.x
> [RFE] Add tooling to manage openshift databases
> -----------------------------------------------
>
> Key: JBDS-3130
> URL: https://issues.jboss.org/browse/JBDS-3130
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: openshift
> Affects Versions: 7.1.1.GA
> Environment: All
> Reporter: Tim Williams
> Assignee: Max Rydahl Andersen
> Priority: Minor
> Fix For: 8.0.x, 9.0.x
>
>
> In OpenShift, a scaled application will have numerous 'gears', each running a copy of the developer's code. If the developer is running a database, there will be only one gear containing this database.
> To export/import/backup/restore the database, a user must ssh to the specific gear that holds the database cartridge. The only current way to do this in JBDS is to print all the environment variables and look for the following:
> $OPENSHIFT_MYSQL_DB_GEAR_UUID
> $OPENSHIFT_MYSQL_DB_GEAR_DNS
> You can then use these values in a terminal to ssh to the database gear:
> $ ssh $OPENSHIFT_MYSQL_DB_GEAR_UUID@$OPENSHIFT_MYSQL_DB_GEAR_DNS
> It would be helpful to have some kind of tooling to either ssh into this gear directly through JBDS, or at least print the ssh command (above) using the environment variables from the gear.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months