April 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19343) integration tests do not fetch their required runtimes if not present in the cache folder

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19343?page=com.atlassian.jira.plugi... ] Vlado Pakan commented on JBIDE-19343: ------------------------------------- PR for integration tests applied thans > integration tests do not fetch their required runtimes if not present in the cache folder > ----------------------------------------------------------------------------------------- > > Key: JBIDE-19343 > URL: https://issues.jboss.org/browse/JBIDE-19343 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: arquillian, build, server > Affects Versions: 4.2.3.Beta1, 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.3.0.Alpha2 > > > There's a problem w/ integration tests not properly bootstrapping (downloading) their runtimes if not present in the cache folder (see jbosstools-dev thread: http://lists.jboss.org/pipermail/jbosstools-dev/2015-February/009770.html ) > Looks like default maven lifecycle causes the pre-integration-test phase to fire, which is fine when we plan to run tests. > There are a number of such phase bindings in this test: > https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.2.x/as/... > And I think this step can be skipped w/ *-DskipTests*. > But the bigger problem is... why won't Jenkins fetch missing deps when they're not in the cache folder? > Here are some console log snipped from builds 119 - 123: > {code} > 11:38:04 [ERROR] Failed to execute goal com.googlecode.maven-download-plugin:maven-download-plugin:1.1.0:wget (install-eap-6.1.0) on project org.jboss.tools.as.test.core: IO Error: /home/hudson/static_build_env/jbds/download-cache/jboss-eap-6.1.1.zip (No such file or directory) -> [Help 1] > 13:29:23 [ERROR] Failed to execute goal com.googlecode.maven-download-plugin:maven-download-plugin:1.1.0:wget (install-wildfly-8.0.0.Beta1) on project org.jboss.tools.as.test.core: IO Error: /home/hudson/static_build_env/jbds/download-cache/wildfly-8.0.0.Beta1.zip (No such file or directory) -> [Help 1] > 16:15:15 [ERROR] Failed to execute goal com.googlecode.maven-download-plugin:maven-download-plugin:1.1.0:wget (install-tomcat6) on project org.jboss.tools.wtp.runtimes.tomcat.tests: IO Error: /home/hudson/static_build_env/jbds/download-cache/apache-tomcat-6.0.39.zip (No such file or directory) -> [Help 1] > {code} -- https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-server_4.... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19343) integration tests do not fetch their required runtimes if not present in the cache folder

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19343?page=com.atlassian.jira.plugi... ] Vlado Pakan edited comment on JBIDE-19343 at 4/7/15 6:45 AM: ------------------------------------------------------------- PR for integration tests applied thanks was (Author: vpakan): PR for integration tests applied thans > integration tests do not fetch their required runtimes if not present in the cache folder > ----------------------------------------------------------------------------------------- > > Key: JBIDE-19343 > URL: https://issues.jboss.org/browse/JBIDE-19343 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: arquillian, build, server > Affects Versions: 4.2.3.Beta1, 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.3.0.Alpha2 > > > There's a problem w/ integration tests not properly bootstrapping (downloading) their runtimes if not present in the cache folder (see jbosstools-dev thread: http://lists.jboss.org/pipermail/jbosstools-dev/2015-February/009770.html ) > Looks like default maven lifecycle causes the pre-integration-test phase to fire, which is fine when we plan to run tests. > There are a number of such phase bindings in this test: > https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.2.x/as/... > And I think this step can be skipped w/ *-DskipTests*. > But the bigger problem is... why won't Jenkins fetch missing deps when they're not in the cache folder? > Here are some console log snipped from builds 119 - 123: > {code} > 11:38:04 [ERROR] Failed to execute goal com.googlecode.maven-download-plugin:maven-download-plugin:1.1.0:wget (install-eap-6.1.0) on project org.jboss.tools.as.test.core: IO Error: /home/hudson/static_build_env/jbds/download-cache/jboss-eap-6.1.1.zip (No such file or directory) -> [Help 1] > 13:29:23 [ERROR] Failed to execute goal com.googlecode.maven-download-plugin:maven-download-plugin:1.1.0:wget (install-wildfly-8.0.0.Beta1) on project org.jboss.tools.as.test.core: IO Error: /home/hudson/static_build_env/jbds/download-cache/wildfly-8.0.0.Beta1.zip (No such file or directory) -> [Help 1] > 16:15:15 [ERROR] Failed to execute goal com.googlecode.maven-download-plugin:maven-download-plugin:1.1.0:wget (install-tomcat6) on project org.jboss.tools.wtp.runtimes.tomcat.tests: IO Error: /home/hudson/static_build_env/jbds/download-cache/apache-tomcat-6.0.39.zip (No such file or directory) -> [Help 1] > {code} -- https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-server_4.... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19555) Migrate Openshift code to use openshift-restclient-java for v3

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19555?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19555: ------------------------------------------ reviewing it but I have a hard time getting over compilation errors. Not all sure what is causing them currently since there are very weird ones where Eclipse platform classes are now missing. I suspect Eclipse bugs again. > Migrate Openshift code to use openshift-restclient-java for v3 > -------------------------------------------------------------- > > Key: JBIDE-19555 > URL: https://issues.jboss.org/browse/JBIDE-19555 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.3.x > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Priority: Blocker > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19507) Search and rename participants for Batch Artifacts

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19507?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19507: --------------------------------------------- what does this do ? please add description for doc/qe etc. > Search and rename participants for Batch Artifacts > -------------------------------------------------- > > Key: JBIDE-19507 > URL: https://issues.jboss.org/browse/JBIDE-19507 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: batch > Reporter: Daniel Azarov > Assignee: Daniel Azarov > Labels: new_and_noteworthy > Fix For: 4.3.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-15714) Dynamic content assist for AngularJS expressions in html files

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15714?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-15714: ---------------------------------------- Priority: Critical (was: Major) > Dynamic content assist for AngularJS expressions in html files > -------------------------------------------------------------- > > Key: JBIDE-15714 > URL: https://issues.jboss.org/browse/JBIDE-15714 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Priority: Critical > Labels: new_and_noteworthy > Fix For: 4.3.0.Alpha2 > > Attachments: Diagram.gliffy, vpe.png > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-15714) Dynamic content assist for AngularJS expressions in html files

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15714?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-15714: ---------------------------------------- Sprint: Sprint 1 of 9.0.0.Alpha2 > Dynamic content assist for AngularJS expressions in html files > -------------------------------------------------------------- > > Key: JBIDE-15714 > URL: https://issues.jboss.org/browse/JBIDE-15714 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Labels: new_and_noteworthy > Fix For: 4.3.0.Alpha2 > > Attachments: Diagram.gliffy, vpe.png > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-15714) Dynamic content assist for AngularJS expressions in html files

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15714?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-15714: ---------------------------------------- Fix Version/s: 4.3.0.Alpha2 (was: 4.3.x) > Dynamic content assist for AngularJS expressions in html files > -------------------------------------------------------------- > > Key: JBIDE-15714 > URL: https://issues.jboss.org/browse/JBIDE-15714 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Labels: new_and_noteworthy > Fix For: 4.3.0.Alpha2 > > Attachments: Diagram.gliffy, vpe.png > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18055) NullPionterException in VPE Preview Editor initialization

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18055?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov resolved JBIDE-18055. -------------------------------------------- Release Notes Text: Cannot reproduce this issue Fix Version/s: 4.3.0.Alpha2 (was: 4.3.x) Resolution: Cannot Reproduce Bug > NullPionterException in VPE Preview Editor initialization > --------------------------------------------------------- > > Key: JBIDE-18055 > URL: https://issues.jboss.org/browse/JBIDE-18055 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.2.0.Beta3 > Reporter: Denis Golovin > Assignee: Konstantin Marmalyukov > Priority: Minor > Fix For: 4.3.0.Alpha2 > > > Exception below can happen sometimes in case re-sizing visual preview part while preview server serving the editor is not started yet. > {code}java.lang.NullPointerException > at org.jboss.tools.vpe.preview.core.server.VpvServer.getPort(VpvServer.java:66) > at org.jboss.tools.vpe.preview.editor.VpvEditor.formRequestToServer(VpvEditor.java:503) > at org.jboss.tools.vpe.preview.editor.VpvEditor.reload(VpvEditor.java:494) > at org.jboss.tools.vpe.preview.editor.VpvEditorPart.updateVisualEditorVisibility(VpvEditorPart.java:769) > at org.jboss.tools.vpe.preview.editor.VpvEditorPart$5.controlResized(VpvEditorPart.java:386) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:235) > 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:1393) > at org.eclipse.swt.widgets.Control.setBounds(Control.java:1042) > at org.eclipse.swt.widgets.Composite.setBounds(Composite.java:1435) > at org.eclipse.swt.widgets.Control.setBounds(Control.java:851) > at org.eclipse.swt.custom.SashForm.onDragSash(SashForm.java:288) > at org.eclipse.swt.custom.SashForm$1.handleEvent(SashForm.java:90) > 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.sendSelectionEvent(Widget.java:1526) > at org.eclipse.swt.widgets.Sash.gtk_motion_notify_event(Sash.java:396) > at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:2104) > 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} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19564) Use background job to detect default connection settings

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-19564: ------------------------------------- Summary: Use background job to detect default connection settings Key: JBIDE-19564 URL: https://issues.jboss.org/browse/JBIDE-19564 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: docker Affects Versions: 4.3.0.Alpha1 Reporter: Xavier Coulon In its current form, the New Connection wizard blocks the UI during opening and this can take a few seconds if the default docker deamon is not running (eg: using the REST API). There should be a background job or an immediate opening with a job (and a progress bar) while trying to detect the settings. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19563) Save docker connections in plugin preferences

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-19563: ------------------------------------- Summary: Save docker connections in plugin preferences Key: JBIDE-19563 URL: https://issues.jboss.org/browse/JBIDE-19563 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: docker Affects Versions: 4.3.0.Alpha1 Reporter: Xavier Coulon Assignee: Xavier Coulon Fix For: 4.3.0.Alpha2 In the current code, the Docker connections are not saved when exiting the workspace, so they need to be setup again after restart -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19425) Error when loading projects in Central with Java 9

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19425?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-19425: --------------------------------------- It turns out that it's not just the tutorials - if I click the HTML5 project, it doesn't work and I get the same error. Furthermore, in this case I also get: Wizard metadata could not be loaded. Please check your Internet connection, Proxy Settings and try again! > Error when loading projects in Central with Java 9 > -------------------------------------------------- > > Key: JBIDE-19425 > URL: https://issues.jboss.org/browse/JBIDE-19425 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Alpha1 > Reporter: Martin Malina > Assignee: Fred Bricon > Labels: Java9 > Fix For: 4.3.x > > > Today I wanted to try out the latest build of Oracle JDK 1.9 beta and discovered a problem with central. > When I started JBDS, I immediately got an error window pop up: > {code} > Refreshing JBoss Tutorials... has encountered a problem. > An internal error occurred during: "Refreshing JBoss Tutorials...". > javax/xml/bind/JAXBException > {code} > This is in the workspace log: > {code} > !ENTRY org.eclipse.core.jobs 4 2 2015-03-10 17:12:52.346 > !MESSAGE An internal error occurred during: "Refreshing JBoss Tutorials...". > !STACK 0 > java.lang.NoClassDefFoundError: javax/xml/bind/JAXBException > at org.jboss.tools.project.examples.model.ProjectExampleUtil.fetchCategories(ProjectExampleUtil.java:389) > at org.jboss.tools.project.examples.model.ProjectExampleUtil.getProjects(ProjectExampleUtil.java:266) > at org.jboss.tools.project.examples.model.ProjectExampleUtil.getProjects(ProjectExampleUtil.java:257) > at org.jboss.tools.central.jobs.RefreshTutorialsJob.run(RefreshTutorialsJob.java:52) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: java.lang.ClassNotFoundException: javax.xml.bind.JAXBException cannot be found by org.jboss.tools.project.examples_3.0.0.Alpha1-v20150213-0945-B3 > at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:439) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:352) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:344) > at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160) > at java.lang.ClassLoader.loadClass(ClassLoader.java:356) > ... 5 more > {code} > I used JBDS 9.0.0.Alpha1 installed on OS X 10.10 Yosemite with Oracle JDK 1.9: > {code} > nattura:9.0.0 rasp$ java -version > java version "1.9.0-ea" > Java(TM) SE Runtime Environment (build 1.9.0-ea-b53) > Java HotSpot(TM) 64-Bit Server VM (build 1.9.0-ea-b53, mixed mode) > {code} > The consequence of this is that the "Start from scratch" section in Central is not loaded and shows "No entries found". > Note: When I installed the same JBDS with Java 8, there was no error. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19452) extension point for editors to tell html5 preview which html content to render

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19452?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-19452: ---------------------------------------- Sprint: Sprint 2 of 9.0.0.Beta1 (was: Sprint 1 of 9.0.0.Alpha2) > extension point for editors to tell html5 preview which html content to render > ------------------------------------------------------------------------------ > > Key: JBIDE-19452 > URL: https://issues.jboss.org/browse/JBIDE-19452 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: visual-page-editor-core > Reporter: Max Rydahl Andersen > Assignee: Konstantin Marmalyukov > Fix For: 4.3.0.Beta1 > > > html preview seem to figure out that text from structured editor is the actual document in the editor. > But when you have something like the Visual JSF Page Editor or Mylyn wiki text editor where the html content is actually not in the main document but something generated html preview does not work. > it would be great if html5 preview would have an extension point where one can install a handler for a specific editor what html should be shown in the preview. > end result: when opening mylyn wiki text editor it should show what corresponds to the Preview tab, not the source tab. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19425) Error when loading projects in Central with Java 9

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19425?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-19425: ---------------------------------- Summary: Error when loading projects in Central with Java 9 (was: Error when loading tutorials in Central with Java 9) > Error when loading projects in Central with Java 9 > -------------------------------------------------- > > Key: JBIDE-19425 > URL: https://issues.jboss.org/browse/JBIDE-19425 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Alpha1 > Reporter: Martin Malina > Assignee: Fred Bricon > Labels: Java9 > Fix For: 4.3.x > > > Today I wanted to try out the latest build of Oracle JDK 1.9 beta and discovered a problem with central. > When I started JBDS, I immediately got an error window pop up: > {code} > Refreshing JBoss Tutorials... has encountered a problem. > An internal error occurred during: "Refreshing JBoss Tutorials...". > javax/xml/bind/JAXBException > {code} > This is in the workspace log: > {code} > !ENTRY org.eclipse.core.jobs 4 2 2015-03-10 17:12:52.346 > !MESSAGE An internal error occurred during: "Refreshing JBoss Tutorials...". > !STACK 0 > java.lang.NoClassDefFoundError: javax/xml/bind/JAXBException > at org.jboss.tools.project.examples.model.ProjectExampleUtil.fetchCategories(ProjectExampleUtil.java:389) > at org.jboss.tools.project.examples.model.ProjectExampleUtil.getProjects(ProjectExampleUtil.java:266) > at org.jboss.tools.project.examples.model.ProjectExampleUtil.getProjects(ProjectExampleUtil.java:257) > at org.jboss.tools.central.jobs.RefreshTutorialsJob.run(RefreshTutorialsJob.java:52) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: java.lang.ClassNotFoundException: javax.xml.bind.JAXBException cannot be found by org.jboss.tools.project.examples_3.0.0.Alpha1-v20150213-0945-B3 > at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:439) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:352) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:344) > at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160) > at java.lang.ClassLoader.loadClass(ClassLoader.java:356) > ... 5 more > {code} > I used JBDS 9.0.0.Alpha1 installed on OS X 10.10 Yosemite with Oracle JDK 1.9: > {code} > nattura:9.0.0 rasp$ java -version > java version "1.9.0-ea" > Java(TM) SE Runtime Environment (build 1.9.0-ea-b53) > Java HotSpot(TM) 64-Bit Server VM (build 1.9.0-ea-b53, mixed mode) > {code} > The consequence of this is that the "Start from scratch" section in Central is not loaded and shows "No entries found". > Note: When I installed the same JBDS with Java 8, there was no error. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19452) extension point for editors to tell html5 preview which html content to render

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19452?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov updated JBIDE-19452: ------------------------------------------- Fix Version/s: 4.3.0.Beta1 (was: 4.3.0.Alpha2) > extension point for editors to tell html5 preview which html content to render > ------------------------------------------------------------------------------ > > Key: JBIDE-19452 > URL: https://issues.jboss.org/browse/JBIDE-19452 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: visual-page-editor-core > Reporter: Max Rydahl Andersen > Assignee: Konstantin Marmalyukov > Fix For: 4.3.0.Beta1 > > > html preview seem to figure out that text from structured editor is the actual document in the editor. > But when you have something like the Visual JSF Page Editor or Mylyn wiki text editor where the html content is actually not in the main document but something generated html preview does not work. > it would be great if html5 preview would have an extension point where one can install a handler for a specific editor what html should be shown in the preview. > end result: when opening mylyn wiki text editor it should show what corresponds to the Preview tab, not the source tab. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19343) integration tests do not fetch their required runtimes if not present in the cache folder

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19343?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19343: ---------------------------------------- and another PR for integration tests: https://github.com/jbosstools/jbosstools-integration-tests/pull/948 [~jpeterka] Could you please review and merge it? > integration tests do not fetch their required runtimes if not present in the cache folder > ----------------------------------------------------------------------------------------- > > Key: JBIDE-19343 > URL: https://issues.jboss.org/browse/JBIDE-19343 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: arquillian, build, server > Affects Versions: 4.2.3.Beta1, 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.3.0.Alpha2 > > > There's a problem w/ integration tests not properly bootstrapping (downloading) their runtimes if not present in the cache folder (see jbosstools-dev thread: http://lists.jboss.org/pipermail/jbosstools-dev/2015-February/009770.html ) > Looks like default maven lifecycle causes the pre-integration-test phase to fire, which is fine when we plan to run tests. > There are a number of such phase bindings in this test: > https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.2.x/as/... > And I think this step can be skipped w/ *-DskipTests*. > But the bigger problem is... why won't Jenkins fetch missing deps when they're not in the cache folder? > Here are some console log snipped from builds 119 - 123: > {code} > 11:38:04 [ERROR] Failed to execute goal com.googlecode.maven-download-plugin:maven-download-plugin:1.1.0:wget (install-eap-6.1.0) on project org.jboss.tools.as.test.core: IO Error: /home/hudson/static_build_env/jbds/download-cache/jboss-eap-6.1.1.zip (No such file or directory) -> [Help 1] > 13:29:23 [ERROR] Failed to execute goal com.googlecode.maven-download-plugin:maven-download-plugin:1.1.0:wget (install-wildfly-8.0.0.Beta1) on project org.jboss.tools.as.test.core: IO Error: /home/hudson/static_build_env/jbds/download-cache/wildfly-8.0.0.Beta1.zip (No such file or directory) -> [Help 1] > 16:15:15 [ERROR] Failed to execute goal com.googlecode.maven-download-plugin:maven-download-plugin:1.1.0:wget (install-tomcat6) on project org.jboss.tools.wtp.runtimes.tomcat.tests: IO Error: /home/hudson/static_build_env/jbds/download-cache/apache-tomcat-6.0.39.zip (No such file or directory) -> [Help 1] > {code} -- https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-server_4.... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19343) integration tests do not fetch their required runtimes if not present in the cache folder

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19343?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-19343: ----------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-server/pull/336, https://github.com/jbosstools/jbosstools-integration-tests/pull/948 (was: https://github.com/jbosstools/jbosstools-server/pull/336) > integration tests do not fetch their required runtimes if not present in the cache folder > ----------------------------------------------------------------------------------------- > > Key: JBIDE-19343 > URL: https://issues.jboss.org/browse/JBIDE-19343 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: arquillian, build, server > Affects Versions: 4.2.3.Beta1, 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.3.0.Alpha2 > > > There's a problem w/ integration tests not properly bootstrapping (downloading) their runtimes if not present in the cache folder (see jbosstools-dev thread: http://lists.jboss.org/pipermail/jbosstools-dev/2015-February/009770.html ) > Looks like default maven lifecycle causes the pre-integration-test phase to fire, which is fine when we plan to run tests. > There are a number of such phase bindings in this test: > https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.2.x/as/... > And I think this step can be skipped w/ *-DskipTests*. > But the bigger problem is... why won't Jenkins fetch missing deps when they're not in the cache folder? > Here are some console log snipped from builds 119 - 123: > {code} > 11:38:04 [ERROR] Failed to execute goal com.googlecode.maven-download-plugin:maven-download-plugin:1.1.0:wget (install-eap-6.1.0) on project org.jboss.tools.as.test.core: IO Error: /home/hudson/static_build_env/jbds/download-cache/jboss-eap-6.1.1.zip (No such file or directory) -> [Help 1] > 13:29:23 [ERROR] Failed to execute goal com.googlecode.maven-download-plugin:maven-download-plugin:1.1.0:wget (install-wildfly-8.0.0.Beta1) on project org.jboss.tools.as.test.core: IO Error: /home/hudson/static_build_env/jbds/download-cache/wildfly-8.0.0.Beta1.zip (No such file or directory) -> [Help 1] > 16:15:15 [ERROR] Failed to execute goal com.googlecode.maven-download-plugin:maven-download-plugin:1.1.0:wget (install-tomcat6) on project org.jboss.tools.wtp.runtimes.tomcat.tests: IO Error: /home/hudson/static_build_env/jbds/download-cache/apache-tomcat-6.0.39.zip (No such file or directory) -> [Help 1] > {code} -- https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-server_4.... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19562) Allow for search and pull images from any Docker registry

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-19562: ------------------------------------- Summary: Allow for search and pull images from any Docker registry Key: JBIDE-19562 URL: https://issues.jboss.org/browse/JBIDE-19562 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: docker Affects Versions: 4.3.0.Alpha1 Reporter: Xavier Coulon Assignee: Xavier Coulon The docker-client now allows for search on a docker registry, so we should leverage that API to search for images, display available info and let the user select the image(s) to pull on the current Docker deamon (ie, Docker host). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19192) provide option for disable html preview

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19192?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-19192: ---------------------------------------- Sprint: Sprint 1 of 9.0.0.Alpha2 > provide option for disable html preview > --------------------------------------- > > Key: JBIDE-19192 > URL: https://issues.jboss.org/browse/JBIDE-19192 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.2.2.Final > Environment: win8.1 64 eclipse luna 4.4.0 jboss 4.2.2 > Reporter: jim harber > Assignee: Konstantin Marmalyukov > Priority: Critical > Fix For: 4.3.0.Alpha2 > > Attachments: Clipboard01.png > > > when i use tween.js to create a html page,i create an array,here is the problem: > var eles = []; > //push such as 500 elements into eles; > .. > then i need call a function to update every element in eles,when these two line: > requestAnimationFrame(animate); > TWEEN.update(); > already in the function,i can't see a change in preview and it makes eclipse shutdown,so i put this two line when i finish the other codes,this time preview become normal. > every time when i type to for(var i=0;i<eles.length;i) eclipse gets stuck. so i wonder is thers any chance i can shutdown living view,i checked preferences panel i didn't find anything. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19447) Constraint violation resolving org.jboss.tools.browsersim.ui

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19447?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-19447: ---------------------------------------- Sprint: Sprint 1 of 9.0.0.Alpha2 > Constraint violation resolving org.jboss.tools.browsersim.ui > ------------------------------------------------------------ > > Key: JBIDE-19447 > URL: https://issues.jboss.org/browse/JBIDE-19447 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Konstantin Marmalyukov > Fix For: 4.3.0.Alpha2 > > > Build is OK, and publish is working, but tests are failing: > {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Master/job/jbosstools-browsersim_master/136/console} > 00:04:56.920 !ENTRY org.jboss.tools.browsersim.eclipse 4 0 2015-03-13 08:51:58.758 > 00:04:56.920 !MESSAGE FrameworkEvent ERROR > 00:04:56.920 !STACK 0 > 00:04:56.920 org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.browsersim.eclipse [265] > 00:04:56.920 Unresolved requirement: Require-Bundle: org.jboss.tools.browsersim.ui; bundle-version="3.3.0" > 00:04:56.921 -> Bundle-SymbolicName: org.jboss.tools.browsersim.ui; bundle-version="3.7.0.Alpha2-v20150313-1249-B136"; singleton:="true" > 00:04:56.921 org.jboss.tools.browsersim.ui [266] > 00:04:56.921 Unresolved requirement: Require-Bundle: org.jboss.tools.browsersim.javafx.mock; bundle-version="3.6.0"; resolution:="optional" > 00:04:56.921 Bundle was not resolved because of a uses contraint violation. > 00:04:56.921 org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.jboss.tools.browsersim.ui [osgi.identity; osgi.identity="org.jboss.tools.browsersim.ui"; type="osgi.bundle"; version:Version="3.7.0.Alpha2-v20150313-1249-B136"; singleton:="true"] because it is exposed to package 'org.eclipse.jetty.util.component' from resources org.eclipse.jetty.util [osgi.identity; osgi.identity="org.eclipse.jetty.util"; type="osgi.bundle"; version:Version="9.2.5.v20141112"] and org.eclipse.jetty.util [osgi.identity; osgi.identity="org.eclipse.jetty.util"; type="osgi.bundle"; version:Version="8.1.14.v20131031"] via two dependency chains. > 00:04:56.922 > 00:04:56.922 Chain 1: > 00:04:56.922 org.jboss.tools.browsersim.ui [osgi.identity; osgi.identity="org.jboss.tools.browsersim.ui"; type="osgi.bundle"; version:Version="3.7.0.Alpha2-v20150313-1249-B136"; singleton:="true"] > 00:04:56.923 require: (&(osgi.wiring.bundle=org.eclipse.jetty.util)(bundle-version>=8.1.14)) > 00:04:56.923 | > 00:04:56.923 provide: osgi.wiring.bundle: org.eclipse.jetty.util > 00:04:56.923 org.eclipse.jetty.util [osgi.identity; osgi.identity="org.eclipse.jetty.util"; type="osgi.bundle"; version:Version="9.2.5.v20141112"] > 00:04:56.923 > 00:04:56.923 Chain 2: > 00:04:56.923 org.jboss.tools.browsersim.ui [osgi.identity; osgi.identity="org.jboss.tools.browsersim.ui"; type="osgi.bundle"; version:Version="3.7.0.Alpha2-v20150313-1249-B136"; singleton:="true"] > 00:04:56.924 require: (&(osgi.wiring.bundle=org.eclipse.jetty.websocket)(bundle-version>=8.1.14)) > 00:04:56.924 | > 00:04:56.924 provide: osgi.wiring.bundle; osgi.wiring.bundle="org.eclipse.jetty.websocket"; bundle-version:Version="8.1.14.v20131031" > 00:04:56.924 org.eclipse.jetty.websocket [osgi.identity; osgi.identity="org.eclipse.jetty.websocket"; type="osgi.bundle"; version:Version="8.1.14.v20131031"] > 00:04:56.924 import: (&(osgi.wiring.package=org.eclipse.jetty.io)(&(version>=8.1.0)(!(version>=9.0.0)))) > 00:04:56.924 | > 00:04:56.925 export: osgi.wiring.package=org.eclipse.jetty.io; uses:=org.eclipse.jetty.util.log > 00:04:56.925 org.eclipse.jetty.io [osgi.identity; osgi.identity="org.eclipse.jetty.io"; type="osgi.bundle"; version:Version="8.1.14.v20131031"] > 00:04:56.925 import: (&(osgi.wiring.package=org.eclipse.jetty.util.log)(&(version>=8.1.0)(!(version>=9.0.0)))) > 00:04:56.925 | > 00:04:56.925 export: osgi.wiring.package: org.eclipse.jetty.util.log; uses:=org.eclipse.jetty.util.component > 00:04:56.925 export: osgi.wiring.package=org.eclipse.jetty.util.component > 00:04:56.925 org.eclipse.jetty.util [osgi.identity; osgi.identity="org.eclipse.jetty.util"; type="osgi.bundle"; version:Version="8.1.14.v20131031"] > 00:04:56.926 at org.eclipse.osgi.container.Module.start(Module.java:434) > 00:04:56.926 at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582) > 00:04:56.926 at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1561) > 00:04:56.926 at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533) > 00:04:56.926 at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476) > 00:04:56.927 at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1) > 00:04:56.927 at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) > 00:04:56.927 at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340){code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19259) JSF or HTML5 support choosing issues

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19259?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-19259: ---------------------------------------- Sprint: Sprint 1 of 9.0.0.Alpha2 > JSF or HTML5 support choosing issues > ------------------------------------ > > Key: JBIDE-19259 > URL: https://issues.jboss.org/browse/JBIDE-19259 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core, xulrunner > Affects Versions: 4.3.0.Alpha1 > Environment: Fedora 20 GNOME 64 bit, Open JDK 7, Alpha2-v20150212-0919-B9496 > Reporter: Vlado Pakan > Assignee: Konstantin Marmalyukov > Fix For: 4.3.0.Alpha2 > > > # GKT2 + xulrunner loaded + JSF support enabled: HTML5 page not rendered - visual part of VPE should contain similar message as in case HTML5 support is enabled for XHTML page informing users about possibility to enable HTML5 suppport > # VPE Preference page should contain checkbox with choice: "Always ask" otherwise user will never be able to get dialog asking to choose between JSF and HTML5 support once he will check check box "Do not show this message again" > # When support is changed page is opened and then Eclipse is restarted it would look better if page won't be opened before Eclipse is restarted. Page should be opened after restart > # With GTK3 "Visual Editor Browser Engine" group within VPE prefrences page is hidden it would be more user friendly just disable it and add some label why it's disabled?.The same way as selecting of GTK for BrowserSim/CordovaSim works. > # Confusing scenario #1: > ## Set HTML5 support > ## Open .xhtml page and say "Stay with HTML5" > ## Open .html page > ## Restart Eclipse > ## Close .html page > ## ERROR: Dialog asking to choose between HTML5 or JSF support is displayed. It's confusing to ask this when page is closed. > # Confusing scenario #2: > ## Set HTML5 support > ## Open .xhtml page and say "Stay with HTML5" > ## Restart Eclipse > ## ERROR: Dialog asking to choose between HTML5 or JSF support is displayed before workspace window appears. This dialog should be displayed once worspace is visible and user actually can see page he is going to open. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19460) No provider for o.j.t.vpe.browsersim.javafx.mock

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19460?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-19460: ---------------------------------------- Sprint: Sprint 1 of 9.0.0.Alpha2 > No provider for o.j.t.vpe.browsersim.javafx.mock > ------------------------------------------------ > > Key: JBIDE-19460 > URL: https://issues.jboss.org/browse/JBIDE-19460 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.2.3.CR1 > Reporter: Nick Boldt > Assignee: Konstantin Marmalyukov > Fix For: 4.3.0.Alpha2 > > > Provider should be *JBoss by Red Hat*, not *null*. > !https://issues.jboss.org/secure/attachment/12388322/810cr1-redux-plugins.png! -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19452) extension point for editors to tell html5 preview which html content to render

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19452?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-19452: ---------------------------------------- Sprint: Sprint 1 of 9.0.0.Alpha2 > extension point for editors to tell html5 preview which html content to render > ------------------------------------------------------------------------------ > > Key: JBIDE-19452 > URL: https://issues.jboss.org/browse/JBIDE-19452 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: visual-page-editor-core > Reporter: Max Rydahl Andersen > Assignee: Konstantin Marmalyukov > Fix For: 4.3.0.Alpha2 > > > html preview seem to figure out that text from structured editor is the actual document in the editor. > But when you have something like the Visual JSF Page Editor or Mylyn wiki text editor where the html content is actually not in the main document but something generated html preview does not work. > it would be great if html5 preview would have an extension point where one can install a handler for a specific editor what html should be shown in the preview. > end result: when opening mylyn wiki text editor it should show what corresponds to the Preview tab, not the source tab. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19561) Display Image info/inspect in properties view

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19561?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-19561: ---------------------------------- Description: Show the equivalent of 'docker images' and 'docker inspect' in the tabs of a properties view when a Docker image node is selected in the Docker Explorer view. (was: Show the equivalent of 'docker ps' and 'docker inspect' in the tabs of a properties view when a Docker container node is selected in the Docker Explorer view. ) > Display Image info/inspect in properties view > --------------------------------------------- > > Key: JBIDE-19561 > URL: https://issues.jboss.org/browse/JBIDE-19561 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: docker > Affects Versions: 4.3.0.Alpha1 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.3.0.Alpha2 > > > Show the equivalent of 'docker images' and 'docker inspect' in the tabs of a properties view when a Docker image node is selected in the Docker Explorer view. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19561) Display Image info/inspect in properties view

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-19561: ------------------------------------- Summary: Display Image info/inspect in properties view Key: JBIDE-19561 URL: https://issues.jboss.org/browse/JBIDE-19561 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: docker Affects Versions: 4.3.0.Alpha1 Reporter: Xavier Coulon Assignee: Xavier Coulon Fix For: 4.3.0.Alpha2 Show the equivalent of 'docker ps' and 'docker inspect' in the tabs of a properties view when a Docker container node is selected in the Docker Explorer view. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19560) Display Container info/inspect in properties view

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19560?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-19560: ---------------------------------- Description: Show the equivalent of 'docker ps' and 'docker inspect' in the tabs of a properties view when a Docker container node is selected in the Docker Explorer view. > Display Container info/inspect in properties view > ------------------------------------------------- > > Key: JBIDE-19560 > URL: https://issues.jboss.org/browse/JBIDE-19560 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: docker > Affects Versions: 4.3.0.Alpha1 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.3.0.Alpha2 > > > Show the equivalent of 'docker ps' and 'docker inspect' in the tabs of a properties view when a Docker container node is selected in the Docker Explorer view. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19559) Display Docker daemon info in properties view

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19559?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-19559: ---------------------------------- Comment: was deleted (was: Show the equivalent of 'docker info' in the properties view when a Docker daemon (ie, a Docker connection) node is selected in the Docker Explorer view.) > Display Docker daemon info in properties view > --------------------------------------------- > > Key: JBIDE-19559 > URL: https://issues.jboss.org/browse/JBIDE-19559 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: docker > Affects Versions: 4.3.0.Alpha1 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.3.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19559) Display Docker daemon info in properties view

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19559?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-19559: ---------------------------------- Description: Show the equivalent of 'docker info' in the properties view when a Docker daemon (ie, a Docker connection) node is selected in the Docker Explorer view. > Display Docker daemon info in properties view > --------------------------------------------- > > Key: JBIDE-19559 > URL: https://issues.jboss.org/browse/JBIDE-19559 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: docker > Affects Versions: 4.3.0.Alpha1 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.3.0.Alpha2 > > > Show the equivalent of 'docker info' in the properties view when a Docker daemon (ie, a Docker connection) node is selected in the Docker Explorer view. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19559) Display Docker daemon info in properties view

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19559?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-19559: --------------------------------------- Show the equivalent of 'docker info' in the properties view when a Docker daemon (ie, a Docker connection) node is selected in the Docker Explorer view. > Display Docker daemon info in properties view > --------------------------------------------- > > Key: JBIDE-19559 > URL: https://issues.jboss.org/browse/JBIDE-19559 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: docker > Affects Versions: 4.3.0.Alpha1 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.3.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19559) Display Docker daemon info in properties view

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-19559: ------------------------------------- Summary: Display Docker daemon info in properties view Key: JBIDE-19559 URL: https://issues.jboss.org/browse/JBIDE-19559 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: docker Affects Versions: 4.3.0.Alpha1 Reporter: Xavier Coulon Assignee: Xavier Coulon Fix For: 4.3.0.Alpha2 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19560) Display Container info/inspect in properties view

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-19560: ------------------------------------- Summary: Display Container info/inspect in properties view Key: JBIDE-19560 URL: https://issues.jboss.org/browse/JBIDE-19560 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: docker Affects Versions: 4.3.0.Alpha1 Reporter: Xavier Coulon Assignee: Xavier Coulon Fix For: 4.3.0.Alpha2 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19499) Refactor Openshift tools to make use of authclient in OSJC

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19499?page=com.atlassian.jira.plugi... ] Andre Dietisheim closed JBIDE-19499. ------------------------------------ nothing for QE to verify, closing > Refactor Openshift tools to make use of authclient in OSJC > ---------------------------------------------------------- > > Key: JBIDE-19499 > URL: https://issues.jboss.org/browse/JBIDE-19499 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Jeff Cantrill > Assignee: Andre Dietisheim > Fix For: 4.3.0.Alpha2 > > > Refactor code to use authclient in OSJC instead of that in core -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19499) Refactor Openshift tools to make use of authclient in OSJC

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19499?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19499: ------------------------------------------ merged and pushed to upstream/master > Refactor Openshift tools to make use of authclient in OSJC > ---------------------------------------------------------- > > Key: JBIDE-19499 > URL: https://issues.jboss.org/browse/JBIDE-19499 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Fix For: 4.3.0.Alpha2 > > > Refactor code to use authclient in OSJC instead of that in core -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19499) Refactor Openshift tools to make use of authclient in OSJC

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19499?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-19499: ---------------------------------------- Assignee: Andre Dietisheim (was: Jeff Cantrill) Resolution: Done > Refactor Openshift tools to make use of authclient in OSJC > ---------------------------------------------------------- > > Key: JBIDE-19499 > URL: https://issues.jboss.org/browse/JBIDE-19499 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Jeff Cantrill > Assignee: Andre Dietisheim > Fix For: 4.3.0.Alpha2 > > > Refactor code to use authclient in OSJC instead of that in core -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19498) docker container view

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19498?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-19498: ---------------------------------- Fix Version/s: 4.3.0.Alpha2 Affects Version/s: 4.3.0.Alpha1 > docker container view > --------------------- > > Key: JBIDE-19498 > URL: https://issues.jboss.org/browse/JBIDE-19498 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: docker > Affects Versions: 4.3.0.Alpha1 > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > Fix For: 4.3.0.Alpha2 > > Attachments: container_mockup.bmml, container_mockup.png > > > the docker view should give a nice overview of what docker containers are running and if possible how much strain they are putting on the system. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19496) docker run wizard

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19496?page=com.atlassian.jira.plugi... ] Xavier Coulon reassigned JBIDE-19496: ------------------------------------- Fix Version/s: 4.3.0.Alpha2 Assignee: Xavier Coulon Affects Version/s: 4.3.0.Alpha1 > docker run wizard > ----------------- > > Key: JBIDE-19496 > URL: https://issues.jboss.org/browse/JBIDE-19496 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: docker > Affects Versions: 4.3.0.Alpha1 > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > Fix For: 4.3.0.Alpha2 > > Attachments: initial_idea_for_docker_run.bmml, initial_idea_for_docker_run.png > > > should have a docker wizard to easily run images. > The wizard should try and capture the most common things in smallest step necessary but still be flexible enough to be used for more advanced usecases. > For example, docker run --help returns ~50 options. We do not want to expose *All* as full ui elements but should try find a way to keep it simple. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19499) Refactor Openshift tools to make use of authclient in OSJC

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19499?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19499: ------------------------------------- Issue Type: Enhancement (was: Feature Request) > Refactor Openshift tools to make use of authclient in OSJC > ---------------------------------------------------------- > > Key: JBIDE-19499 > URL: https://issues.jboss.org/browse/JBIDE-19499 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Fix For: 4.3.0.Alpha2 > > > Refactor code to use authclient in OSJC instead of that in core -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19499) Refactor Openshift tools to make use of authclient in OSJC

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19499?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19499: ------------------------------------- Affects Version/s: 4.3.0.Alpha2 (was: 4.3.x) > Refactor Openshift tools to make use of authclient in OSJC > ---------------------------------------------------------- > > Key: JBIDE-19499 > URL: https://issues.jboss.org/browse/JBIDE-19499 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Fix For: 4.3.0.Alpha2 > > > Refactor code to use authclient in OSJC instead of that in core -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19499) Refactor Openshift tools to make use of authclient in OSJC

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19499?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19499: ------------------------------------- Fix Version/s: 4.3.0.Alpha2 (was: 4.3.x) > Refactor Openshift tools to make use of authclient in OSJC > ---------------------------------------------------------- > > Key: JBIDE-19499 > URL: https://issues.jboss.org/browse/JBIDE-19499 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Fix For: 4.3.0.Alpha2 > > > Refactor code to use authclient in OSJC instead of that in core -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19496) docker run wizard

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19496?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-19496: ---------------------------------------- Sprint: Sprint 1 (was: Sprint 1) > docker run wizard > ----------------- > > Key: JBIDE-19496 > URL: https://issues.jboss.org/browse/JBIDE-19496 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: docker > Reporter: Max Rydahl Andersen > Attachments: initial_idea_for_docker_run.bmml, initial_idea_for_docker_run.png > > > should have a docker wizard to easily run images. > The wizard should try and capture the most common things in smallest step necessary but still be flexible enough to be used for more advanced usecases. > For example, docker run --help returns ~50 options. We do not want to expose *All* as full ui elements but should try find a way to keep it simple. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19496) docker run wizard

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19496?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-19496: ---------------------------------------- Sprint: Sprint 1 > docker run wizard > ----------------- > > Key: JBIDE-19496 > URL: https://issues.jboss.org/browse/JBIDE-19496 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: docker > Reporter: Max Rydahl Andersen > Attachments: initial_idea_for_docker_run.bmml, initial_idea_for_docker_run.png > > > should have a docker wizard to easily run images. > The wizard should try and capture the most common things in smallest step necessary but still be flexible enough to be used for more advanced usecases. > For example, docker run --help returns ~50 options. We do not want to expose *All* as full ui elements but should try find a way to keep it simple. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19557) Connection wizard: authentication form disappears when checking server type

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19557?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19557: ------------------------------------- Workaround Description: Switch "Server Type" to "OpenShift 2" and then to "OpenShift 3" again. Workaround: Workaround Exists > Connection wizard: authentication form disappears when checking server type > --------------------------------------------------------------------------- > > Key: JBIDE-19557 > URL: https://issues.jboss.org/browse/JBIDE-19557 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Alpha2 > > Attachments: no-authentication-form-for-openshift3.png > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19557) Connection wizard: authentication form disappears when checking server type

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19557?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19557: ------------------------------------- Steps to Reproduce: # EXEC: Open connection wizard dialog. # EXEC: Set the server type to "OpenShift 3" # EXEC: Set the server type to "<Automatic>" # EXEC: Set the server type to "OpenShift 3" !no-authentication-form-for-openshift3.png! OR: # EXEC: Open connection wizard dialog. # EXEC: Set the server type to "<Automatic>" and input a v3 server url # EXEC. Click the "Check Server Type" button. # ASSERT: It can check the server type to v3, but the username and password disappear. result: In the step 3, the username and password disappear again. If I change the server type from "<Automatic>"to "Openshift 2", or change from "Openshift 2" to "Openshift 3", The username and password doesn't disappear. was: # EXEC: Open connection wizard dialog. # EXEC: Set the server type to "<Automatic>" # EXEC: Set the server type to "OpenShift 3" !no-authentication-form-for-openshift3.png! OR: # EXEC: Open connection wizard dialog. # EXEC: Set the server type to "<Automatic>" and input a v3 server url # EXEC. Click the "Check Server Type" button. # ASSERT: It can check the server type to v3, but the username and password disappear. result: In the step 3, the username and password disappear again. If I change the server type from "<Automatic>"to "Openshift 2", or change from "Openshift 2" to "Openshift 3", The username and password doesn't disappear. > Connection wizard: authentication form disappears when checking server type > --------------------------------------------------------------------------- > > Key: JBIDE-19557 > URL: https://issues.jboss.org/browse/JBIDE-19557 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Alpha2 > > Attachments: no-authentication-form-for-openshift3.png > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19558) Central search for customer portal doesnt work - again

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19558?page=com.atlassian.jira.plugi... ] Rastislav Wagner updated JBIDE-19558: ------------------------------------- Fix Version/s: 4.3.0.Alpha2 > Central search for customer portal doesnt work - again > ------------------------------------------------------ > > Key: JBIDE-19558 > URL: https://issues.jboss.org/browse/JBIDE-19558 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.2.3.Final, 4.3.0.Alpha1 > Reporter: Rastislav Wagner > Priority: Minor > Fix For: 4.3.0.Alpha2 > > > Same as JBIDE-18666 > Search URL changed again -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19558) Central search for customer portal doesnt work - again

by Rastislav Wagner (JIRA)

Rastislav Wagner created JBIDE-19558: ---------------------------------------- Summary: Central search for customer portal doesnt work - again Key: JBIDE-19558 URL: https://issues.jboss.org/browse/JBIDE-19558 Project: Tools (JBoss Tools) Issue Type: Bug Components: central Affects Versions: 4.3.0.Alpha1, 4.2.3.Final Reporter: Rastislav Wagner Priority: Minor Same as JBIDE-18666 Search URL changed again -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19557) Connection wizard: authentication form disappears when checking server type

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19557?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19557: ------------------------------------- Attachment: no-authentication-form-for-openshift3.png > Connection wizard: authentication form disappears when checking server type > --------------------------------------------------------------------------- > > Key: JBIDE-19557 > URL: https://issues.jboss.org/browse/JBIDE-19557 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Alpha2 > > Attachments: no-authentication-form-for-openshift3.png > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19557) Connection wizard: authentication form disappears when checking server type

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19557?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19557: ------------------------------------- Steps to Reproduce: # EXEC: Open connection wizard dialog. # EXEC: Set the server type to "<Automatic>" # EXEC: Set the server type to "OpenShift 3" !no-authentication-form-for-openshift3.png! OR: # EXEC: Open connection wizard dialog. # EXEC: Set the server type to "<Automatic>" and input a v3 server url # EXEC. Click the "Check Server Type" button. # ASSERT: It can check the server type to v3, but the username and password disappear. result: In the step 3, the username and password disappear again. If I change the server type from "<Automatic>"to "Openshift 2", or change from "Openshift 2" to "Openshift 3", The username and password doesn't disappear. was: # EXEC: Open connection wizard dialog. # EXEC: Set the server type to "<Automatic>" # EXEC: Set the server type to "OpenShift 3" or: # EXEC: Open connection wizard dialog. # EXEC: Set the server type to "<Automatic>" and input a v3 server url # EXEC. Click the "Check Server Type" button. # ASSERT: It can check the server type to v3, but the username and password disappear. result: In the step 3, the username and password disappear again. If I change the server type from "<Automatic>"to "Openshift 2", or change from "Openshift 2" to "Openshift 3", The username and password doesn't disappear. > Connection wizard: authentication form disappears when checking server type > --------------------------------------------------------------------------- > > Key: JBIDE-19557 > URL: https://issues.jboss.org/browse/JBIDE-19557 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Alpha2 > > Attachments: no-authentication-form-for-openshift3.png > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19557) Connection wizard: authentication form disappears when checking server type

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19557?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19557: ------------------------------------- Steps to Reproduce: # EXEC: Open connection wizard dialog. # EXEC: Set the server type to "<Automatic>" # EXEC: Set the server type to "OpenShift 3" or: # EXEC: Open connection wizard dialog. # EXEC: Set the server type to "<Automatic>" and input a v3 server url # EXEC. Click the "Check Server Type" button. # ASSERT: It can check the server type to v3, but the username and password disappear. result: In the step 3, the username and password disappear again. If I change the server type from "<Automatic>"to "Openshift 2", or change from "Openshift 2" to "Openshift 3", The username and password doesn't disappear. was: 1. Open connection wizard dialog. 2. Set the server type to "<Automatic>" 3. Set the server type to "OpenShift 3" or: 1. Open connection wizard dialog. 2. Set the server type to "<Automatic>" and input a v3 server url 3. Click the check server type button. It can check the server type to v3, but the username and password disappear. result: In the step 3, the username and password disappear again. If I change the server type from "<Automatic>"to "Openshift 2", or change from "Openshift 2" to "Openshift 3", The username and password doesn't disappear. > Connection wizard: authentication form disappears when checking server type > --------------------------------------------------------------------------- > > Key: JBIDE-19557 > URL: https://issues.jboss.org/browse/JBIDE-19557 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19557) Connection wizard: authentication form disappears when checking server type

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19557?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-19557: ---------------------------------------- Fix Version/s: 4.3.0.Alpha2 Description: (was: 1. Open connection wizard dialog. 2. Set the server type to "<Automatic>" 3. Set the server type to "OpenShift 3" or: 1. Open connection wizard dialog. 2. Set the server type to "<Automatic>" and input a v3 server url 3. Click the check server type button. It can check the server type to v3, but the username and password disappear. result: In the step 3, the username and password disappear again. If I change the server type from "<Automatic>"to "Openshift 2", or change from "Openshift 2" to "Openshift 3", The username and password doesn't disappear.) Steps to Reproduce: 1. Open connection wizard dialog. 2. Set the server type to "<Automatic>" 3. Set the server type to "OpenShift 3" or: 1. Open connection wizard dialog. 2. Set the server type to "<Automatic>" and input a v3 server url 3. Click the check server type button. It can check the server type to v3, but the username and password disappear. result: In the step 3, the username and password disappear again. If I change the server type from "<Automatic>"to "Openshift 2", or change from "Openshift 2" to "Openshift 3", The username and password doesn't disappear. Assignee: Andre Dietisheim Affects Version/s: 4.3.0.Alpha2 Component/s: openshift > Connection wizard: authentication form disappears when checking server type > --------------------------------------------------------------------------- > > Key: JBIDE-19557 > URL: https://issues.jboss.org/browse/JBIDE-19557 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19548) Connection wizard: Can't connect to openshift v3 , no place to enter username and password in authentication

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19548?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-19548 at 4/7/15 4:17 AM: ------------------------------------------------------------------ Before looking into this new bug, I have to note that this is a new bug which belongs to a new issue. I'll close this bug and file the new report to a new jira: JBIDE-19557 was (Author: adietish): Before looking into this new bug, I have to note that this is a new bug which belongs to a new issue. I'll close this bug and file the new report to a new jira. > Connection wizard: Can't connect to openshift v3 , no place to enter username and password in authentication > ------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-19548 > URL: https://issues.jboss.org/browse/JBIDE-19548 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Environment: 3.0.0.Alpha2-v20150401-1037-B749 > Reporter: Ma Deshuai > Assignee: Andre Dietisheim > Labels: connection_wizard > Fix For: 4.3.0.Alpha2 > > Attachments: openshift-v3.png, v3-auth-form.png, v3-error.png > > > 1. Open connection wizard > 2. Select the server type to OpenShift 3 > 3. Input the server url > 4. Click the finish button to connect the v3 server > Result: > 2. In the authentication, there is no place to input the username and password. > 4. Can't connect the openshift v3 server. The error info tip username may not be null, but there no place to input username and password. http://fpaste.org/206303/52218142/ -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19557) Connection wizard: authentication form disappears when checking server type

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-19557: ---------------------------------------- Summary: Connection wizard: authentication form disappears when checking server type Key: JBIDE-19557 URL: https://issues.jboss.org/browse/JBIDE-19557 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Andre Dietisheim 1. Open connection wizard dialog. 2. Set the server type to "<Automatic>" 3. Set the server type to "OpenShift 3" or: 1. Open connection wizard dialog. 2. Set the server type to "<Automatic>" and input a v3 server url 3. Click the check server type button. It can check the server type to v3, but the username and password disappear. result: In the step 3, the username and password disappear again. If I change the server type from "<Automatic>"to "Openshift 2", or change from "Openshift 2" to "Openshift 3", The username and password doesn't disappear. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-621) Rework and Finalize Article about Generating a HTML5 Web App

by Supriya Bharadwaj (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-621?page=com.atlassian.jira.plug... ] Supriya Bharadwaj commented on TOOLSDOC-621: -------------------------------------------- Added images and converted the article to Markdown. Shall send it across to Aakanksha to have her go through it. Also, was this QE'd while Aakanksha had been working on it? > Rework and Finalize Article about Generating a HTML5 Web App > ------------------------------------------------------------ > > Key: TOOLSDOC-621 > URL: https://issues.jboss.org/browse/TOOLSDOC-621 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: General documentation issues > Reporter: Misha Ali > Assignee: Supriya Bharadwaj > Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19543) org.sonatype.m2e.egit is not compatible with EGit 4.0

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19543?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19543: ---------------------------------------- Any chance this build issue for m2eclipse-egit can be fixed pretty soon? If it is impossible to have this bundle working with EGit 4.0 for next JBT milestone, we'll have to temporarily remove it from TP, and remove everything that depends on it from our build/delivery. > org.sonatype.m2e.egit is not compatible with EGit 4.0 > ----------------------------------------------------- > > Key: JBIDE-19543 > URL: https://issues.jboss.org/browse/JBIDE-19543 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Reporter: Mickael Istria > Assignee: Fred Bricon > Priority: Blocker > > While trying to move the Mars M6, I noticed that org.sonatype.m2e.egit feature/bundle is not compatible with the upcoming EGit 4.0 version (might be just a matter of version range). > We need to have a compatible version soon to be able to build next JBT/JBDS against Mars M6. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19539) Create and use Mars M6 target-platform

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19539?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-19539: ----------------------------------- Comment: was deleted (was: Any chance this build issue for m2eclipse-egit can be fixed pretty soon? If it is impossible to have this bundle working with EGit 4.0 for next JBT milestone, we'll have to temporarily remove it from TP, and remove everything that depends on it from our build/delivery.) > Create and use Mars M6 target-platform > -------------------------------------- > > Key: JBIDE-19539 > URL: https://issues.jboss.org/browse/JBIDE-19539 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: target-platform > Reporter: Mickael Istria > Priority: Critical > > Mars M6 was released and contains interesting changes (in Platform UI), important version updates (EGit 4.0 and TM 4.0). > We need to start using it ASAP to leverage new functionalities and adapt to the most important changes. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19539) Create and use Mars M6 target-platform

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19539?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19539: ---------------------------------------- Any chance this build issue for m2eclipse-egit can be fixed pretty soon? If it is impossible to have this bundle working with EGit 4.0 for next JBT milestone, we'll have to temporarily remove it from TP, and remove everything that depends on it from our build/delivery. > Create and use Mars M6 target-platform > -------------------------------------- > > Key: JBIDE-19539 > URL: https://issues.jboss.org/browse/JBIDE-19539 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: target-platform > Reporter: Mickael Istria > Priority: Critical > > Mars M6 was released and contains interesting changes (in Platform UI), important version updates (EGit 4.0 and TM 4.0). > We need to start using it ASAP to leverage new functionalities and adapt to the most important changes. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19556) Bump some versions

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-19556: -------------------------------------- Summary: Bump some versions Key: JBIDE-19556 URL: https://issues.jboss.org/browse/JBIDE-19556 Project: Tools (JBoss Tools) Issue Type: Task Components: aerogear-hybrid Affects Versions: 4.3.0.Alpha2 Reporter: Mickael Istria Priority: Blocker Now that JBT 4.2.3 is released and used as baseline, the version comparison mojo highlights that FeedHenry artifacts have same version on 4.2.x branch and master. See https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... or run a local build (mvn clean verify) for more details -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19556) Bump some versions

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19556?page=com.atlassian.jira.plugi... ] Mickael Istria reassigned JBIDE-19556: -------------------------------------- Assignee: Gorkem Ercan > Bump some versions > ------------------ > > Key: JBIDE-19556 > URL: https://issues.jboss.org/browse/JBIDE-19556 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: aerogear-hybrid > Affects Versions: 4.3.0.Alpha2 > Reporter: Mickael Istria > Assignee: Gorkem Ercan > Priority: Blocker > Fix For: 4.3.0.Alpha2 > > > Now that JBT 4.2.3 is released and used as baseline, the version comparison mojo highlights that FeedHenry artifacts have same version on 4.2.x branch and master. > See https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... or run a local build (mvn clean verify) for more details -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19556) Bump some versions

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19556?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-19556: ----------------------------------- Fix Version/s: 4.3.0.Alpha2 > Bump some versions > ------------------ > > Key: JBIDE-19556 > URL: https://issues.jboss.org/browse/JBIDE-19556 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: aerogear-hybrid > Affects Versions: 4.3.0.Alpha2 > Reporter: Mickael Istria > Assignee: Gorkem Ercan > Priority: Blocker > Fix For: 4.3.0.Alpha2 > > > Now that JBT 4.2.3 is released and used as baseline, the version comparison mojo highlights that FeedHenry artifacts have same version on 4.2.x branch and master. > See https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... or run a local build (mvn clean verify) for more details -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19553) Weld exclude doesn't work for CDI 1.1+

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19553?page=com.atlassian.jira.plugi... ] Rastislav Wagner updated JBIDE-19553: ------------------------------------- Attachment: beans.xml beans.xml attached > Weld exclude doesn't work for CDI 1.1+ > -------------------------------------- > > Key: JBIDE-19553 > URL: https://issues.jboss.org/browse/JBIDE-19553 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Affects Versions: 4.3.0.Alpha1 > Reporter: Rastislav Wagner > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.Alpha2 > > Attachments: beans.xml > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19548) Connection wizard: Can't connect to openshift v3 , no place to enter username and password in authentication

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19548?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19548: ------------------------------------------ Before looking into this new bug, I have to note that this is a new bug which belongs to a new issue. I'll close this bug and file the new report to a new jira. > Connection wizard: Can't connect to openshift v3 , no place to enter username and password in authentication > ------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-19548 > URL: https://issues.jboss.org/browse/JBIDE-19548 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Environment: 3.0.0.Alpha2-v20150401-1037-B749 > Reporter: Ma Deshuai > Assignee: Andre Dietisheim > Labels: connection_wizard > Fix For: 4.3.0.Alpha2 > > Attachments: openshift-v3.png, v3-auth-form.png, v3-error.png > > > 1. Open connection wizard > 2. Select the server type to OpenShift 3 > 3. Input the server url > 4. Click the finish button to connect the v3 server > Result: > 2. In the authentication, there is no place to input the username and password. > 4. Can't connect the openshift v3 server. The error info tip username may not be null, but there no place to input username and password. http://fpaste.org/206303/52218142/ -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19548) Connection wizard: Can't connect to openshift v3 , no place to enter username and password in authentication

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19548?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-19548. -------------------------------------- Resolution: Done > Connection wizard: Can't connect to openshift v3 , no place to enter username and password in authentication > ------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-19548 > URL: https://issues.jboss.org/browse/JBIDE-19548 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Environment: 3.0.0.Alpha2-v20150401-1037-B749 > Reporter: Ma Deshuai > Assignee: Andre Dietisheim > Labels: connection_wizard > Fix For: 4.3.0.Alpha2 > > Attachments: openshift-v3.png, v3-auth-form.png, v3-error.png > > > 1. Open connection wizard > 2. Select the server type to OpenShift 3 > 3. Input the server url > 4. Click the finish button to connect the v3 server > Result: > 2. In the authentication, there is no place to input the username and password. > 4. Can't connect the openshift v3 server. The error info tip username may not be null, but there no place to input username and password. http://fpaste.org/206303/52218142/ -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3386) add org.eclipse.wst.jsdt.feature.patch into both JBT 4.2 and JBDS 8 (Luna) Eclipse Marketplace connectors

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3386?page=com.atlassian.jira.plugin.... ] Mickael Istria resolved JBDS-3386. ---------------------------------- Resolution: Done Marketplace entries were updated to include the WTP patch feature. > add org.eclipse.wst.jsdt.feature.patch into both JBT 4.2 and JBDS 8 (Luna) Eclipse Marketplace connectors > --------------------------------------------------------------------------------------------------------- > > Key: JBDS-3386 > URL: https://issues.jboss.org/browse/JBDS-3386 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Components: target-platform > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 8.1.0.GA > > > When we release JBT 4.2.3 and JBDS 8.1.0, we need to remember to add 1 new feature, org.eclipse.wst.jsdt.feature.patch, into both the JBT 4.2 and JBDS 8 (Luna) Eclipse Marketplace connectors. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3393) Early Access Enabled banner appears w/out EA content installed

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3393?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-3393: -------------------------------------- I believe what you've tried should work. Can you place a breakpoint on https://github.com/jbosstools/jbosstools-central/blob/master/central/plug... and check which URL is actually resolved? > Early Access Enabled banner appears w/out EA content installed > -------------------------------------------------------------- > > Key: JBDS-3393 > URL: https://issues.jboss.org/browse/JBDS-3393 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central > Affects Versions: 8.1.0.CR1 > Reporter: Paul Leacu > Assignee: Paul Leacu > Attachments: ss1.png, ss2.png, x1.png > > > 1. Start w/ Eclipse JEE Luna SR2 > 2. Install JBDS 8.0.2 > 3. ./eclipse -vmargs -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/8.0.1.CR1/devstudio-integration-stack-directory.xml -Djboss.discovery.site.integration-stack.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/8.0.1.CR1 > Then "JBoss Integration and SOA Development" will appear - as designed - in both the standard released update selection window and > in the early access window. This particular connector/ category has both released and early access components in it. ref ss1.png > Selecting "JBoss Integration and SOA Development" and restarting - I get the message "Early Access Installed" even though I haven't > yet enabled early access. ref ss2.png. The plugin.xmls are here: > https://github.com/jbosstools/jbosstools-integration-stack/blob/master/de... > https://github.com/jbosstools/jbosstools-integration-stack/blob/master/de... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-625) JBDS-IS 8.0.1: Create an article about upgrading from previous to current version of JBDS-IS

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-625?page=com.atlassian.jira.plug... ] Misha Ali updated TOOLSDOC-625: ------------------------------- Description: >From Petr's feedback: c) instructions on upgrading and uninstalling the IS are missing altogether, compared to the Fuse Tooling installation guide JBDS-IS docs team has committed to this in time for GA. * Create and populate the upgrading article * Send link to Gemma for B*MS splash page was: >From Petr's feedback: c) instructions on upgrading and uninstalling the IS are missing altogether, compared to the Fuse Tooling installation guide JBDS-IS docs team has committed to this in time for GA. > JBDS-IS 8.0.1: Create an article about upgrading from previous to current version of JBDS-IS > -------------------------------------------------------------------------------------------- > > Key: TOOLSDOC-625 > URL: https://issues.jboss.org/browse/TOOLSDOC-625 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Misha Ali > Assignee: Misha Ali > > From Petr's feedback: > c) instructions on upgrading and uninstalling the IS are missing altogether, compared to the Fuse Tooling installation guide > JBDS-IS docs team has committed to this in time for GA. > * Create and populate the upgrading article > * Send link to Gemma for B*MS splash page -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-616) JBDS-IS 8.0.1: Generate Release Notes

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-616?page=com.atlassian.jira.plug... ] Misha Ali updated TOOLSDOC-616: ------------------------------- Summary: JBDS-IS 8.0.1: Generate Release Notes (was: Generate Release Notes for JBDS-IS 8.0.1 GA) > JBDS-IS 8.0.1: Generate Release Notes > ------------------------------------- > > Key: TOOLSDOC-616 > URL: https://issues.jboss.org/browse/TOOLSDOC-616 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Misha Ali > Assignee: Misha Ali > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-616) JBDS-IS 8.0.1: Generate Release Notes

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-616?page=com.atlassian.jira.plug... ] Misha Ali updated TOOLSDOC-616: ------------------------------- Description: * Generate release notes * Get QE approval * Send Gemma link for B*MS splash page > JBDS-IS 8.0.1: Generate Release Notes > ------------------------------------- > > Key: TOOLSDOC-616 > URL: https://issues.jboss.org/browse/TOOLSDOC-616 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Misha Ali > Assignee: Misha Ali > > * Generate release notes > * Get QE approval > * Send Gemma link for B*MS splash page -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-624) Update JBDS-IS Install Document for 8.0.1

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-624?page=com.atlassian.jira.plug... ] Misha Ali updated TOOLSDOC-624: ------------------------------- Description: 1. Installation Guide - in Fuse, we have our own Fuse Tooling Installation Guide. After comparing the content of the two installation guides, I don't have objections to getting rid of ours and reusing the one from JBDS IS. But: a) the guide should include (a link to) JBDS installation instructions; this information is currently missing and imo is very important in the isolated context of individual products' docs suites b) the "From the table of categories, select the JBoss Developer Studio Integration Stack functionality you want to install and click Next." step of each procedure should be expanded with specific instructions for individual products, i.e. what components of the IS to install for Fuse, DV and B*MS > Update JBDS-IS Install Document for 8.0.1 > ----------------------------------------- > > Key: TOOLSDOC-624 > URL: https://issues.jboss.org/browse/TOOLSDOC-624 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Misha Ali > Assignee: Misha Ali > > 1. Installation Guide - in Fuse, we have our own Fuse Tooling Installation Guide. After comparing the content of the two installation guides, I don't have objections to getting rid of ours and reusing the one from JBDS IS. But: > a) the guide should include (a link to) JBDS installation instructions; this information is currently missing and imo is very important in the isolated context of individual products' docs suites > b) the "From the table of categories, select the JBoss Developer Studio Integration Stack functionality you want to install and click Next." step of each procedure should be expanded with specific instructions for individual products, i.e. what components of the IS to install for Fuse, DV and B*MS -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-624) JBDS-IS 8.0.1: Update Install Document

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-624?page=com.atlassian.jira.plug... ] Misha Ali updated TOOLSDOC-624: ------------------------------- Summary: JBDS-IS 8.0.1: Update Install Document (was: Update JBDS-IS Install Document for 8.0.1) > JBDS-IS 8.0.1: Update Install Document > --------------------------------------- > > Key: TOOLSDOC-624 > URL: https://issues.jboss.org/browse/TOOLSDOC-624 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Misha Ali > Assignee: Misha Ali > > 1. Installation Guide - in Fuse, we have our own Fuse Tooling Installation Guide. After comparing the content of the two installation guides, I don't have objections to getting rid of ours and reusing the one from JBDS IS. But: > a) the guide should include (a link to) JBDS installation instructions; this information is currently missing and imo is very important in the isolated context of individual products' docs suites > b) the "From the table of categories, select the JBoss Developer Studio Integration Stack functionality you want to install and click Next." step of each procedure should be expanded with specific instructions for individual products, i.e. what components of the IS to install for Fuse, DV and B*MS -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-625) JBDS-IS 8.0.1: Create an article about upgrading from previous to current version of JBDS-IS

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-625?page=com.atlassian.jira.plug... ] Misha Ali updated TOOLSDOC-625: ------------------------------- Description: >From Petr's feedback: c) instructions on upgrading and uninstalling the IS are missing altogether, compared to the Fuse Tooling installation guide JBDS-IS docs team has committed to this in time for GA. > JBDS-IS 8.0.1: Create an article about upgrading from previous to current version of JBDS-IS > -------------------------------------------------------------------------------------------- > > Key: TOOLSDOC-625 > URL: https://issues.jboss.org/browse/TOOLSDOC-625 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Misha Ali > Assignee: Misha Ali > > From Petr's feedback: > c) instructions on upgrading and uninstalling the IS are missing altogether, compared to the Fuse Tooling installation guide > JBDS-IS docs team has committed to this in time for GA. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-615) Start Developing Guide: Use and Evaluate Guide & Determine Format for JBDS 9.0

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-615?page=com.atlassian.jira.plug... ] Misha Ali updated TOOLSDOC-615: ------------------------------- Sprint: 2015/S9 (27-Apr > 10-May) (was: 2015/S8 (13-Apr > 26-Apr)) > Start Developing Guide: Use and Evaluate Guide & Determine Format for JBDS 9.0 > ------------------------------------------------------------------------------ > > Key: TOOLSDOC-615 > URL: https://issues.jboss.org/browse/TOOLSDOC-615 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Enhancement > Components: Getting Started Guide > Affects Versions: 4.3.0.Final > Reporter: Misha Ali > Assignee: Misha Ali > > Requirements: > * Use the current Start Developing Guide to test content > * Review contents and determine if this would be better as a new series of articles rather than a document for 9.0 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-616) Generate Release Notes for JBDS-IS 8.0.1 GA

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-616?page=com.atlassian.jira.plug... ] Misha Ali updated TOOLSDOC-616: ------------------------------- Sprint: 2015/S7 (30-Mar > 12-Apr) (was: 2015/S8 (13-Apr > 26-Apr)) > Generate Release Notes for JBDS-IS 8.0.1 GA > ------------------------------------------- > > Key: TOOLSDOC-616 > URL: https://issues.jboss.org/browse/TOOLSDOC-616 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Misha Ali > Assignee: Misha Ali > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-624) Update JBDS-IS Install Document for 8.0.1

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-624?page=com.atlassian.jira.plug... ] Misha Ali updated TOOLSDOC-624: ------------------------------- Sprint: 2015/S7 (30-Mar > 12-Apr) (was: 2015/S8 (13-Apr > 26-Apr)) > Update JBDS-IS Install Document for 8.0.1 > ----------------------------------------- > > Key: TOOLSDOC-624 > URL: https://issues.jboss.org/browse/TOOLSDOC-624 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Misha Ali > Assignee: Misha Ali > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-625) JBDS-IS 8.0.1: Create an article about upgrading from previous to current version of JBDS-IS

by Misha Ali (JIRA)

Misha Ali created TOOLSDOC-625: ---------------------------------- Summary: JBDS-IS 8.0.1: Create an article about upgrading from previous to current version of JBDS-IS Key: TOOLSDOC-625 URL: https://issues.jboss.org/browse/TOOLSDOC-625 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Bug Reporter: Misha Ali Assignee: Misha Ali -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-625) JBDS-IS 8.0.1: Create an article about upgrading from previous to current version of JBDS-IS

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-625?page=com.atlassian.jira.plug... ] Misha Ali updated TOOLSDOC-625: ------------------------------- Sprint: 2015/S7 (30-Mar > 12-Apr) (was: 2015/S8 (13-Apr > 26-Apr)) > JBDS-IS 8.0.1: Create an article about upgrading from previous to current version of JBDS-IS > -------------------------------------------------------------------------------------------- > > Key: TOOLSDOC-625 > URL: https://issues.jboss.org/browse/TOOLSDOC-625 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Misha Ali > Assignee: Misha Ali > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-624) Update JBDS-IS Install Document for 8.0.1

by Misha Ali (JIRA)

Misha Ali created TOOLSDOC-624: ---------------------------------- Summary: Update JBDS-IS Install Document for 8.0.1 Key: TOOLSDOC-624 URL: https://issues.jboss.org/browse/TOOLSDOC-624 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Bug Reporter: Misha Ali Assignee: Misha Ali -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3361) Cannot install JBDS 8.0.2.GA in offline mode

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3361?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3361: ------------------------------------- Additional PR released to master. Verified in latest installer build. Installer jar now has normal size: {code}jboss-devstudio-9.0.0.Alpha2-v20150406-2349-B2919-installer-standalone.jar 469.81 MB{code} > Cannot install JBDS 8.0.2.GA in offline mode > -------------------------------------------- > > Key: JBDS-3361 > URL: https://issues.jboss.org/browse/JBDS-3361 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: updatesite > Affects Versions: 8.0.2.GA > Reporter: Tomáš Sedmík > Assignee: Denis Golovin > Priority: Blocker > > Cannot install JBDS 8.0.2.GA in offline mode - see the problem > {code:borderStyle=solid} > Cannot complete the install because one or more required items could not be found. > Software being installed: JBoss Developer Studio (Core Features) 8.0.2.GA-v20150114-2029-B382 (com.jboss.devstudio.core.feature.feature.group 8.0.2.GA-v20150114-2029-B382) > Missing requirement: JBoss Developer Studio (Core Features) 8.0.2.GA-v20150114-2029-B382 (com.jboss.devstudio.core.feature.feature.group 8.0.2.GA-v20150114-2029-B382) requires 'org.eclipse.core.runtime.compatibility.auth 0.0.0' but it could not be found > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3361) Cannot install JBDS 8.0.2.GA in offline mode

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3361?page=com.atlassian.jira.plugin.... ] Denis Golovin reassigned JBDS-3361: ----------------------------------- Resolution: (was: Done) Assignee: Denis Golovin (was: Nick Boldt) Fix Version/s: (was: 9.0.0.Alpha2) Reopening, because now it seems installer again includes .jar and .pack.gz.jar artifacts. The reason is pack200 profile activated when build is running on hudson. > Cannot install JBDS 8.0.2.GA in offline mode > -------------------------------------------- > > Key: JBDS-3361 > URL: https://issues.jboss.org/browse/JBDS-3361 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: updatesite > Affects Versions: 8.0.2.GA > Reporter: Tomáš Sedmík > Assignee: Denis Golovin > Priority: Blocker > > Cannot install JBDS 8.0.2.GA in offline mode - see the problem > {code:borderStyle=solid} > Cannot complete the install because one or more required items could not be found. > Software being installed: JBoss Developer Studio (Core Features) 8.0.2.GA-v20150114-2029-B382 (com.jboss.devstudio.core.feature.feature.group 8.0.2.GA-v20150114-2029-B382) > Missing requirement: JBoss Developer Studio (Core Features) 8.0.2.GA-v20150114-2029-B382 (com.jboss.devstudio.core.feature.feature.group 8.0.2.GA-v20150114-2029-B382) requires 'org.eclipse.core.runtime.compatibility.auth 0.0.0' but it could not be found > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3397) Add FeedHenry: Create Your First Hybrid Mobile Application with JBoss Developer Studio

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/JBDS-3397?page=com.atlassian.jira.plugin.... ] Misha Ali closed JBDS-3397. --------------------------- Resolution: Done Closed issue and created a tracking JIRA in the docs project instead and added Burr to new JIRA: https://issues.jboss.org/browse/TOOLSDOC-623 > Add FeedHenry: Create Your First Hybrid Mobile Application with JBoss Developer Studio > -------------------------------------------------------------------------------------- > > Key: JBDS-3397 > URL: https://issues.jboss.org/browse/JBDS-3397 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: documentation > Reporter: Burr Sutter > > https://access.redhat.com/articles/1295913 > We should add FeedHenry to this document. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-623) Add FeedHenry Information to Existing Article about Hybrid Mobile Apps

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-623?page=com.atlassian.jira.plug... ] Misha Ali updated TOOLSDOC-623: ------------------------------- Description: Originally reported by Burr here: https://issues.jboss.org/browse/JBDS-3397 Description: https://access.redhat.com/articles/1295913 We should add FeedHenry to this document. > Add FeedHenry Information to Existing Article about Hybrid Mobile Apps > ---------------------------------------------------------------------- > > Key: TOOLSDOC-623 > URL: https://issues.jboss.org/browse/TOOLSDOC-623 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Misha Ali > Assignee: Misha Ali > > Originally reported by Burr here: https://issues.jboss.org/browse/JBDS-3397 > Description: https://access.redhat.com/articles/1295913 > We should add FeedHenry to this document. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-623) Add FeedHenry Information to Existing Article about Hybrid Mobile Apps

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-623?page=com.atlassian.jira.plug... ] Misha Ali updated TOOLSDOC-623: ------------------------------- Reporter: Burr Sutter (was: Misha Ali) > Add FeedHenry Information to Existing Article about Hybrid Mobile Apps > ---------------------------------------------------------------------- > > Key: TOOLSDOC-623 > URL: https://issues.jboss.org/browse/TOOLSDOC-623 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Burr Sutter > Assignee: Misha Ali > > Originally reported by Burr here: https://issues.jboss.org/browse/JBDS-3397 > Description: https://access.redhat.com/articles/1295913 > We should add FeedHenry to this document. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-623) Add FeedHenry Information to Existing Article about Hybrid Mobile Apps

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-623?page=com.atlassian.jira.plug... ] Misha Ali reassigned TOOLSDOC-623: ---------------------------------- Assignee: Supriya Bharadwaj (was: Misha Ali) > Add FeedHenry Information to Existing Article about Hybrid Mobile Apps > ---------------------------------------------------------------------- > > Key: TOOLSDOC-623 > URL: https://issues.jboss.org/browse/TOOLSDOC-623 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Burr Sutter > Assignee: Supriya Bharadwaj > > Originally reported by Burr here: https://issues.jboss.org/browse/JBDS-3397 > Description: https://access.redhat.com/articles/1295913 > We should add FeedHenry to this document. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-623) Add FeedHenry Information to Existing Article about Hybrid Mobile Apps

by Misha Ali (JIRA)

Misha Ali created TOOLSDOC-623: ---------------------------------- Summary: Add FeedHenry Information to Existing Article about Hybrid Mobile Apps Key: TOOLSDOC-623 URL: https://issues.jboss.org/browse/TOOLSDOC-623 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Bug Reporter: Misha Ali Assignee: Misha Ali -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3398) Add FeedHenry: Create Your First Hybrid Mobile Application with JBoss Developer Studio

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/JBDS-3398?page=com.atlassian.jira.plugin.... ] Misha Ali closed JBDS-3398. --------------------------- Resolution: Done Closing clone and logging issue in Docs project for scoping and management and ccing Burr. > Add FeedHenry: Create Your First Hybrid Mobile Application with JBoss Developer Studio > -------------------------------------------------------------------------------------- > > Key: JBDS-3398 > URL: https://issues.jboss.org/browse/JBDS-3398 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: documentation > Reporter: Burr Sutter > > https://access.redhat.com/articles/1295913 > We should add FeedHenry to this document. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3398) Add FeedHenry: Create Your First Hybrid Mobile Application with JBoss Developer Studio

by Misha Ali (JIRA)

Misha Ali created JBDS-3398: ------------------------------- Summary: Add FeedHenry: Create Your First Hybrid Mobile Application with JBoss Developer Studio Key: JBDS-3398 URL: https://issues.jboss.org/browse/JBDS-3398 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: documentation Reporter: Burr Sutter https://access.redhat.com/articles/1295913 We should add FeedHenry to this document. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19499) Refactor Openshift tools to make use of authclient in OSJC

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19499?page=com.atlassian.jira.plugi... ] Jeff Cantrill updated JBIDE-19499: ---------------------------------- Affects Version/s: 4.3.x > Refactor Openshift tools to make use of authclient in OSJC > ---------------------------------------------------------- > > Key: JBIDE-19499 > URL: https://issues.jboss.org/browse/JBIDE-19499 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.x > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Fix For: 4.3.x > > > Refactor code to use authclient in OSJC instead of that in core -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19499) Refactor Openshift tools to make use of authclient in OSJC

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19499?page=com.atlassian.jira.plugi... ] Jeff Cantrill updated JBIDE-19499: ---------------------------------- Fix Version/s: 4.3.x > Refactor Openshift tools to make use of authclient in OSJC > ---------------------------------------------------------- > > Key: JBIDE-19499 > URL: https://issues.jboss.org/browse/JBIDE-19499 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.x > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Fix For: 4.3.x > > > Refactor code to use authclient in OSJC instead of that in core -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19555) Migrate Openshift code to use openshift-restclient-java for v3

by Jeff Cantrill (JIRA)

Jeff Cantrill created JBIDE-19555: ------------------------------------- Summary: Migrate Openshift code to use openshift-restclient-java for v3 Key: JBIDE-19555 URL: https://issues.jboss.org/browse/JBIDE-19555 Project: Tools (JBoss Tools) Issue Type: Task Components: openshift Affects Versions: 4.3.x Reporter: Jeff Cantrill Assignee: Jeff Cantrill Priority: Blocker -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3393) Early Access Enabled banner appears w/out EA content installed

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBDS-3393?page=com.atlassian.jira.plugin.... ] Paul Leacu updated JBDS-3393: ----------------------------- Attachment: x1.png > Early Access Enabled banner appears w/out EA content installed > -------------------------------------------------------------- > > Key: JBDS-3393 > URL: https://issues.jboss.org/browse/JBDS-3393 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central > Affects Versions: 8.1.0.CR1 > Reporter: Paul Leacu > Assignee: Paul Leacu > Attachments: ss1.png, ss2.png, x1.png > > > 1. Start w/ Eclipse JEE Luna SR2 > 2. Install JBDS 8.0.2 > 3. ./eclipse -vmargs -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/8.0.1.CR1/devstudio-integration-stack-directory.xml -Djboss.discovery.site.integration-stack.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/8.0.1.CR1 > Then "JBoss Integration and SOA Development" will appear - as designed - in both the standard released update selection window and > in the early access window. This particular connector/ category has both released and early access components in it. ref ss1.png > Selecting "JBoss Integration and SOA Development" and restarting - I get the message "Early Access Installed" even though I haven't > yet enabled early access. ref ss2.png. The plugin.xmls are here: > https://github.com/jbosstools/jbosstools-integration-stack/blob/master/de... > https://github.com/jbosstools/jbosstools-integration-stack/blob/master/de... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3393) Early Access Enabled banner appears w/out EA content installed

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBDS-3393?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBDS-3393: ---------------------------------- [~mickael_istria] - I'm still stuck with the EA banner issue - if you have a second, could you please try: ./eclipse -vmargs \ -Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/discovery/development/integration-stack/4.2.1.CR2/jbosstools-integration-stack-directory.xml \ -Djboss.discovery.site.url=http://download.jboss.org/jbosstools/updates/development/luna/ \ -Djboss.discovery.site.integration-stack.url=http://download.jboss.org/jbosstools/discovery/development/integration-stack/4.2.1.CR2 \ -Djboss.discovery.earlyaccess.site.url=http://download.jboss.org/jbosstools/earlyaccess/development/luna/ \ -Djboss.discovery.earlyaccess.list.url=http://download.jboss.org/jbosstools/updates/development/luna/jbosstools-earlyaccess.properties The earlyaccess.properties is down to just fuse tooling and switchyard. When I examine the installation details it appears the BPEL editor and the jBPM runtime detector are coming across as EA. (see attachment x1.png). I can't see how that's occurring. Are my ide-config.properties definitions ok? Thanks for any help. > Early Access Enabled banner appears w/out EA content installed > -------------------------------------------------------------- > > Key: JBDS-3393 > URL: https://issues.jboss.org/browse/JBDS-3393 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central > Affects Versions: 8.1.0.CR1 > Reporter: Paul Leacu > Assignee: Paul Leacu > Attachments: ss1.png, ss2.png > > > 1. Start w/ Eclipse JEE Luna SR2 > 2. Install JBDS 8.0.2 > 3. ./eclipse -vmargs -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/8.0.1.CR1/devstudio-integration-stack-directory.xml -Djboss.discovery.site.integration-stack.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/8.0.1.CR1 > Then "JBoss Integration and SOA Development" will appear - as designed - in both the standard released update selection window and > in the early access window. This particular connector/ category has both released and early access components in it. ref ss1.png > Selecting "JBoss Integration and SOA Development" and restarting - I get the message "Early Access Installed" even though I haven't > yet enabled early access. ref ss2.png. The plugin.xmls are here: > https://github.com/jbosstools/jbosstools-integration-stack/blob/master/de... > https://github.com/jbosstools/jbosstools-integration-stack/blob/master/de... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19514) Ionic Palette: New ion-spinner wizard

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19514?page=com.atlassian.jira.plugi... ] Daniel Azarov updated JBIDE-19514: ---------------------------------- Attachment: (was: ios-small9.png) > Ionic Palette: New ion-spinner wizard > ------------------------------------- > > Key: JBIDE-19514 > URL: https://issues.jboss.org/browse/JBIDE-19514 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.Beta1 > > Attachments: IonicSpinner.png, IonicSpinnerWizBan.png, ios.gif > > > http://ionicframework.com/docs/nightly/api/directive/ionSpinner/ -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19514) Ionic Palette: New ion-spinner wizard

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19514?page=com.atlassian.jira.plugi... ] Daniel Azarov updated JBIDE-19514: ---------------------------------- Attachment: (was: ios-small8.png) > Ionic Palette: New ion-spinner wizard > ------------------------------------- > > Key: JBIDE-19514 > URL: https://issues.jboss.org/browse/JBIDE-19514 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.Beta1 > > Attachments: IonicSpinner.png, IonicSpinnerWizBan.png, ios.gif > > > http://ionicframework.com/docs/nightly/api/directive/ionSpinner/ -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19514) Ionic Palette: New ion-spinner wizard

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19514?page=com.atlassian.jira.plugi... ] Daniel Azarov updated JBIDE-19514: ---------------------------------- Attachment: (was: ios-small3.png) > Ionic Palette: New ion-spinner wizard > ------------------------------------- > > Key: JBIDE-19514 > URL: https://issues.jboss.org/browse/JBIDE-19514 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.Beta1 > > Attachments: IonicSpinner.png, IonicSpinnerWizBan.png, ios.gif > > > http://ionicframework.com/docs/nightly/api/directive/ionSpinner/ -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19514) Ionic Palette: New ion-spinner wizard

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19514?page=com.atlassian.jira.plugi... ] Daniel Azarov updated JBIDE-19514: ---------------------------------- Attachment: (was: ios-small12.png) > Ionic Palette: New ion-spinner wizard > ------------------------------------- > > Key: JBIDE-19514 > URL: https://issues.jboss.org/browse/JBIDE-19514 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.Beta1 > > Attachments: IonicSpinner.png, IonicSpinnerWizBan.png, ios.gif > > > http://ionicframework.com/docs/nightly/api/directive/ionSpinner/ -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19514) Ionic Palette: New ion-spinner wizard

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19514?page=com.atlassian.jira.plugi... ] Daniel Azarov updated JBIDE-19514: ---------------------------------- Attachment: (was: ios-small6.png) > Ionic Palette: New ion-spinner wizard > ------------------------------------- > > Key: JBIDE-19514 > URL: https://issues.jboss.org/browse/JBIDE-19514 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.Beta1 > > Attachments: IonicSpinner.png, IonicSpinnerWizBan.png, ios.gif > > > http://ionicframework.com/docs/nightly/api/directive/ionSpinner/ -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19514) Ionic Palette: New ion-spinner wizard

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19514?page=com.atlassian.jira.plugi... ] Daniel Azarov updated JBIDE-19514: ---------------------------------- Attachment: (was: ios-small7.png) > Ionic Palette: New ion-spinner wizard > ------------------------------------- > > Key: JBIDE-19514 > URL: https://issues.jboss.org/browse/JBIDE-19514 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.Beta1 > > Attachments: IonicSpinner.png, IonicSpinnerWizBan.png, ios.gif > > > http://ionicframework.com/docs/nightly/api/directive/ionSpinner/ -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19514) Ionic Palette: New ion-spinner wizard

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19514?page=com.atlassian.jira.plugi... ] Daniel Azarov updated JBIDE-19514: ---------------------------------- Attachment: (was: ios-small11.png) > Ionic Palette: New ion-spinner wizard > ------------------------------------- > > Key: JBIDE-19514 > URL: https://issues.jboss.org/browse/JBIDE-19514 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.Beta1 > > Attachments: IonicSpinner.png, IonicSpinnerWizBan.png, ios.gif > > > http://ionicframework.com/docs/nightly/api/directive/ionSpinner/ -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19514) Ionic Palette: New ion-spinner wizard

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19514?page=com.atlassian.jira.plugi... ] Daniel Azarov updated JBIDE-19514: ---------------------------------- Attachment: (was: ios-small2.png) > Ionic Palette: New ion-spinner wizard > ------------------------------------- > > Key: JBIDE-19514 > URL: https://issues.jboss.org/browse/JBIDE-19514 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.Beta1 > > Attachments: IonicSpinner.png, IonicSpinnerWizBan.png, ios.gif > > > http://ionicframework.com/docs/nightly/api/directive/ionSpinner/ -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19514) Ionic Palette: New ion-spinner wizard

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19514?page=com.atlassian.jira.plugi... ] Daniel Azarov updated JBIDE-19514: ---------------------------------- Attachment: (was: ios-small4.png) > Ionic Palette: New ion-spinner wizard > ------------------------------------- > > Key: JBIDE-19514 > URL: https://issues.jboss.org/browse/JBIDE-19514 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.Beta1 > > Attachments: IonicSpinner.png, IonicSpinnerWizBan.png, ios.gif > > > http://ionicframework.com/docs/nightly/api/directive/ionSpinner/ -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19514) Ionic Palette: New ion-spinner wizard

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19514?page=com.atlassian.jira.plugi... ] Daniel Azarov updated JBIDE-19514: ---------------------------------- Attachment: (was: ios-small5.png) > Ionic Palette: New ion-spinner wizard > ------------------------------------- > > Key: JBIDE-19514 > URL: https://issues.jboss.org/browse/JBIDE-19514 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.Beta1 > > Attachments: IonicSpinner.png, IonicSpinnerWizBan.png, ios.gif > > > http://ionicframework.com/docs/nightly/api/directive/ionSpinner/ -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19514) Ionic Palette: New ion-spinner wizard

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19514?page=com.atlassian.jira.plugi... ] Daniel Azarov updated JBIDE-19514: ---------------------------------- Attachment: (was: ios8.png) > Ionic Palette: New ion-spinner wizard > ------------------------------------- > > Key: JBIDE-19514 > URL: https://issues.jboss.org/browse/JBIDE-19514 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.Beta1 > > Attachments: IonicSpinner.png, IonicSpinnerWizBan.png, ios-small1.png, ios-small11.png, ios-small12.png, ios-small2.png, ios-small3.png, ios-small4.png, ios-small5.png, ios-small6.png, ios-small7.png, ios-small8.png, ios-small9.png, ios.gif > > > http://ionicframework.com/docs/nightly/api/directive/ionSpinner/ -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19514) Ionic Palette: New ion-spinner wizard

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19514?page=com.atlassian.jira.plugi... ] Daniel Azarov updated JBIDE-19514: ---------------------------------- Attachment: (was: ios9.png) > Ionic Palette: New ion-spinner wizard > ------------------------------------- > > Key: JBIDE-19514 > URL: https://issues.jboss.org/browse/JBIDE-19514 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.Beta1 > > Attachments: IonicSpinner.png, IonicSpinnerWizBan.png, ios-small1.png, ios-small11.png, ios-small12.png, ios-small2.png, ios-small3.png, ios-small4.png, ios-small5.png, ios-small6.png, ios-small7.png, ios-small8.png, ios-small9.png, ios.gif > > > http://ionicframework.com/docs/nightly/api/directive/ionSpinner/ -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues April 2015