[JBoss JIRA] (JBDS-3282) Screencasts: OpenShift v3
by Rodney Russ (JIRA)
[ https://issues.jboss.org/browse/JBDS-3282?page=com.atlassian.jira.plugin.... ]
Rodney Russ updated JBDS-3282:
------------------------------
Priority: Minor (was: Major)
> Screencasts: OpenShift v3
> -------------------------
>
> Key: JBDS-3282
> URL: https://issues.jboss.org/browse/JBDS-3282
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: openshift, requirements
> Reporter: Burr Sutter
> Priority: Minor
> Fix For: 9.0.0.GA
>
>
> A series of short (5 minutes), educational videos to illustrate the new capabilities of JBDS associated with OpenShift.
> Including:
> - OpenShift's new web UI
> - OpenShift Explorer in the context of v3
> - perhaps an overview of Kubernetes, depends on how "pods" become visible to our end-user
> - an overview of Docker, depends on how 'containers" become visible to our end-user
> and all the typical start, stop, add, delete/remove, view logs, set env vars, etc.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBDS-3282) Screencasts: OpenShift v3
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3282?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-3282:
-----------------------------
CDW release: + (was: ?)
> Screencasts: OpenShift v3
> -------------------------
>
> Key: JBDS-3282
> URL: https://issues.jboss.org/browse/JBDS-3282
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: openshift, requirements
> Reporter: Burr Sutter
> Fix For: 9.0.0.GA
>
>
> A series of short (5 minutes), educational videos to illustrate the new capabilities of JBDS associated with OpenShift.
> Including:
> - OpenShift's new web UI
> - OpenShift Explorer in the context of v3
> - perhaps an overview of Kubernetes, depends on how "pods" become visible to our end-user
> - an overview of Docker, depends on how 'containers" become visible to our end-user
> and all the typical start, stop, add, delete/remove, view logs, set env vars, etc.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBDS-3282) Screencasts: OpenShift v3
by Rodney Russ (JIRA)
[ https://issues.jboss.org/browse/JBDS-3282?page=com.atlassian.jira.plugin.... ]
Rodney Russ updated JBDS-3282:
------------------------------
CDW devel_ack: + (was: ?)
> Screencasts: OpenShift v3
> -------------------------
>
> Key: JBDS-3282
> URL: https://issues.jboss.org/browse/JBDS-3282
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: openshift, requirements
> Reporter: Burr Sutter
> Fix For: 9.0.0.GA
>
>
> A series of short (5 minutes), educational videos to illustrate the new capabilities of JBDS associated with OpenShift.
> Including:
> - OpenShift's new web UI
> - OpenShift Explorer in the context of v3
> - perhaps an overview of Kubernetes, depends on how "pods" become visible to our end-user
> - an overview of Docker, depends on how 'containers" become visible to our end-user
> and all the typical start, stop, add, delete/remove, view logs, set env vars, etc.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBDS-2874) Support updating JBDS via BYOE (update site) w/o having to update product too
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2874?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-2874:
----------------------------------
{quote}I don't see how this allow piecemal updates ? At least that is not what is shown in the screenshots (its still updating the overall big jbds feature){quote}
To clarify Max's comment, please look carefully at the versions of the features in the screenshot. When I mocked this up locally, I went from an install of JBDS 8.0.0.Alpha1 timestamp *1516* to a mix of JBDS 8.0.0.Alpha1 Branded Product *1516* and Core Feature *1540*.
This proves you can update a *child* of the Product without having to update the product itself.
> Support updating JBDS via BYOE (update site) w/o having to update product too
> -----------------------------------------------------------------------------
>
> Key: JBDS-2874
> URL: https://issues.jboss.org/browse/JBDS-2874
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: updatesite
> Reporter: Nick Boldt
> Assignee: Len DiMaggio
> Fix For: 8.x
>
> Attachments: update-BYOE-without-updating-product_710cr1-ga-could-not-be-done-without-also-updating-product.png, update-BYOE-without-updating-product_BEFORE.png, update-BYOE-without-updating-product_result.png
>
>
> I've found a way to make it possible to update JBDS contents (eg., the Core Features) without having to update the product too. This makes the JBDS-in-Eclipse and JBDS-via-installer experience the same in terms of being able to update piecemeal - you can now update Eclipse / product OR the JBDS features, or both.
> Do we want this?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBDS-3359) Cannot install Hybrid Mobile tools onto 8.0.0 without triggering p2 remediation
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3359?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3359:
----------------------------------
The reason this happens for JBDS 8.0.0 users (who installed via the installer, and possibly BYOE / marketplace too) is that:
JBDS 8.0.0 Branded Product feature *includes* JBDS 8.0.0 Core Features feature which *includes* org.jboss.tools.vpe.browsersim.feature (version="0.0.0" in com.jboss.devstudio.core.feature/feature.xml). For JBDS 8.0.0. that's org.jboss.tools.vpe.browsersim.feature 3.6.0.Final-v20141016-1910-B34. And in JBDS 8.0.2, it's version 3.6.1.
So when you attempt to update a single part of JBDS (org.jboss.tools.vpe.browsersim.feature 3.6.0 -> 3.6.1) p2 says you can't because there's a parent feature that *INCLUDES* that child. Solution: update the parent *AND* the child at the same time, via the suggested remediation.
As I said before, the workaround here is to either
a) update JBDS to 8.0.2, then install stuff from Central, or
b) use the remediation option when installing from Central to update JBDS at the same time to 8.0.2
In terms of a solution for JBDS 8.1 that might be slightly better, we can use *require* instead of *include* in the JBDS 8.1 Core Feature, but that will only help for users of the *JBDS BYOE / Marketplace install* method. Users of the installer jar will still have to update everything.
Or we can un-reject my proposal from last year to to allow installation of the Core Feature feature in parallel to the Branded Product feature (which we could also extend to all the pieces of JBT inside JBDS, if we wanted). See JBDS-2874.
> Cannot install Hybrid Mobile tools onto 8.0.0 without triggering p2 remediation
> -------------------------------------------------------------------------------
>
> Key: JBDS-3359
> URL: https://issues.jboss.org/browse/JBDS-3359
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: aerogear-hybrid, browsersim
> Reporter: Burr Sutter
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 8.1.0.Beta1, 8.1.0.CR1
>
>
> The updatesite for JBDS 8.0.0 seems to have removed CordovaSim. When I go to install the Hybrid Mobile tools (clicking on Hybrid Mobile Project of JBoss Central), then the default action is to "not install CordovaSim".
> Windows
> http://www.screencast.com/t/Wk8js7zf6kec
> Mac OSX
> http://www.screencast.com/t/1Jz7BTwzo8P
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19109) Cordovasim: Livereload stop working after pressing 'Refresh' button from the Platform toolbar
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19109?page=com.atlassian.jira.plugi... ]
Ilya Buziuk commented on JBIDE-19109:
-------------------------------------
Pushed to 4.2.x
> Cordovasim: Livereload stop working after pressing 'Refresh' button from the Platform toolbar
> ----------------------------------------------------------------------------------------------
>
> Key: JBIDE-19109
> URL: https://issues.jboss.org/browse/JBIDE-19109
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim, cordovasim
> Affects Versions: 4.2.2.Final
> Reporter: Ilya Buziuk
> Assignee: Ilya Buziuk
> Fix For: 4.2.3.Beta1
>
>
> Both SWT and JavaFX are affected.
> Stack trace for javaFx web engine:
> {code}
> Exception in thread "JavaFX Application Thread" org.eclipse.swt.SWTException: Widget is disposed
> at org.eclipse.swt.SWT.error(SWT.java:4441)
> at org.eclipse.swt.SWT.error(SWT.java:4356)
> at org.eclipse.swt.SWT.error(SWT.java:4327)
> at org.eclipse.swt.widgets.Widget.error(Widget.java:476)
> at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:348)
> at org.eclipse.swt.widgets.Control.forceFocus(Control.java:1075)
> at org.jboss.tools.vpe.cordovasim.events.RippleInjector.inject(RippleInjector.java:68)
> at org.jboss.tools.vpe.cordovasim.events.RippleInjector.access$1(RippleInjector.java:55)
> at org.jboss.tools.vpe.cordovasim.events.RippleInjector$1.run(RippleInjector.java:44)
> at com.sun.javafx.application.PlatformImpl$6$1.run(PlatformImpl.java:301)
> at com.sun.javafx.application.PlatformImpl$6$1.run(PlatformImpl.java:298)
> at java.security.AccessController.doPrivileged(Native Method)
> at com.sun.javafx.application.PlatformImpl$6.run(PlatformImpl.java:298)
> at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
> at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2549)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3759)
> at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.startCordovaSim(CordovaSimRunner.java:114)
> at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.main(CordovaSimRunner.java:91)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBDS-3285) Git: Easy Import
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBDS-3285?page=com.atlassian.jira.plugin.... ]
Mickael Istria commented on JBDS-3285:
--------------------------------------
If in main site/installer, that would mean that's we'd need the framework in the target-definition, and that we'd aggregate some jbosstools-playground bundles into JBT.
> Git: Easy Import
> ----------------
>
> Key: JBDS-3285
> URL: https://issues.jboss.org/browse/JBDS-3285
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: requirements, upstream
> Affects Versions: 8.0.0.GA
> Reporter: Burr Sutter
> Assignee: Mickael Istria
> Labels: usability
> Fix For: 9.0.x
>
>
> As a Java EE developer, in some cases using Git for the first time (or only familiar with command line git), I find it very difficult to clone and import a project correctly into JBDS, having the appropriate facets configured, if it has a maven pom.xml, correctly setting the build path, where it is easily deployable to a localhost EAP instance.
> The mission here is to make the Git experience much more user friendly.
> Progress/Status (updated progressively):
> {quote}
> Easymport framework has been contributed to e4 (Platform Incubator): in http://git.eclipse.org/c/e4/org.eclipse.e4.ui.git/tree/bundles , see all org.eclipse.e4.ui.importer* . You can install it in your IDE from http://download.eclipse.org/e4/snapshots/org.eclipse.e4.ui . The entry-points are either the new menu "File > Import projects from folder..." or from legacy import wizard under "General > Local folder(s) as project into workspace".
> We have working extensions that allow to import Java EE & Maven: https://github.com/jbosstools/jbosstools-playground/tree/master/plugins (install from http://download.jboss.org/jbosstools/builds/staging/jbosstools-playground... ) , that we plan to contribute upstream when projects such as m2e and WTP when the framework seems mature enough.
> There is not yet an easy link from the EGit wizard to the Easymport one, nor an easy link from SVN wizard to Easymport.
> There is almost no chance that this can be included in Eclipse IDE for Mars release in June. But we could already think about including it in next JBoss Tools and JBoss Developer Studio milestones, so that we'd get more feedback. At this point, feedback from users and adopters is the key point.
> I invite you to give it a try, and to report issues here.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBDS-3271) Cordova App Splash Screen Support
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBDS-3271?page=com.atlassian.jira.plugin.... ]
Gorkem Ercan commented on JBDS-3271:
------------------------------------
[~burrsutter] According to comments on FH-53 for the FH build server adding this feature is just a matter of upgrading Cordova CLI dependency. I am not sure when this will happen but I am sure that it will happen during the life time of JBDS9. I think our best strategy is our earlier strategy of being compatible with Cordova CLI.
> Cordova App Splash Screen Support
> ---------------------------------
>
> Key: JBDS-3271
> URL: https://issues.jboss.org/browse/JBDS-3271
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: aerogear-hybrid, requirements
> Reporter: Burr Sutter
> Assignee: Gorkem Ercan
> Fix For: 9.0.0.CR1
>
>
> As a HTML5+Cordova mobile app developer, I need to change the splash screen associated with the application launch.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months