April 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19727) An error of "0" is displayed to the user after a failed Cordova mobile engine install

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19727?page=com.atlassian.jira.plugi... ] Len DiMaggio updated JBIDE-19727: --------------------------------- Component/s: aerogear-hybrid (was: integration-platform) > An error of "0" is displayed to the user after a failed Cordova mobile engine install > ------------------------------------------------------------------------------------- > > Key: JBIDE-19727 > URL: https://issues.jboss.org/browse/JBIDE-19727 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Gorkem Ercan > Attachments: error.png, jbosstools-diagnostics-20150428131923.zip > > > When trying to install a 4.0 Cordova mobile engine, this error dialog is displayed: > An error has occurred. See error log for more details. > 0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19728) Easy Import - The first and second screens in the dialog should be merged into one

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19728?page=com.atlassian.jira.plugi... ] Gorkem Ercan reassigned JBIDE-19728: ------------------------------------ Assignee: Mickael Istria (was: Ilya Buziuk) > Easy Import - The first and second screens in the dialog should be merged into one > ---------------------------------------------------------------------------------- > > Key: JBIDE-19728 > URL: https://issues.jboss.org/browse/JBIDE-19728 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid, integration-platform > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Mickael Istria > Attachments: import_1.png, import_2.png > > > See the attached screenshots - in the first dialog screen (1/6), the user is presented with a largely blank display. After he/she selects "next" the dialog (2/6) shows the projects that are eligible to be imported. > Why not simply skip the first screen and start with the second? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19725) EasyImport plugin title misspelled

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19725?page=com.atlassian.jira.plugi... ] Ilya Buziuk reassigned JBIDE-19725: ----------------------------------- Assignee: Gorkem Ercan (was: Ilya Buziuk) > EasyImport plugin title misspelled > ---------------------------------- > > Key: JBIDE-19725 > URL: https://issues.jboss.org/browse/JBIDE-19725 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-platform > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Gorkem Ercan > Attachments: import.png > > > The plugin name is spelled as: > JBoss Easymport for Aerogear -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19728) Easy Import - The first and second screens in the dialog should be merged into one

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19728?page=com.atlassian.jira.plugi... ] Len DiMaggio reassigned JBIDE-19728: ------------------------------------ Assignee: Ilya Buziuk > Easy Import - The first and second screens in the dialog should be merged into one > ---------------------------------------------------------------------------------- > > Key: JBIDE-19728 > URL: https://issues.jboss.org/browse/JBIDE-19728 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid, integration-platform > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Ilya Buziuk > Attachments: import_1.png, import_2.png > > > See the attached screenshots - in the first dialog screen (1/6), the user is presented with a largely blank display. After he/she selects "next" the dialog (2/6) shows the projects that are eligible to be imported. > Why not simply skip the first screen and start with the second? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19727) An error of "0" is displayed to the user after a failed Cordova mobile engine install

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19727?page=com.atlassian.jira.plugi... ] Ilya Buziuk reassigned JBIDE-19727: ----------------------------------- Assignee: Gorkem Ercan (was: Ilya Buziuk) > An error of "0" is displayed to the user after a failed Cordova mobile engine install > ------------------------------------------------------------------------------------- > > Key: JBIDE-19727 > URL: https://issues.jboss.org/browse/JBIDE-19727 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-platform > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Gorkem Ercan > Attachments: error.png, jbosstools-diagnostics-20150428131923.zip > > > When trying to install a 4.0 Cordova mobile engine, this error dialog is displayed: > An error has occurred. See error log for more details. > 0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19728) Easy Import - The first and second screens in the dialog should be merged into one

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19728?page=com.atlassian.jira.plugi... ] Len DiMaggio updated JBIDE-19728: --------------------------------- Attachment: import_2.png import_1.png > Easy Import - The first and second screens in the dialog should be merged into one > ---------------------------------------------------------------------------------- > > Key: JBIDE-19728 > URL: https://issues.jboss.org/browse/JBIDE-19728 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid, integration-platform > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Attachments: import_1.png, import_2.png > > > See the attached screenshots - in the first dialog screen (1/6), the user is presented with a largely blank display. After he/she selects "next" the dialog (2/6) shows the projects that are eligible to be imported. > Why not simply skip the first screen and start with the second? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19728) Easy Import - The first and second screens in the dialog should be merged into one

by Len DiMaggio (JIRA)

Len DiMaggio created JBIDE-19728: ------------------------------------ Summary: Easy Import - The first and second screens in the dialog should be merged into one Key: JBIDE-19728 URL: https://issues.jboss.org/browse/JBIDE-19728 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: aerogear-hybrid, integration-platform Affects Versions: 4.3.0.Alpha2 Reporter: Len DiMaggio See the attached screenshots - in the first dialog screen (1/6), the user is presented with a largely blank display. After he/she selects "next" the dialog (2/6) shows the projects that are eligible to be imported. Why not simply skip the first screen and start with the second? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19532) "Edit Server Runtime Environment" Dialog configuration validation is broken

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19532?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-19532: ------------------------------------- Denis: I've set up the same situation you have, but I'm still seeing validation errors. And yes, I'm using the browse button, and selecting a folder that is sym-linked to the home directory. The error message I see is Configuration file is not found: /home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded_sym/configuration/standalone.xml The wizard is not completable due to this error. [~mmalina] Can you test this? My workflow is: 1) Create new wf 8.2 server+runtime with homedir /home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded 2) Create symlink /home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded_sym -> /home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded 3) Double-click server to open editor, click Runtime Environment 4) Click "browse" on "Server Base Directory" (or Configuration Base Directory if you're using a previous version) 5) Browse to /home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded_sym 6) Check if there's an error message > "Edit Server Runtime Environment" Dialog configuration validation is broken > --------------------------------------------------------------------------- > > Key: JBIDE-19532 > URL: https://issues.jboss.org/browse/JBIDE-19532 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.3.CR1 > Reporter: Denis Golovin > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > Attachments: data-folder-config.png, Edit Server Runtime Environment _102.png > > > If I use "Browse" button for "Configuration base directory" and "Configuration file" validation has no complains, but result is broken Server that cannot start. > {code}java.lang.IllegalStateException: basedir /home/eskimo/Java/wildfly-8.0.0.Final/configuration does not exist. > at org.apache.tools.ant.DirectoryScanner.scan(DirectoryScanner.java:879) > at org.jboss.ide.eclipse.as.core.extensions.descriptors.AntFileFilter.getIncludedFiles(AntFileFilter.java:40) > at org.jboss.ide.eclipse.as.core.extensions.descriptors.XPathQuery.refresh(XPathQuery.java:133) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.findPort(XPathsPortsController.java:80) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.getPortOffset(XPathsPortsController.java:128) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.getJBossWebPort(XPathsPortsController.java:110) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.findPort(XPathsPortsController.java:58) > at org.jboss.ide.eclipse.as.core.server.internal.JBossServer.findPort(JBossServer.java:209) > at org.jboss.ide.eclipse.as.core.server.internal.JBossServer.getJBossWebPort(JBossServer.java:195) > at org.jboss.ide.eclipse.as.core.extensions.polling.WebPortPoller.getURL(WebPortPoller.java:84) > at org.jboss.ide.eclipse.as.core.extensions.polling.WebPortPoller.getCurrentStateSynchronous(WebPortPoller.java:155) > at org.jboss.ide.eclipse.as.core.util.PollThreadUtils.isServerStarted(PollThreadUtils.java:227) > at org.jboss.ide.eclipse.as.core.util.PollThreadUtils.isServerStarted(PollThreadUtils.java:213) > at org.jboss.ide.eclipse.as.core.server.internal.launch.StandardLocalJBossStartLaunchDelegate.isServerStarted(StandardLocalJBossStartLaunchDelegate.java:68) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.AbstractStartJavaServerLaunchDelegate.preLaunchCheck(AbstractStartJavaServerLaunchDelegate.java:117) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalJBossLaunchController.preLaunchCheck(LocalJBossLaunchController.java:119) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.preLaunchCheck(ControllableServerLaunchConfiguration.java:86) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:840) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731) > at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3541) > at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3477) > at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19532) "Edit Server Runtime Environment" Dialog configuration validation is broken

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19532?page=com.atlassian.jira.plugi... ] Rob Stryker edited comment on JBIDE-19532 at 4/28/15 1:22 PM: -------------------------------------------------------------- Denis: I've set up the same situation you have, but I'm still NOT seeing validation errors. And yes, I'm using the browse button, and selecting a folder that is sym-linked to the home directory. The error message I see is Configuration file is not found: /home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded_sym/configuration/standalone.xml The wizard is not completable due to this error. [~mmalina] Can you test this? My workflow is: 1) Create new wf 8.2 server+runtime with homedir /home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded 2) Create symlink /home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded_sym -> /home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded 3) Double-click server to open editor, click Runtime Environment 4) Click "browse" on "Server Base Directory" (or Configuration Base Directory if you're using a previous version) 5) Browse to /home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded_sym 6) Check if there's an error message was (Author: rob.stryker): Denis: I've set up the same situation you have, but I'm still seeing validation errors. And yes, I'm using the browse button, and selecting a folder that is sym-linked to the home directory. The error message I see is Configuration file is not found: /home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded_sym/configuration/standalone.xml The wizard is not completable due to this error. [~mmalina] Can you test this? My workflow is: 1) Create new wf 8.2 server+runtime with homedir /home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded 2) Create symlink /home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded_sym -> /home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded 3) Double-click server to open editor, click Runtime Environment 4) Click "browse" on "Server Base Directory" (or Configuration Base Directory if you're using a previous version) 5) Browse to /home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded_sym 6) Check if there's an error message > "Edit Server Runtime Environment" Dialog configuration validation is broken > --------------------------------------------------------------------------- > > Key: JBIDE-19532 > URL: https://issues.jboss.org/browse/JBIDE-19532 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.3.CR1 > Reporter: Denis Golovin > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > Attachments: data-folder-config.png, Edit Server Runtime Environment _102.png > > > If I use "Browse" button for "Configuration base directory" and "Configuration file" validation has no complains, but result is broken Server that cannot start. > {code}java.lang.IllegalStateException: basedir /home/eskimo/Java/wildfly-8.0.0.Final/configuration does not exist. > at org.apache.tools.ant.DirectoryScanner.scan(DirectoryScanner.java:879) > at org.jboss.ide.eclipse.as.core.extensions.descriptors.AntFileFilter.getIncludedFiles(AntFileFilter.java:40) > at org.jboss.ide.eclipse.as.core.extensions.descriptors.XPathQuery.refresh(XPathQuery.java:133) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.findPort(XPathsPortsController.java:80) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.getPortOffset(XPathsPortsController.java:128) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.getJBossWebPort(XPathsPortsController.java:110) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.XPathsPortsController.findPort(XPathsPortsController.java:58) > at org.jboss.ide.eclipse.as.core.server.internal.JBossServer.findPort(JBossServer.java:209) > at org.jboss.ide.eclipse.as.core.server.internal.JBossServer.getJBossWebPort(JBossServer.java:195) > at org.jboss.ide.eclipse.as.core.extensions.polling.WebPortPoller.getURL(WebPortPoller.java:84) > at org.jboss.ide.eclipse.as.core.extensions.polling.WebPortPoller.getCurrentStateSynchronous(WebPortPoller.java:155) > at org.jboss.ide.eclipse.as.core.util.PollThreadUtils.isServerStarted(PollThreadUtils.java:227) > at org.jboss.ide.eclipse.as.core.util.PollThreadUtils.isServerStarted(PollThreadUtils.java:213) > at org.jboss.ide.eclipse.as.core.server.internal.launch.StandardLocalJBossStartLaunchDelegate.isServerStarted(StandardLocalJBossStartLaunchDelegate.java:68) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.AbstractStartJavaServerLaunchDelegate.preLaunchCheck(AbstractStartJavaServerLaunchDelegate.java:117) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalJBossLaunchController.preLaunchCheck(LocalJBossLaunchController.java:119) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.preLaunchCheck(ControllableServerLaunchConfiguration.java:86) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:840) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731) > at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3541) > at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3477) > at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19727) An error of "0" is displayed to the user after a failed Cordova mobile engine install

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19727?page=com.atlassian.jira.plugi... ] Len DiMaggio updated JBIDE-19727: --------------------------------- Attachment: jbosstools-diagnostics-20150428131923.zip > An error of "0" is displayed to the user after a failed Cordova mobile engine install > ------------------------------------------------------------------------------------- > > Key: JBIDE-19727 > URL: https://issues.jboss.org/browse/JBIDE-19727 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-platform > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Attachments: error.png, jbosstools-diagnostics-20150428131923.zip > > > When trying to install a 4.0 Cordova mobile engine, this error dialog is displayed: > An error has occurred. See error log for more details. > 0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19727) An error of "0" is displayed to the user after a failed Cordova mobile engine install

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19727?page=com.atlassian.jira.plugi... ] Len DiMaggio reassigned JBIDE-19727: ------------------------------------ Assignee: Ilya Buziuk > An error of "0" is displayed to the user after a failed Cordova mobile engine install > ------------------------------------------------------------------------------------- > > Key: JBIDE-19727 > URL: https://issues.jboss.org/browse/JBIDE-19727 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-platform > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Ilya Buziuk > Attachments: error.png, jbosstools-diagnostics-20150428131923.zip > > > When trying to install a 4.0 Cordova mobile engine, this error dialog is displayed: > An error has occurred. See error log for more details. > 0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19727) An error of "0" is displayed to the user after a failed Cordova mobile engine install

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19727?page=com.atlassian.jira.plugi... ] Len DiMaggio updated JBIDE-19727: --------------------------------- Attachment: error.png The error logged is: !ENTRY org.eclipse.jface 4 2 2015-04-28 12:50:49.578 !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.jface". !STACK 0 java.lang.ArrayIndexOutOfBoundsException: 0 at org.eclipse.thym.ui.internal.engine.AvailableCordovaEnginesSection$1.checkStateChanged(AvailableCordovaEnginesSection.java:307) at org.eclipse.jface.viewers.CheckboxTreeViewer$1.run(CheckboxTreeViewer.java:167) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173) at org.eclipse.jface.viewers.CheckboxTreeViewer.fireCheckStateChanged(CheckboxTreeViewer.java:164) at org.eclipse.jface.viewers.CheckboxTreeViewer.handleSelect(CheckboxTreeViewer.java:295) at org.eclipse.jface.viewers.StructuredViewer$4.widgetSelected(StructuredViewer.java:1257) at org.eclipse.jface.util.OpenStrategy.fireSelectionEvent(OpenStrategy.java:242) at org.eclipse.jface.util.OpenStrategy.access$4(OpenStrategy.java:236) at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:408) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4477) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1322) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3815) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3425) at org.eclipse.jface.window.Window.runEventLoop(Window.java:827) at org.eclipse.jface.window.Window.open(Window.java:803) at org.jboss.tools.central.editors.GettingStartedPage.openWizard(GettingStartedPage.java:700) at org.jboss.tools.central.editors.GettingStartedPage.access$14(GettingStartedPage.java:685) at org.jboss.tools.central.editors.GettingStartedPage$7.linkActivated(GettingStartedPage.java:639) at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleActivate(AbstractHyperlink.java:233) at org.eclipse.ui.forms.widgets.ImageHyperlink.handleActivate(ImageHyperlink.java:201) at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleMouseUp(AbstractHyperlink.java:327) at org.eclipse.ui.forms.widgets.AbstractHyperlink.access$2(AbstractHyperlink.java:311) at org.eclipse.ui.forms.widgets.AbstractHyperlink$4.handleEvent(AbstractHyperlink.java:125) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4477) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1322) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3815) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3425) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1112) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:993) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138) 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:380) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235) 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) > An error of "0" is displayed to the user after a failed Cordova mobile engine install > ------------------------------------------------------------------------------------- > > Key: JBIDE-19727 > URL: https://issues.jboss.org/browse/JBIDE-19727 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-platform > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Attachments: error.png > > > When trying to install a 4.0 Cordova mobile engine, this error dialog is displayed: > An error has occurred. See error log for more details. > 0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19727) An error of "0" is displayed to the user after a failed Cordova mobile engine install

by Len DiMaggio (JIRA)

Len DiMaggio created JBIDE-19727: ------------------------------------ Summary: An error of "0" is displayed to the user after a failed Cordova mobile engine install Key: JBIDE-19727 URL: https://issues.jboss.org/browse/JBIDE-19727 Project: Tools (JBoss Tools) Issue Type: Bug Components: integration-platform Affects Versions: 4.3.0.Alpha2 Reporter: Len DiMaggio When trying to install a 4.0 Cordova mobile engine, this error dialog is displayed: An error has occurred. See error log for more details. 0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-2044) .eclipseproduct file no longer refers to JBDS

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-2044?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-2044: -------------------------------- Description: Before, with the linux x64 installer (jbdevstudio-product-linux-gtk-x86_64-5.0.0.v201202271832M-H79-Beta1.jar) the .eclipseproduct file read: {code} name=JBoss Developer Studio id=com.jboss.jbds.all version=5.0.0.v201202271832M-H79-Beta1 {code} Now, with the universal installer (jbdevstudio-product-universal-5.0.0.v201202271832M-H79-Beta1.jar), it reads: {code} name=Eclipse Platform id=org.eclipse.platform version=3.7.0 {code} Latest code in equinox.runtime master branch is located http://git.eclipse.org/c/equinox/rt.equinox.framework.git/tree/bundles/or... was: Before, with the linux x64 installer (jbdevstudio-product-linux-gtk-x86_64-5.0.0.v201202271832M-H79-Beta1.jar) the .eclipseproduct file read: {code} name=JBoss Developer Studio id=com.jboss.jbds.all version=5.0.0.v201202271832M-H79-Beta1 {code} Now, with the universal installer (jbdevstudio-product-universal-5.0.0.v201202271832M-H79-Beta1.jar), it reads: {code} name=Eclipse Platform id=org.eclipse.platform version=3.7.0 {code} > .eclipseproduct file no longer refers to JBDS > --------------------------------------------- > > Key: JBDS-2044 > URL: https://issues.jboss.org/browse/JBDS-2044 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 5.0.0.Beta1 > Reporter: Nick Boldt > Assignee: Denis Golovin > Labels: discuss > Fix For: 8.x > > > Before, with the linux x64 installer (jbdevstudio-product-linux-gtk-x86_64-5.0.0.v201202271832M-H79-Beta1.jar) the .eclipseproduct file read: > {code} > name=JBoss Developer Studio > id=com.jboss.jbds.all > version=5.0.0.v201202271832M-H79-Beta1 > {code} > Now, with the universal installer (jbdevstudio-product-universal-5.0.0.v201202271832M-H79-Beta1.jar), it reads: > {code} > name=Eclipse Platform > id=org.eclipse.platform > version=3.7.0 > {code} > Latest code in equinox.runtime master branch is located http://git.eclipse.org/c/equinox/rt.equinox.framework.git/tree/bundles/or... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19712) Application wizard: Add create from template details pane

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19712?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-19712: --------------------------------------- [~adietish] added details pane. please review and merge > Application wizard: Add create from template details pane > --------------------------------------------------------- > > Key: JBIDE-19712 > URL: https://issues.jboss.org/browse/JBIDE-19712 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Labels: application_wizard > Fix For: 4.3.0.Beta1 > > > Add details pane similiar to v2 where you get template details when you select an individual template. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19719) EasyImport of MobileHybrid project results in errors - lack of configured Andriod SDK is written to .log, but it is not communicated to the user via the UI

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19719?page=com.atlassian.jira.plugi... ] Gorkem Ercan commented on JBIDE-19719: -------------------------------------- During import Android SDK is not really needed. It is logged only as a consequence of a chain of calls that tries to precompile the cordova-android runtime to generate the cordova.jar. Hence the "Android SDK location is not defined" exception is always logged but not shown to the user until it actually becomes a blocker for the user. An error dialog that opens up the appropriate preference is fired when you try to run the project on Android device/simulator or export for android native formats. I think we can completely remove the logging or make it a warning but we should not open a dialog during import. > EasyImport of MobileHybrid project results in errors - lack of configured Andriod SDK is written to .log, but it is not communicated to the user via the UI > ----------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19719 > URL: https://issues.jboss.org/browse/JBIDE-19719 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-platform > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Gorkem Ercan > Attachments: jbosstools-diagnostics-20150427143128.zip, jbosstools-diagnostics-20150428105107.zip > > > This issue is related to JBIDE-19716 > Multiple errors are raised when a mobile hybrid project created in Central in JBoss Tools 4.3.0.alpha2 is exported and then imported from a directory using easy import. > See attached .zip for the error file (logs, etc..) > The error message logged is: > eclipse.core.runtime.CoreException: Android SDK location is not defined -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19726) Error messages related to failures configuring Cordova version 4 engine are written to .log, not displayed to user

by Len DiMaggio (JIRA)

Len DiMaggio created JBIDE-19726: ------------------------------------ Summary: Error messages related to failures configuring Cordova version 4 engine are written to .log, not displayed to user Key: JBIDE-19726 URL: https://issues.jboss.org/browse/JBIDE-19726 Project: Tools (JBoss Tools) Issue Type: Bug Components: integration-platform Affects Versions: 4.3.0.Alpha2 Reporter: Len DiMaggio Attempts to configure Cordova version 4.0 fail - another case of changes in directory tree - the errors are written to the .log, and are not communicated to the user via the UI !ENTRY org.eclipse.thym.android.core 2 0 2015-04-28 11:28:43.882 !MESSAGE Missing Android engine file /home/ldimaggi/.cordova/lib/android/cordova/4.0.0/framework/cordova-4.0.0.jar !ENTRY org.eclipse.thym.android.core 2 0 2015-04-28 11:28:43.882 !MESSAGE Missing Android engine file /home/ldimaggi/.cordova/lib/android/cordova/4.0.0/framework/assets/www/cordova.js !ENTRY org.eclipse.thym.ios.core 4 0 2015-04-28 11:28:43.882 !MESSAGE Can not detect version. VERSION file /home/ldimaggi/.cordova/lib/android/cordova/4.0.0/CordovaLib/VERSION is missing -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19725) EasyImport plugin title misspelled

by Len DiMaggio (JIRA)

Len DiMaggio created JBIDE-19725: ------------------------------------ Summary: EasyImport plugin title misspelled Key: JBIDE-19725 URL: https://issues.jboss.org/browse/JBIDE-19725 Project: Tools (JBoss Tools) Issue Type: Bug Components: integration-platform Affects Versions: 4.3.0.Alpha2 Reporter: Len DiMaggio Attachments: import.png The plugin name is spelled as: JBoss Easymport for Aerogear -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19725) EasyImport plugin title misspelled

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19725?page=com.atlassian.jira.plugi... ] Len DiMaggio reassigned JBIDE-19725: ------------------------------------ Assignee: Ilya Buziuk > EasyImport plugin title misspelled > ---------------------------------- > > Key: JBIDE-19725 > URL: https://issues.jboss.org/browse/JBIDE-19725 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-platform > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Ilya Buziuk > Attachments: import.png > > > The plugin name is spelled as: > JBoss Easymport for Aerogear -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19725) EasyImport plugin title misspelled

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19725?page=com.atlassian.jira.plugi... ] Len DiMaggio updated JBIDE-19725: --------------------------------- Attachment: import.png > EasyImport plugin title misspelled > ---------------------------------- > > Key: JBIDE-19725 > URL: https://issues.jboss.org/browse/JBIDE-19725 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-platform > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Ilya Buziuk > Attachments: import.png > > > The plugin name is spelled as: > JBoss Easymport for Aerogear -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19476) Add label validation

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19476?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-19476: --------------------------------------- [~adietish] rebased after your merge to jbide-19009 create from template > Add label validation > -------------------- > > Key: JBIDE-19476 > URL: https://issues.jboss.org/browse/JBIDE-19476 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Priority: Blocker > Fix For: 4.3.0.Beta1 > > > Add label key and value validations to the 'label' page in accordance of what is valid in Kubernetes. This should be part of the 'edit label' page that will be presented to a user -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-431) Designer requires a new luna IS-TP complete with new version of LOCUS

by Paul Richardson (JIRA)

Paul Richardson created JBTIS-431: ------------------------------------- Summary: Designer requires a new luna IS-TP complete with new version of LOCUS Key: JBTIS-431 URL: https://issues.jboss.org/browse/JBTIS-431 Project: JBoss Tools Integration Stack Issue Type: Enhancement Components: target-platform Affects Versions: 4.2.0.Final-TP Reporter: Paul Richardson https://issues.jboss.org/browse/LOCUS-23 defines a new requirement in locus that results in a new version of the locus update site. Once a new build is available, Teiid Designer will need this locus version integrated into a new LUNA build of the IS-TP. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (LOCUS-41) New release of 4.2.x required to include new version of LOCUS

by Paul Richardson (JIRA)

Paul Richardson created LOCUS-41: ------------------------------------ Summary: New release of 4.2.x required to include new version of LOCUS Key: LOCUS-41 URL: https://issues.jboss.org/browse/LOCUS-41 Project: JBoss Tools Locus Issue Type: Enhancement Reporter: Paul Richardson https://issues.jboss.org/browse/LOCUS-23 defines a new requirement in locus that results in a new version of the locus update site. Once a new build is necessary, Designer will need this locus version integrated into a new LUNA build of the IS TP. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19716) JBoss Tools 4.3.0.Alpha2 does not recognize an installed Android SDK

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19716?page=com.atlassian.jira.plugi... ] Len DiMaggio commented on JBIDE-19716: -------------------------------------- This JIRA is a user error as while the SDK was downloaded, its installation was not completed. We should at least add a note to the user docs to remind the user that he/she must complete the install of the SDK. > JBoss Tools 4.3.0.Alpha2 does not recognize an installed Android SDK > -------------------------------------------------------------------- > > Key: JBIDE-19716 > URL: https://issues.jboss.org/browse/JBIDE-19716 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Gorkem Ercan > Attachments: Android_SDK.png, sdk_change.png > > > With 4.3.0.Alpha2: > * Install Android SDK from: http://dl.google.com/android/android-sdk_r24.1.2-linux.tgz > * Attempt to configure the installed SDK in Perferences->Hybrid Mobile->Android > * See the attached screen shot for the "Not a valid Android SDK directory" error. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19719) EasyImport of MobileHybrid project results in errors - lack of configured Andriod SDK is written to .log, but it is not communicated to the user via the UI

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19719?page=com.atlassian.jira.plugi... ] Len DiMaggio commented on JBIDE-19719: -------------------------------------- The solution to this JIRA will be to communication this error directly to the user in a dialog during the project import - and give him/her an opportunity to configure an already installed SDK during the project creation: org.eclipse.core.runtime.CoreException: Android SDK location is not defined > EasyImport of MobileHybrid project results in errors - lack of configured Andriod SDK is written to .log, but it is not communicated to the user via the UI > ----------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19719 > URL: https://issues.jboss.org/browse/JBIDE-19719 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-platform > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Gorkem Ercan > Attachments: jbosstools-diagnostics-20150427143128.zip, jbosstools-diagnostics-20150428105107.zip > > > This issue is related to JBIDE-19716 > Multiple errors are raised when a mobile hybrid project created in Central in JBoss Tools 4.3.0.alpha2 is exported and then imported from a directory using easy import. > See attached .zip for the error file (logs, etc..) > The error message logged is: > eclipse.core.runtime.CoreException: Android SDK location is not defined -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19719) EasyImport of MobileHybrid project results in errors - lack of configured Andriod SDK is written to .log, but it is not communicated to the user via the UI

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19719?page=com.atlassian.jira.plugi... ] Len DiMaggio edited comment on JBIDE-19719 at 4/28/15 11:39 AM: ---------------------------------------------------------------- Sorry that the steps were not clear - the steps that must be performed to avoid the errors are: * Starting with a clean install of JBoss Tools 4.3.0.alpha2, and a new/empty workspace * From JBoss Central, create a new Mobile Hybrid project ("start from scratch") ** In the process of the project creation, download a cordova mobile engine * Configure an already installed Android SDK (I used android-sdk_r24.1.2-linux) ** If this^ step is not performed at this point, the project creation will complete with errors * Export the project to a directory outside of the workspace * Delete the project from the workspace * Attempt to import the project using the "import from directory" option was (Author: ldimaggio): Sorry that the steps were not clear - the steps are: * From JBoss Central, create a new Mobile Hybrid project ("start from scratch") * Configure an Android SDK (I used android-sdk_r24.1.2-linux) * Export the project to a directory outside of the workspace * Delete the project from the workspace * Attempt to import the project using the "import from directory" option > EasyImport of MobileHybrid project results in errors - lack of configured Andriod SDK is written to .log, but it is not communicated to the user via the UI > ----------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19719 > URL: https://issues.jboss.org/browse/JBIDE-19719 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-platform > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Gorkem Ercan > Attachments: jbosstools-diagnostics-20150427143128.zip, jbosstools-diagnostics-20150428105107.zip > > > This issue is related to JBIDE-19716 > Multiple errors are raised when a mobile hybrid project created in Central in JBoss Tools 4.3.0.alpha2 is exported and then imported from a directory using easy import. > See attached .zip for the error file (logs, etc..) > The error message logged is: > eclipse.core.runtime.CoreException: Android SDK location is not defined -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19719) EasyImport of MobileHybrid project results in errors - lack of configured Andriod SDK is written to .log, but it is not communicated to the user via the UI

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19719?page=com.atlassian.jira.plugi... ] Len DiMaggio updated JBIDE-19719: --------------------------------- Summary: EasyImport of MobileHybrid project results in errors - lack of configured Andriod SDK is written to .log, but it is not communicated to the user via the UI (was: "EasyImport" of Mobile Hybrid project fails on JBoss Tools 4.3.0.Alpha2) Description: This issue is related to JBIDE-19716 Multiple errors are raised when a mobile hybrid project created in Central in JBoss Tools 4.3.0.alpha2 is exported and then imported from a directory using easy import. See attached .zip for the error file (logs, etc..) The error message logged is: eclipse.core.runtime.CoreException: Android SDK location is not defined was: This issue is related to JBIDE-19716 Multiple errors are raised when a mobile hybrid project created in Central in JBoss Tools 4.3.0.alpha2 is exported and then imported from a directory using easy import. See attached .zip for the error file (logs, etc..) > EasyImport of MobileHybrid project results in errors - lack of configured Andriod SDK is written to .log, but it is not communicated to the user via the UI > ----------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19719 > URL: https://issues.jboss.org/browse/JBIDE-19719 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-platform > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Gorkem Ercan > Attachments: jbosstools-diagnostics-20150427143128.zip, jbosstools-diagnostics-20150428105107.zip > > > This issue is related to JBIDE-19716 > Multiple errors are raised when a mobile hybrid project created in Central in JBoss Tools 4.3.0.alpha2 is exported and then imported from a directory using easy import. > See attached .zip for the error file (logs, etc..) > The error message logged is: > eclipse.core.runtime.CoreException: Android SDK location is not defined -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19719) "EasyImport" of Mobile Hybrid project fails on JBoss Tools 4.3.0.Alpha2

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19719?page=com.atlassian.jira.plugi... ] Len DiMaggio updated JBIDE-19719: --------------------------------- Attachment: jbosstools-diagnostics-20150428105107.zip > "EasyImport" of Mobile Hybrid project fails on JBoss Tools 4.3.0.Alpha2 > ----------------------------------------------------------------------- > > Key: JBIDE-19719 > URL: https://issues.jboss.org/browse/JBIDE-19719 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-platform > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Gorkem Ercan > Attachments: jbosstools-diagnostics-20150427143128.zip, jbosstools-diagnostics-20150428105107.zip > > > This issue is related to JBIDE-19716 > Multiple errors are raised when a mobile hybrid project created in Central in JBoss Tools 4.3.0.alpha2 is exported and then imported from a directory using easy import. > See attached .zip for the error file (logs, etc..) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19719) "EasyImport" of Mobile Hybrid project fails on JBoss Tools 4.3.0.Alpha2

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19719?page=com.atlassian.jira.plugi... ] Len DiMaggio commented on JBIDE-19719: -------------------------------------- The svn issues that Max referred to will be addressed in a separate JIRA. The JBoss Tools configuration used had all of JBoss Tools installed. The report file: jbosstools-diagnostics-20150428105107.zip - just attached to this JIRA reflects a JBoss Tools configuration with only "JBoss Tools Abridged" installed. The svn errors are not included in the log in this report file. > "EasyImport" of Mobile Hybrid project fails on JBoss Tools 4.3.0.Alpha2 > ----------------------------------------------------------------------- > > Key: JBIDE-19719 > URL: https://issues.jboss.org/browse/JBIDE-19719 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-platform > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Gorkem Ercan > Attachments: jbosstools-diagnostics-20150427143128.zip > > > This issue is related to JBIDE-19716 > Multiple errors are raised when a mobile hybrid project created in Central in JBoss Tools 4.3.0.alpha2 is exported and then imported from a directory using easy import. > See attached .zip for the error file (logs, etc..) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19719) "EasyImport" of Mobile Hybrid project fails on JBoss Tools 4.3.0.Alpha2

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19719?page=com.atlassian.jira.plugi... ] Len DiMaggio edited comment on JBIDE-19719 at 4/28/15 11:10 AM: ---------------------------------------------------------------- Sorry that the steps were not clear - the steps are: * From JBoss Central, create a new Mobile Hybrid project ("start from scratch") * Configure an Android SDK (I used android-sdk_r24.1.2-linux) * Export the project to a directory outside of the workspace * Delete the project from the workspace * Attempt to import the project using the "import from directory" option was (Author: ldimaggio): Sorry that the steps were not clear - the steps are: * From JBoss Central, create a new Mobile Hybrid project ("start from scratch") * Export the project to a directory outside of the workspace * Attempt to import the project using the "import from directory" option > "EasyImport" of Mobile Hybrid project fails on JBoss Tools 4.3.0.Alpha2 > ----------------------------------------------------------------------- > > Key: JBIDE-19719 > URL: https://issues.jboss.org/browse/JBIDE-19719 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-platform > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Gorkem Ercan > Attachments: jbosstools-diagnostics-20150427143128.zip > > > This issue is related to JBIDE-19716 > Multiple errors are raised when a mobile hybrid project created in Central in JBoss Tools 4.3.0.alpha2 is exported and then imported from a directory using easy import. > See attached .zip for the error file (logs, etc..) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19724) Provide public version of alpha releases for testing JBT

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19724?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-19724: ---------------------------------- Component/s: build > Provide public version of alpha releases for testing JBT > -------------------------------------------------------- > > Key: JBIDE-19724 > URL: https://issues.jboss.org/browse/JBIDE-19724 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: ehsavoie Hugonnet > > As a participant of the jbosstools-cat project whenever a testing release is done I have to install all of it by hand to have a clean instance to test on. > Could you provide such a bundle à la JBDS during the testing periods ? > http://lists.jboss.org/pipermail/jbosstools-cat/2015-April/000027.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3424) Easymport is missing from JBDS 9.0.0.Alpha2

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3424?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-3424. ---------------------------- Fix Version/s: 9.0.0.Alpha2 (was: 9.0.0.Beta1) Resolution: Cannot Reproduce Bug Cannot reproduce. Closing for 9.0.0.Alpha2 fixversion. > Easymport is missing from JBDS 9.0.0.Alpha2 > ------------------------------------------- > > Key: JBDS-3424 > URL: https://issues.jboss.org/browse/JBDS-3424 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 9.0.0.Alpha2 > Environment: Version: 9.0.0.Alpha2 > Build id: Alpha2-v20150405-1144-B2918 > Build date: 20150405-1144 > Reporter: Len DiMaggio > Assignee: Nick Boldt > Fix For: 9.0.0.Alpha2 > > Attachments: jbds900alpha2_file-menu.png, jbds900alpha2_import-option.png, jbds900alpha2_version.png, JBT_423_Alpha2_easyimport2.png, JBT_423_Alpha2_easyimport3.png, JBT_430_Alpha2_easyimport1.png > > > See attached screenshots from JBoss Tools 4.3.0.Alpha2 - the corresponding import menu entries are missing from JBDS 9.0.0.Alpha2 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3424) Easymport is missing from JBDS 9.0.0.Alpha2

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3424?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3424: ----------------------------- Attachment: jbds900alpha2_import-option.png jbds900alpha2_file-menu.png jbds900alpha2_version.png After a BYOE install of JBDS 9 Alpha2 (B24): !jbds900alpha2_version.png! !jbds900alpha2_file-menu.png! !jbds900alpha2_import-option.png! > Easymport is missing from JBDS 9.0.0.Alpha2 > ------------------------------------------- > > Key: JBDS-3424 > URL: https://issues.jboss.org/browse/JBDS-3424 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 9.0.0.Alpha2 > Environment: Version: 9.0.0.Alpha2 > Build id: Alpha2-v20150405-1144-B2918 > Build date: 20150405-1144 > Reporter: Len DiMaggio > Assignee: Nick Boldt > Fix For: 9.0.0.Beta1 > > Attachments: jbds900alpha2_file-menu.png, jbds900alpha2_import-option.png, jbds900alpha2_version.png, JBT_423_Alpha2_easyimport2.png, JBT_423_Alpha2_easyimport3.png, JBT_430_Alpha2_easyimport1.png > > > See attached screenshots from JBoss Tools 4.3.0.Alpha2 - the corresponding import menu entries are missing from JBDS 9.0.0.Alpha2 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3424) Easymport is missing from JBDS 9.0.0.Alpha2

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3424?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3424: ---------------------------------- [~mickael_istria] Not true. You added it to the core.feature (BYOE) 13 days ago. https://github.com/jbdevstudio/jbdevstudio-product/commit/c110ead7919fe26... https://github.com/jbdevstudio/jbdevstudio-product/blob/jbosstools-4.3.0.... https://github.com/jbdevstudio/jbdevstudio-product/blob/master/features/c... So... either it's not being activated (missing deps?) or Len's version of JBDS is corrupt. In fact it looks like the problem is Len's using an old pre-Alpha version: Alpha2-v20150405 is 3 weeks old. *Thanks for providing the specific version you installed!* Way better than just saying "I installed the Alpha2". :D Len, the latest Alpha is here: http://www.qa.jboss.com/binaries/RHDS/9.0/snapshots/builds/devstudio.prod... Or the latest Beta: http://www.qa.jboss.com/binaries/RHDS/9.0/snapshots/builds/devstudio.prod... > Easymport is missing from JBDS 9.0.0.Alpha2 > ------------------------------------------- > > Key: JBDS-3424 > URL: https://issues.jboss.org/browse/JBDS-3424 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 9.0.0.Alpha2 > Environment: Version: 9.0.0.Alpha2 > Build id: Alpha2-v20150405-1144-B2918 > Build date: 20150405-1144 > Reporter: Len DiMaggio > Assignee: Nick Boldt > Fix For: 9.0.0.Beta1 > > Attachments: JBT_423_Alpha2_easyimport2.png, JBT_423_Alpha2_easyimport3.png, JBT_430_Alpha2_easyimport1.png > > > See attached screenshots from JBoss Tools 4.3.0.Alpha2 - the corresponding import menu entries are missing from JBDS 9.0.0.Alpha2 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (LOCUS-23) New version of Saxon-HE required in locus

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/LOCUS-23?page=com.atlassian.jira.plugin.s... ] Paul Richardson commented on LOCUS-23: -------------------------------------- [~maxandersen] re. JBTIS. No problem. I can raise a JIRA on Paul to take the new version of locus. When would that new version of locus be available to take? re. provisional. I set up this link some time ago so that devs would not have to generate a local TP for Teiid Designer and that the 'new' saxon version would be available to builds in jenkins. It seemed a logical addendum to the publishing script in jenkins to set the TARGET_FOLDER variable, ie. -PARENT_FOLDER locus -TARGET_FOLDER provisional. The objective was to get new versions of Teiid Designer building with the new target-platform (new saxon version) until at such point the JBTIS version can be updated in the former's poms use the new version containing the new locus containing the new version of saxon. Thus, the current Teiid Designer target-platform pom looks like this https://github.com/Teiid-Designer/teiid-designer/blob/master/target-platf... - note the commented-out sections and the attaching of the [teiid-designer-extras-4.2.0.Final.target|https://github.com/Teiid-Designe...] If this objective can be achieved in a better way, can you point it out for me. Apologies if this was the incorrect protocol. > New version of Saxon-HE required in locus > ----------------------------------------- > > Key: LOCUS-23 > URL: https://issues.jboss.org/browse/LOCUS-23 > Project: JBoss Tools Locus > Issue Type: Feature Request > Affects Versions: 1.1.0 > Reporter: Paul Richardson > Assignee: Mickael Istria > Fix For: 1.2.0 > > > The Teiid Server project has updated their dependencies, including increasing the Saxon-HE version to 9.1.5-6j. > Since Teiid Designer takes a cut of the Teiid Server's client, it is necessary to update the Saxon-HE dependency in the former in order to remain in sync. Designer gets it Saxon library from the Locus repository. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19724) Provide public version of alpha releases for testing JBT

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19724?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-19724: ----------------------------------- Project: Tools (JBoss Tools) (was: Developer Studio (JBoss Developer Studio)) Key: JBIDE-19724 (was: JBDS-3429) Workflow: GIT Pull Request workflow (was: CDW v1) Status: Open (was: New) Affects Version/s: 4.3.0.Alpha2 (was: 9.0.0.Alpha2) Docs QE Status: (was: NEW) > Provide public version of alpha releases for testing JBT > -------------------------------------------------------- > > Key: JBIDE-19724 > URL: https://issues.jboss.org/browse/JBIDE-19724 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Affects Versions: 4.3.0.Alpha2 > Reporter: ehsavoie Hugonnet > > As a participant of the jbosstools-cat project whenever a testing release is done I have to install all of it by hand to have a clean instance to test on. > Could you provide such a bundle à la JBDS during the testing periods ? > http://lists.jboss.org/pipermail/jbosstools-cat/2015-April/000027.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19723) Add templates from openshift namespace for 'create from template'

by Jeff Cantrill (JIRA)

Jeff Cantrill created JBIDE-19723: ------------------------------------- Summary: Add templates from openshift namespace for 'create from template' Key: JBIDE-19723 URL: https://issues.jboss.org/browse/JBIDE-19723 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 4.3.0.Beta1 Reporter: Jeff Cantrill When getting templates for your project to create a new application, also get the templates from the 'openshift' namespace -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3424) Easymport is missing from JBDS 9.0.0.Alpha2

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3424?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-3424: -------------------------------------- Easymport in included in the category.xml (JBDS repository), but not in the JBDS feature, so it's not included when using installer or the BYOE feature. > Easymport is missing from JBDS 9.0.0.Alpha2 > ------------------------------------------- > > Key: JBDS-3424 > URL: https://issues.jboss.org/browse/JBDS-3424 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 9.0.0.Alpha2 > Environment: Version: 9.0.0.Alpha2 > Build id: Alpha2-v20150405-1144-B2918 > Build date: 20150405-1144 > Reporter: Len DiMaggio > Assignee: Nick Boldt > Fix For: 9.0.0.Beta1 > > Attachments: JBT_423_Alpha2_easyimport2.png, JBT_423_Alpha2_easyimport3.png, JBT_430_Alpha2_easyimport1.png > > > See attached screenshots from JBoss Tools 4.3.0.Alpha2 - the corresponding import menu entries are missing from JBDS 9.0.0.Alpha2 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3429) Provide public version of alpha releases for testing JBT

by ehsavoie Hugonnet (JIRA)

[ https://issues.jboss.org/browse/JBDS-3429?page=com.atlassian.jira.plugin.... ] ehsavoie Hugonnet updated JBDS-3429: ------------------------------------ Description: As a participant of the jbosstools-cat project whenever a testing release is done I have to install all of it by hand to have a clean instance to test on. Could you provide such a bundle à la JBDS during the testing periods ? http://lists.jboss.org/pipermail/jbosstools-cat/2015-April/000027.html was: As a participant of the jbosstools-cat project whenever a testing release is done I have to install all of it by hand to have a clean instance to test on. Could you provide such a bundle à la JBDS during the testing periods ? > Provide public version of alpha releases for testing JBT > -------------------------------------------------------- > > Key: JBDS-3429 > URL: https://issues.jboss.org/browse/JBDS-3429 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Affects Versions: 9.0.0.Alpha2 > Reporter: ehsavoie Hugonnet > > As a participant of the jbosstools-cat project whenever a testing release is done I have to install all of it by hand to have a clean instance to test on. > Could you provide such a bundle à la JBDS during the testing periods ? > http://lists.jboss.org/pipermail/jbosstools-cat/2015-April/000027.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3429) Provide public version of alpha releases for testing JBT

by ehsavoie Hugonnet (JIRA)

ehsavoie Hugonnet created JBDS-3429: --------------------------------------- Summary: Provide public version of alpha releases for testing JBT Key: JBDS-3429 URL: https://issues.jboss.org/browse/JBDS-3429 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Affects Versions: 9.0.0.Alpha2 Reporter: ehsavoie Hugonnet As a participant of the jbosstools-cat project whenever a testing release is done I have to install all of it by hand to have a clean instance to test on. Could you provide such a bundle à la JBDS during the testing periods ? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3424) Easymport is missing from JBDS 9.0.0.Alpha2

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3424?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3424: ----------------------------- CDW release: + (was: ?) > Easymport is missing from JBDS 9.0.0.Alpha2 > ------------------------------------------- > > Key: JBDS-3424 > URL: https://issues.jboss.org/browse/JBDS-3424 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 9.0.0.Alpha2 > Environment: Version: 9.0.0.Alpha2 > Build id: Alpha2-v20150405-1144-B2918 > Build date: 20150405-1144 > Reporter: Len DiMaggio > Assignee: Nick Boldt > Fix For: 9.0.0.Beta1 > > Attachments: JBT_423_Alpha2_easyimport2.png, JBT_423_Alpha2_easyimport3.png, JBT_430_Alpha2_easyimport1.png > > > See attached screenshots from JBoss Tools 4.3.0.Alpha2 - the corresponding import menu entries are missing from JBDS 9.0.0.Alpha2 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3424) Easymport is missing from JBDS 9.0.0.Alpha2

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3424?page=com.atlassian.jira.plugin.... ] CDW Engine reassigned JBDS-3424: -------------------------------- > Easymport is missing from JBDS 9.0.0.Alpha2 > ------------------------------------------- > > Key: JBDS-3424 > URL: https://issues.jboss.org/browse/JBDS-3424 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 9.0.0.Alpha2 > Environment: Version: 9.0.0.Alpha2 > Build id: Alpha2-v20150405-1144-B2918 > Build date: 20150405-1144 > Reporter: Len DiMaggio > Assignee: Nick Boldt > Fix For: 9.0.0.Beta1 > > Attachments: JBT_423_Alpha2_easyimport2.png, JBT_423_Alpha2_easyimport3.png, JBT_430_Alpha2_easyimport1.png > > > See attached screenshots from JBoss Tools 4.3.0.Alpha2 - the corresponding import menu entries are missing from JBDS 9.0.0.Alpha2 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3424) Easymport is missing from JBDS 9.0.0.Alpha2

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3424?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3424: ----------------------------- CDW qa_ack: + (was: ?) > Easymport is missing from JBDS 9.0.0.Alpha2 > ------------------------------------------- > > Key: JBDS-3424 > URL: https://issues.jboss.org/browse/JBDS-3424 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 9.0.0.Alpha2 > Environment: Version: 9.0.0.Alpha2 > Build id: Alpha2-v20150405-1144-B2918 > Build date: 20150405-1144 > Reporter: Len DiMaggio > Assignee: Nick Boldt > Fix For: 9.0.0.Beta1 > > Attachments: JBT_423_Alpha2_easyimport2.png, JBT_423_Alpha2_easyimport3.png, JBT_430_Alpha2_easyimport1.png > > > See attached screenshots from JBoss Tools 4.3.0.Alpha2 - the corresponding import menu entries are missing from JBDS 9.0.0.Alpha2 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3424) EasyImport is missing from JBDS 9.0.0.Alpha2

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3424?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3424: ---------------------------------- How did you install JBDS 9 Alpha2, and which features are installed? In JBDS, you should have: * org.jboss.tools.central.easymport.feature (CoreTools / Abridged JBDS / BYOE / installer) In JBT, you could have: * org.jboss.tools.aerogear.easymport.feature (AdditionalTools, MobileTools) * org.jboss.tools.central.easymport.feature (CoreTools / Abridged JBT) [~mickael_istria] This is correct, right? Is there another feature / plugin that's needed in JBDS for Easymport to work? > EasyImport is missing from JBDS 9.0.0.Alpha2 > -------------------------------------------- > > Key: JBDS-3424 > URL: https://issues.jboss.org/browse/JBDS-3424 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 9.0.0.Alpha2 > Environment: Version: 9.0.0.Alpha2 > Build id: Alpha2-v20150405-1144-B2918 > Build date: 20150405-1144 > Reporter: Len DiMaggio > Assignee: Nick Boldt > Fix For: 9.0.0.Beta1 > > Attachments: JBT_423_Alpha2_easyimport2.png, JBT_423_Alpha2_easyimport3.png, JBT_430_Alpha2_easyimport1.png > > > See attached screenshots from JBoss Tools 4.3.0.Alpha2 - the corresponding import menu entries are missing from JBDS 9.0.0.Alpha2 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3424) Easymport is missing from JBDS 9.0.0.Alpha2

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3424?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3424: ----------------------------- Summary: Easymport is missing from JBDS 9.0.0.Alpha2 (was: EasyImport is missing from JBDS 9.0.0.Alpha2) > Easymport is missing from JBDS 9.0.0.Alpha2 > ------------------------------------------- > > Key: JBDS-3424 > URL: https://issues.jboss.org/browse/JBDS-3424 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 9.0.0.Alpha2 > Environment: Version: 9.0.0.Alpha2 > Build id: Alpha2-v20150405-1144-B2918 > Build date: 20150405-1144 > Reporter: Len DiMaggio > Assignee: Nick Boldt > Fix For: 9.0.0.Beta1 > > Attachments: JBT_423_Alpha2_easyimport2.png, JBT_423_Alpha2_easyimport3.png, JBT_430_Alpha2_easyimport1.png > > > See attached screenshots from JBoss Tools 4.3.0.Alpha2 - the corresponding import menu entries are missing from JBDS 9.0.0.Alpha2 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3424) Easymport is missing from JBDS 9.0.0.Alpha2

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3424?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3424: ----------------------------- CDW devel_ack: + (was: ?) > Easymport is missing from JBDS 9.0.0.Alpha2 > ------------------------------------------- > > Key: JBDS-3424 > URL: https://issues.jboss.org/browse/JBDS-3424 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 9.0.0.Alpha2 > Environment: Version: 9.0.0.Alpha2 > Build id: Alpha2-v20150405-1144-B2918 > Build date: 20150405-1144 > Reporter: Len DiMaggio > Assignee: Nick Boldt > Fix For: 9.0.0.Beta1 > > Attachments: JBT_423_Alpha2_easyimport2.png, JBT_423_Alpha2_easyimport3.png, JBT_430_Alpha2_easyimport1.png > > > See attached screenshots from JBoss Tools 4.3.0.Alpha2 - the corresponding import menu entries are missing from JBDS 9.0.0.Alpha2 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3424) EasyImport is missing from JBDS 9.0.0.Alpha2

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3424?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3424: ----------------------------- Fix Version/s: 9.0.0.Beta1 > EasyImport is missing from JBDS 9.0.0.Alpha2 > -------------------------------------------- > > Key: JBDS-3424 > URL: https://issues.jboss.org/browse/JBDS-3424 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 9.0.0.Alpha2 > Environment: Version: 9.0.0.Alpha2 > Build id: Alpha2-v20150405-1144-B2918 > Build date: 20150405-1144 > Reporter: Len DiMaggio > Assignee: Nick Boldt > Fix For: 9.0.0.Beta1 > > Attachments: JBT_423_Alpha2_easyimport2.png, JBT_423_Alpha2_easyimport3.png, JBT_430_Alpha2_easyimport1.png > > > See attached screenshots from JBoss Tools 4.3.0.Alpha2 - the corresponding import menu entries are missing from JBDS 9.0.0.Alpha2 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19716) JBoss Tools 4.3.0.Alpha2 does not recognize an installed Android SDK

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19716?page=com.atlassian.jira.plugi... ] Gorkem Ercan commented on JBIDE-19716: -------------------------------------- it seeks the tools and platform-tools folders. The download you have pointed out is missing the "platform-tools" which has the adb command. Did you install a platform? I wonder if platform-tools actually comes with a platform. You can do that by running the "android" command from tools folder. > JBoss Tools 4.3.0.Alpha2 does not recognize an installed Android SDK > -------------------------------------------------------------------- > > Key: JBIDE-19716 > URL: https://issues.jboss.org/browse/JBIDE-19716 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Gorkem Ercan > Attachments: Android_SDK.png, sdk_change.png > > > With 4.3.0.Alpha2: > * Install Android SDK from: http://dl.google.com/android/android-sdk_r24.1.2-linux.tgz > * Attempt to configure the installed SDK in Perferences->Hybrid Mobile->Android > * See the attached screen shot for the "Not a valid Android SDK directory" error. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19719) "EasyImport" of Mobile Hybrid project fails on JBoss Tools 4.3.0.Alpha2

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19719?page=com.atlassian.jira.plugi... ] Len DiMaggio updated JBIDE-19719: --------------------------------- Component/s: integration-platform (was: build) > "EasyImport" of Mobile Hybrid project fails on JBoss Tools 4.3.0.Alpha2 > ----------------------------------------------------------------------- > > Key: JBIDE-19719 > URL: https://issues.jboss.org/browse/JBIDE-19719 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-platform > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Gorkem Ercan > Attachments: jbosstools-diagnostics-20150427143128.zip > > > This issue is related to JBIDE-19716 > Multiple errors are raised when a mobile hybrid project created in Central in JBoss Tools 4.3.0.alpha2 is exported and then imported from a directory using easy import. > See attached .zip for the error file (logs, etc..) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19190) migrate VersionWatch to jbosstools-* repo

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19190?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19190: ------------------------------------ Steps 3 and 4 are part of JBIDE-15481, but steps 1 and 2 still need to be done here before we can resolve this issue. > migrate VersionWatch to jbosstools-* repo > ----------------------------------------- > > Key: JBIDE-19190 > URL: https://issues.jboss.org/browse/JBIDE-19190 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: qa > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Jiri Peterka > Priority: Minor > Fix For: 4.3.0.Beta1 > > > 0. decide where to put this... under jbosstools-ci or some new repo? Create a new component in JIRA accordingly. > 1. remove all refs to QA Jenkins file paths to make this more generic > 2. migrate those internal file paths into jenkins config.xml files > 3. document how to do installs for Eclipse, JBT or JBDS BYOE via commandline for setting up the footprint of installs against which to do baseline version watches -- pre-existing doc here: > http://download.jboss.org/jbosstools/updates/scripted-installation/ > https://devstudio.redhat.com/download/scripted-install/ > 4. test #3 to ensure it works, and that a mix of "studio" and "eclipse" folders can be used in a vwatch report -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-15481) setup of vwatch for jboss tools installations

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15481?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-15481: ------------------------------- Description: 1. use the install robot and then run versionwatch aginst JBoss Tools install with all of central content installed. usecases: * find missing/weird versions * duplicate components * get list of potential unnecessary plugins in TP 2. document how to do installs for Eclipse, JBT or JBDS BYOE via commandline for setting up the footprint of installs against which to do baseline version watches – pre-existing doc here: http://download.jboss.org/jbosstools/updates/scripted-installation/ https://devstudio.redhat.com/download/scripted-install/ 3. test #2 to ensure it works, and that a mix of "studio" and "eclipse" folders can be used in a vwatch report 4. create new jobs (or extend existing ones) to provide reports about JBT, JBT+Central, JBT+Central+EA; repeat for JBDS combinations. Maybe migrate jobs to matrixes? was: 1. use the install robot and then run versionwatch aginst JBoss Tools install with all of central content installed. usecases: * find missing/weird versions * duplicate components * get list of potential unnecessary plugins in TP 2. document how to do installs for Eclipse, JBT or JBDS BYOE via commandline for setting up the footprint of installs against which to do baseline version watches – pre-existing doc here: http://download.jboss.org/jbosstools/updates/scripted-installation/ https://devstudio.redhat.com/download/scripted-install/ 3. test #2 to ensure it works, and that a mix of "studio" and "eclipse" folders can be used in a vwatch report > setup of vwatch for jboss tools installations > --------------------------------------------- > > Key: JBIDE-15481 > URL: https://issues.jboss.org/browse/JBIDE-15481 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 4.3.0.Beta1 > > Attachments: jbide15481.png > > > 1. use the install robot and then run versionwatch aginst JBoss Tools install with all of central content installed. > usecases: > * find missing/weird versions > * duplicate components > * get list of potential unnecessary plugins in TP > 2. document how to do installs for Eclipse, JBT or JBDS BYOE via commandline for setting up the footprint of installs against which to do baseline version watches – pre-existing doc here: > http://download.jboss.org/jbosstools/updates/scripted-installation/ > https://devstudio.redhat.com/download/scripted-install/ > 3. test #2 to ensure it works, and that a mix of "studio" and "eclipse" folders can be used in a vwatch report > 4. create new jobs (or extend existing ones) to provide reports about JBT, JBT+Central, JBT+Central+EA; repeat for JBDS combinations. Maybe migrate jobs to matrixes? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-15481) setup of vwatch for jboss tools installations

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15481?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-15481: ------------------------------- Description: 1. use the install robot and then run versionwatch aginst JBoss Tools install with all of central content installed. usecases: * find missing/weird versions * duplicate components * get list of potential unnecessary plugins in TP 2. document how to do installs for Eclipse, JBT or JBDS BYOE via commandline for setting up the footprint of installs against which to do baseline version watches – pre-existing doc here: http://download.jboss.org/jbosstools/updates/scripted-installation/ https://devstudio.redhat.com/download/scripted-install/ 3. test #2 to ensure it works, and that a mix of "studio" and "eclipse" folders can be used in a vwatch report was: use the install robot and then run versionwatch aginst JBoss Tools install with all of central content installed. usecases: * find missing/weird versions * duplicate components * get list of potential unnecessary plugins in TP > setup of vwatch for jboss tools installations > --------------------------------------------- > > Key: JBIDE-15481 > URL: https://issues.jboss.org/browse/JBIDE-15481 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 4.3.0.Beta1 > > Attachments: jbide15481.png > > > 1. use the install robot and then run versionwatch aginst JBoss Tools install with all of central content installed. > usecases: > * find missing/weird versions > * duplicate components > * get list of potential unnecessary plugins in TP > 2. document how to do installs for Eclipse, JBT or JBDS BYOE via commandline for setting up the footprint of installs against which to do baseline version watches – pre-existing doc here: > http://download.jboss.org/jbosstools/updates/scripted-installation/ > https://devstudio.redhat.com/download/scripted-install/ > 3. test #2 to ensure it works, and that a mix of "studio" and "eclipse" folders can be used in a vwatch report -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-15481) setup of vwatch for jboss tools installations

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15481?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-15481: ---------------------------------- Assignee: Nick Boldt > setup of vwatch for jboss tools installations > --------------------------------------------- > > Key: JBIDE-15481 > URL: https://issues.jboss.org/browse/JBIDE-15481 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 4.3.0.Beta1 > > Attachments: jbide15481.png > > > use the install robot and then run versionwatch aginst JBoss Tools install with all of central content installed. > usecases: > * find missing/weird versions > * duplicate components > * get list of potential unnecessary plugins in TP -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-15481) setup of vwatch for jboss tools installations

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15481?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-15481: ------------------------------- Fix Version/s: 4.3.0.Beta1 (was: 4.3.x) > setup of vwatch for jboss tools installations > --------------------------------------------- > > Key: JBIDE-15481 > URL: https://issues.jboss.org/browse/JBIDE-15481 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Max Rydahl Andersen > Fix For: 4.3.0.Beta1 > > Attachments: jbide15481.png > > > use the install robot and then run versionwatch aginst JBoss Tools install with all of central content installed. > usecases: > * find missing/weird versions > * duplicate components > * get list of potential unnecessary plugins in TP -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-416) Need to doc split of SOA Development between release and early access

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-416?page=com.atlassian.jira.plugin.... ] Paul Leacu closed JBTIS-416. ---------------------------- Fix Version/s: 8.0.1.GA Resolution: Done Updated docs looks good. > Need to doc split of SOA Development between release and early access > --------------------------------------------------------------------- > > Key: JBTIS-416 > URL: https://issues.jboss.org/browse/JBTIS-416 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Affects Versions: 8.0.1.GA, 4.2.1.Final > Reporter: Paul Leacu > Assignee: Misha Ali > Fix For: 8.0.1.GA > > Attachments: ss0.png, ss1.png > > > Component categorization for the SOA Development tooling falls in both the released and Early Access update sites. B*MS tooling is now being productized and Fuse Tooling/ SwitchYard are in 'Early Access'. This situation is temporary (until Fuse Tooling/SwitchYard are GA). > To address this issue I've done the following: > JBDSIS 8.0.1.GA: > site-ga: (released) > JBoss Business Process and Rules Development > *All features available > JBoss Data Virtualization Development > *All features available > JBoss Integration and SOA Development > *All features except Fuse Tooling and SwitchYard > JBoss SOA 5.x Development > *All features available > > site-ea: (early access) > JBoss Fuse Development > *All features available > JBoss Integration and SOA Development > *Fuse Tooling and SwitchYard only available > To simplify the user experience, Early Access will contain only features which are early access. Released (production) features will appear in the primary update window. > The community JBTIS install will do something similar. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-429) JBDSIS 8.0.2 component updates

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-429?page=com.atlassian.jira.plugin.... ] Paul Leacu closed JBTIS-429. ---------------------------- Resolution: Done Documented updates look good. > JBDSIS 8.0.2 component updates > ------------------------------ > > Key: JBTIS-429 > URL: https://issues.jboss.org/browse/JBTIS-429 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Affects Versions: 8.0.1.GA > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 8.0.2.GA > > > Update components for JBDSIS 8.0.2/ JBTIS 4.2.2 (Luna). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19716) JBoss Tools 4.3.0.Alpha2 does not recognize an installed Android SDK

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19716?page=com.atlassian.jira.plugi... ] Len DiMaggio commented on JBIDE-19716: -------------------------------------- What (old) version of the SDK do you have installed that is recognized? > JBoss Tools 4.3.0.Alpha2 does not recognize an installed Android SDK > -------------------------------------------------------------------- > > Key: JBIDE-19716 > URL: https://issues.jboss.org/browse/JBIDE-19716 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Gorkem Ercan > Attachments: Android_SDK.png, sdk_change.png > > > With 4.3.0.Alpha2: > * Install Android SDK from: http://dl.google.com/android/android-sdk_r24.1.2-linux.tgz > * Attempt to configure the installed SDK in Perferences->Hybrid Mobile->Android > * See the attached screen shot for the "Not a valid Android SDK directory" error. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19716) JBoss Tools 4.3.0.Alpha2 does not recognize an installed Android SDK

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19716?page=com.atlassian.jira.plugi... ] Len DiMaggio edited comment on JBIDE-19716 at 4/28/15 9:04 AM: --------------------------------------------------------------- What - in other words - which specific directories are required for JBoss Tools to "recognize" an Andoid SDK? was (Author: ldimaggio): What - in other words - which specific directories are required to recognize an Andoid SDK? > JBoss Tools 4.3.0.Alpha2 does not recognize an installed Android SDK > -------------------------------------------------------------------- > > Key: JBIDE-19716 > URL: https://issues.jboss.org/browse/JBIDE-19716 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Gorkem Ercan > Attachments: Android_SDK.png, sdk_change.png > > > With 4.3.0.Alpha2: > * Install Android SDK from: http://dl.google.com/android/android-sdk_r24.1.2-linux.tgz > * Attempt to configure the installed SDK in Perferences->Hybrid Mobile->Android > * See the attached screen shot for the "Not a valid Android SDK directory" error. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19722) Update Visual Editor FAQ(bluejeans plugin error is fixed)

by Konstantin Marmalyukov (JIRA)

Konstantin Marmalyukov created JBIDE-19722: ---------------------------------------------- Summary: Update Visual Editor FAQ(bluejeans plugin error is fixed) Key: JBIDE-19722 URL: https://issues.jboss.org/browse/JBIDE-19722 Project: Tools (JBoss Tools) Issue Type: Task Components: visual-page-editor-core Affects Versions: 4.3.0.Alpha2 Reporter: Konstantin Marmalyukov Since bluejeans update which fixes https://bugs.eclipse.org/bugs/show_bug.cgi?id=433606 is available, we need to update our FAQ where recommend user to update bluejeans -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19716) JBoss Tools 4.3.0.Alpha2 does not recognize an installed Android SDK

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19716?page=com.atlassian.jira.plugi... ] Len DiMaggio commented on JBIDE-19716: -------------------------------------- What - in other words - which specific directories are required to recognize an Andoid SDK? > JBoss Tools 4.3.0.Alpha2 does not recognize an installed Android SDK > -------------------------------------------------------------------- > > Key: JBIDE-19716 > URL: https://issues.jboss.org/browse/JBIDE-19716 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Gorkem Ercan > Attachments: Android_SDK.png, sdk_change.png > > > With 4.3.0.Alpha2: > * Install Android SDK from: http://dl.google.com/android/android-sdk_r24.1.2-linux.tgz > * Attempt to configure the installed SDK in Perferences->Hybrid Mobile->Android > * See the attached screen shot for the "Not a valid Android SDK directory" error. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19719) "EasyImport" of Mobile Hybrid project fails on JBoss Tools 4.3.0.Alpha2

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19719?page=com.atlassian.jira.plugi... ] Len DiMaggio commented on JBIDE-19719: -------------------------------------- Sorry that the steps were not clear - the steps are: * From JBoss Central, create a new Mobile Hybrid project ("start from scratch") * Export the project to a directory outside of the workspace * Attempt to import the project using the "import from directory" option > "EasyImport" of Mobile Hybrid project fails on JBoss Tools 4.3.0.Alpha2 > ----------------------------------------------------------------------- > > Key: JBIDE-19719 > URL: https://issues.jboss.org/browse/JBIDE-19719 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Gorkem Ercan > Attachments: jbosstools-diagnostics-20150427143128.zip > > > This issue is related to JBIDE-19716 > Multiple errors are raised when a mobile hybrid project created in Central in JBoss Tools 4.3.0.alpha2 is exported and then imported from a directory using easy import. > See attached .zip for the error file (logs, etc..) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (LOCUS-23) New version of Saxon-HE required in locus

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/LOCUS-23?page=com.atlassian.jira.plugin.s... ] Max Rydahl Andersen commented on LOCUS-23: ------------------------------------------ [~phantomjinx] to get into integration-stack you need to open bug for JBTIS (as always ;) and be specific about what versions needs this. I assume this is just for Mars based version thus this should be fairly easy to get in but that is [~pleacu] that manage JBTIS TP. btw. please do not publish stuff to locations like nightly/locus/provisional when you can just use a local generated one. By you doing this you triggered regen of http://download.jboss.org/jbosstools/updates/nightly/locus/ which now includes your experiment despite its not yet included. > New version of Saxon-HE required in locus > ----------------------------------------- > > Key: LOCUS-23 > URL: https://issues.jboss.org/browse/LOCUS-23 > Project: JBoss Tools Locus > Issue Type: Feature Request > Affects Versions: 1.1.0 > Reporter: Paul Richardson > Assignee: Mickael Istria > Fix For: 1.2.0 > > > The Teiid Server project has updated their dependencies, including increasing the Saxon-HE version to 9.1.5-6j. > Since Teiid Designer takes a cut of the Teiid Server's client, it is necessary to update the Saxon-HE dependency in the former in order to remain in sync. Designer gets it Saxon library from the Locus repository. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19721) look at fixing quickaccess resizing bug

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-19721: ------------------------------------------- Summary: look at fixing quickaccess resizing bug Key: JBIDE-19721 URL: https://issues.jboss.org/browse/JBIDE-19721 Project: Tools (JBoss Tools) Issue Type: Bug Components: upstream Reporter: Max Rydahl Andersen Assignee: Koen Aers See https://bugs.eclipse.org/bugs/show_bug.cgi?id=432688 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (LOCUS-23) New version of Saxon-HE required in locus

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/LOCUS-23?page=com.atlassian.jira.plugin.s... ] Paul Richardson commented on LOCUS-23: -------------------------------------- [~mickael_istria] Have tested the PR. * Built it in jenkins under the jbosstools-locus.site_branch-testing project (build #2) - successful * Build published to http://download.jboss.org/jbosstools/updates/nightly/locus/provisional - successful * Re-generated Teiid Designer's target locally against this new provisional build and validated - successful * Executed Designer build and tests - successful On that basic happy for it to be merged. Assuming it is merged, what is the turnaround going to be for seeing this in the integration-stack? > New version of Saxon-HE required in locus > ----------------------------------------- > > Key: LOCUS-23 > URL: https://issues.jboss.org/browse/LOCUS-23 > Project: JBoss Tools Locus > Issue Type: Feature Request > Affects Versions: 1.1.0 > Reporter: Paul Richardson > Assignee: Mickael Istria > Fix For: 1.2.0 > > > The Teiid Server project has updated their dependencies, including increasing the Saxon-HE version to 9.1.5-6j. > Since Teiid Designer takes a cut of the Teiid Server's client, it is necessary to update the Saxon-HE dependency in the former in order to remain in sync. Designer gets it Saxon library from the Locus repository. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-2044) .eclipseproduct file no longer refers to JBDS

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2044?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-2044: ------------------------------------------- but because its used there it should be using our product id should it not ? > .eclipseproduct file no longer refers to JBDS > --------------------------------------------- > > Key: JBDS-2044 > URL: https://issues.jboss.org/browse/JBDS-2044 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 5.0.0.Beta1 > Reporter: Nick Boldt > Assignee: Denis Golovin > Labels: discuss > Fix For: 8.x > > > Before, with the linux x64 installer (jbdevstudio-product-linux-gtk-x86_64-5.0.0.v201202271832M-H79-Beta1.jar) the .eclipseproduct file read: > {code} > name=JBoss Developer Studio > id=com.jboss.jbds.all > version=5.0.0.v201202271832M-H79-Beta1 > {code} > Now, with the universal installer (jbdevstudio-product-universal-5.0.0.v201202271832M-H79-Beta1.jar), it reads: > {code} > name=Eclipse Platform > id=org.eclipse.platform > version=3.7.0 > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19007) As a user, I want to retrieve the build hook URL for a build config so I can configure my git repo to trigger a build on commit

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19007?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19007: ------------------------------------------ [~jcantrill] [~mlabuda] wants to verify this jira and is wondering how to test this. Can you please provide steps so that he can reproduce and verify it? > As a user, I want to retrieve the build hook URL for a build config so I can configure my git repo to trigger a build on commit > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19007 > URL: https://issues.jboss.org/browse/JBIDE-19007 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.2.2.Final > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Labels: explorer > Fix For: 4.3.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19007) As a user, I want to retrieve the build hook URL for a build config so I can configure my git repo to trigger a build on commit

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19007?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-19007 at 4/28/15 6:51 AM: ------------------------------------------------------------------- [~jcantrill]: [~mlabuda] wants to verify this jira and is wondering how to test this. Can you please provide steps so that he can reproduce and verify it? was (Author: adietish): [~jcantrill] [~mlabuda] wants to verify this jira and is wondering how to test this. Can you please provide steps so that he can reproduce and verify it? > As a user, I want to retrieve the build hook URL for a build config so I can configure my git repo to trigger a build on commit > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19007 > URL: https://issues.jboss.org/browse/JBIDE-19007 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.2.2.Final > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Labels: explorer > Fix For: 4.3.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19190) migrate VersionWatch to jbosstools-* repo

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19190?page=com.atlassian.jira.plugi... ] Jiri Peterka commented on JBIDE-19190: -------------------------------------- PRs are applied. Cleanup is finished IMHO. > migrate VersionWatch to jbosstools-* repo > ----------------------------------------- > > Key: JBIDE-19190 > URL: https://issues.jboss.org/browse/JBIDE-19190 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: qa > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Jiri Peterka > Priority: Minor > Fix For: 4.3.0.Beta1 > > > 0. decide where to put this... under jbosstools-ci or some new repo? Create a new component in JIRA accordingly. > 1. remove all refs to QA Jenkins file paths to make this more generic > 2. migrate those internal file paths into jenkins config.xml files > 3. document how to do installs for Eclipse, JBT or JBDS BYOE via commandline for setting up the footprint of installs against which to do baseline version watches -- pre-existing doc here: > http://download.jboss.org/jbosstools/updates/scripted-installation/ > https://devstudio.redhat.com/download/scripted-install/ > 4. test #3 to ensure it works, and that a mix of "studio" and "eclipse" folders can be used in a vwatch report -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19719) "EasyImport" of Mobile Hybrid project fails on JBoss Tools 4.3.0.Alpha2

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19719?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19719: --------------------------------------------- The relevant errors are this: {code} !ENTRY org.eclipse.thym.ui 2 0 2015-04-27 14:16:05.461 !MESSAGE Pre-compilation for engine cordova-android 3.6.4 has failed !STACK 1 org.eclipse.core.runtime.CoreException: Android SDK location is not defined at org.eclipse.thym.android.core.adt.AndroidSDKManager.getManager(AndroidSDKManager.java:263) at org.eclipse.thym.android.core.adt.AndroidProjectUtils.selectBestValidTarget(AndroidProjectUtils.java:69) at org.eclipse.thym.android.core.adt.AndroidLibraryResolver.preCompile(AndroidLibraryResolver.java:101) at org.eclipse.thym.core.engine.HybridMobileEngine.preCompile(HybridMobileEngine.java:102) at org.eclipse.thym.ui.internal.engine.AvailableCordovaEnginesSection$6.run(AvailableCordovaEnginesSection.java:400) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) !SUBENTRY 1 org.eclipse.thym.android.core 4 200 2015-04-27 14:16:05.461 !MESSAGE Android SDK location is not defined !ENTRY org.tigris.subversion.subclipse.core 4 0 2015-04-27 14:16:34.335 !MESSAGE Could not auto-share project SimpleHybridProject !STACK 1 org.tigris.subversion.subclipse.core.SVNException: Provided SVN information does not match that on disk for project 'SimpleHybridProject'. at org.tigris.subversion.subclipse.core.resources.SVNWorkspaceRoot.setSharing(SVNWorkspaceRoot.java:206) at org.tigris.subversion.subclipse.core.SVNTeamProviderType$AutoShareJob.autoconnectSVNProject(SVNTeamProviderType.java:140) at org.tigris.subversion.subclipse.core.SVNTeamProviderType$AutoShareJob.run(SVNTeamProviderType.java:106) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) !SUBENTRY 1 org.tigris.subversion.subclipse.core 4 4 2015-04-27 14:16:34.335 !MESSAGE Provided SVN information does not match that on disk for project 'SimpleHybridProject'. {code} I agree that aerogear should not be logging errors just because default SDK is not set - that should be a warning on the project, not a error in the logs (but I believe that is a separate issue) But what I do not get is why svn is triggered for you [~ldimaggio] can you proivde the exact steps you did to do this easyimport ? > "EasyImport" of Mobile Hybrid project fails on JBoss Tools 4.3.0.Alpha2 > ----------------------------------------------------------------------- > > Key: JBIDE-19719 > URL: https://issues.jboss.org/browse/JBIDE-19719 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Gorkem Ercan > Attachments: jbosstools-diagnostics-20150427143128.zip > > > This issue is related to JBIDE-19716 > Multiple errors are raised when a mobile hybrid project created in Central in JBoss Tools 4.3.0.alpha2 is exported and then imported from a directory using easy import. > See attached .zip for the error file (logs, etc..) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19716) JBoss Tools 4.3.0.Alpha2 does not recognize an installed Android SDK

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19716?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-19716: -------------------------------- Attachment: sdk_change.png Directory structure has changed drastically. I guess that's the issue - !sdk_change.png|thumbnail! > JBoss Tools 4.3.0.Alpha2 does not recognize an installed Android SDK > -------------------------------------------------------------------- > > Key: JBIDE-19716 > URL: https://issues.jboss.org/browse/JBIDE-19716 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Gorkem Ercan > Attachments: Android_SDK.png, sdk_change.png > > > With 4.3.0.Alpha2: > * Install Android SDK from: http://dl.google.com/android/android-sdk_r24.1.2-linux.tgz > * Attempt to configure the installed SDK in Perferences->Hybrid Mobile->Android > * See the attached screen shot for the "Not a valid Android SDK directory" error. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19716) JBoss Tools 4.3.0.Alpha2 does not recognize an installed Android SDK

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19716?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-19716: -------------------------------- Component/s: aerogear-hybrid (was: cordovasim) > JBoss Tools 4.3.0.Alpha2 does not recognize an installed Android SDK > -------------------------------------------------------------------- > > Key: JBIDE-19716 > URL: https://issues.jboss.org/browse/JBIDE-19716 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Gorkem Ercan > Attachments: Android_SDK.png > > > With 4.3.0.Alpha2: > * Install Android SDK from: http://dl.google.com/android/android-sdk_r24.1.2-linux.tgz > * Attempt to configure the installed SDK in Perferences->Hybrid Mobile->Android > * See the attached screen shot for the "Not a valid Android SDK directory" error. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3308) Promote JBoss Tools CAT in JBT/JBDS About box

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3308?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3308: ------------------------------------------- Central is suggested in JBIDE-18871 and i think it would make sense to make visible there somehow - especially in context of earlyaccess > Promote JBoss Tools CAT in JBT/JBDS About box > --------------------------------------------- > > Key: JBDS-3308 > URL: https://issues.jboss.org/browse/JBDS-3308 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product > Reporter: Vlado Pakan > Assignee: Denis Golovin > Priority: Optional > Fix For: 9.0.0.Beta1 > > Attachments: about-jbds.png > > > Would be nice to put link to JBT CAT or JBT CAT logo with link to it to JBDS/JBT About box to make JBT CAT more visible. > New link/image should be visible without resizing About box -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-17284) OpenJDK seem to have issues with SSL/TLS handshakes when using URLConnection

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17284?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen reassigned JBIDE-17284: ------------------------------------------- Assignee: Ilya Buziuk (was: Max Rydahl Andersen) > OpenJDK seem to have issues with SSL/TLS handshakes when using URLConnection > ---------------------------------------------------------------------------- > > Key: JBIDE-17284 > URL: https://issues.jboss.org/browse/JBIDE-17284 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream, xulrunner > Affects Versions: 4.2.0.Final > Reporter: Max Rydahl Andersen > Assignee: Ilya Buziuk > Priority: Blocker > Fix For: 4.3.0.Beta1 > > Attachments: jbds-via-html5-vpe.png > > > We've received multiple reports about instant crashes of users running JBoss Tools and Developer Studio. > The common issue is that it happens when they use OpenJDK vm, not Oracle. > The crash log normally contains something similar to: > Java frames: (J=compiled Java code, j=interpreted, Vv=VM code) > j sun.security.pkcs11.wrapper.PKCS11.C_CreateObject(J[Lsun/security/pkcs11/wrapper/CK_ATTRIBUTE;)J+0 > j sun.security.pkcs11.P11ECKeyFactory.generatePublic(Ljava/security/spec/ECPoint;Ljava/security/spec/ECParameterSpec;)Ljava/security/PublicKey;+170 > j sun.security.pkcs11.P11ECKeyFactory.engineGeneratePublic(Ljava/security/spec/KeySpec;)Ljava/security/PublicKey;+80 > j java.security.KeyFactory.generatePublic(Ljava/security/spec/KeySpec;)Ljava/security/PublicKey;+25 > j sun.security.ssl.HandshakeMessage$ECDH_ServerKeyExchange.<init>(Lsun/security/ssl/HandshakeInStream;Ljava/security/PublicKey;[B[BLjava/util/Collection;Lsun/security/ssl/ProtocolVersion;)V+228 > Opening this bug to collect and use a key issue for hunting down the cause. > Note: This issue is *not* specific to JBoss Tools as far as I can see, but it does affect us since we lookup a file located behind https url at key times which seem to trigger the crash. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-15291) xulrunner under 64bit Linux produce "NSSUTIL_3.13 not found" and blocks marketplace, m2e connector discovery ...

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15291?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen reassigned JBIDE-15291: ------------------------------------------- Assignee: Ilya Buziuk (was: Max Rydahl Andersen) > xulrunner under 64bit Linux produce "NSSUTIL_3.13 not found" and blocks marketplace, m2e connector discovery ... > ------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-15291 > URL: https://issues.jboss.org/browse/JBIDE-15291 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core, xulrunner > Affects Versions: 4.1.0.Final > Environment: Linux 3.8.13-gentoo #1 SMP Sun Jun 23 23:34:36 CEST 2013 x86_64 Intel(R) Core(TM) i7-2720QM CPU @ 2.20GHz GenuineIntel GNU/Linux > IcedTea JDK 7.2.4.1 > eclipse-standard-kepler-R-linux-gtk-x86_64.tar.gz > Reporter: Jochen Buchholz > Assignee: Ilya Buziuk > Priority: Critical > Fix For: 4.3.x > > Attachments: .log, click-on-jbosscentral-button.png, frozen-marketplace.png, gentoo.png, internal-error1.png, m2e-connectors.png > > > I installed the eclipse standard kepler and go to market place. I choose JBoss developer studio 7.0.0 GA and install it via marketplace. After the restart I choose File->Import->Maven->"checkout Maven Projects from SCM" and click on the "Find out more SCM connectors in the m2e Marketplace. I got the error: "Failed to discover all connectors." > I cant Use the Marketplace anymore, because he is frozen while load the content. > In the error log I found this line: > Caused by: java.io.IOException: /mnt/usb/eclipse/plugins/org.mozilla.xulrunner.gtk.linux.x86_64_1.9.2.19pre/xulrunner/libnssutil3.so: version `NSSUTIL_3.13' not found (required by /usr/lib64/libnss3.so) > like in the old issue JBIDE-10628 reported also by me > Developer Studio is unusable under 64bit Linux. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-15291) xulrunner under 64bit Linux produce "NSSUTIL_3.13 not found" and blocks marketplace, m2e connector discovery ...

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15291?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-15291: ---------------------------------------- Sprint: Sprint #2 April 2015 > xulrunner under 64bit Linux produce "NSSUTIL_3.13 not found" and blocks marketplace, m2e connector discovery ... > ------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-15291 > URL: https://issues.jboss.org/browse/JBIDE-15291 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core, xulrunner > Affects Versions: 4.1.0.Final > Environment: Linux 3.8.13-gentoo #1 SMP Sun Jun 23 23:34:36 CEST 2013 x86_64 Intel(R) Core(TM) i7-2720QM CPU @ 2.20GHz GenuineIntel GNU/Linux > IcedTea JDK 7.2.4.1 > eclipse-standard-kepler-R-linux-gtk-x86_64.tar.gz > Reporter: Jochen Buchholz > Assignee: Max Rydahl Andersen > Priority: Critical > Fix For: 4.3.x > > Attachments: .log, click-on-jbosscentral-button.png, frozen-marketplace.png, gentoo.png, internal-error1.png, m2e-connectors.png > > > I installed the eclipse standard kepler and go to market place. I choose JBoss developer studio 7.0.0 GA and install it via marketplace. After the restart I choose File->Import->Maven->"checkout Maven Projects from SCM" and click on the "Find out more SCM connectors in the m2e Marketplace. I got the error: "Failed to discover all connectors." > I cant Use the Marketplace anymore, because he is frozen while load the content. > In the error log I found this line: > Caused by: java.io.IOException: /mnt/usb/eclipse/plugins/org.mozilla.xulrunner.gtk.linux.x86_64_1.9.2.19pre/xulrunner/libnssutil3.so: version `NSSUTIL_3.13' not found (required by /usr/lib64/libnss3.so) > like in the old issue JBIDE-10628 reported also by me > Developer Studio is unusable under 64bit Linux. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18556) battery status is not reflected in browsersim's status bar

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18556?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-18556: -------------------------------- Sprint: Sprint #3 May 2015 (was: Sprint #2 April 2015) > battery status is not reflected in browsersim's status bar > ---------------------------------------------------------- > > Key: JBIDE-18556 > URL: https://issues.jboss.org/browse/JBIDE-18556 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cordovasim > Reporter: Max Rydahl Andersen > Assignee: Ilya Buziuk > Fix For: 4.3.x > > Attachments: log.png > > > create basic cordova app. > run in cordova sim. > changing the battery level and is-plugged does not take effect in the simulator. > Should it not be able to detect these ? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-1696) seemingly irrelevant warning/error thrown when installing JBDS 4 / 5 on Fedora 12 32-bit - can we suppress that?

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-1696?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen resolved JBDS-1696. --------------------------------------- Resolution: Out of Date yeah, this is ancient and seems nooone else reported it thus closing as out of date. > seemingly irrelevant warning/error thrown when installing JBDS 4 / 5 on Fedora 12 32-bit - can we suppress that? > ---------------------------------------------------------------------------------------------------------------- > > Key: JBDS-1696 > URL: https://issues.jboss.org/browse/JBDS-1696 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer, upstream > Affects Versions: 4.1.0.CR2, 5.0.0.M2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 7.1.x > > > An error like this is thrown EVERY TIME I install JBDS onto Fedora 12 32-bit. > Is this a problem @ my end or something we can fix or at least suppress? > $ java -jar jbdevstudio-product-linux-gtk-5.0.0.v201106180702R-H3-M2.jar > Jun 20, 2011 12:06:03 PM com.sun.corba.se.impl.ior.IORImpl getProfile > WARNING: "IOP00511201: (INV_OBJREF) IOR must have at least one IIOP profile" > org.omg.CORBA.INV_OBJREF: vmcid: SUN minor code: 1201 completed: No > at com.sun.corba.se.impl.logging.IORSystemException.iorMustHaveIiopProfile(IORSystemException.java:473) > at com.sun.corba.se.impl.logging.IORSystemException.iorMustHaveIiopProfile(IORSystemException.java:495) > at com.sun.corba.se.impl.ior.IORImpl.getProfile(IORImpl.java:334) > at com.sun.corba.se.impl.encoding.CDRInputStream_1_0.read_Object(CDRInputStream_1_0.java:787) > at com.sun.corba.se.impl.encoding.CDRInputStream_1_0.read_Object(CDRInputStream_1_0.java:761) > at com.sun.corba.se.impl.encoding.CDRInputStream.read_Object(CDRInputStream.java:231) > at com.sun.corba.se.impl.resolver.INSURLOperationImpl.getIORFromString(INSURLOperationImpl.java:120) > at com.sun.corba.se.impl.resolver.INSURLOperationImpl.operate(INSURLOperationImpl.java:130) > at com.sun.corba.se.impl.orb.ORBImpl.string_to_object(ORBImpl.java:836) > at org.GNOME.Accessibility.AccessUtil.getRegistryObject(AccessUtil.java:143) > at org.GNOME.Accessibility.JavaBridge.registerApplication(JavaBridge.java:1099) > at org.GNOME.Accessibility.JavaBridge.<init>(JavaBridge.java:364) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:532) > at java.lang.Class.newInstance0(Class.java:372) > at java.lang.Class.newInstance(Class.java:325) > at java.awt.Toolkit.loadAssistiveTechnologies(Toolkit.java:786) > at java.awt.Toolkit.getDefaultToolkit(Toolkit.java:875) > at com.jgoodies.looks.LookUtils.isLowResolution(LookUtils.java:480) > at com.jgoodies.looks.LookUtils.<clinit>(LookUtils.java:249) > at com.jgoodies.looks.plastic.PlasticLookAndFeel.<clinit>(PlasticLookAndFeel.java:135) > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Class.java:264) > at javax.swing.SwingUtilities.loadSystemClass(SwingUtilities.java:1875) > at javax.swing.UIManager.setLookAndFeel(UIManager.java:573) > at com.izforge.izpack.installer.GUIInstaller.loadLookAndFeel(Unknown Source) > at com.izforge.izpack.installer.GUIInstaller.init(Unknown Source) > at com.izforge.izpack.installer.GUIInstaller.<init>(Unknown Source) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:532) > at java.lang.Class.newInstance0(Class.java:372) > at java.lang.Class.newInstance(Class.java:325) > at com.izforge.izpack.installer.Installer.main(Unknown Source) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19009) As a user, I want to create OpenShift resources from a template

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19009?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19009: --------------------------------------------- we really should try limit using subtasks since they get collapsed on the board. > As a user, I want to create OpenShift resources from a template > --------------------------------------------------------------- > > Key: JBIDE-19009 > URL: https://issues.jboss.org/browse/JBIDE-19009 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.2.2.Final > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Fix For: 4.3.0.Beta1 > > Attachments: Create app from template mockup.bmml, Create app from template mockup.bmml, Create app from template mockup.png, create from source.png, create from template.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19009) As a user, I want to create OpenShift resources from a template

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19009?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-19009: ---------------------------------------- Sprint: Sprint #2 April 2015 > As a user, I want to create OpenShift resources from a template > --------------------------------------------------------------- > > Key: JBIDE-19009 > URL: https://issues.jboss.org/browse/JBIDE-19009 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.2.2.Final > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Fix For: 4.3.0.Beta1 > > Attachments: Create app from template mockup.bmml, Create app from template mockup.bmml, Create app from template mockup.png, create from source.png, create from template.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3256) JBoss specific Docker Tooling (Basic Integration)

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3256?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3256: -------------------------------------- Component/s: docker (was: openshift) > JBoss specific Docker Tooling (Basic Integration) > ------------------------------------------------- > > Key: JBDS-3256 > URL: https://issues.jboss.org/browse/JBDS-3256 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: docker, requirements > Reporter: Burr Sutter > Assignee: Xavier Coulon > Attachments: multiview_properties_docker_idea.bmml, multiview_properties_docker_idea.png > > > Goal: to allow the Eclipse user to easily discover, pull, run, deploy my .war or .ear to it, stop, commit, push for docker images/containers. > Expected end-user flow 1: > 0) Installation - assumes boot2docker pre-installed on the end-user's machine > 1) I, the Java developer, need to browse a docker registry (either DockerHub or private registry), identify the image that I wish to have local and download (docker pull) for that image+tag. > 2) Assumption: the docker image includes not only the operating system + JVM but also the EAP, Wildfly or Tomcat installed in a 'known' location. > 3) I start (docker run) the image which auto-starts the embedded app server > 4) I can then deploy my .war or .ear to the running app server > 5) I can restart the running app server in debug mode and run the debugger > 6) I can undeploy and redeploy my .war or .ear > 7) I can stop/restart the running, embedded app server > 8) I can then commit (docker commit) > 9) then I can publish my changes (docker push) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3256) JBoss specific Docker Tooling (Basic Integration)

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3256?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3256: ----------------------------- CDW devel_ack: ? (was: +) > JBoss specific Docker Tooling (Basic Integration) > ------------------------------------------------- > > Key: JBDS-3256 > URL: https://issues.jboss.org/browse/JBDS-3256 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: docker, requirements > Reporter: Burr Sutter > Assignee: Xavier Coulon > Attachments: multiview_properties_docker_idea.bmml, multiview_properties_docker_idea.png > > > Goal: to allow the Eclipse user to easily discover, pull, run, deploy my .war or .ear to it, stop, commit, push for docker images/containers. > Expected end-user flow 1: > 0) Installation - assumes boot2docker pre-installed on the end-user's machine > 1) I, the Java developer, need to browse a docker registry (either DockerHub or private registry), identify the image that I wish to have local and download (docker pull) for that image+tag. > 2) Assumption: the docker image includes not only the operating system + JVM but also the EAP, Wildfly or Tomcat installed in a 'known' location. > 3) I start (docker run) the image which auto-starts the embedded app server > 4) I can then deploy my .war or .ear to the running app server > 5) I can restart the running app server in debug mode and run the debugger > 6) I can undeploy and redeploy my .war or .ear > 7) I can stop/restart the running, embedded app server > 8) I can then commit (docker commit) > 9) then I can publish my changes (docker push) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19146) Make sure new tooling can restore a workspace that was created with JBT 4.2.0.Final

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19146?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19146: ------------------------------------- Sprint: Sprint #2 April 2015 > Make sure new tooling can restore a workspace that was created with JBT 4.2.0.Final > ----------------------------------------------------------------------------------- > > Key: JBIDE-19146 > URL: https://issues.jboss.org/browse/JBIDE-19146 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Beta1 > > > We have to make sure that the new tooling (with the new plugins and the code reorg in JBIDE-19048) can restore a workspace that was created with JBT 4.2.0.Final / JBDS 8.0.0: > - restore opened views (explorer) > - restore connections > - restore server editor(s) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19009) As a user, I want to create OpenShift resources from a template

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19009?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-19009: ---------------------------------------- Sprint: (was: Sprint #2 April 2015) > As a user, I want to create OpenShift resources from a template > --------------------------------------------------------------- > > Key: JBIDE-19009 > URL: https://issues.jboss.org/browse/JBIDE-19009 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.2.2.Final > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Fix For: 4.3.0.Beta1 > > Attachments: Create app from template mockup.bmml, Create app from template mockup.bmml, Create app from template mockup.png, create from source.png, create from template.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19010) As a user, I want to create OpenShift resources that support an existing “deployment” that does not require source code from a template

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19010?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-19010: ---------------------------------------- Sprint: (was: Sprint #2 April 2015) > As a user, I want to create OpenShift resources that support an existing “deployment” that does not require source code from a template > --------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19010 > URL: https://issues.jboss.org/browse/JBIDE-19010 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Jeff Cantrill > Priority: Blocker > Fix For: 4.3.0.Beta1 > > > https://trello.com/c/HyTyFlHw > This is the usecase where we want to deploy an image that most likely does not include a buildconfig, i.e. a database image. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19010) As a user, I want to create OpenShift resources that support an existing “deployment” that does not require source code from a template

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19010?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19010: ------------------------------------- Sprint: Sprint #2 April 2015 > As a user, I want to create OpenShift resources that support an existing “deployment” that does not require source code from a template > --------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19010 > URL: https://issues.jboss.org/browse/JBIDE-19010 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Jeff Cantrill > Priority: Blocker > Fix For: 4.3.0.Beta1 > > > https://trello.com/c/HyTyFlHw > This is the usecase where we want to deploy an image that most likely does not include a buildconfig, i.e. a database image. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3306) Create Deployment from Template

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3306?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3306: -------------------------------------- Sprint: (was: Sprint #2 April 2015) > Create Deployment from Template > ------------------------------- > > Key: JBDS-3306 > URL: https://issues.jboss.org/browse/JBDS-3306 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: openshift, requirements > Reporter: Burr Sutter > Assignee: Jeff Cantrill > Priority: Blocker > Fix For: 9.0.0.Beta1 > > > Use Case #3 > Create Deployment from Template > a) Assume OpenShift is started remotely and provides an entrypoint URL > b) Assume end-user is logged in (ignore auth for now) > c) Eclipse user will open a dialog and enter the URL from step a > d) Eclipse user will then be presented with a list of templates from the template library > (initially a set of files on the local filesystem until openshift has a real template library api) > e) The template list should allow sorting so that higher priority items are at the top > We will likely need some form of categorization for templates also > f) The template list should be searchable by keyword > g) Eclipse user will select a particular template and > h) Create a new openshift deployment based on selected template > i) follow steps JBDS-3297 f through j (clone, import, project facets, etc) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19603) NPE in openshift application wizard after several attempts to remember credentials

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19603?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19603: ------------------------------------- Sprint: Sprint #2 April 2015 > NPE in openshift application wizard after several attempts to remember credentials > ---------------------------------------------------------------------------------- > > Key: JBIDE-19603 > URL: https://issues.jboss.org/browse/JBIDE-19603 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Environment: Linux > Reporter: Denis Golovin > Assignee: Andre Dietisheim > Fix For: 4.3.0.Beta1 > > Attachments: open-shift-npe.mp4 > > > I was trying to recover my password with try and fail method and finally succeeded to recover it but next step I got NPE's after pushing Browse button. > Authorization error was: > {code}com.openshift.client.InvalidCredentialsOpenShiftException: Your credentials are not authorized to access "https://openshift.redhat.com/broker/rest/user" > at com.openshift.internal.client.RestService.request(RestService.java:114) > at com.openshift.internal.client.RestService.request(RestService.java:92) > at com.openshift.internal.client.AbstractOpenShiftResource$ServiceRequest.execute(AbstractOpenShiftResource.java:143) > at com.openshift.internal.client.APIResource$GetUserRequest.execute(APIResource.java:400) > at com.openshift.internal.client.APIResource.getUser(APIResource.java:101) > at org.jboss.tools.openshift.express.internal.core.connection.ExpressConnection.doCreateUser(ExpressConnection.java:221) > at org.jboss.tools.openshift.express.internal.core.connection.ExpressConnection.createUser(ExpressConnection.java:206) > at org.jboss.tools.openshift.express.internal.core.connection.ExpressConnection.connect(ExpressConnection.java:183) > at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPageModel.connect(ConnectionWizardPageModel.java:316) > at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPage$ConnectJob.doRun(ConnectionWizardPage.java:459) > at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: com.openshift.internal.client.httpclient.UnauthorizedException: HTTP Basic: Access denied. > at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:196) > at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:165) > at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:144) > at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.get(UrlConnectionHttpClient.java:103) > at com.openshift.internal.client.RestService.request(RestService.java:160) > at com.openshift.internal.client.RestService.request(RestService.java:107) > ... 11 more > Caused by: java.io.IOException: Server returned HTTP response code: 401 for URL: https://openshift.redhat.com/broker/rest/user > at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1627) > at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254) > at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:161) > ... 15 more{code} > and then NPE: > {code}java.lang.NullPointerException > at org.jboss.tools.openshift.express.internal.ui.wizard.application.SelectApplicationWizardPageModel.loadDomains(SelectApplicationWizardPageModel.java:71) > at org.jboss.tools.openshift.express.internal.ui.wizard.application.SelectApplicationWizardPageModel.loadOpenShiftResources(SelectApplicationWizardPageModel.java:67) > at org.jboss.tools.openshift.express.internal.ui.wizard.application.SelectApplicationWizardPage.onPageActivated(SelectApplicationWizardPage.java:135) > at org.jboss.tools.openshift.internal.common.ui.wizard.AbstractOpenShiftWizardPage$1.pageChanged(AbstractOpenShiftWizardPage.java:87) > at org.eclipse.jface.wizard.WizardDialog$9.run(WizardDialog.java:1505) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50) > at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173) > at org.eclipse.jface.wizard.WizardDialog.firePageChanged(WizardDialog.java:1502) > at org.eclipse.jface.wizard.WizardDialog.update(WizardDialog.java:1308) > at org.eclipse.jface.wizard.WizardDialog.showStartingPage(WizardDialog.java:1258) > at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:599) > at org.eclipse.jface.window.Window.create(Window.java:430) > at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1096) > at org.eclipse.jface.window.Window.open(Window.java:792) > at org.jboss.tools.openshift.express.internal.ui.wizard.application.ApplicationTemplateWizardPage$2.widgetSelected(ApplicationTemplateWizardPage.java:237) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4477) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1322) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3815) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3425) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:827) > at org.eclipse.jface.window.Window.open(Window.java:803) > at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(WizardHandler.java:269) > at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:290) > at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295) > at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90) > 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.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55) > at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:247) > at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:229) > at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132) > at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152) > at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499) > at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) > at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210) > at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:343) > at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:160) > at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595) > at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511) > at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4477) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1322) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3815) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3425) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1112) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:993) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138) > 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:380) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235) > 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} > and then one more NPE: > {code}java.lang.NullPointerException > at org.jboss.tools.openshift.express.internal.ui.wizard.application.SelectApplicationWizardPageModel.refreshDomains(SelectApplicationWizardPageModel.java:49) > at org.jboss.tools.openshift.express.internal.ui.wizard.application.SelectApplicationWizardPageModel.refresh(SelectApplicationWizardPageModel.java:44) > at org.jboss.tools.openshift.express.internal.ui.wizard.application.SelectApplicationWizardPage$2$1.run(SelectApplicationWizardPage.java:148) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55){code} > Then I pushed Back and Next and was able to see cartridges and browse my old applications. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19009) As a user, I want to create OpenShift resources from a template

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19009?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19009: ------------------------------------- Sprint: Sprint #2 April 2015 > As a user, I want to create OpenShift resources from a template > --------------------------------------------------------------- > > Key: JBIDE-19009 > URL: https://issues.jboss.org/browse/JBIDE-19009 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.2.2.Final > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Fix For: 4.3.0.Beta1 > > Attachments: Create app from template mockup.bmml, Create app from template mockup.bmml, Create app from template mockup.png, create from source.png, create from template.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3306) Create Deployment from Template

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-3306?page=com.atlassian.jira.plugin.... ] Andre Dietisheim updated JBDS-3306: ----------------------------------- Sprint: Sprint #2 April 2015 > Create Deployment from Template > ------------------------------- > > Key: JBDS-3306 > URL: https://issues.jboss.org/browse/JBDS-3306 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: openshift, requirements > Reporter: Burr Sutter > Assignee: Jeff Cantrill > Priority: Blocker > Fix For: 9.0.0.Beta1 > > > Use Case #3 > Create Deployment from Template > a) Assume OpenShift is started remotely and provides an entrypoint URL > b) Assume end-user is logged in (ignore auth for now) > c) Eclipse user will open a dialog and enter the URL from step a > d) Eclipse user will then be presented with a list of templates from the template library > (initially a set of files on the local filesystem until openshift has a real template library api) > e) The template list should allow sorting so that higher priority items are at the top > We will likely need some form of categorization for templates also > f) The template list should be searchable by keyword > g) Eclipse user will select a particular template and > h) Create a new openshift deployment based on selected template > i) follow steps JBDS-3297 f through j (clone, import, project facets, etc) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19604) Save Password in New Openshift Application Wizard is annoying

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19604?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19604: ------------------------------------- Sprint: Sprint #2 April 2015 > Save Password in New Openshift Application Wizard is annoying > ------------------------------------------------------------- > > Key: JBIDE-19604 > URL: https://issues.jboss.org/browse/JBIDE-19604 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Environment: Linux, x86_64, Open JDK 7 > Reporter: Denis Golovin > Assignee: Andre Dietisheim > Fix For: 4.3.0.Beta1 > > Attachments: openshif-save-password.mp4 > > > Selected "Save Password" option in wizard triggers secure storage login that cannot be canceled in on click. This dialog keeps coming back after Cancel is pressed (three or more times). After reopening wizard first Security Storage Login pops up that I have to Cancel it several times (see attached video). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3258) Docker Tooling (Advanced Integration)

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3258?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3258: -------------------------------------- Component/s: docker (was: openshift) > Docker Tooling (Advanced Integration) > ------------------------------------- > > Key: JBDS-3258 > URL: https://issues.jboss.org/browse/JBDS-3258 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: docker, requirements > Reporter: Burr Sutter > Assignee: Xavier Coulon > > Once significant delta between the "basic" and advanced scenarios is that here I wish to custom craft my own docker images instead of using an existing one - where my custom crafted image includes my .war or .ear. > In addition to the basic integrations of pull, run, stop, commit and push > boot2docker init > boot2docker up > boot2docker down > boot2docker ip > docker run -d > docker ps > docker rm > docker rmi > docker build > End-user steps: > 0) assumes boot2docker has been dowloaded and installed > 1) boot2docker init : required to to insure boot2docker-vm is properly initialized > 2) boot2docker up : starts the VirtualBox boot2docker-vm > 3) boot2docker ip : returns the IP address - this will be vital when it comes to testing - it would need to be integrated with our Run - As on Docker capability. > 4) docker run -i -t -p 80:8080 jboss/wildfly -d : the -d means detached, I may need to run N containers simultaneously > 5) docker ps : allows me to see all my currently running containers > 6) docker rm : allows me to kill a currently running container > 7) docker rmi : allows me to remove a local image > 8) docker build : assumes that I have crafted a Dockerfile - this will create the local image - with my .war or .ear embedded > 9) docker run : this new created image > The docker build scenario can be triggered via a Maven plugin > The docker build scenario can also be triggered via an Eclipse menu option (like a Maven install) > We need to figure out the file-system layout so that the Dockerfile and the maven project are all nicely checked into git/svn. So that Jenkins can pick up this repository and perform an automated "docker build" (post Maven install) and then run all the appropriate unit, integration and functional tests. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19467) repository-utils :: FetchSourcesFromManifests should create its own source zip, not rely on publish.sh

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19467?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-19467: ---------------------------------------- Priority: Blocker (was: Major) > repository-utils :: FetchSourcesFromManifests should create its own source zip, not rely on publish.sh > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-19467 > URL: https://issues.jboss.org/browse/JBIDE-19467 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.3.0.Beta1 > > > In repository-utils, FetchSourcesFromManifests should create its own source zip, not rely on publish.sh. Because we no longer use publish.sh and don't want to have rsync.sh produce artifacts, only rsync them. > Here's what publish.sh does: > {code} > # collect component zips from upstream aggregated build jobs > if [[ ${JOB_NAME/.aggregate} != ${JOB_NAME} ]] && [[ -d ${WORKSPACE}/sources/aggregate/site/zips ]]; then > mkdir -p ${STAGINGDIR}/components > for z in $(find ${WORKSPACE}/sources/aggregate/site/zips -name "*updatesite-*.zip"); do > # generate MD5 sum for zip (file contains only the hash, not the hash + filename) > for m in $(md5sum ${z}); do if [[ $m != ${z} ]]; then echo $m > ${z}.MD5; fi; done > mv $z ${z}.MD5 ${STAGINGDIR}/components > done > # TODO :: JBIDE-9870 When we have a -Update-Sources- zip, this can be removed > mkdir -p ${STAGINGDIR}/all/sources > # OLD: unpack component source zips like jbosstools-pi4soa-3.1_trunk-Sources-SNAPSHOT.zip or jbosstools-3.2_trunk.component--ws-Sources-SNAPSHOT.zip > # NEW: JBIDE-16632: unpack component source zips like jbosstools-base_Alpha2-v20140221-1555-B437_184e18cc3ac7c339ce406974b6a4917f73909cc4_sources.zip > for z in $(find ${WORKSPACE}/sources/aggregate/site/zips -name "*Sources*.zip" -o -name "*_sources.zip" -o -name "*-src.zip"); do > zn=${z%*-Sources*.zip}; zn=${zn%*_sources.zip}; zn=${zn%*-src.zip}; zn=${zn#*--}; zn=${zn##*/}; zn=${zn#jbosstools-}; > # zn=${zn%_trunk}; zn=${zn%_stable_branch}; > mkdir -p ${STAGINGDIR}/all/sources/${zn}/ > # remove one level of folder nesting - don't want an extra jbosstools-base-184e18cc3ac7c339ce406974b6a4917f73909cc4 folder under jbosstools-base_Alpha2-v20140221-1555-B437_184e18cc3ac7c339ce406974b6a4917f73909cc4 > unzip -qq -o -d ${tmpdir}/${zn}/ $z > mkdir -p ${STAGINGDIR}/all/sources/${zn}/ > mv ${tmpdir}/${zn}/jbosstools-*/* ${STAGINGDIR}/all/sources/${zn}/ > rm -fr ${tmpdir}/${zn}/ > done > # add component sources into sources zip > pushd ${STAGINGDIR}/all/sources > zip ${STAGINGDIR}/all/${SRCSNAME} -q -r * -x hudson_workspace\* -x documentation\* -x download.jboss.org\* -x requirements\* \ > -x workingset\* -x labs\* -x build\* -x \*test\* -x \*target\* -x \*.class -x \*classes\* -x \*bin\* -x \*.zip \ > -x \*docs\* -x \*reference\* -x \*releng\* -x \*.git\* -x \*/lib/\*.jar -x \*getRemoteFile\* > popd > rm -fr ${STAGINGDIR}/all/sources > z=${STAGINGDIR}/all/${SRCSNAME}; for m in $(md5sum ${z}); do if [[ $m != ${z} ]]; then echo $m > ${z}.MD5; fi; done > # JBIDE-7444 get aggregate metadata xml properties file > if [[ -f ${WORKSPACE}/sources/aggregate/site/zips/build.properties.all.xml ]]; then > rsync -aq ${WORKSPACE}/sources/aggregate/site/zips/build.properties.all.xml ${STAGINGDIR}/logs/ > fi > fi > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19662) Create New and Noteworthy for 4.3.0.Alpha2

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19662?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen resolved JBIDE-19662. ----------------------------------------- Resolution: Done > Create New and Noteworthy for 4.3.0.Alpha2 > ------------------------------------------ > > Key: JBIDE-19662 > URL: https://issues.jboss.org/browse/JBIDE-19662 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: website > Reporter: Alexey Kazakov > Assignee: Max Rydahl Andersen > Priority: Blocker > Fix For: 4.3.0.Alpha2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for all N&N -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3425) Disable Unintsaller generation for Mac OS X

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3425?page=com.atlassian.jira.plugin.... ] Martin Malina commented on JBDS-3425: ------------------------------------- I have one worry here. If we change the runtimes location to ~/Library/Application Support/jbdevstudio9/runtimes as was suggested in JBDS-3411, then having an uninstaller would actually be helpful, because just removing the app will leave the installed runtime on the disk (if one installs the installer with eap). > Disable Unintsaller generation for Mac OS X > ------------------------------------------- > > Key: JBDS-3425 > URL: https://issues.jboss.org/browse/JBDS-3425 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 9.0.0.Alpha2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 9.0.0.Beta1 > > > Uninstaller doesn't make sense for Mac platform, because it is literally just removing .app package. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-1234) Installer could check OS architecture

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-1234?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-1234: -------------------------------------- In "it is supported by IzPack", what is "it" ? Is it something that will improve user experience or developer productivity? > Installer could check OS architecture > ------------------------------------- > > Key: JBDS-1234 > URL: https://issues.jboss.org/browse/JBDS-1234 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 3.0.1.GA > Reporter: Jiri Peterka > Assignee: Denis Golovin > Fix For: 9.0.0.Beta2 > > > Installer could check OS architecture, for example if installing 32-bit package on 64 bit OS there should be a warning and non-compatible package should be forced to exit installation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-1234) Installer could check OS architecture

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-1234?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-1234: ------------------------------------- It is supported by IzPack, so we at least can add Linux/Mac/Windows platforms right away, arch support is not that clear, but I can figure it out :) > Installer could check OS architecture > ------------------------------------- > > Key: JBDS-1234 > URL: https://issues.jboss.org/browse/JBDS-1234 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 3.0.1.GA > Reporter: Jiri Peterka > Assignee: Denis Golovin > Fix For: 9.0.0.Beta2 > > > Installer could check OS architecture, for example if installing 32-bit package on 64 bit OS there should be a warning and non-compatible package should be forced to exit installation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3308) Promote JBoss Tools CAT in JBT/JBDS About box

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3308?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3308: ------------------------------------- Central? > Promote JBoss Tools CAT in JBT/JBDS About box > --------------------------------------------- > > Key: JBDS-3308 > URL: https://issues.jboss.org/browse/JBDS-3308 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product > Reporter: Vlado Pakan > Assignee: Denis Golovin > Priority: Optional > Fix For: 9.0.0.Beta1 > > Attachments: about-jbds.png > > > Would be nice to put link to JBT CAT or JBT CAT logo with link to it to JBDS/JBT About box to make JBT CAT more visible. > New link/image should be visible without resizing About box -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-416) Need to doc split of SOA Development between release and early access

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/JBTIS-416?page=com.atlassian.jira.plugin.... ] Misha Ali commented on JBTIS-416: --------------------------------- Thanks, Paul and Andrej. This is now pushed public and available here: https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Developer_Stu... If this is all that was required for this particular JIRA, we can probably close it, unless we need to change/remove this content in one of the upcoming releases? > Need to doc split of SOA Development between release and early access > --------------------------------------------------------------------- > > Key: JBTIS-416 > URL: https://issues.jboss.org/browse/JBTIS-416 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Affects Versions: 8.0.1.GA, 4.2.1.Final > Reporter: Paul Leacu > Assignee: Misha Ali > Attachments: ss0.png, ss1.png > > > Component categorization for the SOA Development tooling falls in both the released and Early Access update sites. B*MS tooling is now being productized and Fuse Tooling/ SwitchYard are in 'Early Access'. This situation is temporary (until Fuse Tooling/SwitchYard are GA). > To address this issue I've done the following: > JBDSIS 8.0.1.GA: > site-ga: (released) > JBoss Business Process and Rules Development > *All features available > JBoss Data Virtualization Development > *All features available > JBoss Integration and SOA Development > *All features except Fuse Tooling and SwitchYard > JBoss SOA 5.x Development > *All features available > > site-ea: (early access) > JBoss Fuse Development > *All features available > JBoss Integration and SOA Development > *Fuse Tooling and SwitchYard only available > To simplify the user experience, Early Access will contain only features which are early access. Released (production) features will appear in the primary update window. > The community JBTIS install will do something similar. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-638) JBDS-IS: Add uninstall instructions to the Install Guide

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-638?page=com.atlassian.jira.plug... ] Misha Ali updated TOOLSDOC-638: ------------------------------- Component/s: Installation Guide > JBDS-IS: Add uninstall instructions to the Install Guide > -------------------------------------------------------- > > Key: TOOLSDOC-638 > URL: https://issues.jboss.org/browse/TOOLSDOC-638 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: Installation Guide > Reporter: Misha Ali > Assignee: Supriya Bharadwaj > > We need instructions for how to uninstall JBDS-IS included in the Install Guide. This should be reviewed by QE as the correct method to remove the installation from the machine and then a new revision history entry should be added to the guide. Misha will push this public once it is reviewed and ready. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-638) JBDS-IS: Add uninstall instructions to the Install Guide

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-638?page=com.atlassian.jira.plug... ] Misha Ali updated TOOLSDOC-638: ------------------------------- Priority: Minor (was: Major) > JBDS-IS: Add uninstall instructions to the Install Guide > -------------------------------------------------------- > > Key: TOOLSDOC-638 > URL: https://issues.jboss.org/browse/TOOLSDOC-638 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: Installation Guide > Reporter: Misha Ali > Assignee: Supriya Bharadwaj > Priority: Minor > > We need instructions for how to uninstall JBDS-IS included in the Install Guide. This should be reviewed by QE as the correct method to remove the installation from the machine and then a new revision history entry should be added to the guide. Misha will push this public once it is reviewed and ready. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

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